| 34L |
|
Pointer to Process URL (P2P URL) for initiating a URL to carry all other data elements encoded in an AIDC media according to the following rule: Scan the code and initiate the URL starting with the P2P URL string, omitting DI 34L and ISO/IEC 15434 envelope syntax (prefix and postfix) and append all other data elements that have been scanned in same sequence as encoded in the media, including DIs and data element separators. Convert special characters in the appended data into RFC 1738 format (e.g., Group Separator GS translated into RFC 1738 sequence %1D). Note that this does not apply to the P2P URL itself.
Example: Encoded data string (using ISO/IEC 15434) [)>RS06GS25SUN123456789PA12345GS4LUSGS16D20131108
GS34LHTTP://WWW.SECUREUID.COM/ITEMDATA/?SCAN=
RS05 GS13131108RSEOT
results in the following URL with the transmitted data: HTTP://WWW.SECUREUID.COM/ITEMDATA/?SCAN=25SU N123456789PA12345%1D4LUS%1D16D20131108
NOTE data from the 05 format envelope was not incorporated in the URL since the 34L was encoded in the 06 format envelope |
False |
False |
| 35L |
an3+a2+an3...27 |
A government-assigned approval number of vessel / aquaculture site / farm / processor, starting with an ISO 3166-1 alpha-2 country code, followed by the approval number.
All characters of the GS1 General Specification-defined sub- set of ISO/IEC 646 are allowed.
Example:
35LIECK0107EC = Country; Ireland. Vessel Name; FV Endurance DA31. |
False |
False |
| 36L |
an3+a2+an3...27 |
A government-assigned approval number of producer or farm or first deboning / cutting hall, starting with an ISO 3166-1 alpha-2 country code, followed by the approval number.
All characters of the GS1 General Specification-defined sub- set of ISO/IEC 646 are allowed.
Example:
36LIECK0107EC = Country; Ireland. Vessel Name; FV Endurance DA31. |
False |
False |
| 51L |
an3+an1...9 |
Ship From: - Location code defined by a postal authority (e.g., 5-digit and 9-digit ZIP codes identifying U.S. locations or 6-character postal codes identifying Canadian locations). |
False |
False |
| 52L |
an3+an1...9 |
Ship To: - Location code defined by a postal authority (e.g., 5-digit and 9-digit ZIP codes identifying U.S. locations or
6-character postal codes identifying Canadian locations). |
False |
False |
| 54L |
an3+an1...9 |
Ship From: - Location code defined by a postal authority in the format: postal codes (e.g., 5-digit ZIP codes identifying
U.S. locations or 6- or 7-character postal codes identifying United Kingdom locations) followed by two-character
ISO 3166 country code (e.g., US or GB). |
False |
False |
| 55L |
an3+an1...9 |
Ship To: - Location code defined by a postal authority in the format: postal codes (e.g., 5-digit ZIP codes identifying U.S. locations or 6- or 7-character postal codes identifying United Kingdom locations) followed by two-character ISO 3166 country code (e.g., US or GB). |
False |
False |
| 10M |
|
Army Form 2410 data. Format is data value preceded by the block number of the form 2410. Field lengths and acceptable characters can be found at:
http://www.apd.army.mil/pdffiles/p738_751.pdf.
2020 Update: The URL has been modified to: https://armypubs.army.mil/ProductMaps/PubForm/Details.asp x?PUB_ID=1408 |
False |
False |
| 11M |
|
Army Form 2408 data. Format is data value preceded by the block number of the form 2408. Field lengths and acceptable characters can be found at:
http://www.apd.army.mil/pdffiles/p738_751.pdf.
2020 Update: The URL has been modified to: https://armypubs.army.mil/ProductMaps/PubForm/Details.asp x?PUB_ID=1400 |
False |
False |
| 12M |
|
Army Form 2407 data. Format is data value preceded by the block number of the form 2407. Field lengths and acceptable characters can be found at:
http://www.apd.army.mil/pdffiles/p738_751.pdf.
2020 Update: The URL has been modified to: https://armypubs.army.mil/ProductMaps/PubForm/Details.asp x?PUB_ID=1391 |
False |
False |
| 13M |
|
Air Force Form 95 data. Format is data value preceded by the block number of the form 95. Field lengths and acceptable characters can be found at:
http://www.gsa.gov/portal/forms/download/116418.
2020 Update: The Name of the Form is Air Force Technical Order Form 95 (AFTO Form 95). Details about the Form are sourced in Air Force Technical Order (TO) 00-20-1. The URL for this TO has been modified to:
https://www.tinker.af.mil/Portals/106/Documents/Technical%2 0Orders/AFD-180615-00-20-1.pdf |
False |
False |
| 14M |
|
Navy Form 4790 data. Format is data value preceded by the block number of the form 2410. Field lengths and acceptable characters can be found at:
http://www.navair.navy.mil/logistics/4790/library/Chapter%201 5.pdf.
2020 Update: The URL is no longer valid. |
False |
False |
| N |
an1+an13...15 |
National/NATO Stock Number (NSN). |
False |
False |
| 1N |
|
Product Characteristic Data defined by the Chemical Industry Data Exchange (CIDX). |
False |
False |
| 2N |
|
Reserved. |
False |
False |
| 3N |
|
Coding Structure in Accordance with Format Defined by Electronic Industries Association Japan (EIAJ). |
False |
False |
| 4N |
|
Coding Structure and Formats in Accordance with GS1 Application Identifiers (AI plus data) (GS1). |
False |
False |
| 5N |
|
Coding Structure and Formats in Accordance with AIAG Recommendations. The full Data Identifier is in the form 5Nxx where the xx is found in the full code list that can be found at https://www.aiag.org/. |
False |
False |
| 6N |
|
U.S. DOD Requisition and Issue Procedure Codes. The format is the appropriate MILSTRIP code followed by the data value associated with that code. The full list of codes is available at:
http://www2.dla.mil/j- 6/dlmso/elibrary/Manuals/DLM/MILSTRIP/MILSTRIP.pdf. 2020 Update: The URL has been modified to:
https://www.dla.mil/HQ/InformationOperations/DLMS/elibrary/
manuals/MILSTRIP/ |
False |
False |
| 7N |
|
U.S. Defense Transportation Regulation Codes. The format is the DTR code followed by the appropriate data value associated with that code. The full list of codes is available at:
http://www.transcom.mil/dtr/part-ii/dtr_part_ii_toc.pdf. 2020 Update: The URL has been modified to: https://www.ustranscom.mil/dtr/part-ii/dtr_part_ii_toc.pdf |
False |
False |
| 8N |
|
Production Animal Identification Codes. The format is the production animal code followed by the appropriate data value associated with that code. The Technical Report and the full list of Extended Data Elements (codes) is maintained at:
http://www.aimglobal.org/store/view_product.asp?id=4926441 Extended Data Elements (Codes).
http://www.aimglobal.org/store/view_product.asp?id=4926483 Technical Report.
2020 Update: The URLs have been modified to:
https://web.aimglobal.org/external/wcpages/wcecommerce/ec omlistpage.aspx?Keyword=animal |
False |
False |
| 9N |
an2+an11...28 |
Pharmacy Product Number maintained by IFA (www.ifaffm.de) with the following elements; Data Identifier (DI), two-digit product registration agency code (PRAC), the product reference (PR), and the two PPN check digits (CC), in the form DI PRAC PR CC.
NOTE space is added as a separator for visual clarity and is not part of the data.
Examples:
? 9N1112345678CC
? 9N1312345MEDDEVICE1245678900CC |
False |
False |
| 10N |
|
Data in the format and using semantics defined by the holder of a Company Identification Number (CIN) that has been issued by an Issuing Agency Code (IAC) in accordance with ISO/IEC 15459, defined as a sequence of concatenated data elements: IAC, followed by CIN, followed by the separator character : (colon) followed by the data in the format and using semantics as defined by the CIN holder.
NOTE Only the data syntax rules (if any) as provided by the declared IAC+CIN within each DI 10N data stream shall be applied to the data following DI 10N+IAC+CIN. |
False |
False |
|
|
NOTE Due to an error in the assignment of DI 10N (there is no central authority for data-definition nor maintenance), no new uses of DI 10N should be implemented.
The function of DI 10N is established in Category 18, MISCELLANEOUS with DI 5R. It is strongly recommended that existing applications that use DI 10N migrate to DI 5R. |
False |
False |
| 11N |
|
The Data construct is defined and controlled by the RLA and is comprised of 2 segments: the field identifier code, immediately followed by the data as defined for that element according to the data dictionary of the RLA. It is essentially a catalog of fields with standardized content. The Field Identifiers are posted at http://rla.org/11ncodes. The use and structure of these codes are defined at: http://rla.org/11nformat. Additional examples can be found at that site as well. DI 11N shall never be encoded in a 2D or RFID tag together with any other DI elements. |
False |
False |