- SubjectPractice instrumentWhat the note concerns.aboutEntityIds connects the asset to the subject
- ResourceEvidence noteOne exact UTF-8 realization.The carrier embeds the realization and binds the manifest
- DeliveryVAO carrierA manifest, carrier mapping and embedded note.
Key idea & worked example
A reusable result keeps its identity, source and validation scope visible.
A passing check belongs to specific contents and a stated profile.See the worked example →On this page
A small package you can finish
Start with one instrument identity and one text note. This supported workflow is intentionally small: it teaches the same distinction between a subject, a logical assetLogical assetAn intellectual or functional resource, such as a take, a mesh or a score. Its role is distinguished from the particular bytes used to represent it.Work through the Cuntz example → and exact realizationRealizationOne exact byte sequence representing an asset. Different encodings or derivatives have different exact identities.Work through the Cuntz example → bytes that larger recording or model packages require. The example begins as an attributed learning derivative of the standard’s minimal fixture, with its own identifiers and authoring activity.
Your evidence package
Change the label or note, inspect the connections, and validate. Introduce a digest mismatch to learn what an exact-byte error means, then repair and check again.
A text evidence note, embedded in a VAO 0.5.0 carrier. This is a generic practice example.
Technical files · inspect or edit
Direct edits can introduce real validation errors. Rebind / repair updates the supported example’s checksums or representation link.
The instrument identity anchors what the note is about.
The asset groups one exact realization.
The digest and byte count identify the resource.
Binds the manifest and embeds the resource.
The drawing explains the supported form. Direct edits to technical files are checked by the reference validator; inspect those files for their exact relationships.
Edit the example, then run validation. Every edit clears the previous result.
Loading the verified example…
Validation runs locally in a worker after you click. The first check loads roughly 20 MB of Python and pinned tools. Inputs are kept in this page’s memory. Downloads are practice outputs; repository publication and additional application profiles need their own checks.
Workflow and reference commands
- Edit the source-evidence note or generic instrument graph in the starter kit.
- For a VAO, update the realization byte count and digest, group total, and carrier manifest byte count and SHA-256.
- Run the pinned validator. Fix errors before exporting. A successful check applies to the declared profile and current files.
Download the verified starter kit ↓
python Tools/vao05.py validate vao-workspace --json python Tools/vao05.py pack vao-workspace learning.vao python Tools/vao05.py validate learning.vao --json
The native starter contains the unchanged released VAO fixture. The browser starts with a separately identified and attributed learning derivative.
Read the report before exporting
The released VAO 0.5.0 tool checks JSON Schema conditions, semantic references, declared profiles and the actual embedded bytes. The packer writes a carrierCarrierA package or workspace that contains a manifest, carrier mapping and selected realizations. Bootstrap, preservation-closure and custom carriers serve different delivery purposes.Work through the Cuntz example → only after workspace validation; that packed carrier is then checked again. Download is enabled only for the current passing contents. Editing clears the result, so an earlier pass cannot stand in for a new check.
Move from practice to your own project
- Keep the original evidence and identify its source, permissions and processing history. Use identifiers appropriate to your project; the example.org identifiers in this practice package are placeholders.
- For an audio recording, use audio technical metadata and any required additional profiles. Do not rename source.txt to .wav or copy this document realization as an audio declaration. Follow the package guide and native tools for that workflow.
- Choose acquisition groups and capabilities for your intended delivery. A bootstrap carrier may provide a useful subset without establishing preservation closure.
- Run the reference checks on the exact files you will distribute. Check repository descriptors and citation requirements separately.
Make a change you can check
A reusable result keeps its identity, source and validation scope visible.
- SubjectPractice instrumentWhat the note concerns.aboutEntityIds connects the asset to the subject
- ResourceEvidence noteOne exact UTF-8 realization.The carrier embeds the realization and binds the manifest
- DeliveryVAO carrierA manifest, carrier mapping and embedded note.
Work through the example 3 STEPS
Use the generic practice example to make one deliberate edit and see what changes.
Edit a label or note
The supported form creates a coherent practice record. Direct technical edits can introduce errors.
Check the current contents
The released validator evaluates the exact current input and returns its actual report.
Export the passing result
An edit clears the previous pass. Export the current checked graph or packed carrier with its report.
- VAO Standard 0.5.0 ↗
Unmodified released reference validator, packer, schemas and minimal fixture. Software Apache 2.0; schemas and examples CC BY 4.0, Dominik Ukolov and contributors.
This is an illustrative workflow, not a historical claim or a repository certification.
The useful distinction. A passing check belongs to specific contents and a stated profile.