[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
A URN NID for the EPCglobal Electronic Product Code (EPC)
Hi everyone,
This NID has been developed by EPCglobal which is a joint effort
between the Uniform Code Council (UCC) and EAN to develop network
standards for e-commerce. UCC and EAN are the assignment authorities for
UPC codes around the world and are the caretakers of the EPCglobal
Network standards process that is developing the EPC, RFID hardware and
RF standards, and the data exchange and network infrastructure needed to
allow applications such as Track and Trace of products, chain of
custody/pedigree, and shrink prevention through greater inventory
visibility.
The drafts repository is currently closed due to the upcoming IETF
meeting so this draft won't be available until a few days afterward.
-MM
Network Working Group M. Mealling
Internet-Draft Refactored Networks, LLC
Expires: August 22, 2005 February 18, 2005
A Uniform Resource Name Namespace For The EPCglobal Electronic
Product Code (EPC)
draft-mealling-epc-urn-00.txt
Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026 except that the right to
produce derivative works is not granted.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 22, 2005.
Copyright Notice
Copyright (C) The Internet Society (2005). All Rights Reserved.
Abstract
This document describes a URN namespace that will identify various
objects within the EPCglobal system for identifying products within
ecommerce and supply chain management applications.
1. Introduction
The EPCglobal Network is set of specifications for reading, managing
and acting on product codes plus other sensor data as the products
pass through a supply chain. Events and metadata about a product are
Mealling Expires August 22, 2005 [Page 1]
Internet-Draft The EPC URN February 2005
stored in EPC Information Services (EPC-IS) that are essentially web
services that implement agreed upon schema and services.
Each item that is tracked by the EPC Network is identified by one or
more managed identifiers. In many cases these identification systems
existed prior to the Internet becoming widely used. One such
namespace is the Global Trade Item Number, or GTIN. GTINs are widely
used in global commerce and are managed jointly by the European
Article Numbering (EAN) Association and the Uniform Code Council
(UCC). In order for the EPC Network to fully apply the Internet to
the EPC Network, the GTIN namespace (and others such as Global
Location Numbers (GLNs), Serialized Shipping Container Code (SSCC),
etc) need to be brought into the URI system of identifiers.
GTINs, GLNs and SSCCs are all managed by the EAN.UCC partnership
known as EPCglobal, Inc. For these, and possibly future namespaces,
a single Uniform Resource Name (URN) Namespace ID (NID) is being
requested: 'epc'. Each of the namespaces mentioned will have a
separate sub-space beneath the top level 'epc' NID.
In addition to existing supply chain naming systems, the EPC Network
will require new namespaces for naming system components. In many
cases the EPC Network is XML [10] based and as such will require
naming schemes for its XML schema [8] and various namespaces [9].
Since the EPC Network is engineered for wide spread and general use,
this namespace specification is a formal one and the namespace ID
that is being requested is 'epc'. It is important to note that it is
the explicit intent that various sub-namespaces actually name real,
physical objects and/or corporeal entities.
2. Specification Template
Namespace ID:
"epc" requested.
Registration Information:
Registration Version Number: 1
Registration Date: 2005-02-15
Declared registrant of the namespace:
EPCglobal, Inc. is a joint venture of EAN and the UCC
Mealling Expires August 22, 2005 [Page 2]
Internet-Draft The EPC URN February 2005
Princeton Pike Corporate Center
1009 Lenox Drive, Suite 202
Lawrenceville, NJ 08648, USA
msouthall at epcglobalus.org
Tel: +1-609-620-4542
Declaration of structure:
The 'epc' namespace is a set of sub-namespaces that can be
extended in the future. The following ABNF defines how the
sub-namespaces are identified and any restrictions on their
syntax (definitions not specified below can be found in RFC
2141 [1]):
EPC-URN = "urn:epc:" sub-namespace-name ":" sub-namespace
sub-namespace-name = <let-num> [ 1*<let-num-hyp> ]
sub-namespace = <URN chars>
For example, the sub-namespace 'sgtin' has the following
definition (this ABNF is non-normative):
SGTIN-URI = "urn:epc:id:sgtin:" SGTINURIBody
SGTINURIBody = 2*(PaddedNumericComponent ".") NumericComponent
NumericComponent = ZeroComponent | NonZeroComponent
ZeroComponent = "0"
NonZeroComponent = NonZeroDigit *Digit
PaddedNumericComponent = *Digit
Digit = "0" | NonZeroDigit
NonZeroDigit = "1" | "2" | "3" | "4" | "5" | "6" | "7" | "8" | "9"
This equates to a namespace that has three period separated
series of digits:
urn:epc:id:sgtin:900100.0003456.1234567
The first series is a manufacturer id, the 2nd denotes a
product made by that manufacturer and the third is a serial
number for a specific instance of that product.
There are numererous other namespaces. Their definitions can
be found in the EPC "Tag Data Standards" [7] definition as well
as other EPC Network specifications.
Relevant ancillary documentation:
Mealling Expires August 22, 2005 [Page 3]
Internet-Draft The EPC URN February 2005
The standards that define the EPCglobal Network and the
processes for creating new sub-namespaces are managed by
EPCglobal, Inc and can be found on its website. Several
sub-namespaces are defined in the "EPC Tag Data Standards" [7]
and the "PML Core Specification 1.0" [6] specifications.
Identifier uniqueness considerations:
The namespaces that make up the 'epc' namespace are all managed
by an organization with almost 50 years of namespace management
experience. In all cases (existing or new) the uniqueness of
each namespace is an inherent part of the EPCglobal Network.
Identifier persistence considerations:
The assignment process guarantees that names are not reassigned
and that the binding between the name and and its resource is
permanent, regardless of any standards or organizational
changes.
Process of identifier assignment:
Names are assigned by the EPCglobal standards publication
process and by any entities that are sub-delegated by
EPCglobal. It is important to note that in many cases the
names assigned will explicitly denote physical objects and not
an electronic representation of that object. For example, a
'get' type operation on some identifiers can cause a physical
object to be transported from one phyiscal location to another.
Process of identifier resolution:
Certain sub-namespaces are resolved via the Object Naming
Service which is defined in "Auto-ID Object Naming Service
(ONS) 1.0" [5] which is a valid implementation of the Dynamic
Delegation Discovery System that is defined in RFC 3401 [4].
Rules for Lexical Equivalence:
The entire URN is case-sensitive.
Conformance with URN Syntax:
There are no additional characters reserved except as noted in
the ABNF above.
Mealling Expires August 22, 2005 [Page 4]
Internet-Draft The EPC URN February 2005
Validation mechanism:
In the case of each sub-namespace there will be namespace
specific rules for determining validity. In each case the
reader is referred to the appropriate EPC Global maintained
documentation.
Scope:
Global
3. IANA Considerations
This document includes a URN Namespace registration that is to be
entered into the IANA registry for URN NIDs.
4. Community Considerations
The EPCglobal Network is intended to bring the Internet to the world
of supply chain management and beyond. It can be used to tie
physical objects to their virtual descriptions and as such has many
wide ranging applications for the average Internet use. Thus it is
very much the intent that this namespace and the entire EPCglobal
Network consider the entire Internet as the scope of its community.
5. Security Considerations
The EPCglobal Network is based almost exclusively on Internet and Web
standards. Thus the security impacts of each of its underlying
technologies should be examined for weaknesses and threats. The
primary threats will come from the fact that these names will
identify physical things that can be of high value, thus the
temptation to spoof metadata about that identifier (its cost, size,
etc) will be much greater. Therefore the role of digital signatures,
secure resolution mechanisms and trust relationships is very
fundamental to the system.
6. References
6.1 Normative References
[1] Moats, R., "URN Syntax", RFC 2141, May 1997.
[2] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997.
[3] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource
Mealling Expires August 22, 2005 [Page 5]
Internet-Draft The EPC URN February 2005
Identifiers (URI): Generic Syntax", RFC 2396, August 1998.
[4] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part
One: The Comprehensive DDDS", RFC 3401, October 2002.
[5] Mealling, M., "EPCglobal Network Object Name Service (ONS) 1.0",
EPCglobal ONS 1.0, August 2003,
<http://www.epcglobalinc.org/standards_technology/Secure/v1.0/WD
-ons-1.0-20030930.pdf>.
[6] EPCglobal, Inc., "PML Core Specification 1.0", EPCglobal PML
1.0, September 2003,
<http://www.epcglobalinc.org/standards_technology/Secure/v1.0/PM
L_Core_Specification_v1.0.pdf>.
[7] EPCglobal, Inc., "EPC(tm) Tag Data Standards Version 1.1, Rev
1.22", EPCglobal Tag Data Standards 1.1, Feburary 2004,
<http://www.epcglobalinc.org/standards_technology/specifications
.html>.
6.2 Non-normative References
[8] Maloney, M., Beech, D., Thompson, H. and N. Mendelsohn, "XML
Schema Part 1: Structures Second Edition", W3C
REC REC-xmlschema-1-20041028, October 2004.
[9] Tobin, R., Hollander, D., Layman, A. and T. Bray, "Namespaces
in XML 1.1", W3C REC REC-xml-names11-20040204, February 2004.
[10] Yergeau, F., Paoli, J., Sperberg-McQueen, C., Bray, T. and E.
Maler, "Extensible Markup Language (XML) 1.0 (Third Edition)",
W3C REC REC-xml-20040204, February 2004.
Author's Address
Michael Mealling
Refactored Networks, LLC
1635 Old Hwy 41
Suite 112, Box 138
Kennesaw, GA 30152
US
Phone: +1 678 581 9656
Email: michael at refactored-networks.com
URI: http://www.refactored-networks.com
Mealling Expires August 22, 2005 [Page 6]
Internet-Draft The EPC URN February 2005
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP 11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
Full Copyright Statement
Copyright (C) The Internet Society (2005). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
Mealling Expires August 22, 2005 [Page 7]
Internet-Draft The EPC URN February 2005
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
Mealling Expires August 22, 2005 [Page 8]
--
Michael Mealling Refactored Networks, LLC
CEO & President 1645 Old Hwy 41
Office: +1-678-581-9656 Suite 112, Box 138
Cell: +1-678-640-6884 Kennesaw, GA 30152
http://refactored-networks.com/