New pages

From imde.io

New pages
Hide registered users | Hide bots | Show redirects

2 November 2026

  • 12:4112:41, 2 November 2026 DataTopic TechnicalDocumentation (hist | edit) [4,596 bytes] Yuri (talk | contribs) (Created page with "[Draft] XML: <pre> <DataTopic Topic="TechnicalDossier" Format="Azlon" Version="1.0"> <TechnicalDossier xmlns="https://imde.io/schema/azlon/1.0/technicaldossier"> <Document> <DocumentCode>EV-000001</DocumentCode> <DocumentType CodeList="IMDE">DECLARATION_OF_CONFORMITY</DocumentType> <ComplianceIndicators> <ComplianceIndicator> <CodeList>IMDE</CodeList> <Value>HEAVY_METALS_LIMIT...")

26 October 2026

  • 11:4011:40, 26 October 2026 Message (hist | edit) [18,597 bytes] Yuri (talk | contribs) (Created page with "The IMDEMessages structure is mandatory for every message and defines the type of datacontainers and all related parties. Every IMDE message is encapsulated in an IMDEMessages container which can contain 1 or more IMDEMessage objects. ==Dictionary== {| class="wikitable" |+ List of data elements used in Message Header |- ! Data element !! Definition |- | DataSender || The legal entity or system sending the data. In this example Wonka is the chocolate manufacturer sending...")

14 October 2026

  • 12:4112:41, 14 October 2026 Packaging Digital Link - DT (hist | edit) [11,067 bytes] HansdG (talk | contribs) (Created page with "The '''Packaging Digital Link''' is a web link that identifies one Packaging System and gives access to its packaging dossier: the EU Declarations of Conformity, the technical documentation and the packaging composition. It is built on ISO/IEC, ANSI and GS1 standards, and its content follows the IMDE Packaging System data container. __TOC__ == Purpose == One Packaging System is often used by many sales units and transport units. In private label, these units are placed...")

12 October 2026

  • 13:4713:47, 12 October 2026 DataTopic PackagingSystemKeyInfo (hist | edit) [1,060 bytes] Yuri (talk | contribs) (Created page with "[Draft] XML: <pre> <DataTopic Topic="PackagingSystemMasterKeyInfo" Format="Azlon" Version="1.0"> <PackagingSystemMasterKeyInfo xmlns="https://imde.io/schema/azlon/1.0/packagingsystemmasterkeyinfo"> <ItemIdentifiers> <Identifiers> <Identifier Type="GID">VTA-MPLA-PS-2YJNUXXX</Identifier> </Identifiers> </ItemIdentifiers> </PackagingSystemMasterKeyInfo> </DataTopic> </pre> JSON: <pre> { "Topic": "PackagingSystemMasterKeyInfo", "Format": "Azlon", "Vers...")

8 October 2026

  • 11:4111:41, 8 October 2026 DataTopic DeclarationOfConformity (hist | edit) [1,724 bytes] Yuri (talk | contribs) (Created page with "XML: <pre> <DataTopic Topic="DeclarationOfConformity" Format="Azlon" Version="1.0"> <DeclarationOfConformity xmlns="https://imde.io/schema/azlon/1.0/declarationofconformity"> <KeyInfo> <DocumentNr>DOC-00004</DocumentNr> <Revision>R01</Revision> <IssueDate>2026-08-11T08:07:28Z</IssueDate> <Status>Unsigned</Status> <Manufacturer>Jumbo</Manufacturer> </KeyInfo> <Urls> <Url> <Language>de</Language> <Url>https://ota-vault.perennis.io/PS/VTA-MP...")
  • 10:4910:49, 8 October 2026 DataContainer - PackagingSystem (hist | edit) [448 bytes] Yuri (talk | contribs) (Created page with "XML: <pre> <IMDEMessages xmlns="https://imde.io/schema/imdemessages/3.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="https://imde.io/schema/imdemessages/3.0 https://imde.io/schema/3.0/IMDEMessages.xsd"> <IMDEMessage> <Header DataContainerType="Item"> <DataSender> <Identifiers> <Identifier Type="GLN">8719328024279</Identifier> </Identifiers> </DataSender>...") originally created as "DataContainer -PackagingSystemMaster"

1 October 2026

  • 14:3814:38, 1 October 2026 Reserved Code List Values: UNSPECIFIED and NOT APPLICABLE - TX (hist | edit) [9,213 bytes] HansdG (talk | contribs) (Created page with "== Purpose and scope == Every code list attribute in an exchange file (XML or JSON) can carry two reserved values, <code>UNSPECIFIED</code> and <code>NOT_APPLICABLE</code>, on top of its own business values. These two values let a sender say ''why'' a business value is missing, rather than leaving a gap the receiver has to guess at. This matters most for regulatory data (PPWR, ESPR/DPP), where "no", "we don't know yet" and "this question doesn't apply" lead to different...")

9 September 2026

  • 12:4312:43, 9 September 2026 Facility - TX (hist | edit) [7,963 bytes] HansdG (talk | contribs) (Created page with "'''Facility''' is a place where one or more defined activities are carried out, operated by a legal entity, and situated at a Location. A Facility answers two questions that a Location cannot: ''what happens here'', and ''who runs it''. It is the operational object that compliance statements, certificates, accreditations and evidence attach to. == Facility Functions == A Facility does not have a type. It has one or more '''Functions'''. This is a deliberate model...")
  • 12:2612:26, 9 September 2026 Material System - TX (hist | edit) [3,051 bytes] HansdG (talk | contribs) (Created page with "Material Platform A Material Platform is the unit of identity for a packaging material, one level below the Packaging Master. It is where everything that is true about the material itself is recorded and maintained once: composition, substances of concern, test reports, recyclability inputs, recycled content and its chain of custody, each carrying its method, version and date. A Packaging Master references the Material Platform instead of copying its data. What is spec...") originally created as "Material Platform - TX"