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

611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
return a string corresponding to a version of this specification to which the
implementation fully complies, and SHOULD return the string corresponding to the latest
version to which it complies. To indicate compliance with this Version 1.0 of the ALE
specification, the implementation SHALL return the string 1.0. The method
getVendorVersion returns a string that identifies what vendor extensions this
implementation provides. The possible values of this string and their meanings are
vendor-defined, except that the empty string SHALL indicate that the implementation
implements only standard functionality with no vendor extensions. When an
implementation chooses to return a non-empty string, the value returned SHALL be a
URI where the vendor is the owning authority. For example, this may be an HTTP URL
whose authority portion is a domain name owned by the vendor, a URN having a URN
namespace identifier issued to the vendor by IANA, an OID URN whose initial path is a
Private Enterprise Number assigned to the vendor, etc.
8.1.1 Error Conditions
Methods of the ALE API signal error conditions to the client by means of exceptions.
The following exceptions are defined. All the exception types in the following table are
extensions of a common ALEException base type, which contains one string element
giving the reason for the exception.
Exception Name
SecurityException
DuplicateNameException
ECSpecValidationException
InvalidURIException
NoSuchNameException
NoSuchSubscriberException
Meaning
The operation was not permitted due to an
access control violation or other security
concern. The specific circumstances that
may cause this exception are
implementation-specific, and outside the
scope of this specification.
The specified ECSpec name already
exists.
The specified ECSpec is invalid; e.g., it
specifies both a start trigger and a repeat
period. The complete list of rules for
generating this exception are specified in
Section 8.2.11.
The URI specified for a subscriber cannot
be parsed, does not name a scheme
recognized by the implementation, or
violates rules imposed by a particular
scheme.
The specified ECSpec name does not
exist.
The specified subscriber does not exist.
Copyright © 2005, 2004 EPCglobal Inc, All Rights Reserved. Page 20 of 71