IptcEnvelopeRecordDataSet enumeration Leave feedback
On this page
Defines IPTC Envelope Record dataSet numbers.
The IptcEnvelopeRecordDataSet type exposes the following members:
| Field | Description |
|---|---|
| MODEL_VERSION | A binary number identifying the version of the Information
Interchange Model, Part I, utilised by the provider. Version numbers are assigned by IPTC and NAA. The version number of this record is four (4). |
| DESTINATION | Optional, repeatable, maximum 1024 octets, consisting of sequentially contiguous graphic characters.
This DataSet is to accommodate some providers who require routing information above the appropriate OSI layers. |
| FILE_FORMAT | File format. |
| FILE_FORMAT_VERSION | Mandatory, not repeatable, two octets.
A binary number representing the particular version of the File Format specified in 1:20. A list of File Formats, including version cross references, is included as Appendix A. |
| SERVICE_IDENTIFIER | Mandatory, not repeatable. Up to 10 octets, consisting of graphic characters.
Identifies the provider and product. |
| ENVELOPE_NUMBER | Mandatory, not repeatable, eight octets, consisting of numeric characters.
The characters form a number that will be unique for the date specified in 1:70 and for the Service Identifier specified in 1:30. If identical envelope numbers appear with the same date and with the same Service Identifier, records 2-9 must be unchanged from the original. This is not intended to be a sequential serial number reception check. |
| PRODUCT_ID | Optional, repeatable. Up to 32 octets, consisting of graphic characters.
Allows a provider to identify subsets of its overall service. Used to provide receiving organization data on which to select, route, or otherwise handle data. |
| ENVELOPE_PRIORITY | Optional, not repeatable. A single octet, consisting of a numeric character.
Specifies the envelope handling priority and not the editorial urgency (see 2:10, Urgency). ‘1’ indicates the most urgent, ‘5’ the normal urgency, and ‘8’ the least urgent copy. The numeral ‘9’ indicates a User Defined Priority. The numeral ‘0’ is reserved for future use. |
| DATE_SENT | Mandatory, not repeatable. Eight octets, consisting of numeric characters.
Uses the format CCYYMMDD (century, year, month, day) as defined in ISO 8601 to indicate year, month and day the service sent the material. |
| TIME_SENT | Uses the format HHMMSS±HHMM where HHMMSS refers to
local hour, minute and seconds and HHMM refers to hours and minutes ahead (+) or behind (-) Universal Coordinated Time as described in ISO 8601. This is the time the service sent the material. |
| CODED_CHARACTER_SET | Optional, not repeatable, up to 32 octets, consisting of one or
more control functions used for the announcement, invocation or designation of coded character sets. The control functions follow the ISO 2022 standard and may consist of the escape control character and one or more graphic characters. For more details see Appendix C, the IPTC-NAA Code Library. |
| UNO | Invalid (eternal identifier). |
| ARM_IDENTIFIER | The DataSet identifies the Abstract Relationship Method (ARM) which is described
in a document registered by the originator of the ARM with the IPTC and NAA. |
| ARM_VERSION | Binary number representing the particular version of the ARM specified in DataSet 1:120. |
Was this page helpful?
Any additional feedback you'd like to share with us?
Please tell us how we can improve this page.
Thank you for your feedback!
We value your opinion. Your feedback will help us improve our documentation.
