IEC 61406-2:2024 complements IEC 61406-1 by providing additional requirements for those cases where data elements are encoded within the Structured Identification Link string with standardized syntax and semantics. In addition, this document covers cases where the uniqueness relates to product types\/models or lots\/batches. The default assumption is that the Identification Link identifies unique objects such as unique serialized products, assets, persons or packages, unless otherwise identified.<\/p>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
| 6<\/td>\n | Annex ZA (normative)Normative references to international publicationswith their corresponding European publications <\/td>\n<\/tr>\n | ||||||
| 7<\/td>\n | English CONTENTS <\/td>\n<\/tr>\n | ||||||
| 10<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
| 12<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
| 13<\/td>\n | 1 Scope 2 Normative references 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
| 15<\/td>\n | 4 General <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | 5 URL parameter 5.1 Data elements encoded in URL parameters 5.1.1 Requirements 5.1.2 Rationale and supplemental guidance 5.2 Parameter name and value tuples for data elements 5.2.1 Requirement 5.2.2 Rationale and supplemental guidance 5.3 SIDIs as parameter names 5.3.1 Requirement 5.3.2 Rationale and supplemental guidance <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | 5.4 One data element per parameter 5.4.1 Requirement 5.4.2 Rationale and supplemental guidance 5.5 Order of parameters is irrelevant 5.5.1 Requirement 5.5.2 Rationale and supplemental guidance 5.6 Parameter values conform to Data Identifier specifications 5.6.1 Requirement 5.6.2 Rationale and supplemental guidance <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | 5.7 Consistency rule for the Identification Link 5.7.1 Requirement 5.7.2 Rationale and supplemental guidance 6 Data Identifier categories and related object types 6.1 Generic support of Data Identifiers 6.1.1 Requirement 6.1.2 Rationale and supplemental guidance 6.2 Designated object type defined by Data Identifier category 6.2.1 Requirement <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | 6.2.2 Rationale and supplemental guidance Tables Table 1 \u2013 Kinds of objects and related Data Identifier categories <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | 6.3 Specific rules for traceability numbers and license plates 6.3.1 Requirement Table 2 \u2013 Traceability numbers and license plates for products and packages <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | 6.3.2 Rationale and supplemental guidance 7 Uniqueness within the domain 7.1 Requirement 7.2 Rationale and supplemental guidance <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | 8 Identification Link frame 8.1 Modified Identification Link frame for product type level, product model level, lot level or batch level 8.1.1 Requirement 8.1.2 Rationale and supplemental guidance Figures Figure 1 \u2013 Identification Link frame with bevelled corner <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | 8.2 Identification Link frames only for physical objects 8.2.1 Requirement 8.2.2 Rationale and supplemental guidance <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | Annex A (informative) Example of process flow for parsing Figure A.1 \u2013 Example of process flow for parsing <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | Annex B (informative) Examples of Structured Identification Link strings B.1 Serialized item B.1.1 General B.1.2 Example of a serialized item without product code B.1.3 Example of a serialized item without product code and scheme Table B.1 \u2013 Structure of example of a serialized item without recognizable product code <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | B.1.4 Example of a serialized item without product code, scheme and www B.1.5 Example of a serialized item with special top-level domain Table B.2 \u2013 Structure of example of a serialized item without product code and scheme Table B.3 \u2013 Structure of example of a serialized item without product code, scheme and www <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | B.1.6 Example of a serialized item with product code in own data element Table B.4 \u2013 Structure of example of a serialized item with special top-level domain Table B.5 \u2013 Structure of example of a serialized item with product code in own data element <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | B.1.7 Example of a serialized item with DUNS number as company code, product code and serial number B.1.8 Example of a serialized item with product code, serial number, production date, weight and capacity Table B.6 \u2013 Structure of example serialized item with DUNS number, product code and serial number <\/td>\n<\/tr>\n | ||||||
| 29<\/td>\n | B.2 Non-serialized item B.2.1 General Table B.7 \u2013 Structure of example of a serialized item with product code in own data element <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | B.2.2 Example of a non-serialized item with product code and lot code B.2.3 Example of a non-serialized item with product code only Table B.8 \u2013 Structure of example with product code and lot code Table B.9 \u2013 Structure of example with product code only <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | B.2.4 Example of a non-serialized item with GTIN only B.2.5 Example of a product code and company code Table B.10 \u2013 Structure of example with product code only Table B.11 \u2013 Structure of example with product code only <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | B.3 Cases other than items B.3.1 General B.3.2 Example of a human B.3.3 Example of a storage location Table B.12 \u2013 Structure of example of a human <\/td>\n<\/tr>\n | ||||||
| 33<\/td>\n | Table B.13 \u2013 Structure of example for a storage location <\/td>\n<\/tr>\n | ||||||
| 34<\/td>\n | Annex C (informative) Considerations for the use case of Identification Linksin Digital Product Passports <\/td>\n<\/tr>\n | ||||||
| 35<\/td>\n | Annex D (informative) Identification Link authentication: Inclusion of a digital signature conforming to ISO\/IEC 20248 Table D.1 \u2013 Readmethods <\/td>\n<\/tr>\n | ||||||
| 37<\/td>\n | Annex E (informative) Default hostname derived from IL string Table E.1 \u2013 Example 1 for derived default hostname from IL string Table E.2 \u2013 Example 2 for derived default hostname from IL string <\/td>\n<\/tr>\n | ||||||
| 38<\/td>\n | Annex F (informative) Embedding of IL Strings into DevIDs according to IEEE 802.1ARTM-2018 Table F.1 \u2013 Additional ABNF Core Rules Table F.2 \u2013 ABNF Description for a DevID URI <\/td>\n<\/tr>\n | ||||||
| 40<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Identification link – Types\/models, lots\/batches, items and characteristics<\/b><\/p>\n |