The Application Level Events (ALE) Specification, Version 1.0 - GS1

More documents

Recommendations

Info

835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 An EPC pattern is a URI-formatted string that denotes a single EPC or set of EPCs. The general format is: urn:epc:pat:TagFormat:Filter.Company.Item.Serial where TagFormat denotes one of the tag formats defined by the Tag Data Specification, and the four fields Filter, Company, Item, and SerialNumber correspond to data fields of the EPC. The meaning and number of these fields, as well as their formal names, varies according to what TagFormat is named. In an EPC pattern, each of the data fields may be (a) a decimal integer, meaning that a matching EPC must have that specific value in the corresponding field; (b) an asterisk (*), meaning that a matching EPC may have any value in that field; or (c) a range denoted like [lo-hi], meaning that a matching EPC must have a value between the decimal integers lo and hi, inclusive. Depending on the tag format, there may be other restrictions; see the EPCglobal Tag Data Specification for full details. Here are some examples. In these examples, assume that all tags are of the GID-96 format (which lacks the Filter data field), and that 20 is the Domain Manager (Company field) for XYZ Corporation, and 300 is the Object Class (Item field) for its UltraWidget product. urn:epc:pat:gid-96:20.300.4000 urn:epc:pat:gid-96:20.300.* urn:epc:pat:gid-96:20.*.[5000-9999] urn:epc:pat:gid-96:*.*.* Matches the EPC for UltraWidget serial number 4000. Matches any UltraWidget’s EPC, regardless of serial number. Matches any XYZ Corporation product whose serial number is between 5000 and 9999, inclusive. Matches any GID-96 tag 8.2.9 ECGroupSpec ECGroupSpec defines how filtered EPCs are grouped together for reporting. patternList : List // of pattern URIs --- Each element of the pattern list is an EPC Pattern URI as defined by the EPCglobal Tag Data Specification Version 1.1 [TDS1.1] (see Section 8.2.8 for an informal description of this syntax), extended by allowing the character X in each position where a * character is allowed. All restrictions on the use of the * character as defined in the Tag Data Specification apply equally to the use of the X character. For example, the following are legal URIs for use in the pattern list: urn:epc:pat:sgtin-64:3.*.*.* urn:epc:pat:sgtin-64:3.*.X.* Copyright © 2005, 2004 EPCglobal Inc, All Rights Reserved. Page 28 of 71
865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 urn:epc:pat:sgtin-64:3.X.*.* urn:epc:pat:sgtin-64:3.X.X.* But the following are not: urn:epc:pat:sgtin-64:3.*.12345.* urn:epc:pat:sgtin-64:3.X.12345.* Pattern URIs used in an ECGroupSpec are interpreted as follows: Pattern URI Field X Meaning Create a different group for each distinct value of this field. * All values of this field belong to the same group. Number [Lo-Hi] Only EPCs having Number in this field will belong to this group. Only EPCs whose value for this field falls within the specified range will belong to this group. Here are examples of pattern URIs used as group operators: Pattern URI urn:epc:pat:sgtin-64:X.*.*.* urn:epc:pat:sgtin-64:*.X.*.* urn:epc:pat:sgtin-64:*.X.X.* urn:epc:pat:sgtin-64:X.X.X.* urn:epc:pat:sgtin-64:3.X.*.[0-100] Meaning groups by filter value (e.g., case/pallet) groups by company prefix groups by company prefix and item reference (i.e., groups by specific product) groups by company prefix, item reference, and filter create a different group for each company prefix, including in each such group only EPCs having a filter value of 3 and serial numbers in the range 0 through 100, inclusive In the corresponding ECReport, each group is named by another EPC Pattern URI that is identical to the group operator URI, except that the group name URI has an actual value in every position where the group operator URI had an X character. For example, if these are the filtered EPCs read for the current event cycle: urn:epc:tag:sgtin-64:3.0036000.123456.400 urn:epc:tag:sgtin-64:3.0036000.123456.500 Copyright © 2005, 2004 EPCglobal Inc, All Rights Reserved. Page 29 of 71
Page 1 and 2: 1 2 3 The Application Level Events
Page 3 and 4: 52 53 54 55 56 57 58 59 60 61 62 63
Page 5 and 6: 115 116 117 118 119 120 121 122 123
Page 7 and 8: 171 172 173 174 175 176 177 178 179
Page 9 and 10: 256 257 258 259 260 261 262 263 264
Page 11 and 12: EPC1 EPC2 EPC3 EPC1 EPC2 EPC4 EPC3
Page 13 and 14: 388 389 390 391 392 393 394 395 396
Page 15 and 16: 465 466 467 468 469 470 471 472 473
Page 17 and 18: 535 536 537 538 539 540 541 542 543
Page 19 and 20: 591 592 593 594 595 596 597 Once re
Page 21 and 22: 629 630 Exception Name DuplicateSub
Page 23 and 24: 657 658 659 660 661 662 663 664 665
Page 25 and 26: 731 732 733 734 735 736 737 738 739
Page 27: 800 801 802 803 804 805 806 807 808
Page 31 and 32: 903 904 905 906 907 908 909 910 911
Page 33 and 34: 964 965 966 967 968 969 970 971 972
Page 35 and 36: 1007 1008 1009 1010 1011 1012 1013
Page 37 and 38: 1078 1079 1080 1081 1082 1083 1084
Page 39 and 40: 1151 1152 1153 1154 1155 1156 1157
Page 41 and 42: 1232 1233 1234 1235 1236 1237 1238
Page 43 and 44: 1331 1332 1333 1334 1335 1336 1337
Page 45 and 46: 1471 1472 1473 1474 1475 1476 1477
Page 47 and 48: 1611 1612 1613 1614 1615 1616 1617
Page 49 and 50: 1751 1752 1753 1754 1755 1756 1757
Page 51 and 52: 1875 1876 1877 1878 1879 1880 1881
Page 53 and 54: 2015 2016 2017 2018 2019 2020 2021
Page 55 and 56: 2155 2156 2157 2158 2159 2160 2161
Page 57 and 58: 2295 2296 2297 2298 2299 2300 2301
Page 59 and 60: 2435 2436 2437 2438 2439 2440 2441
Page 61 and 62: 2575 2576 2577 2578 2579 2580 2581
Page 63 and 64: 2660 2661 2662 2663 2664 2665 2666
Page 65 and 66: 2691 2692 2693 2694 2695 2696 2697
Page 67 and 68: 2741 2742 2743 2744 2745 2746 2747
Page 69 and 70: 2780 2781 2782 2783 2784 2785 2786
Page 71: 2818 2819 2820 2821 2822 2823 2824

The Application Level Events (ALE) Specification, Version 1.0 - GS1

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?