Derivative ID type. This can be a GUID represented in RFC 4122 Base64-URL form (so 16 bytes convert to a 22-byte string). This might use a more terse form, but some namespace resolution is needed first.
Enhancement sequence number within a PEID. This is an xs:int with a domain of zero to 65,535 (two binary bytes). These sequence numbers are assigned to message-addressable nodes in the campaign description associated with PEIDs and ETypes. The PEID+EPSID can be used to locate the node, and its EType allows further navigation. EpsidType is limited to two binary bytes.
These numbers are processing identifiers assigned to message-addressable nodes in the campaign description (i.e, containing a PEID+EPSID). The PEID+EPSID can be used to locate the node, and its EType identifies specific message processing associated with that node. EventIdType is an xs:int with a domain of zero to 99.
A derivative of xs:string that is required to have content. Implementations using this in place of xs:string MUST NOT leave required attribute or element content empty. Whitespace-only content MAY be used.
This is an xs:int restricted to zero or positive content. Note: As opposed to xs:nonNegativeInteger, which derives from Integer, NonNegativeIntType derives from xs:int, which has a much smaller domain.
The indentifier of a CIP document message-addressable node. This identifier MUST be unique over all time. For all interoperable use, this MUST be an xs:string of 22 characters which contains a GUID represented in RFC 4122 Base64-URL form (so 16 bytes convert to a 22-byte string). For private use the PEID can be under namespace control, so the length MAY be less than 22, but MUST be non-zero.
This is an xs:int restricted to positive content.
This identifies a complete application. It is a key to access the application characterization in the application repository.
The attribute set for characterizing an application. The repositoryAppKey characterizes an application according to the specification format, and the OrgID,AppID,version identify a specific expression of that repository template held in the application repository. AppId/orgId/appVer are a set, all present or absent. Either that set or appDataReverence or both MUST be present for the applicationDefinition to be valid.
Note that appVer is to be deprecated in a future release. Implementations SHOULD use appVerMajor and appVerMinor instead.
Attribute set that defines some instant, or an interval starting at some instant. The instant is offset from some event, usually the start of flight (as xs:duration), and the interval is a duration after the offset.
Attribute set that defines some instant, or an interval starting at some instant, but MAY also be empty. The instant is offset from some event defined by application convention (as xs:duration), and the interval is a duration after the offset.
A syscode is a unique human-readable identifier that tends to represent an insertion point (such as a splicer). These system-level syscodes are at the MSO level within a given market. Larger network areas are represented by a syscode that is itself composed of syscodes.
UUID is a 16-byte integer, encoded using RFC 4122 Base64-URL form. This encodes to ceiling((bytes)/3)*4 = 24 Base64 bytes less padding, or 22 total. It would be about 43 decimal, or 32 hex digits.
A US Postal ZIP code in either five-digit or five-plus-four-digit notation.
UserInput is a string used to store a user's response to a poll, RFI, and so on. This element is OPTIONAL as it will not be included in messages representing Service Metric updates.
An OPTIONAL unconstrained xs:string used to pass other relevant data.
Human-readable contact phone, which may have extension, etc. Not expected to be machine-processable.
Major version provides the macro versioning number for each interface. Versions containing the same major version SHOULD provide backwards compatibility.
The MinSchemaVersion SHOULD refer to a MajorVersion number.
MinorVersion, when positive, starts at one and identifies incremential and backwards compatible updates to a major version. Minor version numbers which are negative ordinals, starting at -1 and decreasing, identify development versions derived from the referenced major version but which are otherwise completely independent.
MicroVersion is negative ordinals starting at -1 for ReleaseCandidates, and non-negative ordinals starting at 0 for releases. Assumed to be zero if omitted.
MinSchemaVersion is the lowest compatible schema version number (assumes all forward compatible within MajorVersion). A document with a minSchemaVersion of 2 MUST be compatible with any processor implementing schema version 2 or higher, but not with a processor implementing schema 1.
MinSchemaMinorVersion is the lowest compatible schema minor version number. If missing, all minor version numbers are assumed to be compatible.
Extensibility - provides for elements from any namespace.
GeographicCode is an identifier used to denote the location of the device/unit. This could be a ZIP Code or a syscode.
A name-value pair report data set
Defines an absolute time range.
Defines a standard fault model for the SaFI web services.
Contains identifiers used to unambiguously identify a stewarded package.