The structure of the XML documents is the very prescriptive part of the eBIZ/TC Upstream framework:
using the eBIZ/TC Upstream documents, the prescriptions must be completely respected about structure of the documents, names and coding,
optionality or mandatory use of elements, meaning of each element.
Otherwise the documents could be not validable with the XML Schema (that are the only way to check the
formal compliance of the documents) or could generate misunderstandings about the meaning of the message on the side of your partners.
The allowable customisations are about the use or not of a document or about the elements of the document that are declared 'optional'; they can
be used to simplify the documents (not all the elements are always necessary).
The (template of) eBIZ/TC Upstream documents of each release are on www.ebiz.enea.it or www.moda-ml.org and are represented by:
Document Information for consumer | ||
---|---|---|
Document |
Information for consumer (New) | |
Description | Traceability and sustainability information for consumer. This document can be used to synchronize the data of a consumer APP capable of retrieving specific information about the batch or product instance. | |
Release date | 06/09/2022 | |
Scope |
This guide aims to illustrate the standard XML format of the document type "Information for consumer", providing instructions for its use in the context of a TRANSPARENCY SYSTEM involving Fashion Manufacturers, their customers, third parties and in case customs authorities, eBusiness and eCommerce platforms. All the rules necessary for the construction and validation of the document are expressed through a specific XML schema, which is presented in detail in the paragraph "Implementation Guide".
| |
Credits | This document was produced by Piero De Sabbata, Arianna Brutti e Gessica Ciaccio for ENEA X-LAB with the contribution of Marco Vallini of Domina and the partners of the TRICK project. | |
Back compatibility | New | |
Document Code | TRC022 | |
Resources |
[Guide] [XML Schema] [JSON Schema] | |
Used in Processes |
|
|