Internet DRAFT - draft-odette-ianaurnjaif
draft-odette-ianaurnjaif
INTERNET-DRAFT J. Walther
Intended Status: INFORMATIONAL (Odette International)
Expires: 2017-11-11 2017-05-10
URN Namespace for the Joint Automotive Industry Forum
draft-odette-ianaurnjaif-00
Abstract
This document describes a Uniform Resource Name (URN) namespace used
by the Joint Automotive Industry Forum (JAIF) for naming or
identifying information entities in the automotive industry,
including identifiers for parts, returnable transport items, shipping
units and elements of XML schemas or EDI guidelines and other
documents.
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
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/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
Copyright and License Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
J. Walther Expires 2017-11-11 [Page 1]
INTERNET DRAFT urn "jaif" 2017-05-10
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Completed Namespace Specification Template . . . . . . . . . . 3
3.1. Namespace ID: . . . . . . . . . . . . . . . . . . . . . . . 3
3.2. Registration information: . . . . . . . . . . . . . . . . . 3
3.3 Declared registrant of the namespace: . . . . . . . . . . . 3
3.4 Declaration of syntactic structure: . . . . . . . . . . . . 3
3.5. Relevant ancillary documentation: . . . . . . . . . . . . . 4
3.6. Identifier uniqueness considerations: . . . . . . . . . . . 4
3.7. Identifier persistence considerations: . . . . . . . . . . 4
3.8. Process of identifier assignment: . . . . . . . . . . . . . 4
3.9. Process of identifier resolution: . . . . . . . . . . . . . 4
3.10. Rules for Lexical Equivalence: . . . . . . . . . . . . . . 4
3.11. Conformance with URN Syntax: . . . . . . . . . . . . . . . 5
3.12. Validation mechanism: . . . . . . . . . . . . . . . . . . 5
3.13. Scope: . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Namespace Considerations . . . . . . . . . . . . . . . . . . . 5
6. Community Considerations . . . . . . . . . . . . . . . . . . . 5
7. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
9.1. Normative References . . . . . . . . . . . . . . . . . . . 6
Appendix A. Acknowledgement . . . . . . . . . . . . . . . . . . . 6
Author's Address: . . . . . . . . . . . . . . . . . . . . . . . . 6
J. Walther Expires 2017-11-11 [Page 2]
INTERNET DRAFT urn "jaif" 2017-05-10
1. Introduction
The Joint Automotive Industry Forum consists of the automotive
industry associations AIAG (USA), JAMA and JAPIA (Japan) and Odette
Europe). It provides a collaboration platform for the development of
global guidelines for logistics processes, data exchange and best
practices in the automotive supply chain.
The JAIF wishes to use a unique URN to qualify information attributes
used in various data exchange scenarios, specifically in the exchange
of event information captured by auto-ID technologies such as
barcodes or Radio Frequency Identifiers (RFID).
2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
3. Completed Namespace Specification Template
3.1. Namespace ID:
"jaif"
3.2. Registration information:
Registration version number: 1
Registration Date: 2017-05-10
3.3 Declared registrant of the namespace:
Organisation: Odette International
Address: 71 Great Peter Street London SW1P 2BN
United Kingdom
Email: jwalther@odette.org
3.4 Declaration of syntactic structure:
The Namespace Specific String (NSS) of all URNs assigned by the JAIF
will have the following hierarchical structure:
urn:jaif:{category}:{string}
where the "category" is a US-ASCII string that conforms to URN syntax
J. Walther Expires 2017-11-11 [Page 3]
INTERNET DRAFT urn "jaif" 2017-05-10
requirements , and "{string}" is a string that conforms to URN syntax
requirements .
3.5. Relevant ancillary documentation:
The JAIF provides information on registration for each URN. The
specifications and registration information are publishedat
https://www.odette.org.
3.6. Identifier uniqueness considerations:
The JAIF will manage resources using the "jaif" NID and will be the
authority for managing the "jaif-urn" strings. In the associated
procedures, JAIF will ensure the uniqueness of the strings themselves
or MAY permit secondary responsibility for management of well-defined
sub-trees.
3.7. Identifier persistence considerations:
The JAIF is committed to maintaining the accessibility and
persistence of all resources that are officially assigned URNs by the
member organizations.
JAIF will provide clear documentation of the registered uses of the
"jaif" NID. This will be structured such that each "jaif-urn", if
needed, will have a separate description and registration table.
The registration tables and information will be published and
maintained by JAIF in appropriate documents and published on its
members' web sites.
3.8. Process of identifier assignment:
All the assignments of identifiers are fully controlled and managed
by the JAIF.
3.9. Process of identifier resolution:
The namespace is not listed with an RDS; this is not relevant.
3.10. Rules for Lexical Equivalence:
The "{category}" is case-insensitive. Thus, the portion of the URN:
urn:jaif:{category}:
is case-insensitive for matches. The remainder of the identifier
shall be considered case-sensitive. Consequently, URNsare only
J. Walther Expires 2017-11-11 [Page 4]
INTERNET DRAFT urn "jaif" 2017-05-10
lexically equivalent if they are also lexically identical in the
remaining {string} field.
3.11. Conformance with URN Syntax:
No special considerations.
3.12. Validation mechanism:
None specified. URN assignment will be handled by procedures
supported and maintained by the JAIF.
3.13. Scope:
Global.
4. Examples
The following examples are not guaranteed to be real. They are
provided for pedagogical reasons only.
urn:jaif:rfid:eventID
urn:jaif:edi:codelist:JAI016
urn:jaif:rti:type:2467
5. Namespace Considerations
The JAIF is developing a variety of B2B recommendations. Some of
these require information entities to be fully qualified. For proper
operation, descriptions of the exchanged information must exist and
be available in a unique, reliable, and persistent manner.
As JAIF recommendations and specifications cover many technical
areas, the possibility of using various other namespace repositories
has been deemed impractical. Each object or description, as defined
in the JAIF, could possibly be related to multiple different other
namespaces. The JAIF wishes to avoid any potential conflict with
other namespaces by maintaining its own namespace hierarchy for those
objects.
6. Community Considerations
The objects and descriptions produced by the JAIF and necessary for
compliant implementation or system development are generally
available to its membership and to other organizations.
J. Walther Expires 2017-11-11 [Page 5]
INTERNET DRAFT urn "jaif" 2017-05-10
7. Security Considerations
There are no security considerations other than those normally
associated with the use and resolution of URNs in general.
8. IANA Considerations
IANA registers a new URN NID with the registration information
provided in Section 2.
"jaif" strings are managed by the JAIF. Thus, creating a new urn
within the "jaif" namespace does not require any IANA action.
9. References
9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
Appendix A. Acknowledgement
Thanks to Rob Exell and Thomas Grabscheit for their feedback and
review.
Author's Address:
Joerg WALTHER
Odette International Ltd.
71 Great Peter Street
London
SW1P 2BN
United Kingdom
EMail: jwalther@odette.org
J. Walther Expires 2017-11-11 [Page 6]
