@tracepass/dpp-epcis 0.1.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,65 @@
+<div align="center">
+<a href="https://www.tracepass.eu"><img src="https://www.tracepass.eu/tracepass-logo.svg" alt="TracePass" height="72"></a>
+
+# @tracepass/dpp-epcis
+
+**Map Digital Product Passport events to GS1 EPCIS 2.0, with a CBV vocabulary extended for steel. No third-party runtime dependencies.**
+
+[![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](../../LICENSE)
+[![Dependencies](https://img.shields.io/badge/third--party%20runtime%20deps-0-success)](#)
+
+Part of [**tracepass-open**](https://github.com/malinoto/tracepass-open) · Maintained by [TracePass](https://www.tracepass.eu)
+</div>
+
+---
+
+Build conformant **GS1 EPCIS 2.0** events from passport data — commissioning, service,
+ownership transfer, and supply-chain transformation — as pure functions over plain
+objects.
+
+```bash
+npm install @tracepass/dpp-epcis
+```
+
+```ts
+import { buildCommissioningEvent, validateEpcisDocument, EPCIS_JSONLD_CONTEXT } from "@tracepass/dpp-epcis";
+
+const event = buildCommissioningEvent(
+  new Date("2026-01-01T00:00:00Z"),       // publishedAt
+  "urn:epc:id:sgtin:0952012.345678.SN1",  // product EPC
+  "passport-1",
+  "5012345678900",                         // manufacturer GLN
+);
+
+const doc = {
+  "@context": EPCIS_JSONLD_CONTEXT,
+  type: "EPCISDocument",
+  schemaVersion: "2.0",
+  creationDate: new Date().toISOString(),
+  epcisBody: { eventList: [event] },
+};
+
+validateEpcisDocument(doc).valid;  // true
+```
+
+The event carries a CBV business step (`https://ref.gs1.org/cbv/BizStep-commissioning`)
+and a GS1 location reference (`https://id.gs1.org/414/5012345678900`).
+
+## Extending CBV for steel
+
+Core Business Vocabulary 2.0 has no business steps for several steel production stages.
+Rather than misuse an unrelated step, this package coins them under a vendor namespace —
+the extension pattern GS1 sanctions for exactly this case:
+
+```
+https://tracepass.eu/voc/cbv/bizstep/smelting
+https://tracepass.eu/voc/cbv/bizstep/casting
+https://tracepass.eu/voc/cbv/bizstep/rolling
+```
+
+Standard steps are used wherever one exists. `validateEpcisDocument` is a structural
+check — envelope, event type, event time — not a full JSON Schema validation.
+
+## License
+
+[Apache-2.0](../../LICENSE)

package/dist/cbv.d.ts

@@ -0,0 +1,131 @@
+/**
+ * CBV (Core Business Vocabulary) mapping for TracePass EPCIS events.
+ *
+ * EPCIS defines the *shape* of an event; CBV defines the controlled
+ * vocabulary that fills the `bizStep` and `disposition` slots. CBV 2.0
+ * ships a FIXED list of bizStep values (commissioning, shipping,
+ * receiving, inspecting, repairing, …). Many real production steps —
+ * smelting, rolling, finishing — are simply not in that list.
+ *
+ * Decision [Q2] from the 2026-05-22 EPCIS review: for production steps
+ * absent from CBV we coin TracePass-owned vocabulary URIs under
+ * `https://tracepass.eu/voc/cbv/bizstep/<step>`. EPCIS 2.0 explicitly
+ * permits bizStep values outside standard CBV provided they are URIs;
+ * this is the GS1-sanctioned industry-extension pattern. We do NOT use
+ * the weaker "everything is `commissioning` + a free-text annotation"
+ * hack — that buries the meaningful detail in a non-standard field.
+ *
+ * This module is the single source of truth for those mappings. It is
+ * pure data + pure functions — no IO, unit-tested in tests/epcis/cbv.test.ts.
+ *
+ * What we own and must maintain: the `TRACEPASS_BIZSTEP` table below is
+ * a small steel/metals-oriented vocabulary. When a new category needs
+ * production steps, extend this table — and keep the published
+ * vocabulary document (served from the marketing/voc route) in sync.
+ */
+import type { ServiceEventType } from "@tracepass/dpp-types";
+/**
+ * The subset of standard CBV bizSteps TracePass actually emits. Kept
+ * as a typed record so a typo surfaces at compile time, not as a
+ * silently-wrong URI in a customer's EPCIS feed.
+ */
+export declare const CBV_BIZSTEP_URI: {
+    readonly commissioning: "https://ref.gs1.org/cbv/BizStep-commissioning";
+    readonly shipping: "https://ref.gs1.org/cbv/BizStep-shipping";
+    readonly receiving: "https://ref.gs1.org/cbv/BizStep-receiving";
+    readonly inspecting: "https://ref.gs1.org/cbv/BizStep-inspecting";
+    readonly repairing: "https://ref.gs1.org/cbv/BizStep-repairing";
+    readonly decommissioning: "https://ref.gs1.org/cbv/BizStep-decommissioning";
+    readonly storing: "https://ref.gs1.org/cbv/BizStep-storing";
+    readonly shipping_returned: "https://ref.gs1.org/cbv/BizStep-shipping";
+};
+/**
+ * The subset of standard CBV dispositions TracePass emits.
+ */
+export declare const CBV_DISPOSITION_URI: {
+    readonly active: "https://ref.gs1.org/cbv/Disp-active";
+    readonly in_progress: "https://ref.gs1.org/cbv/Disp-in_progress";
+    readonly in_transit: "https://ref.gs1.org/cbv/Disp-in_transit";
+    readonly in_repair: "https://ref.gs1.org/cbv/Disp-in_progress";
+    readonly recalled: "https://ref.gs1.org/cbv/Disp-recalled";
+    readonly destroyed: "https://ref.gs1.org/cbv/Disp-destroyed";
+    readonly returned: "https://ref.gs1.org/cbv/Disp-returned";
+};
+/**
+ * TracePass-coined bizStep URIs for production / lifecycle steps that
+ * standard CBV does not define. Each key is a normalised step token;
+ * each value is a resolvable `tracepass:` vocabulary URI.
+ *
+ * Steel/metals-oriented for the lead vertical. Extend (don't replace)
+ * when other categories need their own production steps — and update
+ * the published vocabulary doc in the same change.
+ */
+export declare const TRACEPASS_BIZSTEP_URI: {
+    readonly mining: "https://tracepass.eu/voc/cbv/bizstep/mining";
+    readonly smelting: "https://tracepass.eu/voc/cbv/bizstep/smelting";
+    readonly casting: "https://tracepass.eu/voc/cbv/bizstep/casting";
+    readonly rolling: "https://tracepass.eu/voc/cbv/bizstep/rolling";
+    readonly forging: "https://tracepass.eu/voc/cbv/bizstep/forging";
+    readonly finishing: "https://tracepass.eu/voc/cbv/bizstep/finishing";
+    readonly coating: "https://tracepass.eu/voc/cbv/bizstep/coating";
+    readonly heat_treatment: "https://tracepass.eu/voc/cbv/bizstep/heat-treatment";
+    readonly machining: "https://tracepass.eu/voc/cbv/bizstep/machining";
+    readonly assembly: "https://tracepass.eu/voc/cbv/bizstep/assembly";
+    readonly recycling: "https://tracepass.eu/voc/cbv/bizstep/recycling";
+};
+/**
+ * Result of mapping a free-text event type onto CBV. `standard` flags
+ * whether the bizStep is a ratified CBV value (true) or a
+ * TracePass-coined extension URI (false) — the EPCIS document builder
+ * uses this to decide nothing today, but it lets the conformance
+ * self-test report "N standard / M extension bizSteps".
+ */
+export interface BizStepMapping {
+    /** The bizStep URI to put on the event. Always a URI. */
+    bizStep: string;
+    /** True when `bizStep` is a ratified CBV value; false when it is a
+     *  TracePass extension URI. */
+    standard: boolean;
+}
+/**
+ * Normalise a free-text event-type string into a lookup token:
+ * lower-cased, trimmed, internal whitespace + hyphens collapsed to a
+ * single underscore. "Heat Treatment" / "heat-treatment" → "heat_treatment".
+ */
+export declare function normalizeStepToken(raw: string): string;
+/**
+ * Map a free-text `supplyChainEvents[].eventType` string (the steel
+ * template's field 77 — "smelting", "rolling", "shipping", …) to a
+ * bizStep URI.
+ *
+ * Resolution order:
+ *   1. Standard CBV bizStep whose name matches the token exactly.
+ *   2. TracePass-coined production-step URI.
+ *   3. Fallback: a TracePass extension URI minted from the token
+ *      itself — an unknown step still produces a *valid, resolvable*
+ *      URI rather than dropping the bizStep. The conformance test
+ *      surfaces these so the vocabulary table can be extended.
+ *
+ * Never throws — an EPCIS document builder must not fail on an
+ * unexpected production-step string.
+ */
+export declare function mapEventTypeToBizStep(eventType: string): BizStepMapping;
+/**
+ * Map a `ServiceEvent.type` enum value to a (bizStep, disposition)
+ * pair. ServiceEvents become EPCIS ObjectEvents in the Layer A export.
+ * Unlike production steps these map cleanly onto standard CBV — repair
+ * and inspection are first-class CBV business steps.
+ */
+export declare function mapServiceEventType(type: ServiceEventType): {
+    bizStep: string;
+    disposition: string;
+    standard: boolean;
+};
+/**
+ * Disposition for an `OwnershipTransfer`. Ownership changes become
+ * ObjectEvents; "returned" maps to the CBV `returned` disposition,
+ * everything else (sale, resale, donation) is a plain ownership
+ * change with the object still `active`.
+ */
+export declare function mapOwnershipReasonDisposition(reason: string): string;
+//# sourceMappingURL=cbv.d.ts.map

package/dist/cbv.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"cbv.d.ts","sourceRoot":"","sources":["../src/cbv.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;GAwBG;AAEH,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,sBAAsB,CAAC;AAsB7D;;;;GAIG;AACH,eAAO,MAAM,eAAe;;;;;;;;;CASlB,CAAC;AAEX;;GAEG;AACH,eAAO,MAAM,mBAAmB;;;;;;;;CAQtB,CAAC;AAEX;;;;;;;;GAQG;AACH,eAAO,MAAM,qBAAqB;;;;;;;;;;;;CAYxB,CAAC;AAEX;;;;;;GAMG;AACH,MAAM,WAAW,cAAc;IAC7B,yDAAyD;IACzD,OAAO,EAAE,MAAM,CAAC;IAChB;mCAC+B;IAC/B,QAAQ,EAAE,OAAO,CAAC;CACnB;AAED;;;;GAIG;AACH,wBAAgB,kBAAkB,CAAC,GAAG,EAAE,MAAM,GAAG,MAAM,CAMtD;AAED;;;;;;;;;;;;;;;GAeG;AACH,wBAAgB,qBAAqB,CAAC,SAAS,EAAE,MAAM,GAAG,cAAc,CAqBvE;AAED;;;;;GAKG;AACH,wBAAgB,mBAAmB,CAAC,IAAI,EAAE,gBAAgB,GAAG;IAC3D,OAAO,EAAE,MAAM,CAAC;IAChB,WAAW,EAAE,MAAM,CAAC;IACpB,QAAQ,EAAE,OAAO,CAAC;CACnB,CAwCA;AAED;;;;;GAKG;AACH,wBAAgB,6BAA6B,CAAC,MAAM,EAAE,MAAM,GAAG,MAAM,CAIpE"}

package/dist/cbv.js

@@ -0,0 +1,201 @@
+/**
+ * CBV (Core Business Vocabulary) mapping for TracePass EPCIS events.
+ *
+ * EPCIS defines the *shape* of an event; CBV defines the controlled
+ * vocabulary that fills the `bizStep` and `disposition` slots. CBV 2.0
+ * ships a FIXED list of bizStep values (commissioning, shipping,
+ * receiving, inspecting, repairing, …). Many real production steps —
+ * smelting, rolling, finishing — are simply not in that list.
+ *
+ * Decision [Q2] from the 2026-05-22 EPCIS review: for production steps
+ * absent from CBV we coin TracePass-owned vocabulary URIs under
+ * `https://tracepass.eu/voc/cbv/bizstep/<step>`. EPCIS 2.0 explicitly
+ * permits bizStep values outside standard CBV provided they are URIs;
+ * this is the GS1-sanctioned industry-extension pattern. We do NOT use
+ * the weaker "everything is `commissioning` + a free-text annotation"
+ * hack — that buries the meaningful detail in a non-standard field.
+ *
+ * This module is the single source of truth for those mappings. It is
+ * pure data + pure functions — no IO, unit-tested in tests/epcis/cbv.test.ts.
+ *
+ * What we own and must maintain: the `TRACEPASS_BIZSTEP` table below is
+ * a small steel/metals-oriented vocabulary. When a new category needs
+ * production steps, extend this table — and keep the published
+ * vocabulary document (served from the marketing/voc route) in sync.
+ */
+import { TRACEPASS_VOC_BASE } from "./context.js";
+/**
+ * Standard CBV 2.0 bizStep URI prefix. Values under this prefix are
+ * the official, GS1-ratified business steps — a strict EPCIS consumer
+ * recognises them without dereferencing our vocabulary.
+ */
+const CBV_BIZSTEP = "https://ref.gs1.org/cbv/BizStep-";
+/**
+ * Standard CBV 2.0 disposition URI prefix.
+ */
+const CBV_DISP = "https://ref.gs1.org/cbv/Disp-";
+/**
+ * TracePass-owned bizStep prefix for production steps CBV doesn't
+ * cover. Resolvable — the vocabulary document published at
+ * `<TRACEPASS_VOC_BASE>cbv/bizstep` describes each term.
+ */
+const TP_BIZSTEP = `${TRACEPASS_VOC_BASE}cbv/bizstep/`;
+/**
+ * The subset of standard CBV bizSteps TracePass actually emits. Kept
+ * as a typed record so a typo surfaces at compile time, not as a
+ * silently-wrong URI in a customer's EPCIS feed.
+ */
+export const CBV_BIZSTEP_URI = {
+    commissioning: `${CBV_BIZSTEP}commissioning`,
+    shipping: `${CBV_BIZSTEP}shipping`,
+    receiving: `${CBV_BIZSTEP}receiving`,
+    inspecting: `${CBV_BIZSTEP}inspecting`,
+    repairing: `${CBV_BIZSTEP}repairing`,
+    decommissioning: `${CBV_BIZSTEP}decommissioning`,
+    storing: `${CBV_BIZSTEP}storing`,
+    shipping_returned: `${CBV_BIZSTEP}shipping`,
+};
+/**
+ * The subset of standard CBV dispositions TracePass emits.
+ */
+export const CBV_DISPOSITION_URI = {
+    active: `${CBV_DISP}active`,
+    in_progress: `${CBV_DISP}in_progress`,
+    in_transit: `${CBV_DISP}in_transit`,
+    in_repair: `${CBV_DISP}in_progress`,
+    recalled: `${CBV_DISP}recalled`,
+    destroyed: `${CBV_DISP}destroyed`,
+    returned: `${CBV_DISP}returned`,
+};
+/**
+ * TracePass-coined bizStep URIs for production / lifecycle steps that
+ * standard CBV does not define. Each key is a normalised step token;
+ * each value is a resolvable `tracepass:` vocabulary URI.
+ *
+ * Steel/metals-oriented for the lead vertical. Extend (don't replace)
+ * when other categories need their own production steps — and update
+ * the published vocabulary doc in the same change.
+ */
+export const TRACEPASS_BIZSTEP_URI = {
+    mining: `${TP_BIZSTEP}mining`,
+    smelting: `${TP_BIZSTEP}smelting`,
+    casting: `${TP_BIZSTEP}casting`,
+    rolling: `${TP_BIZSTEP}rolling`,
+    forging: `${TP_BIZSTEP}forging`,
+    finishing: `${TP_BIZSTEP}finishing`,
+    coating: `${TP_BIZSTEP}coating`,
+    heat_treatment: `${TP_BIZSTEP}heat-treatment`,
+    machining: `${TP_BIZSTEP}machining`,
+    assembly: `${TP_BIZSTEP}assembly`,
+    recycling: `${TP_BIZSTEP}recycling`,
+};
+/**
+ * Normalise a free-text event-type string into a lookup token:
+ * lower-cased, trimmed, internal whitespace + hyphens collapsed to a
+ * single underscore. "Heat Treatment" / "heat-treatment" → "heat_treatment".
+ */
+export function normalizeStepToken(raw) {
+    return raw
+        .trim()
+        .toLowerCase()
+        .replace(/[\s-]+/g, "_")
+        .replace(/[^a-z0-9_]/g, "");
+}
+/**
+ * Map a free-text `supplyChainEvents[].eventType` string (the steel
+ * template's field 77 — "smelting", "rolling", "shipping", …) to a
+ * bizStep URI.
+ *
+ * Resolution order:
+ *   1. Standard CBV bizStep whose name matches the token exactly.
+ *   2. TracePass-coined production-step URI.
+ *   3. Fallback: a TracePass extension URI minted from the token
+ *      itself — an unknown step still produces a *valid, resolvable*
+ *      URI rather than dropping the bizStep. The conformance test
+ *      surfaces these so the vocabulary table can be extended.
+ *
+ * Never throws — an EPCIS document builder must not fail on an
+ * unexpected production-step string.
+ */
+export function mapEventTypeToBizStep(eventType) {
+    const token = normalizeStepToken(eventType);
+    if (token in CBV_BIZSTEP_URI) {
+        return {
+            bizStep: CBV_BIZSTEP_URI[token],
+            standard: true,
+        };
+    }
+    if (token in TRACEPASS_BIZSTEP_URI) {
+        return {
+            bizStep: TRACEPASS_BIZSTEP_URI[token],
+            standard: false,
+        };
+    }
+    // Unknown step — mint a stable extension URI from the token so the
+    // event is still valid EPCIS. token is already URI-safe.
+    return {
+        bizStep: `${TP_BIZSTEP}${token || "unspecified"}`,
+        standard: false,
+    };
+}
+/**
+ * Map a `ServiceEvent.type` enum value to a (bizStep, disposition)
+ * pair. ServiceEvents become EPCIS ObjectEvents in the Layer A export.
+ * Unlike production steps these map cleanly onto standard CBV — repair
+ * and inspection are first-class CBV business steps.
+ */
+export function mapServiceEventType(type) {
+    switch (type) {
+        case "repair":
+        case "replacement":
+            return {
+                bizStep: CBV_BIZSTEP_URI.repairing,
+                disposition: CBV_DISPOSITION_URI.in_repair,
+                standard: true,
+            };
+        case "warranty_claim":
+            return {
+                bizStep: CBV_BIZSTEP_URI.repairing,
+                disposition: CBV_DISPOSITION_URI.active,
+                standard: true,
+            };
+        case "maintenance":
+        case "inspection":
+            return {
+                bizStep: CBV_BIZSTEP_URI.inspecting,
+                disposition: CBV_DISPOSITION_URI.active,
+                standard: true,
+            };
+        case "recall":
+            return {
+                bizStep: CBV_BIZSTEP_URI.inspecting,
+                disposition: CBV_DISPOSITION_URI.recalled,
+                standard: true,
+            };
+        default: {
+            // Exhaustiveness guard — a new ServiceEventType added to the
+            // union without a mapping here is a compile error on this line.
+            const _exhaustive = type;
+            void _exhaustive;
+            return {
+                bizStep: CBV_BIZSTEP_URI.inspecting,
+                disposition: CBV_DISPOSITION_URI.active,
+                standard: true,
+            };
+        }
+    }
+}
+/**
+ * Disposition for an `OwnershipTransfer`. Ownership changes become
+ * ObjectEvents; "returned" maps to the CBV `returned` disposition,
+ * everything else (sale, resale, donation) is a plain ownership
+ * change with the object still `active`.
+ */
+export function mapOwnershipReasonDisposition(reason) {
+    if (reason === "return")
+        return CBV_DISPOSITION_URI.returned;
+    if (reason === "recycling")
+        return CBV_DISPOSITION_URI.in_progress;
+    return CBV_DISPOSITION_URI.active;
+}
+//# sourceMappingURL=cbv.js.map

package/dist/cbv.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"cbv.js","sourceRoot":"","sources":["../src/cbv.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;GAwBG;AAGH,OAAO,EAAE,kBAAkB,EAAE,MAAM,cAAc,CAAC;AAElD;;;;GAIG;AACH,MAAM,WAAW,GAAG,kCAAkC,CAAC;AAEvD;;GAEG;AACH,MAAM,QAAQ,GAAG,+BAA+B,CAAC;AAEjD;;;;GAIG;AACH,MAAM,UAAU,GAAG,GAAG,kBAAkB,cAAc,CAAC;AAEvD;;;;GAIG;AACH,MAAM,CAAC,MAAM,eAAe,GAAG;IAC7B,aAAa,EAAE,GAAG,WAAW,eAAe;IAC5C,QAAQ,EAAE,GAAG,WAAW,UAAU;IAClC,SAAS,EAAE,GAAG,WAAW,WAAW;IACpC,UAAU,EAAE,GAAG,WAAW,YAAY;IACtC,SAAS,EAAE,GAAG,WAAW,WAAW;IACpC,eAAe,EAAE,GAAG,WAAW,iBAAiB;IAChD,OAAO,EAAE,GAAG,WAAW,SAAS;IAChC,iBAAiB,EAAE,GAAG,WAAW,UAAU;CACnC,CAAC;AAEX;;GAEG;AACH,MAAM,CAAC,MAAM,mBAAmB,GAAG;IACjC,MAAM,EAAE,GAAG,QAAQ,QAAQ;IAC3B,WAAW,EAAE,GAAG,QAAQ,aAAa;IACrC,UAAU,EAAE,GAAG,QAAQ,YAAY;IACnC,SAAS,EAAE,GAAG,QAAQ,aAAa;IACnC,QAAQ,EAAE,GAAG,QAAQ,UAAU;IAC/B,SAAS,EAAE,GAAG,QAAQ,WAAW;IACjC,QAAQ,EAAE,GAAG,QAAQ,UAAU;CACvB,CAAC;AAEX;;;;;;;;GAQG;AACH,MAAM,CAAC,MAAM,qBAAqB,GAAG;IACnC,MAAM,EAAE,GAAG,UAAU,QAAQ;IAC7B,QAAQ,EAAE,GAAG,UAAU,UAAU;IACjC,OAAO,EAAE,GAAG,UAAU,SAAS;IAC/B,OAAO,EAAE,GAAG,UAAU,SAAS;IAC/B,OAAO,EAAE,GAAG,UAAU,SAAS;IAC/B,SAAS,EAAE,GAAG,UAAU,WAAW;IACnC,OAAO,EAAE,GAAG,UAAU,SAAS;IAC/B,cAAc,EAAE,GAAG,UAAU,gBAAgB;IAC7C,SAAS,EAAE,GAAG,UAAU,WAAW;IACnC,QAAQ,EAAE,GAAG,UAAU,UAAU;IACjC,SAAS,EAAE,GAAG,UAAU,WAAW;CAC3B,CAAC;AAiBX;;;;GAIG;AACH,MAAM,UAAU,kBAAkB,CAAC,GAAW;IAC5C,OAAO,GAAG;SACP,IAAI,EAAE;SACN,WAAW,EAAE;SACb,OAAO,CAAC,SAAS,EAAE,GAAG,CAAC;SACvB,OAAO,CAAC,aAAa,EAAE,EAAE,CAAC,CAAC;AAChC,CAAC;AAED;;;;;;;;;;;;;;;GAeG;AACH,MAAM,UAAU,qBAAqB,CAAC,SAAiB;IACrD,MAAM,KAAK,GAAG,kBAAkB,CAAC,SAAS,CAAC,CAAC;IAE5C,IAAI,KAAK,IAAI,eAAe,EAAE,CAAC;QAC7B,OAAO;YACL,OAAO,EAAE,eAAe,CAAC,KAAqC,CAAC;YAC/D,QAAQ,EAAE,IAAI;SACf,CAAC;IACJ,CAAC;IACD,IAAI,KAAK,IAAI,qBAAqB,EAAE,CAAC;QACnC,OAAO;YACL,OAAO,EAAE,qBAAqB,CAAC,KAA2C,CAAC;YAC3E,QAAQ,EAAE,KAAK;SAChB,CAAC;IACJ,CAAC;IACD,mEAAmE;IACnE,yDAAyD;IACzD,OAAO;QACL,OAAO,EAAE,GAAG,UAAU,GAAG,KAAK,IAAI,aAAa,EAAE;QACjD,QAAQ,EAAE,KAAK;KAChB,CAAC;AACJ,CAAC;AAED;;;;;GAKG;AACH,MAAM,UAAU,mBAAmB,CAAC,IAAsB;IAKxD,QAAQ,IAAI,EAAE,CAAC;QACb,KAAK,QAAQ,CAAC;QACd,KAAK,aAAa;YAChB,OAAO;gBACL,OAAO,EAAE,eAAe,CAAC,SAAS;gBAClC,WAAW,EAAE,mBAAmB,CAAC,SAAS;gBAC1C,QAAQ,EAAE,IAAI;aACf,CAAC;QACJ,KAAK,gBAAgB;YACnB,OAAO;gBACL,OAAO,EAAE,eAAe,CAAC,SAAS;gBAClC,WAAW,EAAE,mBAAmB,CAAC,MAAM;gBACvC,QAAQ,EAAE,IAAI;aACf,CAAC;QACJ,KAAK,aAAa,CAAC;QACnB,KAAK,YAAY;YACf,OAAO;gBACL,OAAO,EAAE,eAAe,CAAC,UAAU;gBACnC,WAAW,EAAE,mBAAmB,CAAC,MAAM;gBACvC,QAAQ,EAAE,IAAI;aACf,CAAC;QACJ,KAAK,QAAQ;YACX,OAAO;gBACL,OAAO,EAAE,eAAe,CAAC,UAAU;gBACnC,WAAW,EAAE,mBAAmB,CAAC,QAAQ;gBACzC,QAAQ,EAAE,IAAI;aACf,CAAC;QACJ,OAAO,CAAC,CAAC,CAAC;YACR,6DAA6D;YAC7D,gEAAgE;YAChE,MAAM,WAAW,GAAU,IAAI,CAAC;YAChC,KAAK,WAAW,CAAC;YACjB,OAAO;gBACL,OAAO,EAAE,eAAe,CAAC,UAAU;gBACnC,WAAW,EAAE,mBAAmB,CAAC,MAAM;gBACvC,QAAQ,EAAE,IAAI;aACf,CAAC;QACJ,CAAC;IACH,CAAC;AACH,CAAC;AAED;;;;;GAKG;AACH,MAAM,UAAU,6BAA6B,CAAC,MAAc;IAC1D,IAAI,MAAM,KAAK,QAAQ;QAAE,OAAO,mBAAmB,CAAC,QAAQ,CAAC;IAC7D,IAAI,MAAM,KAAK,WAAW;QAAE,OAAO,mBAAmB,CAAC,WAAW,CAAC;IACnE,OAAO,mBAAmB,CAAC,MAAM,CAAC;AACpC,CAAC"}

package/dist/context.d.ts

@@ -0,0 +1,55 @@
+/**
+ * EPCIS 2.0 JSON-LD @context for TracePass-emitted EPCIS documents.
+ *
+ * An EPCIS 2.0 document is JSON-LD — the same linked-data family as the
+ * schema.org JSON-LD the public passport viewer already emits. The
+ * @context tells a consumer which vocabularies the document's terms
+ * come from.
+ *
+ * Four vocabularies compose here:
+ *   1. The GS1-published EPCIS 2.0 context — the canonical source of
+ *      `EPCISDocument`, `ObjectEvent`, `eventTime`, `bizStep`, etc.
+ *      GS1 hosts this at a stable URL; consumers dereference it.
+ *   2. The GS1 CBV terms — Core Business Vocabulary (bizSteps,
+ *      dispositions). Carried inside the EPCIS context for 2.0.
+ *   3. `cbv:` alias — so CBV-standard bizStep/disposition values that
+ *      DO exist in the standard vocabulary are written with the
+ *      official `cbv:` prefix.
+ *   4. `tracepass:` alias — for the terms that are genuinely ours:
+ *      the custom bizStep URIs we coin for production steps absent
+ *      from CBV (smelting, rolling, …), and any TracePass-specific
+ *      annotation we attach to an event.
+ *
+ * Design call (per the 2026-05-22 EPCIS review, decision [Q2]):
+ * production steps that CBV's fixed bizStep list doesn't cover get
+ * TracePass-owned vocabulary URIs under `https://tracepass.eu/cbv/`.
+ * This is the GS1-sanctioned industry-extension pattern — a valid
+ * EPCIS document MAY use bizStep values outside the standard CBV as
+ * long as they are URIs. The `tracepass:` alias keeps those URIs
+ * compact in the serialized JSON.
+ */
+/**
+ * The GS1-hosted EPCIS 2.0 JSON-LD context URL. Stable, published by
+ * GS1. Consumers dereference it to resolve EPCIS + CBV core terms.
+ */
+export declare const EPCIS_CONTEXT_URL = "https://ref.gs1.org/standards/epcis/2.0.0/epcis-context.jsonld";
+/**
+ * Base URI for the TracePass-owned vocabulary. The CBV bizStep
+ * extension URIs (`.../cbv/bizstep/smelting`) and any other
+ * TracePass-namespaced EPCIS term hang off this. Published as a
+ * resolvable JSON-LD vocabulary document — see `cbv.ts` for the
+ * term list and `docs`/the vocabulary route for the published doc.
+ */
+export declare const TRACEPASS_VOC_BASE = "https://tracepass.eu/voc/";
+/**
+ * The `@context` value placed on every EPCIS document TracePass
+ * emits. Array form: the GS1 EPCIS 2.0 context URL first (so its
+ * term definitions take precedence), then a local object defining
+ * the `tracepass:` alias.
+ *
+ * The `cbv:` prefix is already defined inside the GS1 EPCIS context,
+ * so it is NOT redeclared here — redeclaring it would risk shadowing
+ * the official definition.
+ */
+export declare const EPCIS_JSONLD_CONTEXT: ReadonlyArray<string | Record<string, string>>;
+//# sourceMappingURL=context.d.ts.map

package/dist/context.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"context.d.ts","sourceRoot":"","sources":["../src/context.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AAEH;;;GAGG;AACH,eAAO,MAAM,iBAAiB,mEACoC,CAAC;AAEnE;;;;;;GAMG;AACH,eAAO,MAAM,kBAAkB,8BAA8B,CAAC;AAE9D;;;;;;;;;GASG;AACH,eAAO,MAAM,oBAAoB,EAAE,aAAa,CAAC,MAAM,GAAG,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAGtE,CAAC"}