GS1 EPC Tag Data Standard 1.6 - Indicod-Ecr

2053205420552056205720582059206020612062206320642065206620672068206920702071207220732074207520762077207820792080208120822083208420852086208720882089209020912092209313 URIs for EPC PatternsCertain software applications need to specify rules for filtering lists of tags according tovarious criteria. This specification provides an EPC Tag Pattern URI for this purpose.An EPC Tag Pattern URI does not represent a single tag encoding, but rather refers to aset of tag encodings. A typical pattern looks like this:urn:epc:pat:sgtin-96:3.0652642.[102400-204700].*This pattern refers to any tag containing a 96-bit SGTIN EPC Binary Encoding, whoseFilter field is 3, whose GS1 Company Prefix is 0652642, whose Item Reference is in therange 102400 itemReference 00, and whose Serial Number may be anything atall.In general, there is an EPC Tag Pattern URI scheme corresponding to each EPC BinaryEncoding scheme, whose syntax is essentially identical except that ranges or the star (*)character may be used in each field.For the SGTIN, SSCC, SGLN, GRAI, GIAI, GSRN and GDTI patterns, the patternsyntax slightly restricts how wildcards and ranges may be combined. Only twopossibilities are permitted for the CompanyPrefix field. One, it may be a star (*), inwhich case the following field (ItemReference, SerialReference,LocationReference, AssetType,IndividualAssetReference,ServiceReference or DocumentType) must also be a star. Two, it may be aspecific company prefix, in which case the following field may be a number, a range, or astar. A range may not be specified for the CompanyPrefix.Explanation (non-normative): Because the company prefix is variable length, a rangemay not be specified, as the range might span different lengths. When a particularcompany prefix is specified, however, it is possible to match ranges or all values of thefollowing field, because its length is fixed for a given company prefix. The other casethat is allowed is when both fields are a star, which works for all tag encodings becausethe corresponding tag fields (including the Partition field, where present) are simplyignored.The pattern URI for the DoD Construct is as follows:urn:epc:pat:usdod-96:filterPat.CAGECodeOrDODAACPat.serialNumberPatwhere filterPat is either a filter value, a range of the form [lo-hi], or a *character; CAGECodeOrDODAACPat is either a CAGE Code/DODAAC or a *character; and serialNumberPat is either a serial number, a range of the form [lohi],or a * character.The pattern URI for the Aerospace and Defense (ADI) identifier is as follows:urn:epc:pat:adivar:filterPat.CAGECodeOrDODAACPat.partNumberPat.serialNumberPatwhere filterPat is either a filter value, a range of the form [lo-hi], or a *character; CAGECodeOrDODAACPat is either a CAGE Code/DODAAC or a *character; partNumberPat is either an empty string, a part number, or a * character;and serialNumberPat is either a serial number or a * character.Copyright ©2005- 2011 GS1 AISBL, All Rights Reserved. Page 76 of 218