From Cuntz evidence to a portable VAO
Use the same organ, pipe observation and model to understand the exchange contract. Each distinction answers a practical question about what a file contains, how it can be obtained and what a successful check establishes.
Begin with the ontology exampleThe physical organ, its state and the evidence behind an observation.
1. Give a record an explicit meaning
Cuntz · Worked example#
How does JSON become linked data?
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.
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.
Work through the example 3 STEPS
Read the ordinary data first
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.
Identify the terms explicitly
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.
Pin the interpretation
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.
BASIS FOR THIS EXAMPLE
- Cuntz Positiv · VAO 0.5.0-rc.2 ↗
Published manifest: identities, measurement observations, realization digests, profiles and rights. Exact examples checked against this release.
- VAO Standard 0.5.0 ↗
The standard contract is separate from the Cuntz dataset content version 0.5.0-rc.2.
Do not copy a few fields from the manifest and assume the excerpt retains the complete JSON-LD or VAO contract.
The useful distinction. The context explains how the data’s terms connect to identified meanings; it does not add missing evidence.
Exact fields from the published observation · excerpt, not a complete VAO
{
"featureOfInterestId": "urn:musixplora:4010243:cuntz-positiv:rank:ged:pipe:key-036",
"observedProperty": "https://w3id.org/modavis/vao/cuntz-positiv/measurement/GesL",
"result": {
"quantityKind": "https://w3id.org/modavis/vao/cuntz-positiv/quantity/GesL",
"unit": "http://qudt.org/vocab/unit/MilliM",
"value": 1281
},
"qualityFlags": [
"result-time-from-workbook-modification-timestamp",
"source-cell:Holzgedackt 8!D9",
"source-series:2019"
],
"resultTime": "2020-09-16T10:33:05Z"
}Read the identifiers as links to other records, not as a requirement to memorize the strings. The human interpretation is: the specified pipe has an asserted GesL result of 1281 millimetres, traceable to a named workbook cell, with an explicit timestamp qualification. The full manifest supplies the surrounding context and referenced entities.
2. Distinguish a research asset from its files
Cuntz · Worked example#
How can two model files represent one asset?
A logical asset names a role in the research object. A realization identifies one exact encoding of that asset. A distribution says where a realization can be obtained.
The Cuntz manifest groups the 4010243_segmented_03b2 FBX source and GLB runtime model under one logical model asset. Their byte sizes, formats and digests differ.
Work through the example 3 STEPS
Identify the shared asset
The asset groups representations serving the named model role. It supplies the connection that a filename alone cannot guarantee.
Inspect each realization
The FBX source is 61,745,100 bytes; the released GLB is 115,416,448 bytes. The GLB is marked derived, with a model-conversion activity. Each has an independent SHA-256.
Identify the notebook derivative separately
The smaller model served by this notebook is another derived file. Its caption and file identity distinguish it from both published realizations, and its provenance leads back to the released GLB.
BASIS FOR THIS EXAMPLE
- Cuntz Positiv · VAO 0.5.0-rc.2 ↗
Published manifest: identities, measurement observations, realization digests, profiles and rights. Exact examples checked against this release.
- VAO Standard 0.5.0 ↗
The standard contract is separate from the Cuntz dataset content version 0.5.0-rc.2.
The smaller web derivative has not been retroactively inserted into the published VAO manifest.
The useful distinction. “Same asset” expresses a relationship; “same bytes” is a separate, testable claim.
Cuntz · Worked example#
Why does the Cuntz release offer two VAO downloads?
A manifest describes the research object and its resource relationships. A carrier is a package that delivers some or all of those exact resources.
The published Cuntz record offers a bootstrap carrier and a preservation carrier. The release states that both carry the same manifest; the preservation carrier includes every declared realization.
Work through the example 3 STEPS
Begin with the inventory
The bootstrap supplies the semantic inventory and core evidence. It lets a reader discover what exists without first downloading all the media.
Request the required material
A geometry inspection needs the selected model and its dependencies. A playable experience may need audio, control mappings and other groups. Reading metadata does not make those resources locally available.
Choose preservation deliberately
The complete preservation carrier supports the full declared realization inventory. Cite the exact release and record which carrier or selected closure you actually acquired.
BASIS FOR THIS EXAMPLE
- Cuntz Positiv · VAO 0.5.0-rc.2 ↗
Published manifest: identities, measurement observations, realization digests, profiles and rights. Exact examples checked against this release.
- VAO Standard 0.5.0 ↗
The standard contract is separate from the Cuntz dataset content version 0.5.0-rc.2.
A downloaded bootstrap does not prove that every external resource has been fetched or verified.
The useful distinction. One research release can have several delivery packages without becoming several historical interpretations.
Cuntz · Worked example#
What does “dependency closure” mean for a model?
A dependency is something an item needs to work as declared. Closure means including everything required by the selected items, continuing until no required dependency is missing.
Imagine a Cuntz display model delivered with a separate material texture. This is an illustrative delivery scenario; the notebook’s GLB instead embeds its texture.
Work through the example 3 STEPS
Select the model
Begin with the geometry realization needed for the task. Selecting its name alone does not guarantee a complete visual representation.
Follow every declared requirement
If the model needs a texture, include it. If a playback task also requires a sample map and audio files, follow those requirements too. Do not confuse optional enhancements with mandatory dependencies.
Verify the complete selection
Only after the required bytes are acquired and verified can the selected capability be described as materialized. Record missing resources as missing rather than silently substituting unrelated files.
BASIS FOR THIS EXAMPLE
- Cuntz Positiv · VAO 0.5.0-rc.2 ↗
Published manifest: identities, measurement observations, realization digests, profiles and rights. Exact examples checked against this release.
- VAO Standard 0.5.0 ↗
The standard contract is separate from the Cuntz dataset content version 0.5.0-rc.2.
This example explains the selection rule; it does not assert that the published Cuntz GLB uses an external texture or that the web viewer executes a complete VAO.
The useful distinction. Closure is the complete set of prerequisites for a chosen task, not necessarily the entire archive.
3. State what is available and what was checked
Cuntz · Worked example#
Does showing the organ in 3D mean the VAO is playable?
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.
The Cuntz manifest declares Core, Dynamic Delivery, Playable, Physical Instrument, Scientific, Multimodal, Spatial and Zenodo Repository profiles under VAO 0.5.0.
Work through the example 3 STEPS
Read the object’s declarations
The object contains information for several uses, including physical topology, scientific observations and sampled interaction. These requirements describe the package contract.
State the viewer’s operation
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.
Choose another client when the task changes
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.
BASIS FOR THIS EXAMPLE
- Cuntz Positiv · VAO 0.5.0-rc.2 ↗
Published manifest: identities, measurement observations, realization digests, profiles and rights. Exact examples checked against this release.
- VAO Standard 0.5.0 ↗
The standard contract is separate from the Cuntz dataset content version 0.5.0-rc.2.
No acoustics profile or calibrated acoustic response is inferred from the presence of an organ model.
The useful distinction. A working 3D preview proves that the chosen model can be displayed; it does not establish complete VAO conformance or playability.
Cuntz · Worked example#
What does the model’s SHA-256 prove?
A checksum is a fingerprint calculated from bytes. Fixity checking compares that fingerprint with a trusted expected value to detect changed or mismatched files.
The published GLB source for this notebook has SHA-256 beginning 19527c2188b08d85. The display derivative has a different digest because its texture and encoding were changed.
Work through the example 3 STEPS
Compare like with like
Check the complete source GLB digest against the exact source realization. Compare the website derivative against its own expected digest, not against the source GLB’s digest.
Notice byte-changing edits
A texture conversion or mesh encoding change produces a different file identity. Even reformatting a JSON manifest can change its exact-byte hash without changing its parsed meaning.
Keep the scientific question separate
Matching bytes establish which representation was obtained. The digest does not verify the model’s physical scale, the pipe measurement method or a claim about the sound of 1610.
BASIS FOR THIS EXAMPLE
- Cuntz Positiv · VAO 0.5.0-rc.2 ↗
Published manifest: identities, measurement observations, realization digests, profiles and rights. Exact examples checked against this release.
- VAO Standard 0.5.0 ↗
The standard contract is separate from the Cuntz dataset content version 0.5.0-rc.2.
This website verifies the model’s expected byte length and full SHA-256 before passing it to the renderer. That is a file-identity check, not a VAO conformance report.
The useful distinction. Fixity makes evidence identifiable; it does not independently validate the evidence’s interpretation.
Cuntz · Worked example#
How can a file pass validation but support a limited conclusion?
Conformance means meeting a specified contract. Different checks address parsing, structure, relationships, required capabilities and file identity.
Take the published observation with value 1281 millimetres. A reader wants to know both whether its record is valid and whether the measurement answers a question about the pipe.
Work through the example 3 STEPS
Check the structure
A schema can check that the result has the required form and that a numerical field contains a number. Semantic checks can verify that references point to appropriate records.
Check the evidence links
Resolve the pipe, measurement activity and workbook realization; verify the cited source bytes. These operations establish what the record says and which source it identifies.
Assess fitness for the question
The workbook timestamp still is not the measurement-session date. A valid record without a documented calibration uncertainty cannot support an uncertainty claim simply because its schema passed.
BASIS FOR THIS EXAMPLE
- Cuntz Positiv · VAO 0.5.0-rc.2 ↗
Published manifest: identities, measurement observations, realization digests, profiles and rights. Exact examples checked against this release.
- VAO Standard 0.5.0 ↗
The standard contract is separate from the Cuntz dataset content version 0.5.0-rc.2.
The notebook’s JSON teaching excerpt is deliberately incomplete and is not presented as a complete, independently conforming VAO package.
The useful distinction. Validation and scientific assessment complement one another; each needs an explicitly stated scope.
4. Make reuse recoverable
Cuntz · Worked example#
Which Cuntz identifier belongs in a citation?
Versioned citation separates the physical subject, the released research object and the explanation or derived artifact actually used.
A reader uses the notebook’s model to discuss a geometry, while another uses the 1281 mm workbook observation. Their references should identify different evidence even though both concern Cuntz.
Work through the example 3 STEPS
Identify the release
Use version DOI 10.5281/zenodo.22151203 for the inspected dataset. Record the specific realization or observation, rather than citing only the project community.
Identify what was used
For the web preview, retain the derivative’s digest and transformation note. For the observation, identify the pipe, property, source cell and workbook realization.
Cite the explanation separately
Use “Cite this page” for the notebook’s fixed edition. Its fingerprint identifies the explanation; it does not replace the source dataset or model fingerprint.
BASIS FOR THIS EXAMPLE
- Cuntz Positiv · VAO 0.5.0-rc.2 ↗
Published manifest: identities, measurement observations, realization digests, profiles and rights. Exact examples checked against this release.
- VAO Standard 0.5.0 ↗
The standard contract is separate from the Cuntz dataset content version 0.5.0-rc.2.
The dataset content version 0.5.0-rc.2, VAO format version 0.5.0 and website edition are separate version systems.
The useful distinction. A citation chain lets a reader recover both the evidence and the interpretation.
Cuntz · Worked example#
Does an open dataset remove the need for attribution?
A rights record specifies access and reuse information. Provenance separately identifies contributors and transformations; keeping both supports responsible reuse.
The Cuntz release’s explicit rights properties state open access and CC BY-SA 4.0, with a contributor attribution. This notebook’s model is a changed display derivative.
Work through the example 3 STEPS
Read the explicit release statement
Use the rights properties and linked licence for the exact version, rather than an older development README or an opaque identifier suffix.
Carry the attribution forward
Credit the source dataset and contributors, link its version record and licence, and identify the changes made for this website.
Keep file identities distinct
The release retains its original bytes. The website publishes its derivative with its own fingerprint and a transformation note, making the relationship inspectable.
BASIS FOR THIS EXAMPLE
- Cuntz Positiv · VAO 0.5.0-rc.2 ↗
Published manifest: identities, measurement observations, realization digests, profiles and rights. Exact examples checked against this release.
This example describes the release’s recorded terms; it does not assign new rights to unrelated third-party assets.
The useful distinction. Open access and a traceable derivative still require clear source, credit and change information.
Sources & further reading
- Cuntz Positiv · VAO 0.5.0-rc.2
Published manifest: identities, measurement observations, realization digests, profiles and rights. Exact examples checked against this release.
- VAO Standard 0.5.0
The standard contract is separate from the Cuntz dataset content version 0.5.0-rc.2.
- MODAVIS Ontology Network 0.1.0
Identity, state, configuration, evidence, assertions, context and provenance. Teaching examples explain its distinctions without inventing new normative properties.
Page editions 2026-09-r5 ↓
Read a fixed snapshot of this chapter, or return to the current notebook.
Edition 2026-09-r5 · SHA-256
795dc6066f86Page metadata ↗