{ "title": "Built on explicit agreements — Standards & citation", "text": "MODAVIS (2026). Built on explicit agreements — Standards & citation. Research notebooks, October 2026 · Interactive reuse and evidence edition. https://modavis.org/editions/2026-10-workbench/standards/introduction/", "bibtex": "@misc{modavis_standards_introduction_2026_10_workbench,\n author = {{MODAVIS}},\n title = {Built on explicit agreements — Standards & citation},\n year = {2026},\n month = {10},\n version = {2026-10-workbench},\n url = {https://modavis.org/editions/2026-10-workbench/standards/introduction/},\n note = {Content SHA-256: d43ae536d3442fedc8ffa4c2c18b74c0363a4e10a2550082de056bea6e3658c6}\n}", "url": "https://modavis.org/editions/2026-10-workbench/standards/introduction/", "sha256": "d43ae536d3442fedc8ffa4c2c18b74c0363a4e10a2550082de056bea6e3658c6", "edition": "2026-10-workbench", "date": "2026-10-09", "canonicalPayload": "{\"book\":{\"number\":\"08\",\"slug\":\"standards\",\"title\":\"Standards & citation\"},\"chapter\":{\"blocks\":[{\"items\":[{\"detail\":\"An illustrated, practical route from a small working example to your own research.\",\"href\":\"/notebooks/standards/reuse-checklist/\",\"label\":\"Use the release-readiness guide\"}],\"type\":\"links\"},{\"items\":[{\"detail\":\"A continuous worked example: readable explanations, exact records and the limits of each claim.\",\"href\":\"/notebooks/standards/cuntz/\",\"label\":\"Learn this through the Cuntz organ\"}],\"type\":\"links\"},{\"text\":\"MODAVIS connects complementary standards rather than asking one format to do everything. The ontology describes meaning and relationships. VAO binds digital resources into an exchange and preservation contract. Repositories supply persistent version records.\",\"type\":\"p\"},{\"headers\":[\"Layer\",\"Role\"],\"rows\":[[\"MODAVIS Ontology Network\",\"Semantic identities and evidence-qualified relationships.\"],[\"VAO Standard\",\"Manifest, resources, profiles, carriers and file integrity.\"],[\"Persistent identifiers\",\"Stable references to entities and exact releases.\"],[\"Provenance\",\"Documented source, transformation and editorial lineage.\"]],\"type\":\"table\"},{\"text\":\"Established media and research-object formats remain useful within this architecture. A VAO is an integration envelope; it does not replace an audio format, a repository or a domain ontology.\",\"type\":\"p\"},{\"id\":\"agreements\",\"text\":\"The agreement at each boundary\",\"type\":\"heading\"},{\"headers\":[\"Boundary\",\"Agreement needed\"],\"rows\":[[\"A source enters a research workflow\",\"Identity, capture context, transfer structure and attribution.\"],[\"A statement becomes a research representation\",\"Semantic identity, evidence, interpretation and historical applicability.\"],[\"A representation becomes an exchange package\",\"Exact manifest, resources, profiles, rights and carrier mappings.\"],[\"A package becomes a published release\",\"Persistent version information, file identities and repository metadata.\"]],\"type\":\"table\"},{\"text\":\"These agreements address different kinds of interoperability. Two applications can read the same audio encoding while disagreeing about which instrument state the recording represents. Two catalogues can use the same label while assigning it to different concepts. Interoperability therefore requires both usable bytes and an explicit account of their meaning.\",\"type\":\"p\"},{\"boundary\":\"No acoustics profile or calibrated acoustic response is inferred from the presence of an organ model.\",\"caseLabel\":\"Cuntz\",\"concept\":\"A profile names a set of requirements for a capability. A client’s support describes what an application can do with the object; the two declarations must be compared.\",\"evidence\":\"Released record\",\"expanded\":false,\"id\":\"cuntz-profiles\",\"scenario\":\"The Cuntz manifest declares Core, Dynamic Delivery, Playable, Physical Instrument, Scientific, Multimodal, Spatial and Zenodo Repository profiles under VAO 0.5.0.\",\"sources\":[{\"detail\":\"Published manifest: identities, measurement observations, realization digests, profiles and rights. Exact examples checked against this release.\",\"href\":\"https://doi.org/10.5281/zenodo.22151203\",\"label\":\"Cuntz Positiv · VAO 0.5.0-rc.2\"},{\"detail\":\"The standard contract is separate from the Cuntz dataset content version 0.5.0-rc.2.\",\"href\":\"https://doi.org/10.5281/zenodo.22214248\",\"label\":\"VAO Standard 0.5.0\"}],\"steps\":[{\"text\":\"The object contains information for several uses, including physical topology, scientific observations and sampled interaction. These requirements describe the package contract.\",\"title\":\"Read the object’s declarations\"},{\"text\":\"The notebook loads a GLB display derivative and provides camera controls. It does not import the full VAO manifest, evaluate its scientific records or execute its keyboard and stop behavior.\",\"title\":\"State the viewer’s operation\"},{\"text\":\"To test sampled playback or synchronized controls, choose a client whose documented version supports the relevant format, profiles and resources. Record the tested operation separately from successful visual loading.\",\"title\":\"Choose another client when the task changes\"}],\"takeaway\":\"A working 3D preview proves that the chosen model can be displayed; it does not establish complete VAO conformance or playability.\",\"title\":\"Does showing the organ in 3D mean the VAO is playable?\",\"type\":\"example\",\"visual\":{\"caption\":\"This notebook viewer displays a model. It does not claim to play the Cuntz organ or implement a VAO runtime.\",\"layout\":\"compare\",\"nodes\":[{\"detail\":\"A GLB renderer lets you inspect geometry.\",\"icon\":\"cube\",\"label\":\"Visual inspection\",\"value\":\"Model preview\"},{\"detail\":\"Needs appropriate data, profiles and an implementing client.\",\"icon\":\"wave\",\"label\":\"Playable experience\",\"value\":\"Declared runtime capability\"}],\"title\":\"Displaying geometry and playing sound need different support\"}},{\"id\":\"media-formats\",\"text\":\"Reuse established formats inside the envelope\",\"type\":\"heading\"},{\"text\":\"VAO can identify realizations in established media and research formats, such as WAVE or FLAC audio, glTF geometry and MIDI or score data. The carrier adds the relationships, fixed identities and declared capabilities needed to interpret those realizations together. The chosen format still carries its own technical requirements; packaging a file does not make an incompatible renderer understand it.\",\"type\":\"p\"},{\"id\":\"contract-version\",\"text\":\"Version the contract as carefully as the content\",\"type\":\"heading\"},{\"text\":\"Record the exact schema, profile and vocabulary versions used by a release. A moving “latest” pointer can be convenient for discovering documentation, but it cannot identify the rules under which an earlier package was prepared. When migrating, keep the source release available and describe what changed. A successful migration creates an attributable successor rather than retroactively rewriting the old contract.\",\"type\":\"p\"},{\"text\":\"State which contract and profile are supported, and retain the evidence of validation. Conformance is specific to those declarations; it is not a general certificate of historical truth or scientific adequacy.\",\"title\":\"A declared standard is a checkable claim\",\"type\":\"note\"},{\"items\":[{\"detail\":\"The versioned specification and reference tools.\",\"href\":\"https://doi.org/10.5281/zenodo.22214248\",\"label\":\"VAO Standard 0.5.0\"},{\"detail\":\"The published semantic model.\",\"href\":\"https://doi.org/10.5281/zenodo.22126086\",\"label\":\"MODAVIS Ontology Network 0.1.0\"}],\"type\":\"links\"},{\"id\":\"standards-by-task\",\"text\":\"Which standard answers which question?\",\"type\":\"heading\"},{\"headers\":[\"Contract\",\"Role in this ecosystem\",\"Read the result as\"],\"rows\":[[\"JSON Schema Draft 2020-12\",\"Structural validation of the VAO JSON record, with the required format assertions.\",\"A check of the encoded structure, alongside additional semantic rules.\"],[\"JSON-LD 1.1\",\"Explicit mappings from JSON terms to linked-data identifiers and graph relationships.\",\"A semantic interpretation under an identified context, not a replacement for the authoritative VAO JSON.\"],[\"PROV-O\",\"A vocabulary for entities, activities, agents and their provenance relationships.\",\"An account of derivation and responsibility, not a certificate that the resulting assertion is true.\"],[\"SHACL\",\"Validation of an RDF data graph against declared shapes and constraints.\",\"A report for a particular data graph, shapes graph and validation setup.\"],[\"VAO profiles and carrier contracts\",\"Capabilities, exact realizations, dependency closure and package exchange.\",\"A version-specific interoperability claim whose scope must be stated.\"]],\"type\":\"table\"},{\"text\":\"These contracts work at different layers. A JSON record may satisfy its schema while referring to an inappropriate historical state. A graph may satisfy its shapes while an underlying source remains disputed. PROV-O can express that an analysis was generated by an activity associated with an agent; it does not independently verify that the activity used a calibrated instrument. The domain model and the research method provide the interpretation around the technical contract.\",\"type\":\"p\"},{\"text\":\"For implementation, keep the relevant documents and contexts pinned with the release. Start with the project’s specified contract rather than substituting a newer vocabulary or a moving context URL. For reading, consult the official specifications below alongside the project-specific requirements. This separates the general mechanism from the particular agreement MODAVIS or VAO makes with its consumers.\",\"type\":\"p\"},{\"items\":[{\"detail\":\"Contexts and linked-data representation.\",\"href\":\"https://www.w3.org/TR/json-ld11/\",\"label\":\"W3C JSON-LD 1.1\"},{\"detail\":\"The provenance vocabulary.\",\"href\":\"https://www.w3.org/TR/prov-o/\",\"label\":\"W3C PROV-O\"},{\"detail\":\"RDF graph constraints and validation reports.\",\"href\":\"https://www.w3.org/TR/shacl/\",\"label\":\"W3C SHACL\"},{\"detail\":\"Apply these layers to a concrete object.\",\"href\":\"/notebooks/standards/conformance/\",\"label\":\"VAO validation guide\"}],\"type\":\"links\"},{\"boundary\":\"Do not copy a few fields from the manifest and assume the excerpt retains the complete JSON-LD or VAO contract.\",\"caseLabel\":\"Cuntz\",\"concept\":\"JSON is a way to write structured values. JSON-LD adds an explicit context that relates terms to identifiers, so relationships can be interpreted consistently across records.\",\"evidence\":\"Released record\",\"expanded\":false,\"id\":\"cuntz-jsonld\",\"scenario\":\"The Cuntz manifest contains both a formatVersion and an @context. Its observation identifies the property GesL with an IRI and its unit with the QUDT MilliM identifier.\",\"sources\":[{\"detail\":\"Published manifest: identities, measurement observations, realization digests, profiles and rights. Exact examples checked against this release.\",\"href\":\"https://doi.org/10.5281/zenodo.22151203\",\"label\":\"Cuntz Positiv · VAO 0.5.0-rc.2\"},{\"detail\":\"The standard contract is separate from the Cuntz dataset content version 0.5.0-rc.2.\",\"href\":\"https://doi.org/10.5281/zenodo.22214248\",\"label\":\"VAO Standard 0.5.0\"}],\"steps\":[{\"text\":\"A human explanation says: this pipe has a recorded GesL result of 1281 millimetres in this source cell. That sentence should remain understandable before a reader meets graph syntax.\",\"title\":\"Read the ordinary data first\"},{\"text\":\"An identified property and unit avoid relying on an unexplained local word such as “length” or “mm” alone. Their definitions and mapping must be inspected rather than guessed from spelling.\",\"title\":\"Identify the terms explicitly\"},{\"text\":\"Use the context and contract appropriate to the exact VAO version. Changing a context can change interpretation; a moving “latest” mapping is unsuitable for reproducing a fixed release.\",\"title\":\"Pin the interpretation\"}],\"takeaway\":\"The context explains how the data’s terms connect to identified meanings; it does not add missing evidence.\",\"title\":\"How does JSON become linked data?\",\"type\":\"example\",\"visual\":{\"caption\":\"Renaming a key or inventing a context is not a substitute for the released mapping.\",\"layout\":\"flow\",\"nodes\":[{\"detail\":\"The VAO JSON contract remains authoritative.\",\"icon\":\"database\",\"label\":\"JSON record\",\"value\":\"Values & identifiers\"},{\"detail\":\"Use the context required by the format version.\",\"icon\":\"book\",\"label\":\"Pinned context\",\"value\":\"Meaning of each term\"},{\"detail\":\"Validate the claimed graph contract.\",\"icon\":\"network\",\"label\":\"RDF graph\",\"value\":\"Linked statements\"}],\"relations\":[\"process with the context\",\"inspect the graph\"],\"title\":\"A context gives JSON keys explicit meanings\"}}],\"intro\":\"Standards make it possible to exchange a research object without losing the meaning of its parts.\",\"overview\":{\"example\":{\"detail\":\"\",\"href\":\"#cuntz-profiles\",\"label\":\"See the worked example\"},\"summary\":\"A profile names a set of requirements for a capability. A client’s support describes what an application can do with the object; the two declarations must be compared.\",\"takeaway\":\"A working 3D preview proves that the chosen model can be displayed; it does not establish complete VAO conformance or playability.\"},\"slug\":\"introduction\",\"sources\":[{\"detail\":\"The versioned specification and reference tools.\",\"href\":\"https://doi.org/10.5281/zenodo.22214248\",\"label\":\"VAO Standard 0.5.0\"},{\"detail\":\"The published semantic model.\",\"href\":\"https://doi.org/10.5281/zenodo.22126086\",\"label\":\"MODAVIS Ontology Network 0.1.0\"},{\"detail\":\"Official specification; consulted for contexts and linked-data representation.\",\"href\":\"https://www.w3.org/TR/json-ld11/\",\"label\":\"W3C · JSON-LD 1.1\"},{\"detail\":\"Official provenance ontology; entities, activities and agents.\",\"href\":\"https://www.w3.org/TR/prov-o/\",\"label\":\"W3C · PROV-O\"},{\"detail\":\"Official graph-validation specification, including Core and SPARQL-based constraints.\",\"href\":\"https://www.w3.org/TR/shacl/\",\"label\":\"W3C · SHACL\"}],\"title\":\"Built on explicit agreements\"},\"date\":\"2026-10-09\",\"edition\":\"2026-10-workbench\",\"figures\":{},\"glossary\":[{\"definition\":\"A historically scoped condition or arrangement of an instrument. A statement about one state should not automatically describe the instrument at every date.\",\"example\":{\"detail\":\"\",\"href\":\"/notebooks/ontologies/cuntz/#cuntz-state\",\"label\":\"Work through the Cuntz example\"},\"term\":\"Instrument state\"},{\"definition\":\"The circumstances within which a statement applies, such as a historical configuration. Context is distinct from the history of how the statement was recorded.\",\"example\":{\"detail\":\"\",\"href\":\"/notebooks/ontologies/cuntz/#cuntz-time\",\"label\":\"Work through the Cuntz example\"},\"term\":\"Context\"},{\"definition\":\"One exact byte sequence representing an asset. Different encodings or derivatives have different exact identities.\",\"example\":{\"detail\":\"\",\"href\":\"/notebooks/standards/cuntz/#cuntz-asset\",\"label\":\"Work through the Cuntz example\"},\"term\":\"Realization\"},{\"definition\":\"A package or workspace that contains a manifest, carrier mapping and selected realizations. Bootstrap, preservation-closure and custom carriers serve different delivery purposes.\",\"example\":{\"detail\":\"\",\"href\":\"/notebooks/standards/cuntz/#cuntz-carriers\",\"label\":\"Work through the Cuntz example\"},\"term\":\"Carrier\"},{\"definition\":\"A versioned set of additional requirements. A client must satisfy the declared capabilities before claiming full support for that profile.\",\"example\":{\"detail\":\"\",\"href\":\"/notebooks/standards/cuntz/#cuntz-profiles\",\"label\":\"Work through the Cuntz example\"},\"term\":\"Profile\"}]}", "payload": { "edition": "2026-10-workbench", "date": "2026-10-09", "book": { "slug": "standards", "title": "Standards & citation", "number": "08" }, "chapter": { "slug": "introduction", "title": "Built on explicit agreements", "intro": "Standards make it possible to exchange a research object without losing the meaning of its parts.", "blocks": [ { "type": "links", "items": [ { "label": "Use the release-readiness guide", "href": "/notebooks/standards/reuse-checklist/", "detail": "An illustrated, practical route from a small working example to your own research." } ] }, { "type": "links", "items": [ { "label": "Learn this through the Cuntz organ", "href": "/notebooks/standards/cuntz/", "detail": "A continuous worked example: readable explanations, exact records and the limits of each claim." } ] }, { "type": "p", "text": "MODAVIS connects complementary standards rather than asking one format to do everything. The ontology describes meaning and relationships. VAO binds digital resources into an exchange and preservation contract. Repositories supply persistent version records." }, { "type": "table", "headers": [ "Layer", "Role" ], "rows": [ [ "MODAVIS Ontology Network", "Semantic identities and evidence-qualified relationships." ], [ "VAO Standard", "Manifest, resources, profiles, carriers and file integrity." ], [ "Persistent identifiers", "Stable references to entities and exact releases." ], [ "Provenance", "Documented source, transformation and editorial lineage." ] ] }, { "type": "p", "text": "Established media and research-object formats remain useful within this architecture. A VAO is an integration envelope; it does not replace an audio format, a repository or a domain ontology." }, { "type": "heading", "text": "The agreement at each boundary", "id": "agreements" }, { "type": "table", "headers": [ "Boundary", "Agreement needed" ], "rows": [ [ "A source enters a research workflow", "Identity, capture context, transfer structure and attribution." ], [ "A statement becomes a research representation", "Semantic identity, evidence, interpretation and historical applicability." ], [ "A representation becomes an exchange package", "Exact manifest, resources, profiles, rights and carrier mappings." ], [ "A package becomes a published release", "Persistent version information, file identities and repository metadata." ] ] }, { "type": "p", "text": "These agreements address different kinds of interoperability. Two applications can read the same audio encoding while disagreeing about which instrument state the recording represents. Two catalogues can use the same label while assigning it to different concepts. Interoperability therefore requires both usable bytes and an explicit account of their meaning." }, { "type": "example", "id": "cuntz-profiles", "title": "Does showing the organ in 3D mean the VAO is playable?", "concept": "A profile names a set of requirements for a capability. A client’s support describes what an application can do with the object; the two declarations must be compared.", "scenario": "The Cuntz manifest declares Core, Dynamic Delivery, Playable, Physical Instrument, Scientific, Multimodal, Spatial and Zenodo Repository profiles under VAO 0.5.0.", "steps": [ { "title": "Read the object’s declarations", "text": "The object contains information for several uses, including physical topology, scientific observations and sampled interaction. These requirements describe the package contract." }, { "title": "State the viewer’s operation", "text": "The notebook loads a GLB display derivative and provides camera controls. It does not import the full VAO manifest, evaluate its scientific records or execute its keyboard and stop behavior." }, { "title": "Choose another client when the task changes", "text": "To test sampled playback or synchronized controls, choose a client whose documented version supports the relevant format, profiles and resources. Record the tested operation separately from successful visual loading." } ], "takeaway": "A working 3D preview proves that the chosen model can be displayed; it does not establish complete VAO conformance or playability.", "boundary": "No acoustics profile or calibrated acoustic response is inferred from the presence of an organ model.", "sources": [ { "label": "Cuntz Positiv · VAO 0.5.0-rc.2", "href": "https://doi.org/10.5281/zenodo.22151203", "detail": "Published manifest: identities, measurement observations, realization digests, profiles and rights. Exact examples checked against this release." }, { "label": "VAO Standard 0.5.0", "href": "https://doi.org/10.5281/zenodo.22214248", "detail": "The standard contract is separate from the Cuntz dataset content version 0.5.0-rc.2." } ], "expanded": false, "caseLabel": "Cuntz", "evidence": "Released record", "visual": { "layout": "compare", "title": "Displaying geometry and playing sound need different support", "nodes": [ { "label": "Visual inspection", "value": "Model preview", "detail": "A GLB renderer lets you inspect geometry.", "icon": "cube" }, { "label": "Playable experience", "value": "Declared runtime capability", "detail": "Needs appropriate data, profiles and an implementing client.", "icon": "wave" } ], "caption": "This notebook viewer displays a model. It does not claim to play the Cuntz organ or implement a VAO runtime." } }, { "type": "heading", "text": "Reuse established formats inside the envelope", "id": "media-formats" }, { "type": "p", "text": "VAO can identify realizations in established media and research formats, such as WAVE or FLAC audio, glTF geometry and MIDI or score data. The carrier adds the relationships, fixed identities and declared capabilities needed to interpret those realizations together. The chosen format still carries its own technical requirements; packaging a file does not make an incompatible renderer understand it." }, { "type": "heading", "text": "Version the contract as carefully as the content", "id": "contract-version" }, { "type": "p", "text": "Record the exact schema, profile and vocabulary versions used by a release. A moving “latest” pointer can be convenient for discovering documentation, but it cannot identify the rules under which an earlier package was prepared. When migrating, keep the source release available and describe what changed. A successful migration creates an attributable successor rather than retroactively rewriting the old contract." }, { "type": "note", "title": "A declared standard is a checkable claim", "text": "State which contract and profile are supported, and retain the evidence of validation. Conformance is specific to those declarations; it is not a general certificate of historical truth or scientific adequacy." }, { "type": "links", "items": [ { "label": "VAO Standard 0.5.0", "href": "https://doi.org/10.5281/zenodo.22214248", "detail": "The versioned specification and reference tools." }, { "label": "MODAVIS Ontology Network 0.1.0", "href": "https://doi.org/10.5281/zenodo.22126086", "detail": "The published semantic model." } ] }, { "type": "heading", "id": "standards-by-task", "text": "Which standard answers which question?" }, { "type": "table", "headers": [ "Contract", "Role in this ecosystem", "Read the result as" ], "rows": [ [ "JSON Schema Draft 2020-12", "Structural validation of the VAO JSON record, with the required format assertions.", "A check of the encoded structure, alongside additional semantic rules." ], [ "JSON-LD 1.1", "Explicit mappings from JSON terms to linked-data identifiers and graph relationships.", "A semantic interpretation under an identified context, not a replacement for the authoritative VAO JSON." ], [ "PROV-O", "A vocabulary for entities, activities, agents and their provenance relationships.", "An account of derivation and responsibility, not a certificate that the resulting assertion is true." ], [ "SHACL", "Validation of an RDF data graph against declared shapes and constraints.", "A report for a particular data graph, shapes graph and validation setup." ], [ "VAO profiles and carrier contracts", "Capabilities, exact realizations, dependency closure and package exchange.", "A version-specific interoperability claim whose scope must be stated." ] ] }, { "type": "p", "text": "These contracts work at different layers. A JSON record may satisfy its schema while referring to an inappropriate historical state. A graph may satisfy its shapes while an underlying source remains disputed. PROV-O can express that an analysis was generated by an activity associated with an agent; it does not independently verify that the activity used a calibrated instrument. The domain model and the research method provide the interpretation around the technical contract." }, { "type": "p", "text": "For implementation, keep the relevant documents and contexts pinned with the release. Start with the project’s specified contract rather than substituting a newer vocabulary or a moving context URL. For reading, consult the official specifications below alongside the project-specific requirements. This separates the general mechanism from the particular agreement MODAVIS or VAO makes with its consumers." }, { "type": "links", "items": [ { "label": "W3C JSON-LD 1.1", "href": "https://www.w3.org/TR/json-ld11/", "detail": "Contexts and linked-data representation." }, { "label": "W3C PROV-O", "href": "https://www.w3.org/TR/prov-o/", "detail": "The provenance vocabulary." }, { "label": "W3C SHACL", "href": "https://www.w3.org/TR/shacl/", "detail": "RDF graph constraints and validation reports." }, { "label": "VAO validation guide", "href": "/notebooks/standards/conformance/", "detail": "Apply these layers to a concrete object." } ] }, { "type": "example", "id": "cuntz-jsonld", "title": "How does JSON become linked data?", "concept": "JSON is a way to write structured values. JSON-LD adds an explicit context that relates terms to identifiers, so relationships can be interpreted consistently across records.", "scenario": "The Cuntz manifest contains both a formatVersion and an @context. Its observation identifies the property GesL with an IRI and its unit with the QUDT MilliM identifier.", "steps": [ { "title": "Read the ordinary data first", "text": "A human explanation says: this pipe has a recorded GesL result of 1281 millimetres in this source cell. That sentence should remain understandable before a reader meets graph syntax." }, { "title": "Identify the terms explicitly", "text": "An identified property and unit avoid relying on an unexplained local word such as “length” or “mm” alone. Their definitions and mapping must be inspected rather than guessed from spelling." }, { "title": "Pin the interpretation", "text": "Use the context and contract appropriate to the exact VAO version. Changing a context can change interpretation; a moving “latest” mapping is unsuitable for reproducing a fixed release." } ], "takeaway": "The context explains how the data’s terms connect to identified meanings; it does not add missing evidence.", "boundary": "Do not copy a few fields from the manifest and assume the excerpt retains the complete JSON-LD or VAO contract.", "sources": [ { "label": "Cuntz Positiv · VAO 0.5.0-rc.2", "href": "https://doi.org/10.5281/zenodo.22151203", "detail": "Published manifest: identities, measurement observations, realization digests, profiles and rights. Exact examples checked against this release." }, { "label": "VAO Standard 0.5.0", "href": "https://doi.org/10.5281/zenodo.22214248", "detail": "The standard contract is separate from the Cuntz dataset content version 0.5.0-rc.2." } ], "expanded": false, "caseLabel": "Cuntz", "evidence": "Released record", "visual": { "layout": "flow", "title": "A context gives JSON keys explicit meanings", "nodes": [ { "label": "JSON record", "value": "Values & identifiers", "detail": "The VAO JSON contract remains authoritative.", "icon": "database" }, { "label": "Pinned context", "value": "Meaning of each term", "detail": "Use the context required by the format version.", "icon": "book" }, { "label": "RDF graph", "value": "Linked statements", "detail": "Validate the claimed graph contract.", "icon": "network" } ], "caption": "Renaming a key or inventing a context is not a substitute for the released mapping.", "relations": [ "process with the context", "inspect the graph" ] } } ], "sources": [ { "label": "VAO Standard 0.5.0", "href": "https://doi.org/10.5281/zenodo.22214248", "detail": "The versioned specification and reference tools." }, { "label": "MODAVIS Ontology Network 0.1.0", "href": "https://doi.org/10.5281/zenodo.22126086", "detail": "The published semantic model." }, { "label": "W3C · JSON-LD 1.1", "href": "https://www.w3.org/TR/json-ld11/", "detail": "Official specification; consulted for contexts and linked-data representation." }, { "label": "W3C · PROV-O", "href": "https://www.w3.org/TR/prov-o/", "detail": "Official provenance ontology; entities, activities and agents." }, { "label": "W3C · SHACL", "href": "https://www.w3.org/TR/shacl/", "detail": "Official graph-validation specification, including Core and SPARQL-based constraints." } ], "overview": { "summary": "A profile names a set of requirements for a capability. A client’s support describes what an application can do with the object; the two declarations must be compared.", "takeaway": "A working 3D preview proves that the chosen model can be displayed; it does not establish complete VAO conformance or playability.", "example": { "label": "See the worked example", "href": "#cuntz-profiles", "detail": "" } } }, "glossary": [ { "term": "Instrument state", "definition": "A historically scoped condition or arrangement of an instrument. A statement about one state should not automatically describe the instrument at every date.", "example": { "label": "Work through the Cuntz example", "href": "/notebooks/ontologies/cuntz/#cuntz-state", "detail": "" } }, { "term": "Context", "definition": "The circumstances within which a statement applies, such as a historical configuration. Context is distinct from the history of how the statement was recorded.", "example": { "label": "Work through the Cuntz example", "href": "/notebooks/ontologies/cuntz/#cuntz-time", "detail": "" } }, { "term": "Realization", "definition": "One exact byte sequence representing an asset. Different encodings or derivatives have different exact identities.", "example": { "label": "Work through the Cuntz example", "href": "/notebooks/standards/cuntz/#cuntz-asset", "detail": "" } }, { "term": "Carrier", "definition": "A package or workspace that contains a manifest, carrier mapping and selected realizations. Bootstrap, preservation-closure and custom carriers serve different delivery purposes.", "example": { "label": "Work through the Cuntz example", "href": "/notebooks/standards/cuntz/#cuntz-carriers", "detail": "" } }, { "term": "Profile", "definition": "A versioned set of additional requirements. A client must satisfy the declared capabilities before claiming full support for that profile.", "example": { "label": "Work through the Cuntz example", "href": "/notebooks/standards/cuntz/#cuntz-profiles", "detail": "" } } ], "figures": {} } }