{ "title": "A reusable release: from practice to publication — Standards & citation", "text": "MODAVIS (2026). A reusable release: from practice to publication — Standards & citation. Research notebooks, October 2026 · Wider reading and source audit edition. https://modavis.org/editions/2026-10-reading/standards/reuse-checklist/", "bibtex": "@misc{modavis_standards_reuse_checklist_2026_10_reading,\n author = {{MODAVIS}},\n title = {A reusable release: from practice to publication — Standards & citation},\n year = {2026},\n month = {10},\n version = {2026-10-reading},\n url = {https://modavis.org/editions/2026-10-reading/standards/reuse-checklist/},\n note = {Content SHA-256: 01a53eba6fecdfc343f5b3a2b3949221e09424d57a29318021c22c8574d96046}\n}", "url": "https://modavis.org/editions/2026-10-reading/standards/reuse-checklist/", "sha256": "01a53eba6fecdfc343f5b3a2b3949221e09424d57a29318021c22c8574d96046", "edition": "2026-10-reading", "date": "2026-10-09", "canonicalPayload": "{\"book\":{\"number\":\"08\",\"slug\":\"standards\",\"title\":\"Standards & citation\"},\"chapter\":{\"blocks\":[{\"type\":\"visual\",\"visual\":{\"caption\":\"Reusability comes from these connections. A passed check or an attractive viewer alone is not a complete research handover.\",\"layout\":\"flow\",\"nodes\":[{\"detail\":\"A short account of what the package or graph means.\",\"icon\":\"book\",\"label\":\"Explain\",\"value\":\"Subject · source · scope\"},{\"detail\":\"Exact artifacts and reproducible technical outcomes.\",\"icon\":\"check\",\"label\":\"Verify\",\"value\":\"Versions · files · checks\"},{\"detail\":\"Credit, reuse instructions and unresolved questions.\",\"icon\":\"external\",\"label\":\"Hand over\",\"value\":\"Terms · limits · next steps\"}],\"relations\":[\"bind the account to artifacts\",\"give the next person a route\"],\"title\":\"A release another researcher can follow\"}},{\"id\":\"handover-checklist\",\"text\":\"1. Check the handover before making a release claim\",\"type\":\"heading\"},{\"headers\":[\"Question\",\"What the next researcher should receive\"],\"rows\":[[\"What does this represent?\",\"An identified subject and any state, configuration or context that qualifies the account.\"],[\"Which exact release did you use?\",\"The VAO standard and ontology versions, plus the object or dataset content version and immutable source references.\"],[\"Which bytes did you use?\",\"Exact realization and carrier identities, byte sizes and digests, with a clear distinction between originals and derivatives.\"],[\"Why is a statement present?\",\"Its attributable assertion, source fragment, method, generating activity, review status and unresolved qualifications.\"],[\"What can the receiving client do?\",\"Declared capabilities, required profiles, complete groups and dependencies; a report of unavailable or unsupported operations.\"],[\"How may the resources be reused?\",\"Creators, attribution, resource-specific reuse terms, source links and documented changes.\"],[\"How can a result be reproduced?\",\"Input identities, commands, tool versions, check results and checks that were not run.\"]],\"type\":\"table\"},{\"id\":\"run-distinct-checks\",\"text\":\"2. Run checks in an order that makes failures understandable\",\"type\":\"heading\"},{\"type\":\"visual\",\"visual\":{\"caption\":\"Run additional runtime, linked-data or publication checks when those capabilities or profiles are claimed.\",\"layout\":\"layers\",\"nodes\":[{\"detail\":\"Check the record against its declared version and profiles.\",\"icon\":\"network\",\"label\":\"Structure & meaning\",\"value\":\"Parsing · schema · relations\"},{\"detail\":\"Verify the files, carrier mappings and required members.\",\"icon\":\"database\",\"label\":\"Exact artifacts\",\"value\":\"Bytes · bindings · closure\"},{\"detail\":\"Assess the claim and the operation you actually support.\",\"icon\":\"compass\",\"label\":\"Interpretation\",\"value\":\"Source review & capability tests\"}],\"relations\":[\"then verify the artifact\",\"then assess the scope\"],\"title\":\"Different checks protect different parts of the account\"}},{\"text\":\"For a VAO, validate the workspace, pack to a new output, and validate the produced carrier. Check release bindings with the actual release descriptor, not an unrelated example descriptor. Check dependency closure for the groups needed by your intended operation. For an RDF graph, load the pinned ontology hierarchy and shapes. The tutorial helper checks exchange data; publication and application profiles may require further records.\",\"type\":\"p\"},{\"boundary\":\"The notebook’s JSON teaching excerpt is deliberately incomplete and is not presented as a complete, independently conforming VAO package.\",\"concept\":\"Conformance means meeting a specified contract. Different checks address parsing, structure, relationships, required capabilities and file identity.\",\"expanded\":false,\"id\":\"cuntz-conformance\",\"scenario\":\"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.\",\"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 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.\",\"title\":\"Check the structure\"},{\"text\":\"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.\",\"title\":\"Check the evidence links\"},{\"text\":\"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.\",\"title\":\"Assess fitness for the question\"}],\"takeaway\":\"Validation and scientific assessment complement one another; each needs an explicitly stated scope.\",\"title\":\"How can a file pass validation but support a limited conclusion?\",\"type\":\"example\",\"visual\":{\"caption\":\"Technical validation and scientific review answer different questions.\",\"layout\":\"flow\",\"nodes\":[{\"detail\":\"Identify which requirements were checked.\",\"icon\":\"book\",\"label\":\"Contract\",\"value\":\"Version + profiles\"},{\"detail\":\"Parsing, relationships, fixity and other claimed layers.\",\"icon\":\"check\",\"label\":\"Technical checks\",\"value\":\"Recorded outcomes\"},{\"detail\":\"Review what the result can support.\",\"icon\":\"quote\",\"label\":\"Research judgment\",\"value\":\"Evidence & interpretation\"}],\"relations\":[\"run the relevant checks\",\"interpret their limits\"],\"title\":\"A useful result states its scope\"}},{\"id\":\"recover-failures\",\"text\":\"3. Use a failure as a specific next action\",\"type\":\"heading\"},{\"headers\":[\"Observed problem\",\"Useful recovery\"],\"rows\":[[\"A payload digest or byte size differs\",\"Find whether the download failed or the file was transformed. Acquire the pinned realization or document a coherent new derivative; never relabel different bytes as a match.\"],[\"A manifest edit breaks its carrier pin\",\"Recompute the exact manifest-byte bindings for the new release, then check carrier and release descriptors together.\"],[\"A required group is incomplete\",\"Follow the dependency graph and acquire the missing exact members. Report a partial selection honestly.\"],[\"A graph collapses instrument and model identity\",\"Restore distinct IRIs and the representation relation; rerun the negative and positive examples.\"],[\"A timestamp is valid but its meaning is uncertain\",\"Preserve the source qualification. Separate file history, capture time, historical scope and measurement time.\"],[\"A client cannot execute a profile\",\"Keep useful lower-level inspection available and state the unsupported operation. Test a compatible client for the claimed task.\"]],\"type\":\"table\"},{\"id\":\"record-report\",\"text\":\"4. Write a report someone else can inspect\",\"type\":\"heading\"},{\"label\":\"Illustrative handover note · fill with your real inputs\",\"text\":\"Subject and scope:\\n [instrument / state / configuration / research question]\\nSource releases:\\n VAO Standard 0.5.0; MODAVIS Ontology Network 0.1.0\\n [exact object or dataset version and source identifier]\\nInputs:\\n [manifest / graph / realization / carrier identity and SHA-256]\\nTools and commands:\\n [release, environment, exact command and working directory]\\nChecks completed:\\n [profile or layer, result, retained diagnostic report]\\nChecks not performed:\\n [runtime / publication / acoustic / historical review, as applicable]\\nReuse:\\n [resource creators, terms, source links, derivative changes]\\nRemaining questions:\\n [what the evidence does not yet establish]\",\"type\":\"code\"},{\"text\":\"The template is a human-readable handover note, not a normative VAO materialization receipt or a machine-readable validation report. Use the released schema for those artifacts. A receipt documents acquisition; a technical report documents checks; a research account explains what their combined evidence can support.\",\"type\":\"p\"},{\"type\":\"visual\",\"visual\":{\"caption\":\"Cuntz’s published CC BY-SA 4.0 terms and attribution accompany its web derivatives.\",\"layout\":\"flow\",\"nodes\":[{\"detail\":\"Check the specific resource and release.\",\"icon\":\"book\",\"label\":\"Source release\",\"value\":\"Read the rights record\"},{\"detail\":\"Keep creator credit and the applicable terms.\",\"icon\":\"layers\",\"label\":\"Derivative\",\"value\":\"Describe your changes\"},{\"detail\":\"Give downstream readers the source and license.\",\"icon\":\"external\",\"label\":\"Distribution\",\"value\":\"Credit travels with it\"}],\"relations\":[\"retain attribution\",\"carry terms forward\"],\"title\":\"Reuse keeps credit and terms attached\"}},{\"id\":\"share-reusable-outcome\",\"text\":\"5. Make the first reuse easy\",\"type\":\"heading\"},{\"text\":\"Give the next person a small entry point, a concise explanation and one runnable example. Link the full preservation copy, original source, terms and validation evidence. Keep earlier released artifacts immutable when the account changes. For a repository distribution, follow the versioned repository profile and record the actual published carrier identities.\",\"type\":\"p\"},{\"text\":\"For an ontology adaptation, document your application profile and any project-owned terms or mapping graph. Keep assertions and source evidence available behind convenience displays. For a 3D notebook, provide the attributed poster and complete explanation alongside optional rendering. A reader should be able to understand the result without a GPU and distinguish a visual demonstration from a measured or playable research claim.\",\"type\":\"p\"},{\"boundary\":\"The dataset content version 0.5.0-rc.2, VAO format version 0.5.0 and website edition are separate version systems.\",\"concept\":\"Versioned citation separates the physical subject, the released research object and the explanation or derived artifact actually used.\",\"expanded\":false,\"id\":\"cuntz-citation\",\"scenario\":\"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.\",\"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\":\"Use version DOI 10.5281/zenodo.22151203 for the inspected dataset. Record the specific realization or observation, rather than citing only the project community.\",\"title\":\"Identify the release\"},{\"text\":\"For the web preview, retain the derivative’s digest and transformation note. For the observation, identify the pipe, property, source cell and workbook realization.\",\"title\":\"Identify what was used\"},{\"text\":\"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.\",\"title\":\"Cite the explanation separately\"}],\"takeaway\":\"A citation chain lets a reader recover both the evidence and the interpretation.\",\"title\":\"Which Cuntz identifier belongs in a citation?\",\"type\":\"example\",\"visual\":{\"caption\":\"These citations refer to different artifacts; preserve the link among them.\",\"layout\":\"flow\",\"nodes\":[{\"detail\":\"Identifies the published Cuntz package.\",\"icon\":\"book\",\"label\":\"Object release\",\"value\":\"Version DOI\"},{\"detail\":\"Identifies the model bytes actually used.\",\"icon\":\"cube\",\"label\":\"Exact realization\",\"value\":\"Digest & identifier\"},{\"detail\":\"Identifies the teaching text you consulted.\",\"icon\":\"quote\",\"label\":\"Explanation\",\"value\":\"Notebook edition\"}],\"relations\":[\"name the relevant member\",\"cite the explanatory account\"],\"title\":\"Cite the artifact that supports your statement\"}},{\"items\":[{\"detail\":\"Repeat the known-good workspace-to-carrier workflow.\",\"href\":\"/notebooks/vao/reuse/\",\"label\":\"First VAO tutorial\"},{\"detail\":\"Repeat the positive/negative graph and query workflow.\",\"href\":\"/notebooks/ontologies/reuse/\",\"label\":\"First ontology tutorial\"},{\"detail\":\"Read the normative layer boundaries and additional checks.\",\"href\":\"/notebooks/standards/conformance/\",\"label\":\"Full conformance guide\"},{\"detail\":\"Cite a recoverable explanation as well as the object release.\",\"href\":\"/notebooks/standards/versions/\",\"label\":\"Understand fixed notebook editions\"}],\"type\":\"links\"}],\"intro\":\"Make your next VAO or MODAVIS graph useful to someone who was not there when you made it. Use a clear handover, scoped checks, and a release whose sources and exact artifacts can be recovered.\",\"slug\":\"reuse-checklist\",\"sources\":[{\"detail\":\"Specification, schemas, reference tools and fixtures. Use this exact standard version for the exercises.\",\"href\":\"https://doi.org/10.5281/zenodo.22214248\",\"label\":\"VAO Standard 0.5.0 · immutable release\"},{\"detail\":\"Terms, governed vocabularies, versioned shapes and interpretation guide.\",\"href\":\"https://doi.org/10.5281/zenodo.22126086\",\"label\":\"MODAVIS Ontology Network 0.1.0 · immutable release\"},{\"detail\":\"The real observation and model used for the Cuntz examples. Its content version differs from VAO formatVersion 0.5.0.\",\"href\":\"https://doi.org/10.5281/zenodo.22151203\",\"label\":\"Cuntz Positiv · content release 0.5.0-rc.2\"},{\"detail\":\"\",\"href\":\"https://github.com/modavis-project/vao-standard/blob/v0.5.0/Docs/VAO_CONFORMANCE_0.5.0.md\",\"label\":\"VAO 0.5.0 conformance specification\"},{\"detail\":\"\",\"href\":\"https://github.com/modavis-project/modavis-ontology-network/blob/0.1.0/docs/INTERPRETATION_GUIDE.md\",\"label\":\"MODAVIS 0.1.0 interpretation guide\"}],\"title\":\"A reusable release: from practice to publication\"},\"date\":\"2026-10-09\",\"edition\":\"2026-10-reading\",\"figures\":{}}", "payload": { "edition": "2026-10-reading", "date": "2026-10-09", "book": { "slug": "standards", "title": "Standards & citation", "number": "08" }, "chapter": { "slug": "reuse-checklist", "title": "A reusable release: from practice to publication", "intro": "Make your next VAO or MODAVIS graph useful to someone who was not there when you made it. Use a clear handover, scoped checks, and a release whose sources and exact artifacts can be recovered.", "sources": [ { "label": "VAO Standard 0.5.0 · immutable release", "href": "https://doi.org/10.5281/zenodo.22214248", "detail": "Specification, schemas, reference tools and fixtures. Use this exact standard version for the exercises." }, { "label": "MODAVIS Ontology Network 0.1.0 · immutable release", "href": "https://doi.org/10.5281/zenodo.22126086", "detail": "Terms, governed vocabularies, versioned shapes and interpretation guide." }, { "label": "Cuntz Positiv · content release 0.5.0-rc.2", "href": "https://doi.org/10.5281/zenodo.22151203", "detail": "The real observation and model used for the Cuntz examples. Its content version differs from VAO formatVersion 0.5.0." }, { "label": "VAO 0.5.0 conformance specification", "href": "https://github.com/modavis-project/vao-standard/blob/v0.5.0/Docs/VAO_CONFORMANCE_0.5.0.md", "detail": "" }, { "label": "MODAVIS 0.1.0 interpretation guide", "href": "https://github.com/modavis-project/modavis-ontology-network/blob/0.1.0/docs/INTERPRETATION_GUIDE.md", "detail": "" } ], "blocks": [ { "type": "visual", "visual": { "layout": "flow", "title": "A release another researcher can follow", "nodes": [ { "label": "Explain", "value": "Subject · source · scope", "detail": "A short account of what the package or graph means.", "icon": "book" }, { "label": "Verify", "value": "Versions · files · checks", "detail": "Exact artifacts and reproducible technical outcomes.", "icon": "check" }, { "label": "Hand over", "value": "Terms · limits · next steps", "detail": "Credit, reuse instructions and unresolved questions.", "icon": "external" } ], "caption": "Reusability comes from these connections. A passed check or an attractive viewer alone is not a complete research handover.", "relations": [ "bind the account to artifacts", "give the next person a route" ] } }, { "type": "heading", "id": "handover-checklist", "text": "1. Check the handover before making a release claim" }, { "type": "table", "headers": [ "Question", "What the next researcher should receive" ], "rows": [ [ "What does this represent?", "An identified subject and any state, configuration or context that qualifies the account." ], [ "Which exact release did you use?", "The VAO standard and ontology versions, plus the object or dataset content version and immutable source references." ], [ "Which bytes did you use?", "Exact realization and carrier identities, byte sizes and digests, with a clear distinction between originals and derivatives." ], [ "Why is a statement present?", "Its attributable assertion, source fragment, method, generating activity, review status and unresolved qualifications." ], [ "What can the receiving client do?", "Declared capabilities, required profiles, complete groups and dependencies; a report of unavailable or unsupported operations." ], [ "How may the resources be reused?", "Creators, attribution, resource-specific reuse terms, source links and documented changes." ], [ "How can a result be reproduced?", "Input identities, commands, tool versions, check results and checks that were not run." ] ] }, { "type": "heading", "id": "run-distinct-checks", "text": "2. Run checks in an order that makes failures understandable" }, { "type": "visual", "visual": { "layout": "layers", "title": "Different checks protect different parts of the account", "nodes": [ { "label": "Structure & meaning", "value": "Parsing · schema · relations", "detail": "Check the record against its declared version and profiles.", "icon": "network" }, { "label": "Exact artifacts", "value": "Bytes · bindings · closure", "detail": "Verify the files, carrier mappings and required members.", "icon": "database" }, { "label": "Interpretation", "value": "Source review & capability tests", "detail": "Assess the claim and the operation you actually support.", "icon": "compass" } ], "caption": "Run additional runtime, linked-data or publication checks when those capabilities or profiles are claimed.", "relations": [ "then verify the artifact", "then assess the scope" ] } }, { "type": "p", "text": "For a VAO, validate the workspace, pack to a new output, and validate the produced carrier. Check release bindings with the actual release descriptor, not an unrelated example descriptor. Check dependency closure for the groups needed by your intended operation. For an RDF graph, load the pinned ontology hierarchy and shapes. The tutorial helper checks exchange data; publication and application profiles may require further records." }, { "type": "example", "id": "cuntz-conformance", "title": "How can a file pass validation but support a limited conclusion?", "concept": "Conformance means meeting a specified contract. Different checks address parsing, structure, relationships, required capabilities and file identity.", "scenario": "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.", "steps": [ { "title": "Check the structure", "text": "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." }, { "title": "Check the evidence links", "text": "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." }, { "title": "Assess fitness for the question", "text": "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." } ], "takeaway": "Validation and scientific assessment complement one another; each needs an explicitly stated scope.", "boundary": "The notebook’s JSON teaching excerpt is deliberately incomplete and is not presented as a complete, independently conforming VAO package.", "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." } ], "visual": { "layout": "flow", "title": "A useful result states its scope", "nodes": [ { "label": "Contract", "value": "Version + profiles", "detail": "Identify which requirements were checked.", "icon": "book" }, { "label": "Technical checks", "value": "Recorded outcomes", "detail": "Parsing, relationships, fixity and other claimed layers.", "icon": "check" }, { "label": "Research judgment", "value": "Evidence & interpretation", "detail": "Review what the result can support.", "icon": "quote" } ], "caption": "Technical validation and scientific review answer different questions.", "relations": [ "run the relevant checks", "interpret their limits" ] }, "expanded": false }, { "type": "heading", "id": "recover-failures", "text": "3. Use a failure as a specific next action" }, { "type": "table", "headers": [ "Observed problem", "Useful recovery" ], "rows": [ [ "A payload digest or byte size differs", "Find whether the download failed or the file was transformed. Acquire the pinned realization or document a coherent new derivative; never relabel different bytes as a match." ], [ "A manifest edit breaks its carrier pin", "Recompute the exact manifest-byte bindings for the new release, then check carrier and release descriptors together." ], [ "A required group is incomplete", "Follow the dependency graph and acquire the missing exact members. Report a partial selection honestly." ], [ "A graph collapses instrument and model identity", "Restore distinct IRIs and the representation relation; rerun the negative and positive examples." ], [ "A timestamp is valid but its meaning is uncertain", "Preserve the source qualification. Separate file history, capture time, historical scope and measurement time." ], [ "A client cannot execute a profile", "Keep useful lower-level inspection available and state the unsupported operation. Test a compatible client for the claimed task." ] ] }, { "type": "heading", "id": "record-report", "text": "4. Write a report someone else can inspect" }, { "type": "code", "label": "Illustrative handover note · fill with your real inputs", "text": "Subject and scope:\n [instrument / state / configuration / research question]\nSource releases:\n VAO Standard 0.5.0; MODAVIS Ontology Network 0.1.0\n [exact object or dataset version and source identifier]\nInputs:\n [manifest / graph / realization / carrier identity and SHA-256]\nTools and commands:\n [release, environment, exact command and working directory]\nChecks completed:\n [profile or layer, result, retained diagnostic report]\nChecks not performed:\n [runtime / publication / acoustic / historical review, as applicable]\nReuse:\n [resource creators, terms, source links, derivative changes]\nRemaining questions:\n [what the evidence does not yet establish]" }, { "type": "p", "text": "The template is a human-readable handover note, not a normative VAO materialization receipt or a machine-readable validation report. Use the released schema for those artifacts. A receipt documents acquisition; a technical report documents checks; a research account explains what their combined evidence can support." }, { "type": "visual", "visual": { "layout": "flow", "title": "Reuse keeps credit and terms attached", "nodes": [ { "label": "Source release", "value": "Read the rights record", "detail": "Check the specific resource and release.", "icon": "book" }, { "label": "Derivative", "value": "Describe your changes", "detail": "Keep creator credit and the applicable terms.", "icon": "layers" }, { "label": "Distribution", "value": "Credit travels with it", "detail": "Give downstream readers the source and license.", "icon": "external" } ], "caption": "Cuntz’s published CC BY-SA 4.0 terms and attribution accompany its web derivatives.", "relations": [ "retain attribution", "carry terms forward" ] } }, { "type": "heading", "id": "share-reusable-outcome", "text": "5. Make the first reuse easy" }, { "type": "p", "text": "Give the next person a small entry point, a concise explanation and one runnable example. Link the full preservation copy, original source, terms and validation evidence. Keep earlier released artifacts immutable when the account changes. For a repository distribution, follow the versioned repository profile and record the actual published carrier identities." }, { "type": "p", "text": "For an ontology adaptation, document your application profile and any project-owned terms or mapping graph. Keep assertions and source evidence available behind convenience displays. For a 3D notebook, provide the attributed poster and complete explanation alongside optional rendering. A reader should be able to understand the result without a GPU and distinguish a visual demonstration from a measured or playable research claim." }, { "type": "example", "id": "cuntz-citation", "title": "Which Cuntz identifier belongs in a citation?", "concept": "Versioned citation separates the physical subject, the released research object and the explanation or derived artifact actually used.", "scenario": "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.", "steps": [ { "title": "Identify the release", "text": "Use version DOI 10.5281/zenodo.22151203 for the inspected dataset. Record the specific realization or observation, rather than citing only the project community." }, { "title": "Identify what was used", "text": "For the web preview, retain the derivative’s digest and transformation note. For the observation, identify the pipe, property, source cell and workbook realization." }, { "title": "Cite the explanation separately", "text": "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." } ], "takeaway": "A citation chain lets a reader recover both the evidence and the interpretation.", "boundary": "The dataset content version 0.5.0-rc.2, VAO format version 0.5.0 and website edition are separate version systems.", "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." } ], "visual": { "layout": "flow", "title": "Cite the artifact that supports your statement", "nodes": [ { "label": "Object release", "value": "Version DOI", "detail": "Identifies the published Cuntz package.", "icon": "book" }, { "label": "Exact realization", "value": "Digest & identifier", "detail": "Identifies the model bytes actually used.", "icon": "cube" }, { "label": "Explanation", "value": "Notebook edition", "detail": "Identifies the teaching text you consulted.", "icon": "quote" } ], "caption": "These citations refer to different artifacts; preserve the link among them.", "relations": [ "name the relevant member", "cite the explanatory account" ] }, "expanded": false }, { "type": "links", "items": [ { "label": "First VAO tutorial", "href": "/notebooks/vao/reuse/", "detail": "Repeat the known-good workspace-to-carrier workflow." }, { "label": "First ontology tutorial", "href": "/notebooks/ontologies/reuse/", "detail": "Repeat the positive/negative graph and query workflow." }, { "label": "Full conformance guide", "href": "/notebooks/standards/conformance/", "detail": "Read the normative layer boundaries and additional checks." }, { "label": "Understand fixed notebook editions", "href": "/notebooks/standards/versions/", "detail": "Cite a recoverable explanation as well as the object release." } ] } ] }, "figures": {} } }