9 Mapping of DataTypes ToC Previous Next

9.1 Primitive data types ToC Previous Next

9.1.3 CodeTypeDataType ToC Previous Next

This DataType is a String that represents a code type used for an AutoId Identifier.

Its representation in the AddressSpace is defined in Table 25.

Table 25 – CodeTypeString Definition

Attributes Value
BrowseName CodeTypeString
Subtype of String defined in OPC 10000-5.  

The values in the CodeTypeDataTye are extensible by individual manufacturers, starting with “CUSTOM:”. Predefined values are defined in Table 26

Table 26 – CodeType Values

Code Type Value ScanData Value field in union defined in 9.4.2 Data Type Description
“RAW:BYTES” ByteString ByteString AutoID Device specific raw data
“RAW:STRING” String String AutoID Device specific raw data to be interpreted as string
“EPC” Epc ScanDataEpc EPC binary structure as defined in 9.3.6
“UID” ByteString ByteString AutoID Identifier   according to ISO/IEC 18000-3 Mode 3, ISO/IEC 18000-63 and GS1 EPCglobal.
“GS1” ByteString ByteString Raw data containing application identifiers (AI) and data according to ISO/IEC 15418.
In case of RFID bit 0x17 of PC is not set. PC contains no AFI.
In case of barcode data start with macro 05 according ISO/IEC 15434.
“ASC” ByteString ByteString Raw data containing data identifiers (DI) and data according to ISO/IEC 15418.
In case of RFID bit 0x17 is set. PC contains AFI.
In case of barcode data start with macro 06 according ISO/IEC 15434.
“URI” String String URI, e.g. EPC string value according to “GS1 EPC Tag Data Standard 1.6”
Example ScanData String value: “urn:epc:id:sgtin:0614141.112345.400”
Also usable for other URIs
“CUSTOM:xxx” ByteString
String
Custom
ByteString
String
BaseDataType
Any custom defined value (“xxx” is a AutoID Device specific substring of arbitrary length).

Transponder as well as optical 2D-Codes are data carrier for information usually displayed in bits and bytes. But the contained information could be organized in a certain structure. How to do this in a norm conforming way is described in the standard ISO/IEC 15434 “Syntax for high capacity ADC Media” (ADC stands for Automatic Data Capture).

The two most prominent data structures in use are following the rules of GS1 and the ASC MH1. They are described in the standard ISO/IEC 15418 (Data Identifier and Application Identifier).

It is the purpose of these international standards to define the syntax for high capacity ADC media (such as transponder or 2D-Codes), in order to enable ADC users to utilize a single mapping utility, regardless of which high capacity ADC media is employed.

The interoperability of different data structures is achieved by the definition of a Message Header and a Format Header. While the Message Header defines the start and the end of the data contained, the Format Header indicates which data format is used.

Below two examples are shown for a GS1 and an ASC data format.

Example GS1

<Macro05>01312345123457GS1012345GS17101231

Interpretation by the Reader

]d1[)>RS05GS0134012345123457GS1012345GS17101231RSEOT

Example ASC MH 10

<Macro06>25PLEABCBQ3DGS1T234567GS14D101231

Interpretation by the Reader

]d1[)>RS06GS 25PLEABCBQ3DGS1T234567GS14D20101231RSEOT

For RFID the data structures are controlled by AFIs (lower 8 bits of PC) when ISO format is used according ISO/IEC 15961-2 and -3. Depending on the AFI different data compression methods may be used. Details are described for example in ISO 17363, 17364, 17365, 17366 and 17367.

Previous Next