GS1 EPC Tag Data Standard 1.6 - Indicod-Ecr

52765277527852795280528152825283528452855286528752885289529052915292529352945295529652975298529953005301530253035304530553065307530853095310531153125313531453155316| FixedRange “n” “ ”+ VarRange “an”Range ::= FixedRange | VarRangeFixedRange ::= NumberVarRange ::= Number “*” Number?Number ::= (“0”..“9”)+The syntax for COMPONENT for the OIDs and IDString columns make reference toConcat, whose syntax is specified as follows:Concat ::= “%” “x” HexChar HexChar “-” HexChar HexCharHexChar ::= (“0”..“9” | “A”..“F”)The hex value following the hyphen shall be greater than or equal to the hex valuepreceding the hyphen. In the OIDs column, each hex value shall be in the range 30 hex to39 hex , inclusive. In the IDString column, each hex value shall be in the range 20 hex to7E hex , inclusive.J.4 OID input/output representationThe default method for representing the contents of a Packed Object to a receivingsystem is as a series of name/value pairs, where the name is an OID, and the value is thedecoded data string associated with that OID. Unless otherwise specified by a K-RootOID keyword line, the default root OID is urn:oid:1.0.15961.ff, where ff is theData Format encoded in the DSFID. The final arc of the OID is (by default) the IDvalue,but this is typically overridden by an entry in the OIDs column. Note that an encodedApplication Indicator (see I.5.3.1) may change ff from the value indicated by the DSFID.If supported by information in the ID Table’s IDstring column, a receiving system maytranslate the OID output into various alternative formats, based on the IDStringrepresentation of the OIDs. One such format, as described in ISO/IEC 15434, requires asadditional information a two-digit Format identifier; a table registration may provide thisinformation using the K-ISO15434 keyword as described above.The combination of the K-RootOID keyword and the OIDs column provides theregistering entity an ability to assign OIDs to data system identifiers without regard tohow they are actually encoded, and therefore the same OID assignment can applyregardless of the access method.J.4.1 “ID Value OID” output representationIf the receiving system does not have access to the relevant ID Table (possibly because itis newly-registered), the Packed Objects decoder will not have sufficient information toconvert the IDvalue (plus Secondary ID bits) to the intended OID. In order to ease theintroduction of new or external tables, encoders have an option to follow “restricted use”rules (see I.5.3.2).Copyright ©2005- 2011 GS1 AISBL, All Rights Reserved. Page 200 of 218