References¶
Part XI — References and project artefacts¶
36. References¶
36.1 GS1, K10X and product-data sources¶
- K10X, company website: https://k10x.co/
- K10X, Connected Packaging: https://k10x.co/connected-packaging
- K10X, Digital Twin Platform: https://k10x.co/digital-twin-platform
- K10X, GS1 Australia Associate Alliance Partner listing: https://www.gs1au.org/partners/solution-providers/associate-alliance-partner/k10x
- GS1 Web Vocabulary: https://ref.gs1.org/voc/
- GS1 Web Vocabulary overview: https://www.gs1.org/gs1-web-vocabulary
- GS1 Web Vocabulary source repository: https://github.com/gs1/WebVoc
- GS1 Web Vocabulary v1.16 Turtle source: https://raw.githubusercontent.com/gs1/WebVoc/master/v1.16/gs1Voc.ttl
- GS1 Web Vocabulary v1.16 JSON-LD source: https://raw.githubusercontent.com/gs1/WebVoc/master/v1.16/gs1Voc.jsonld
- GS1 Web Vocabulary
allergenStatement: https://ref.gs1.org/voc/allergenStatement - GS1 Web Vocabulary
nutrientBasisQuantity: https://www.gs1.org/voc/nutrientBasisQuantity - GS1 Web Vocabulary
SharpnessOfCheeseCode-MILD: https://ref.gs1.org/voc/SharpnessOfCheeseCode-MILD - GS1 Web Vocabulary
NutritionalClaimTypeCode-FREE_FROM_GLUTEN: https://ref.gs1.org/voc/NutritionalClaimTypeCode-FREE_FROM_GLUTEN - GS1 Web Vocabulary
RegulationTypeCode: https://ref.gs1.org/voc/RegulationTypeCode - GS1 Web Vocabulary
PackagingMaterialTypeCode-COMPOSITE: https://ref.gs1.org/voc/PackagingMaterialTypeCode-COMPOSITE - schema.org blog, “GS1 Web Vocabulary: welcoming the first schema.org external extension”: https://blog.schema.org/2016/02/22/gs1-web-vocabulary-welcoming-the-first-schema-org-external-extension/
- GS1 Belgium & Luxembourg, “Web vocabulary for AI: from product information to reusable data”: https://www.gs1belu.org/en/web-vocabulary-ai-product-information-reusable-data
- GS1 Semantic Data Modelling Technical Bulletin: https://www.gs1.org/docs/architecture/GS1-Technical-Bulletin-SemanticDataModelling.pdf
- GS1 GDSN standards: https://www.gs1.org/standards/gdsn
- GS1 Global Data Model: https://www.gs1.org/services/gdsn/global-data-model
- GS1, How GPC works: https://www.gs1.org/standards/gpc/how-gpc-works
- GS1, GPC Bricks to GDM category mapping: https://www.gs1.org/docs/global-data-model/GPC_to_GDM_Mapping_230523.xlsx
- GS1 GDSN service overview: https://www.gs1.org/services/gdsn
- GS1-Conformant Resolver Standard: https://ref.gs1.org/standards/resolver/
- GS1 Navigator: https://navigator.gs1.org/
CatalogueItemNotification_ADD.xml— supplied GDSN Catalogue Item Notification used for the source-authority example in Section 30.4.GA slide narratives.docx— supplied Vision 2030 narrative source for the identifier/grammar/proof/truth-layer/connections framing.Beideman Excerpts from GA meeting.pptx— supplied portfolio and use-case narrative source.GS1_GDSN_Product_Holon_Architecture_Presentation_v1.1.0.pptx— supplied architecture visual; Phase 4 publication package source.- GS1 US, Product Field Definitions — GPC Brick and Attribute/Attribute Value conventions: https://www.help.gs1us.org/product-field-definitions
- GS1, Activate Quick Start Guide — worked Jam classification using Brick
10000217: https://www.gs1.org/docs/activate/Activate_Quickstart_Guide.pdf - GS1 España, archived GPC listing — Attribute
20000118and Attribute Value30000728(COMPOTE) under Brick10000217: https://www.eway.com.ar/descargas_mexico/GPC_Espanol.pdf
36.2 W3C and schema.org references¶
- SHACL Recommendation: https://www.w3.org/TR/shacl/
- JSON-LD 1.1 Recommendation: https://www.w3.org/TR/json-ld11/
- Verifiable Credentials Data Model v2.0 Recommendation: https://www.w3.org/TR/vc-data-model-2.0/
- Verifiable Credential Data Integrity 1.0 Recommendation: https://www.w3.org/TR/vc-data-integrity/
- Data Integrity ECDSA Cryptosuites v1.0 Recommendation: https://www.w3.org/TR/vc-di-ecdsa/
- Data Integrity EdDSA Cryptosuites v1.0 Recommendation: https://www.w3.org/TR/vc-di-eddsa/
- Controlled Identifiers v1.0 Recommendation: https://www.w3.org/TR/cid-1.0/
- Bitstring Status List v1.0 Recommendation: https://www.w3.org/TR/vc-bitstring-status-list/
- Securing Verifiable Credentials using JOSE and COSE Recommendation: https://www.w3.org/TR/vc-jose-cose/
- Verifiable Credentials Data Model v2.1 Working Draft: https://www.w3.org/TR/vc-data-model-2.1/
- Verifiable Credential Data Integrity 1.1 Working Draft: https://www.w3.org/TR/vc-data-integrity-1.1/
- OWL 2 overview: https://www.w3.org/TR/owl2-overview/
- OWL 2 equivalent object properties: https://www.w3.org/TR/owl2-syntax/#Equivalent_Object_Properties
- OWL 2 Manchester Syntax: https://www.w3.org/TR/owl2-manchester-syntax/
- SPARQL 1.1 Query Language: https://www.w3.org/TR/sparql11-query/
- SWRL W3C Member Submission: https://www.w3.org/submissions/SWRL/
- SKOS mapping relations: https://www.w3.org/TR/skos-reference/#mapping
- schema.org
Product: https://schema.org/Product - schema.org
gtin: https://schema.org/gtin - schema.org
NutritionInformation: https://schema.org/NutritionInformation - schema.org
additionalProperty: https://schema.org/additionalProperty - schema.org
PropertyValue: https://schema.org/PropertyValue - schema.org
Offer: https://schema.org/Offer - schema.org
AggregateOffer: https://schema.org/AggregateOffer
36.3 Mapping standards and research¶
- SSSOM, A Simple Standard for Sharing Ontological Mappings: https://mapping-commons.github.io/sssom/dev/
- SSSOM mapping justifications and SEMAPV: https://mapping-commons.github.io/sssom/dev/mapping-justifications/
- SSSOM specification model: https://mapping-commons.github.io/sssom/dev/spec-model/
- OntoPortal Alliance: https://ontoportal.org/
- Ghazvinian, Noy and Musen, “Creating Mappings For Ontologies in Biomedicine: Simple Methods Work”: https://pmc.ncbi.nlm.nih.gov/articles/PMC2815425/
- Laadhar, Abrahão and Jonquet, “Investigating One Million XRefs in Thirty Ontologies from the OBO World”: https://ceur-ws.org/Vol-2807/paperG.pdf
- Schmidt-Schauß, “Subsumption in KL-ONE is Undecidable”: https://www.semanticscholar.org/paper/Subsumption-in-KL-ONE-is-Undecidable-Schmidt-Schau%C3%9F/3179aa519f0c76e2e724c3aa4ea3d1de57fb1f99
- Sadowski and Chudziak, “Structured Decomposition for LLM Reasoning: Cross-Domain Validation and Semantic Web Integration”: https://arxiv.org/html/2601.01609v1
- Protégé SWRL API FAQ, including DL-safety discussion: https://github.com/protegeproject/swrlapi/wiki/SWRLLanguageFAQ
36.4 Graph retrieval and AI references¶
- Microsoft Research, Project GraphRAG: https://www.microsoft.com/en-us/research/project/graphrag/
- Microsoft Research, “From Local to Global: A Graph RAG Approach to Query-Focused Summarization”: https://www.microsoft.com/en-us/research/publication/from-local-to-global-a-graph-rag-approach-to-query-focused-summarization/
36.5 Reference implementation tools¶
uml2semantics-python: https://github.com/chris-day/uml2semantics-python- Henriette Harmse, UML class diagram to OWL and SROIQ reference: https://henrietteharmse.com/uml-vs-owl/uml-class-diagram-to-owl-and-sroiq-reference/
- RDFLib documentation: https://rdflib.readthedocs.io/
- OWL-RL for RDFLib: https://owl-rl.readthedocs.io/
- BioPortal mappings / LOOM implementation: https://github.com/ncbo/bioportal_mappings
- jsDelivr package API used to inspect the Web Vocabulary repository listing: https://data.jsdelivr.com/v1/packages/gh/gs1/WebVoc@master
36.6 Project artefacts recorded in the source baseline¶
gs1-gdsn-holon-v1.31.0.md— source research and evidence baseline.gdsn.ttl— source-derived GDSN ontology.gpc.ttl— GPC ontology.GDSN_TSV_Transformer_README_v0.1.0.md— Navigator JSON to TSV documentation.GDSN-TSV-Mapping-v0.1.0.md— TSV mapping decisions.gpc-brick-10000030-with-gdsn.shacl.ttl— Cheese (Frozen) generated shape.gpc-brick-10001198-with-gdsn.shacl.ttl— Smartphones generated shape.gpc-brick-10000159-with-gdsn.shacl.ttl— Beer generated shape.gpc-brick-10000043-with-gdsn.shacl.ttl— Sugar/Sugar Substitutes generated shape.gs1_mappings_001.ttl— 474 directional mapping records.gs1_terms.txt— extracted mapping terms.gs1_sortedUnique.txt— deduplicated mapping terms.holon_webvoc_alignment_test.py— representative entailment and projection test.verify_brick10000030_route3.py— Route 3 validation against the real Cheese shape.gs1-holon-bridge.omn— Manchester Syntax bridge example.holon-webvoc-construct-rules.sparql— representative Route 2 and Route 3 queries.CatalogueItemNotification_ADD.xml— concrete source authority and product-instance evidence for the HTML Semantic Proof.gdsn(1).ttl— current supplied GDSN ontology copy inspected for exact namespaces, properties, classes and controlled code values.gpc(1).ttl— current supplied GPC ontology copy inspected for namespace and Brick identity.kato-instances(1).ttl— RDF graph corresponding to the supplied GDSN message, inspected for the native Product Holon graph pattern.GA slide narratives.docx— portfolio narrative evidence for grammar, proof, trust layer and Digital Link connections.Beideman Excerpts from GA meeting.pptx— portfolio and use-case narrative evidence.GS1_GDSN_Product_Holon_Architecture_Presentation_v1.1.0.pptx— architecture presentation evidence, including the Phase 4 publication package.
37. Final evidence assessment¶
The evidence is sufficient to support a credible working architecture and a constrained reference implementation. It demonstrates that bounded Product Holons, generated Brick-scoped validation and deterministic semantic projection are technically feasible. It also demonstrates that the mapping problem cannot be solved safely by label matching alone and that the current reference GDSN shape requires modular expansion.
The evidence is not sufficient to claim formal GS1 approval, complete semantic coverage, production-scale performance, production security, an approved GDSN/GPC-to-Web Vocabulary crosswalk, an approved GS1 Product Statement Credential profile or an operational issuer-authority trust framework. Those remain governance and implementation work items identified in the core architecture roadmap.
The HTML and credential examples demonstrate the required structure and verification boundary but contain placeholder namespaces, digests, status records, verification methods and proof values. They shall not be presented as cryptographically valid product credentials until generated and independently verified by an implementation using approved keys and policies.