GS1 EPC Tag Data Standard 1.6 - Indicod-Ecr

531753185319532053215322532353245325532653275328532953305331533253335334533553365337533853395340534153425343534453455346534753485349535053515352535353545355535653575358When a receiving system has decoded a Packed Object encoded following “restricteduse” rules, but does not have access to the indicated ID Table, it shall construct an “IDValue OID” in the following format:urn:oid:1.0.15961.300.ff.bb.idval.secbitswhere 1.0.15961.300 is a Root OID with a reserved Data Format of “300” that is neverencoded in a DSFID, but is used to distinguish an “ID Value OID” from a true OID (aswould have been used if the ID Table were available). The reserved value of 300 isfollowed by the encoded table’s Data Format (ff) (which may be different from theDSFID’s default), the table ID (bb) (always ‘0’, unless otherwise indicated via anencoded Application Indicator), the encoded ID value, and the decimal representation ofthe invoked Secondary ID bits. This process creates a unique OID for each unique fullyqualifiedID Value. For example, using the hypothetical ID Table shown in Annex L (butassuming, for illustration purposes, that the table’s specified Root OID isurn:oid:1.0.12345.9, then an “AMOUNT” ID with a fourth digit of ‘2’ has a true OIDof:urn:oid:1.0.12345.9.3912and an “ID Value OID” ofurn:oid:1.0.15961.300.9.0.51.2When a single ID Value represents multiple component identifiers via combinations oroptional components, their multiple OIDs and data strings shall be represented separately,each using the same “ID Value OID” (up through and including the Secondary ID bitsarc), but adding as a final arc the component number (starting with “1” for the firstcomponent decoded under that IDvalue).If the decoding system encounters a Packed Object that references an ID Table that isunavailable to the decoder, but the encoder chose not to set the “Restricted Use” bit in theApplication Indicator, then the decoder shall either discard the Packed Object, or relaythe entire Packed Object to the receiving system as a single undecoded binary entity, asequence of octets of the length specified in the ObjectLength field of the Packed Object.The OID for an undecoded Packed Object shall be urn:oid:1.0.15961.301.ff.n, where“301” is a Data Format reserved to indicate an undecoded Packed Object, “ff” shall bethe Data Format encoded in the DSFID at the start of memory, and an optional final arc‘n’ may be incremented sequentially to distinguish between multiple undecoded PackedObjects in the same data carrier memory.Appendix K Packed Objects Encoding tablesPacked Objects primarily utilize two encoding bases: Base 10, which encodes each of the digits ‘0’ through ‘9’ in one Base 10 value Base 30, which encodes the capital letters and selectable punctuation in one Base-30value, and encodes punctuation and control characters from the remainder of theASCII character set in two base-30 values (using a Shift mechanism)For situations where a high percentage of the input data’s non-numeric characters wouldrequire pairs of base-30 values, two alternative bases, Base 74 and Base 256, are alsodefined:Copyright ©2005- 2011 GS1 AISBL, All Rights Reserved. Page 201 of 218