Comment #00731 - Addition of ucode to the URI Identifier List - NFCForum-TS-RTD_URI_1.0_feedback.pdf

Comment 731
Closed (Resolved)
NFCForum-TS-RTD_URI_1.0 - For Feedback Only (Revision 0)
Comment Submitted by
Peter Coster
2012-01-16 22:11:28
Toppan Forms along with YRP and VTT would like to see the inclusion of an identifier for the ucode developed by YRP Ubiquitous Networking Laboratory include in the URI Identifier Code list. The ucode is a 128-bit code used to identify everything and similar to the EPCglobal Incís coding system. Ucodes can be issued for physical and virtual objects as well as abstract ideas. The ucode has a system in place to extend it past the 128-bit length when all the numbers have expired.

The ucode is a key piece to the ubiquitous networking which is gaining popularity around the world, specifically in North Asia and Scandinavia.

A new ID scheme based on using the "ucode" is being proposed as a global standard of the ITU-T and is expected to be officially recognized in late Q2 2012. A current proposal called H.IDscheme at ITU-T SG16, which includes ucode, will be put into AAP (Altenative Approval Process) in May 2012, which is a fast-track approval method of technical standard in an accelerated manner for today's fast-paced ICT environment barring any major objections.

Can the ucode identifier be entered into the URI Identifier Code list in the URI Specification?
Supporting File: NFCForum-TS-RTD_URI_1.0_Updated URI Identifier Code.doc
Submitter Proposed Solution
A line be added to Table 3 in section 3.2.2 as:
36 0x24 urn:ucode:
Developer Response
The proposal to add an abbreviation for ucode to table 3 of the URI RTD has been discussed in the Reference Application working group and be rejected for the following reasons: a) The URI RTD allows to encode a ucode URI by using the 'urn:' abbreviation code followed byte the 'ucode:' namespace. The overhead of 6 byte (length of 'ucode:') should be accepatable given that the 16 byte ucode itself is coded in 32 bytes. b) An update of the URI RTD would require a major change to the specification and could not be justified by the marginal gain in coding efficiency.