Evidence Basis¶

Part I — Evidence basis¶

1. Scope, method and provenance¶

1.1 Source baseline¶

The authoritative baseline for this restructuring is:

• gs1-gdsn-holon-v1.31.0.md, version 1.31.0, dated 30 July 2026.

The baseline combined 29 numbered sections, five appendices and a source list. It recorded the progressive development of the architecture, including findings later corrected by real generated artefacts. This pack consolidates the final position while retaining the reasoning behind material changes.

1.2 Supplied and referenced artefacts¶

The source baseline reports direct inspection or use of the following artefacts:

The current conversation supplied the baseline Markdown file and, for this revision, the GDSN notification XML, the corresponding RDF instance graph, current GDSN/GPC ontology copies, portfolio narratives and Holon presentation listed above. Other historical implementation artefacts remain treated according to the evidence reported in the baseline unless separately inspected.

1.3 Evidence method¶

The original work used several evidence methods:

• direct parsing and counting of GDSN and GPC ontology artefacts;
• inspection of GPC hierarchy, Brick attributes and controlled values;
• inspection of generated SHACL shapes;
• execution of pySHACL against conforming and deliberately invalid instances;
• execution of rdflib and owlrl for representative entailment tests;
• execution of SPARQL CONSTRUCT rules and programmatic output checks;
• inspection of a real Web Vocabulary v1.16 source slice;
• execution and parsing of LOOM/BioPortal mappings;
• literature review of ontology mapping, SSSOM, SWRL, description logic and Graph-RAG;
• review of GS1 Digital Link resolver mechanisms;
• comparison of the evolving design with the independently implemented gs1-gdsn-holon tool.

1.4 Verification boundaries¶

Several limitations remain important:

• the K10X video narration and on-screen content were not transcribed directly;
• the full Web Vocabulary v1.16 source could not be fetched in one pass by the tool used in the source investigation, although later LOOM output covered the extracted full term set;
• the source baseline reports direct inspection of artefacts that are not all present in the current conversation;
• mapping outputs remain candidates until formal human review;
• illustrative product values are not claims about real commercial products;
• the Manchester Syntax listing was hand-checked but not formally parsed in the reported session;
• no production security, performance or resolver deployment was demonstrated.

1.5 Current-versus-historical conclusions¶

The following historical conclusions were superseded and are not used as current architecture positions:

2. Motivating use case and terminology evidence¶

2.1 K10X context¶

The initial investigation concerned a K10X explainer titled “Layer 1 — AI Data Interpretation”. The source baseline described K10X as a product-data and connected-packaging company founded by Aziz Shariff, with Alfonso Bravi identified as CTO and Karim Waljee as COO/AI Lead. It identified K10X as a GS1 Australia Associate Alliance Partner and described the proposition as auditing, enriching and structuring data from PIM, ERP, supplier feeds and spreadsheets for machine-readable shopping experiences.

The video itself was not transcribed in the source investigation because the available retrieval environment could not render and play the JavaScript-based YouTube page. The K10X interpretation was therefore reconstructed from the title, channel metadata, the company’s published product pages and public GS1 material. Statements about the precise narration or diagrams remain unverified.

The motivating logic was:

• product data originates in multiple internal and supplier sources;
• machine interpretation requires standardised, structured product facts;
• GS1 Web Vocabulary and schema.org provide an appropriate public representation layer;
• GS1 Digital Link and 2D barcodes provide a route from an identifier to digital resources;
• trusted personalisation depends on accurate underlying product facts, especially for allergens, claims and regulated information.

The source did not establish that K10X uses the exact Product Holon design defined here. The case is therefore treated as a motivating example, not proof of architecture adoption.

2.2 Web Vocabulary role¶

The source investigation positioned GS1 Web Vocabulary as a public, schema.org-aligned vocabulary whose terms are informed by existing GS1 standards. Its role is to expose supported product information in forms that web pages, search engines, product feeds and AI agents can interpret.

The architecture does not treat Web Vocabulary as a complete internal product model. Its bounded scope is a strength for public publication and a limitation for Brick-specific or deep GDSN semantics. The source baseline also noted public GS1 programme material describing GDSN modernisation and semantic modelling using Web Vocabulary, schema.org and JSON-LD. That contextual material supports convergence between source semantics and web publication rather than a competing ontology strategy, but it does not by itself define the Product Holon architecture.

The resulting pattern is:

construct and validate the Product Holon in source-derived GDSN/GPC semantics; publish an approved view in Web Vocabulary/schema.org semantics.

2.3 Evidence concerning the term “Product Holon”¶

The source baseline reviewed a set of citations offered in support of a “GS1 Product Holon” framework. It found that:

• only one cited source used “holon”, and it did so in a generic enterprise/supply-chain context rather than a GS1 standards context;
• other sources supported genuine GS1 capabilities such as GTIN, SSCC, GLN, EPCIS aggregation and context-based Digital Link resolution;
• the citations did not establish decentralised autonomous product nodes or a GS1-defined holon concept;
• the proposed Product Holon was therefore an external architectural analogy applied to GS1 assets.

The evidence supports use of the term only with an explicit proposal notice. It does not support presenting it as established GS1 terminology.

2.4 Standards-backed and proposed elements¶