The tagencoding
URI is therefore intended for low-level applications which need to write EPCs to
tags or physically sort items based on packaging level. The pure-identity URI format isolates
the application software from details of the bit length of the tags or any fast ?¬?ltering values.
The Tag Data Translation Speci?¬?cation (EPCglobal, 2006b) provides a machine-readable
version of the EPC Tag Data Standards speci?¬?cation. The machine-readable version can be
readily used for validating EPC formats as well as translating between different levels of
representation in a consistent way. This speci?¬?cation describes how to interpret the machinereadable
version. It contains details of the structure and elements of the machine-readable
markup ?¬?les and provides guidance on how it might be used in automatic translation or
validation software, whether standalone or embedded in other systems.
Tag Data Translation capabilities may be implemented at any level of the EPC Network
stack. Tag Data Translation converts between different levels of representation of the EPC
and may make use of external tables. It is envisaged that Tag Data Translation software
will be able to keep itself up-to-date by periodically checking for and downloading TDT
markup ?¬?les, although a continuous network connection should not be required for
performing translations or validations, since the TDT markup ?¬?les and any auxiliary tables
can be cached between periodic checks; in this way, a generic translation mechanism can be
extensible to further coding schemes or variations for longer tag lengths, which may be
introduced in the future.
Pages:
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77