The Application Level Events (ALE) Specification, Version 1.0 - GS1
The Application Level Events (ALE) Specification, Version 1.0 - GS1
The Application Level Events (ALE) Specification, Version 1.0 - GS1
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
964<br />
965<br />
966<br />
967<br />
968<br />
969<br />
970<br />
971<br />
972<br />
973<br />
974<br />
975<br />
976<br />
977<br />
978<br />
979<br />
980<br />
981<br />
982<br />
983<br />
984<br />
985<br />
986<br />
987<br />
988<br />
• Any filter within ECFilterSpec does not conform to the EPC URI pattern syntax<br />
specified in [TDS1.1].<br />
• Any grouping pattern within ECGroupSpec does not conform to the syntax for<br />
grouping patterns specified in Section 8.2.9.<br />
• Any two grouping patterns within ECGroupSpec are determined to be non-disjoint<br />
as that term is defined in Section 8.2.9.<br />
• Within any ECReportSpec of an ECSpec, the ECReportOutputSpec has no<br />
output type specified; i.e., none of includeEPC, includeTag,<br />
includeRawHex, includeRawDecimal, includeCount, nor any vendor<br />
extension output type is specified as true.<br />
8.3 ECReports<br />
ECReports is the output from an event cycle.<br />
specName : string<br />
date : dateTime<br />
<strong>ALE</strong>ID : string<br />
totalMilliseconds : long<br />
terminationCondition : ECTerminationCondition<br />
spec : ECSpec<br />
reports : List<br />
<br />
---<br />
// List of ECReport<br />
<strong>The</strong> “meat” of an ECReports instance is the list of ECReport instances, each<br />
corresponding to an ECReportSpec instance in the event cycle’s ECSpec. In addition<br />
to the reports themselves, ECReports contains a number of “header” fields that provide<br />
useful information about the event cycle:<br />
Field<br />
specName<br />
date<br />
<strong>ALE</strong>ID<br />
Description<br />
<strong>The</strong> name of the ECSpec that controlled this event cycle.<br />
In the case of an ECSpec that was requested using the<br />
immediate method (Section 8.1), this name is one<br />
chosen by the <strong>ALE</strong> implementation.<br />
A representation of the date and time when the event<br />
cycle ended. For bindings in which this field is<br />
represented textually, an ISO-8601 compliant<br />
representation SHOULD be used.<br />
An identifier for the deployed instance of the <strong>ALE</strong><br />
implementation. <strong>The</strong> meaning of this identifier is<br />
Copyright © 2005, 2004 EPCglobal Inc, All Rights Reserved. Page 33 of 71
Change language