GS1 EPC Tag Data Standard 1.6 - Indicod-Ecr

50655066506750685069507050715072507350745075507650775078507950805081508250835084508550865087508850895090509150925093509450955096509750985099510051015102510351045105510651075108column of that row (or a single name, if no OIDs column is present). Therefore, thesequence of combination and selection operations in an IDstring shall exactly matchthose in the row’s OIDs column.A non-empty OIDs cell may contain either a keyword, an ASCII string representing (indecimal) a single OID value, or a compound string (in ABNF notation) that a defines achoice and/or a combination of OIDs. The detailed syntax for compound OID strings inthis column (which also applies to the IDstring column) is as defined in section J.3.Instead of containing a simple or compound OID representation, an OIDs entry maycontain one of the following Keywords:K-Verbatim = OIDddBnn, where “dd” represents the chosen penultimate arc of theOID, and “Bnn” indicates one of the Base 10, Base 40, or Base 74 encoding tables.This entry invokes a number of Secondary ID bits that serve two purposes: They encode an ASCII identifier “name” that might not have existed at the timethe table was registered. The name is encoded in the Secondary ID bits section asa series of Base-n values representing the ASCII characters of the name, precededby a four-bit field indicating the number of Base-n values that follow (zero ispermissible, in order to support RFA entries as described below). The cumulative value of these Secondary ID bits, considered as a single unsignedbinary integer and converted to decimal, is the final “arc” of the OID for this“verbatim-encoded’ identifier.K-Secondary = Snn, where “Snn” represents the Table ID of a Secondary ID Tablein the same registration file. This is equivalent to a Base ID Table row OID entry thatcontains a single Selection list (with no other components at the top level), but insteadof listing these components in the Base ID Table, each component is listed as aseparate row in the Secondary ID Table, where each may be assigned a unique OID,ID string, and FormatString.K-Proprietary=OIDddPnn, where nn represents a fixed number of Secondary IDbits that encode an optional Enterprise Identifier indicating who wrote the proprietarydata (an entry of K-Proprietary=OIDddP0 indicates an “anonymous” proprietarydata item).K-RFA = OIDddBnn, where “Bnn” is as defined above for Verbatim encoding,except that “B0” is a valid assignment (meaning that no Secondary ID bits areinvoked). This keyword represents a Reserved for Future Assignment entry, with anoption for Verbatim encoding of the Identifier “name” once a name is assigned by theentity who registered this Data Format. Encoders may use this entry, with a four-bit“verbatim” length of zero, until an Identifier “name” is assigned. A specificFormatString may be assigned to K-RFA entries, or the default a/n encoding may beutilized.Finally, any OIDs entry may end with a single “R” character (preceded by one or morespace characters), to indicate that a “Repeat” bit shall be encoded as the last SecondaryID bit invoked by the entry. If ‘1’, this bit indicates that another instance of this class ofidentifier is also encoded (that is, this bit acts as if a repeat of the ID Value were encodedon an ID list). If ‘1’, then this bit is followed by another series of Secondary ID bits, torepresent the particulars of this additional instance of the ID Value.Copyright ©2005- 2011 GS1 AISBL, All Rights Reserved. Page 195 of 218