Tagged: Typed links
Typed links, edge metadata, and link syntax
Pages with this tag
Framework crosswalks
1How frameworks map to each other — specific crosswalk tables, column mapping strategies, and matching methods.
Link metadata syntax specification
2Complete specification of the typed-link syntax — wrapping styles, link types, regex patterns, and the two-tier priority system.
Link metadata system
3The theoretical foundation for typed links with edge metadata in Obsidian — how relationships between notes can carry structured data. Also known as edge metadata, typed link system, inline field metadata, or evidence-link edge model.
Challenge 07: Link metadata / edge model for evidence mapping
4Design the edge metadata model for evidence→framework implementation links — the "other" edge type Crosswalker has to support that's NOT a crosswalk. Bases-compatible storage, custom or inherited schema, reviewer attribution, status transitions.
Evidence-link edge model synthesis — junction notes as the committed architecture
5Distilling 2 research sessions directly targeted at Challenge 07 (the link metadata / edge model for evidence mapping). Both converge strongly on junction notes (edge-as-note reification) as the only architecture compatible with Obsidian Bases' flat-YAML constraint, with a concrete 13-field schema validated against 8 GRC tools and OSCAL round-trip.
SKOS
6Simple Knowledge Organization System — the W3C mapping vocabulary that every modern crosswalk standard builds from, but that our research found insufficient for compliance crosswalking on its own.
SSSOM
7Simple Standard for Sharing Ontological Mappings — the edge metadata model that extends SKOS with mandatory provenance, confidence, and negation support.