Typed Graph Schema (TGS) 0.5

This version was published with addresses under https://volland.github.io/obsigraph/, which no longer resolve. It is the same text, served here at https://typedgraph.org/spec/tgs/v0.5/. Its tgs: namespace is now https://typedgraph.org/ns/tgs#; importers read the former one as the same terms. The latest version uses the new addresses.
Files: SPEC.md · tgs.schema.json · namespace.json · conformance examples
Version 0.5 (published 2026-11-11; immutable)
Previous 0.4
This version https://volland.github.io/obsigraph/spec/tgs/v0.5/
JSON Schema https://volland.github.io/obsigraph/spec/tgs/v0.5/tgs.schema.json
Namespace https://volland.github.io/obsigraph/ns/tgs# (prefix tgs:)
Editor Volodymyr Pavlyshyn
Source spec/tgs/ in github.com/Volland/typedgraph
License Text: CC BY 4.0. JSON Schema and examples: MIT.

TGS describes the types of a knowledge graph kept as markdown or AsciiDoc notes: what properties a note of a type has, which typed links it may have to which other types, what properties those links carry, and what the parts inside a note mean: its headings and the XML elements it contains. Every declaration can explain itself in a description, written for people and for AI agents alike. A schema is ordinary YAML frontmatter in ordinary notes, so people can write and review it by hand, and it maps to and from W3C SHACL so the same ontology can be exchanged with RDF tools.

TGS is independent of any one application. Typed Graph (an Obsidian plugin and CLI) is the reference implementation.

1. Conventions

The key words MUST, MUST NOT, SHOULD, SHOULD NOT and MAY are to be read as described in RFC 2119 when they appear in capitals.

2. Data model

TGS types a labelled property graph built from notes:

2.1 AsciiDoc notes

A reader MAY read .adoc files as notes. An AsciiDoc note is ordinary AsciiDoc: every form below hides in a comment or a header attribute, so a standard AsciiDoc processor renders the file exactly as it would without the graph metadata.

A chapter with properties and comment edges:

////
type: Chapter
status: draft
////
= Metagraphs
:tg-pages: 12

// @tg: cites:: [[Pavlyshyn 2024]] {page: 12}
[#definition]
== Definition

A metagraph generalizes a hypergraph.

// @tg: defines:: [[Metagraph]]

reads as a node book/ch03.adoc with label Chapter, title Metagraphs and properties status: draft and pages: 12, and two edges:

Type Target Properties
cites Pavlyshyn 2024 page: 12, section: book/ch03.adoc#Definition
defines Metagraph section: book/ch03.adoc#Definition

The id definition resolves to the section book/ch03.adoc#Definition.

3. Schema notes

A schema note is a markdown note located directly in the schema folder. The schema folder is a reader setting whose default is Types/. Notes in subfolders of the schema folder, and notes elsewhere in the vault, MUST NOT be read as schema notes.

A schema note's frontmatter MAY contain these keys, in any combination:

Key Value Declares
schema type declaration (section 4) the type named by the note's title
schemas mapping: type name → type declaration any number of types
edgeTypes mapping: edge type name → edge type declaration (section 6) edge types
prefixes mapping: prefix → IRI CURIE prefixes for the whole vault (section 7)
tgs version string, e.g. "0.1" the TGS version the note is written for (section 12)

A schema note with none of schema, schemas, edgeTypes and prefixes declares an empty type named by its title. All other frontmatter keys belong to the note itself and readers MUST ignore them. The body of a schema note is free text, except that the body of a note with schema is the template of that type (section 8).

One note can therefore describe a single type:

# Types/Person.md
---
schema:
  properties:
    name: text
    email: {kind: text, required: true}
  edges: {worksAt: Company, knows: Person}
---
## Notes

or a whole subsystem:

# Types/People and Orgs.md
---
schemas:
  Person:
    properties: {name: text, email: {kind: text, required: true}}
    edges: {worksAt: Company, knows: Person}
  Company:
    uri: schema:Organization
    properties: {name: text, founded: date}
edgeTypes:
  worksAt:
    from: Person
    to: Company
    properties: {since: date, role: {kind: text, values: [engineer, manager]}}
---
How people and organisations relate.

3.1 Duplicates

When the same type name, edge type name or prefix is declared more than once, readers MUST use the declaration from the schema note whose path sorts first (by code point) and MUST report a duplicate-declaration naming both notes. A prefix declared twice with the same IRI is not a duplicate.

4. Type declarations

A type declaration is a mapping with these optional keys:

Key Value Meaning
uri IRI or CURIE identifier of the type; default: base IRI + type name
properties section 5 frontmatter properties of notes of this type
edges section 5.3 allowed outgoing edges; absent means any edge is allowed
template link template note for new notes of this type (section 8)
id section 8.1 identifiers generated for new notes of this type (0.2)
visualization mapping display hints (section 11); style is an alias
description string what the type means (section 4.1) (0.4)
elements sections 4.2 to 4.4 XML elements a note of this type may contain (0.4)
sections section 4.5 headings a note of this type has (0.4)

An empty mapping ({}) or a null value declares a type with no constraints.

4.1 Descriptions

A description is a string that says what a declaration means: a type, a property (section 5.1), an edge of a type in map form (section 5.3), an edge type (section 6), an element, an attribute (section 4.3) or a section (section 4.5). It does not affect validation. Readers SHOULD show it wherever they list the declaration, so that a person or an agent writing a note knows what each type, property, edge, element and heading is for. A declaration without a description is read exactly as in 0.3.

4.2 Elements

A note of a type has parts: headings (section 4.5) and elements, block-level XML tags such as <option> or <example> that mark a span of the note. Two notations meet here, and each has one job. A schema note declares an element in YAML; a document contains it as XML. A declaration never uses XML, and a document never uses YAML for an element.

# Types/Decision.md
---
tgs: "0.5"
schema:
  description: A choice that was made, with its reason and the alternatives rejected.
  sections:
    Context: {required: true, description: The forces that made a decision necessary.}
  elements:
    option:
      description: An alternative that was considered, and why it won or lost.
      attributes:
        id: {description: Give one when code or a later decision points at the option.}
        outcome: {values: [chosen, rejected, deferred], required: true, description: What happened to it.}
    consequence: What becomes easier or harder because of the decision.
---

A document of that type then contains:

<option id="redis" outcome="rejected">

Keep sessions in Redis: one more stateful service to run.

</option>

elements is a mapping from tag name to an element declaration. A tag name matches [A-Za-z][A-Za-z0-9_.-]* and is compared without regard to case; a tag declared twice in one mapping is reported as invalid-declaration and the first declaration wins. An element declaration is a mapping with these keys, all optional:

Key Value Default Meaning
description string none what the element means and when to write one
attributes section 4.3 none the attributes of the tag
elements as elements none elements that have a meaning inside this one (section 4.4)
required boolean false each container (section 4.4) holds at least one
many boolean true a container may hold more than one
type type name or list none types an element node gets (section 4.7)
node boolean see section 4.7 whether an element without an id becomes a node

required and many together give how often an element occurs in its container:

required many Occurrences
false true any number (the default)
true true one or more
false false none or one
true false exactly one

On an element, many counts occurrences. On a property (section 5.1) it makes the value a list. That is why the defaults differ.

elements MAY also be written as a list of tag names, and a declaration MAY be written as null (no rules) or as a string (a description and nothing else). Section 4.9 defines what each shorthand means.

Elements are open: a document MAY contain tags that no declaration names, such as HTML's <details>. They are text: they are not validated, they are not nodes unless they have an id, and they do not change the scope of the elements inside them (section 4.4).

4.3 Attributes

attributes declares the attributes of a tag. It is written like properties (section 5.1): a mapping from attribute name to declaration, or a list whose items are names or mappings with a name key, where a declaration is null, a kind, or a mapping. An attribute value is always one string in the document, so only these keys have a meaning:

Key Value Default Meaning
kind a kind from section 5.2 except list text how the value is read
required boolean false the attribute is present and not empty
values list of scalars none the allowed values
description string none what the attribute means

many, default and uri have no meaning on an attribute. Readers MUST accept them, so that every 0.4 note stays valid, and MUST ignore them. Writers SHOULD NOT write them. As for properties, readers MAY check that a value matches its kind.

Attributes are open: an element MAY carry attributes its declaration does not list. They are not reported, and an element node keeps them as properties.

The id attribute. Every element, declared or not, MAY have an id, and its meaning is fixed by this specification: a stable address, unique within the note when compared without regard to case, that makes the element a node addressed as <note>#^<id> (section 4.7). An id SHOULD start with a letter or a digit and contain only letters, digits, -, _ and .. A declaration need not list id. It MAY list it to describe when to give one, or with required: true to demand one, and SHOULD NOT give it values or a kind.

4.4 Nesting and scope

Elements nest. A declaration says where a tag means something, not where it may stand: TGS has no content model, no order and no exclusions.

Scope. The declarations in scope at a point of a document form a chain: the elements of each declared element around the point, innermost first, then the elements of the document's type. An element is resolved to the first declaration of its tag along the chain. An element that resolves to none is undeclared. It follows that:

Containers. Each declaration counts in a container: the declarations in a type's elements count per document (section 4.6), and those in an element's elements count per occurrence of that element. required and many are checked per container, over all the elements inside it, at any depth, that resolve to that declaration.

# Types/Runbook.md
---
tgs: "0.5"
schema:
  description: How to operate one part of the system when something goes wrong.
  elements:
    step:
      description: One action, in order, that an engineer or an agent can run.
      attributes:
        risk: {values: [safe, disruptive], required: true}
      elements:
        check: {required: true, description: How to tell that the step worked.}
    rollback: {required: true, many: false, description: How to undo the steps.}
---

In a runbook, every <step> needs a <check> inside it, and a <check> outside any step is undeclared text. The runbook needs exactly one <rollback>, wherever it stands: at the top, inside a step or inside <details>.

Declarations do not refer to one another. A tag that has a meaning at two levels is declared at both, or once in the type's elements.

4.5 Sections

sections is a mapping from heading text to a section declaration, or a list of headings. A section declaration is null, a string (its description), or a mapping with description and required (default false). A heading inside the document, at any level, matches a declaration when the two texts are equal without regard to case and surrounding whitespace. A required section is one the document has at least once.

Sections declare headings and nothing more: TGS does not say in which order headings come, at which level, or which elements stand under which heading.

4.6 Reading elements

An element starts with an opening tag at the beginning of a line, after at most three spaces (any indentation inside another element), and ends with the matching closing tag at the end of a line, possibly the same one. Tags inside fenced code and frontmatter are not elements, and neither is text between < and > that is not attribute syntax (<insert a summary here>). Attribute values are quoted with " or ', or written bare without spaces. An opening tag that is never closed is an empty element, and what follows it belongs to its parent. Writers SHOULD leave blank lines inside an element so that Markdown readers parse its content as Markdown.

A document of a type is the part of the vault a type applies to: a note of the type, or, in hosts that type sections of a file (such as the reference implementation's lat.md files), each outermost typed section with its subsections. Its title is the note's title or the section's heading.

4.7 Element nodes

A host MAY make elements graph nodes. It SHOULD make a node of an element that has an id, and of one whose declaration gives it a type (unless node: false) or node: true, and leave every other element as text. Undeclared elements become nodes only by an id.

An element node has the label Element followed by the declared types, the element's attributes as properties, and an edge from the innermost note, section or element node that contains it. An element with an id is addressed as <note>#^<id>. A host gives a node without an id an address of its own that never equals an explicit id, but that address is not stable and SHOULD NOT be linked.

4.8 Document validation

A validator that reads note bodies MUST, for each document of a type with elements or sections in its effective schema (section 9), resolve each element by the scope rule of section 4.4 and report:

Diagnostic Reported when
missing-element a container holds no element resolved to a required declaration
too-many-elements a container holds more than one element resolved to a declaration that is not many
missing-attribute a required attribute of a declared element is absent or empty
attribute-value-not-allowed an attribute value of a declared element is not in its values
unclosed-element a declared element is never closed
missing-section a required heading does not occur in the document

Undeclared elements and undeclared attributes are never reported.

4.9 Normal form

Every declaration has one normal form, and two declarations with the same normal form mean the same thing. A reader MUST read each shorthand as the normal form beside it:

Written Normal form
elements: [option, consequence] elements: {option: {}, consequence: {}}
option: (null) option: {}
consequence: What becomes harder. consequence: {description: What becomes harder.}
type: Requirement type: [Requirement]
attributes: [id, kind] attributes: {id: {}, kind: {}}
risk: (null) or risk: number risk: {kind: text} or risk: {kind: number}
attributes: [{name: risk, required: true}] attributes: {risk: {required: true}}
sections: [Context] sections: {Context: {}}
Context: The forces at play. Context: {description: The forces at play.}
a key left out its default from sections 4.2, 4.3 and 4.5

A list of elements or sections holds names only; a list of attributes follows properties (section 5.1).

Writing declarations (informative). Use the mapping form for an element with anything besides a description, a string for an element that has only a description, and a list only for a first draft. Describe every element and every attribute that has values, because the description is how the next writer, person or agent, learns what the tag is for. Exporters SHOULD write this compact form, and the reference implementation does.

Showing declarations (informative). A tool that shows declarations to people or agents SHOULD keep the structure of the YAML: each element, then its attributes, then its nested elements, indented under it. It SHOULD show an attribute the way it shows a property instead of inventing another notation. tg ontology shows the runbook type above as:

    elements:
      <step> — One action, in order, that an engineer or an agent can run.
        attributes:
          risk (text, safe|disruptive, required)
        elements:
          <check>  (required) — How to tell that the step worked.
      <rollback>  (exactly one) — How to undo the steps.

5. Properties and edges

5.1 Property declarations

properties is either a mapping from property name to a property declaration, or a list whose items are a property name (a text property) or a mapping with a name key. A property declaration is either a kind shorthand (born: date) or a mapping:

Key Value Default Meaning
kind one of the kinds below text value type
required boolean false the note must have a non-empty value
many boolean false the value is a list (always true for kind list)
values list of scalars none allowed values (an enumeration)
default any YAML value none value written into new notes
uri IRI or CURIE base IRI + name identifier of the property
description string none what the property means (0.4)

A null declaration (name:) is a text property. Within one type, the first declaration of a property name wins.

5.2 Kinds

Kind Values Obsidian property type XSD datatype
text string Text xsd:string
number number Number xsd:decimal
boolean true / false Checkbox xsd:boolean
date YYYY-MM-DD Date xsd:date
datetime ISO 8601 date and time Date & time xsd:dateTime
link a link to a note or a URL Text (link) none; an IRI
list list of strings List xsd:string, many

An unknown kind MUST be read as text and reported as unknown-kind. TGS 0.1 does not require readers to check that values match their kind.

5.3 Edges of a type

edges lists the edge types a note of this type may have as outgoing edges. Two forms are allowed.

The list form names edge types, each accepting any target: edges: [knows, worksAt].

The map form maps each edge type to its target type, or to a list of target types, or to null (any target), or to a mapping:

Key Value Default Meaning
target type name or list any allowed target types
many boolean true more than one edge of this type is allowed
required boolean false at least one edge of this type is required
description string none what this edge means for the type (0.4)
edges:
  worksAt: Company                          # one target type, many, optional
  knows: [Person, Bot]                      # several target types
  mentor: {target: Person, many: false, required: true}
  likes:                                    # any target

Properties default to a single value and edges default to many, because repeated edges of one type are normal (knows) and frontmatter values usually are not. An empty list or mapping (edges: []) allows no outgoing edges.

6. Edge type declarations

An edge type declaration describes an edge type everywhere it is used:

Key Value Meaning
from type name or list allowed source types; absent means any
to type name or list allowed target types; absent means any
properties as in 5.1 properties written on the edge
uri IRI or CURIE identifier of the edge type (an RDF predicate); default: base IRI + name
visualization mapping display hints for edges of this type (section 11); style is an alias
description string what the edge type means (0.4)

Undeclared edge properties are allowed. When both a type's edges entry and the edge type declare targets, the type's entry wins for sources of that type.

7. Identifiers

Every type, property and edge type has an IRI, so that schemas can be exchanged.

8. Templates

A reader that creates notes from types MUST build the new note's frontmatter from type: <name> and every declared default, and MUST take the body from the first of:

  1. the note that the type's template link points to, without its frontmatter;
  2. the body of the schema note, when the type is declared with schema, if that body is not empty;
  3. a template generated from the schema.

A template link is a wikilink ([[Templates/Person]], resolved as the host resolves links), a markdown link ([Person](../Templates/Person.md), relative to the schema note), or a vault-relative path (Templates/Person, .md optional).

A generated template SHOULD write a key for every declared property (its default, [] for many, empty otherwise) and one placeholder per declared edge that does not itself create an edge, so that a new note is complete but creates no links until it is filled in. The reference implementation writes ## Notes followed by ## Relations with one - <edgeType>:: line per edge.

8.1 Note identifiers

The id key (added in 0.2) names the identifiers a reader generates when it creates a note of the type. It is one id rule, or a list of rules. A rule is a kind (id: uuid7) or a mapping:

Key Value Default Meaning
kind uuid, uuid7, timestamp or luhmann required how the id is made
property property name id frontmatter property that holds the id; required for each rule of a list
auto boolean true, except false for luhmann generate on every new note; otherwise only when the user asks (for luhmann, by placing the note under another)
filename boolean false prefix the file name with the id and a space

The kinds are:

A reader MUST generate ids that are not in use for the same property in the vault, MUST write each generated id as a text property of the new note, and SHOULD treat a property named by a rule but not declared in properties as a declared text property. A reader MUST report an unknown kind, an unknown key, a list entry without property and a repeated property as invalid-declaration and MUST ignore that rule.

A template (section 8) MAY use these tokens, which a reader that supports them replaces: {{title}}, {{date}} (YYYY-MM-DD), {{time}} (HH:mm), {{id}} (the first generated id), {{<property>}} for each generated id, and for a note placed under a parent, {{parent}} (its title), {{parent-id}} and {{parent-link}} (a wikilink to it). Other double-brace text MUST be left unchanged. A template line that contains a parent token is removed when the note has no parent.

9. Validation

Validation is advisory. A validator MUST report diagnostics and MUST NOT remove notes or edges from the graph. Stub targets and targets without labels are never reported as having the wrong type.

For a node with labels L1, L2, …, the effective schema merges the schemas of its labels in order: the first declaration of a property wins; elements and sections are unioned by tag and by heading, and the first label that declares a tag or heading gives its whole declaration; edge rules are unioned per edge type, with targets unioned (any target if one rule allows any), many if any rule allows many and required if any rule requires it; edges is unrestricted only if no label declares it.

Diagnostic Reported when
invalid-declaration a key has a value of the wrong shape (e.g. edges: 5)
unknown-kind a property declares an unsupported kind
duplicate-declaration section 3.1
unknown-prefix section 7
unsupported-version section 12
unknown-key section 12
missing-property a required property is absent, null or empty
value-not-allowed a property value, or an item of a list value, is not in values
unexpected-list a property that is not many holds a list
edge-not-allowed an outgoing edge type is not in the effective edges
missing-edge a required edge has no edge of its type
too-many-edges an edge that is not many has more than one edge of its type
wrong-target-type the target has labels and none is an allowed target type
wrong-source-type the source has labels and none is in the edge type's from
missing-edge-property a required edge property is absent from the edge
edge-value-not-allowed an edge property value is not in its values

Readers SHOULD report each diagnostic with the note path and, for edges, the line of the edge. Message text is not specified.

10. Multiple labels

A note with type: [Person, Employee] is checked against the merged schema of section 9. The style of a node is taken attribute by attribute from the first label that supplies it.

11. Visualization (informative)

visualization is a hint for graph displays and does not affect validation. The reference implementation reads color (CSS color), shape, icon (a Lucide icon name) and label (a property shown as the node label) for types, color and line (solid, dashed, dotted) for edge types, and an edges mapping inside a type's visualization that styles edge types. An edge type's own visualization wins over a type's visualization.edges. Other readers MAY ignore visualization or read further keys.

12. Versioning

A schema note MAY declare tgs: "<major>.<minor>". A reader implementing version M.N:

TGS 0.2 adds the id key (section 8.1) and the template tokens. TGS 0.3 adds AsciiDoc notes (section 2.1) and adds no schema key. TGS 0.4 adds description (section 4.1), elements and sections (sections 4.2 to 4.5) and document validation (section 4.8); unknown keys inside an element declaration are reported like those of a type. TGS 0.5 adds no key. It fixes how elements are declared and read: the attribute keys that have a meaning and the reserved id (section 4.3), the scope of nested declarations and counting per container (section 4.4), and one normal form for every shorthand (section 4.9). Every 0.1 note is a valid 0.2 note, every 0.2 note is a valid 0.3 note, every 0.3 note is a valid 0.4 note, and every 0.4 note is a valid 0.5 note.

Minor versions only add optional keys. A published version never changes.

13. SHACL mapping

TGS maps to the W3C Shapes Constraint Language (SHACL) so that schemas can be exchanged with RDF tools. An exporter writes a schema set as SHACL in Turtle. An importer reads SHACL into TGS declarations.

13.1 Types and properties

Each type becomes a sh:NodeShape named base IRI + type name + Shape:

TGS SHACL
type Person sh:targetClass = the type's IRI; sh:name "Person"
property a property shape with sh:path = the property's IRI and sh:name = its name
kind text, number, boolean, date, datetime sh:datatype per section 5.2
kind link sh:nodeKind sh:IRI
kind list sh:datatype xsd:string and tgs:kind "list", no sh:maxCount
required: true sh:minCount 1
not many sh:maxCount 1
scalar default sh:defaultValue
list default tgs:default with the value as a JSON literal
values sh:in ( … )
declaration order sh:order 0, 1, …
description of a type or property sh:description on its shape (0.4)

13.2 Edges of a type

Each entry of a type's edges becomes a property shape on the type's shape:

TGS SHACL
edge type sh:path = the edge type's IRI; sh:name = its name
one target sh:class = the target type's IRI
several targets sh:or ( [ sh:class A ] [ sh:class B ] )
any target sh:nodeKind sh:IRI and tgs:edge true
required: true sh:minCount 1
many: false sh:maxCount 1
edges declared tgs:edgesClosed true on the node shape
description sh:description on the property shape (0.4)

sh:closed is not used, because it would also close frontmatter properties, which are open in TGS. tgs:edgesClosed records the allow-list without changing what SHACL engines validate.

13.3 Edge types

Each edge type becomes a sh:NodeShape named base IRI + name + EdgeShape that describes the edge as an RDF reification (rdf:Statement):

:worksAtEdgeShape
    a sh:NodeShape ;
    sh:name "worksAt" ;
    sh:property [ sh:path rdf:predicate ; sh:hasValue schema:worksFor ] ;
    sh:property [ sh:path rdf:subject ; sh:class :Person ] ;
    sh:property [ sh:path rdf:object ; sh:class schema:Organization ] ;
    sh:property [ sh:path :since ; sh:name "since" ; sh:datatype xsd:date ; sh:maxCount 1 ; sh:order 0 ] .

An edge type's description is the sh:description of its edge shape. The rdf:predicate constraint identifies the edge type; rdf:subject carries from and rdf:object carries to (with sh:or for several types); the remaining property shapes are the edge's properties. The shape declares no target, so validators apply it to reified statements on request. This uses only SHACL 1.0 and the RDF reification vocabulary; a later TGS version may add RDF 1.2 reifiers.

13.4 Annotations

What SHACL cannot express is kept as annotations, which SHACL engines ignore:

Term On Value
tgs:note node shape path of the schema note that declared it
tgs:template node shape the template link
tgs:templateBody node shape the schema note body of a schema type
tgs:visualization node shape the visualization mapping as a JSON literal
tgs:edgesClosed node shape true when the type declares edges
tgs:edge property shape true for an edge entry without target types
tgs:kind property shape "list" for kind list
tgs:default property shape a non-scalar default as a JSON literal
tgs:elements node shape the type's elements as a JSON literal in the compact form of section 4.9 (0.4)
tgs:sections node shape the type's sections as a JSON literal (0.4)

13.5 Import

An importer MUST read:

An importer MUST report, and otherwise skip, every construct outside this subset, including sh:closed, sh:pattern, sh:minLength, sh:qualifiedValueShape, sh:sparql, sh:and, sh:xone, sh:not, property paths other than a single IRI, unknown datatypes (read as text), sh:maxCount greater than 1 (read as many) and node shapes without a target class. It MUST import the rest of each shape.

An importer that writes notes SHOULD write one note per type by default (or group types by tgs:note), MUST replace only the schema, schemas, edgeTypes and prefixes keys of an existing note, MUST NOT delete notes, and SHOULD refuse to rewrite a note that declares types missing from the import unless the user asks. A note that declares several types has no template body, so an importer that groups types into one note SHOULD report each tgs:templateBody it cannot keep.

13.6 Round trip

For schemas written in TGS, export followed by import MUST reproduce the same types, edge types, properties, edges, identifiers, templates, visualization, descriptions, elements and sections. Exporting the result again yields the same RDF graph; the reference implementation produces byte-identical Turtle.

14. Conformance

Level Requirements
Reader sections 3 to 8 and 12: reads every key, applies defaults, expands identifiers, reports declaration diagnostics; a reader that reads .adoc notes also implements section 2.1
Validator Reader, plus section 9
SHACL exchanger Validator, plus section 13
Document validator Validator, plus sections 4.2 to 4.6 and 4.8

The examples/ folder next to this document contains conformance cases. Each case has a vault/ folder (schema folder Types/, base IRI urn:tgs:) and an expected.json with:

SHACL cases also have a shapes.ttl that an exporter's output must be isomorphic to.

15. JSON Schema

tgs.schema.json (JSON Schema draft 2020-12) validates the TGS keys of a schema note's frontmatter. It is strict about TGS 0.5 keys and leaves visualization and all non-TGS keys open. Notes declaring a newer minor version may not validate against it.

16. References