OpenEPCIS Assessment and Test Vocabulary - Artefacts
How a Digital Product Passport states what was measured, tested or assessed about a product: the assessment that was carried out, the method and the standard that define it, the conditions and protocol settings it ran under, the results it produced, the criteria and thresholds a result is judged against, and the indicators (scores, classes, expected lifetimes) derived from those results. The model follows the assessment pattern of the CIRPASS-2 EU DPP ontologies (textile-assessment, textile-indicator): an assessment execution produces results; a result carries a measured value with its unit and names the performance parameter it observes; an indicator is derived from results and is never the result itself. Values with a unit are gs1:QuantitativeValue (UN/CEFACT Rec 20 unitCode), so they read the same way as every other quantity in a passport. The module sits below the DPP core: it imports only the GS1 Web Vocabulary, schema.org and CCCEV, and oec: (dpp-core) imports it. Sector modules add their own performance parameters, indicator kinds, test methods, standards and criteria as individuals of the classes here (eutex:AbrasionResistance a oea:PerformanceParameter, eutex:MartindaleAbrasionTest a oea:TestMethod), not new classes. EPCIS binding: an assessment carried out on an item is an ObjectEvent with action OBSERVE and bizStep inspecting. The event is the execution: eventTime, readPoint, bizLocation and the source party say when, where and by whom; the oea:Assessment object hangs at event level under oea:hasAssessment and carries method, conditions, settings and results. An equivalent compact form uses the EPCIS sensorElementList: sensorMetadata.dataProcessingMethod names the method, sensorMetadata.bizRules the standard, and each sensorReport carries one result with type set to the oea:PerformanceParameter IRI, value and uom. See docs/EPCIS_BINDING.md. EPCIS 2.0 Extension: This vocabulary is a first-class EPCIS 2.0 extension per Section 12.3. Declare it using: GS1-Extensions: oea=https://ref.openepcis.org/extensions/common/assessment/ References: - Regulation (EU) 2024/1781 (ESPR), Article 7 and Annex I (performance and information requirements) - ISO/IEC 17025:2017, General requirements for the competence of testing and calibration laboratories - CIRPASS-2 EU DPP ontologies, textile-assessment and textile-indicator modules - SEMICeu Core Criterion and Core Evidence Vocabulary (CCCEV) 2.1
https://ref.openepcis.org/extensions/common/assessment/Available Artefacts
| Artefact | Format | Media Type | Latest URL | Versioned URL |
|---|---|---|---|---|
| assessment-ontology.ttl | RDF/Turtle Ontology | text/turtle | /extensions/common/assessment/assessment-ontology.ttl | /extensions/common/assessment/0.15.0/assessment-ontology.ttl |
| assessment-context.jsonld | JSON-LD Context | application/ld+json | /extensions/common/assessment/assessment-context.jsonld | /extensions/common/assessment/0.15.0/assessment-context.jsonld |
| assessment-json-schema.json | JSON Schema | application/schema+json | /extensions/common/assessment/assessment-json-schema.json | /extensions/common/assessment/0.15.0/assessment-json-schema.json |
| assessment-shacl.ttl | SHACL Shapes | text/turtle | /extensions/common/assessment/assessment-shacl.ttl | /extensions/common/assessment/0.15.0/assessment-shacl.ttl |
| assessment.json | Generated JSON (for web apps) | application/json | /extensions/common/assessment/assessment.json | /extensions/common/assessment/0.15.0/assessment.json |
Content Negotiation
The extension namespace URI supports content negotiation. Use the Accept header to request different formats:
# Get Turtle format (ontology)
curl -H "Accept: text/turtle" https://ref.openepcis.org/extensions/common/assessment/
# Get JSON-LD context
curl -H "Accept: application/ld+json" https://ref.openepcis.org/extensions/common/assessment/
# Get JSON Schema
curl -H "Accept: application/schema+json" https://ref.openepcis.org/extensions/common/assessment/