A Uniform Resource Name (URN) Namespace for Foundation for Intelligent Physical Agents (FIPA)
RFC 3616
|
Document |
Type |
|
RFC - Informational
(September 2003; No errata)
|
|
Last updated |
|
2015-10-14
|
|
Stream |
|
ISE
|
|
Formats |
|
plain text
pdf
html
bibtex
|
Stream |
ISE state
|
|
(None)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Document shepherd |
|
No shepherd assigned
|
IESG |
IESG state |
|
RFC 3616 (Informational)
|
|
Telechat date |
|
|
|
Responsible AD |
|
Ted Hardie
|
|
Send notices to |
|
(None)
|
Network Working Group F. Bellifemine
Request for Comments: 3616 Telecom Italia Lab
Category: Informational I. Constantinescu
EPFL
S. Willmott
UPC
September 2003
A Uniform Resource Name (URN) Namespace for
Foundation for Intelligent Physical Agents (FIPA)
Status of this Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract
This document describes a Uniform Resource Name Namespace
Identification (URN NID) for the Foundation for Intelligent Physical
Agents (FIPA). This URN NID will be used for identification of
standard components published by the FIPA standards body in the area
of Agent technology.
Table of Contents
1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Specification Template. . . . . . . . . . . . . . . . . . . . 2
3. Namespace Considerations. . . . . . . . . . . . . . . . . . . 4
4. Community Considerations. . . . . . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
6. Security Considerations . . . . . . . . . . . . . . . . . . . 6
7. References. . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.1. Normative References. . . . . . . . . . . . . . . . . . 6
7.2. Informative References. . . . . . . . . . . . . . . . . 6
8. Authors' Addresses. . . . . . . . . . . . . . . . . . . . . . 7
9. Full Copyright Statement. . . . . . . . . . . . . . . . . . . 8
Bellifemine, et al. Informational [Page 1]
RFC 3616 URN Namespace for FIPA September 2003
1. Introduction
The Foundation for Intelligent Physical Agents (FIPA) was established
in 1996 in Geneva, Switzerland. FIPA is an international non-profit
association of companies and organizations dedicated to promoting the
industry of intelligent agents by openly developing specifications
supporting interoperability among agents and agent-based
applications. The core mission of the FIPA standards consortium is
to facilitate the interworking of agents and agent systems across
multiple vendors' platforms. Since its inception, FIPA has counted
more than 60 member companies from over 20 different countries
worldwide.
FIPA publishes technical specifications, schemas, diagrams and other
documentation related to the area of Agent technology. FIPA wishes
to create and manage globally unique, persistent, location-
independent identifiers for these resources.
2. Specification Template
Namespace ID:
"fipa"
Registration Information:
Version 1
Date: 2002-02-28
Declared registrant of the namespace:
Name: FIPA Secretariat (J. Kelly)
E-mail: secretariat@fipa.org
Affiliation: Foundation for Intelligent Physical Agents (FIPA)
Address: c/o Me Jean-Pierre Jacquemoud
2, rue Bellot
CH-1206 Geneve
Declaration of structure:
The identifier has a hierarchical structure as follows:
urn:<assigned number>:{subspace-id1}:{subspace-id2}:...
subspace-ids can be any US-ASCII string compliant with URI syntax
and not containing the ":" character. The subspaces are used to
divide the assigned namespace along one or more logical schemes.
Bellifemine, et al. Informational [Page 2]
RFC 3616 URN Namespace for FIPA September 2003
Examples of such schemes are:
* By standardization area:
urn:fipa:language:acl
urn:fipa:ontology:management
* By technical committee:
urn:fipa:architecture:example:directory
urn:fipa:architecture:example:greenpolicy
Relevant ancillary documentation:
None.
Identifier uniqueness considerations:
Assignment of URNs in the requested namespace will be managed by
the FIPA Architecture Board (FAB) which will ensure that URNs
assigned in the requested namespace are unique.
Identifier persistence considerations:
FIPA is committed to maintaining the availability and persistence
of all resources identified by assigned URNs.
Process of identifier assignment:
Assignment of URNs in the requested namespace will be managed by
the FIPA Architecture Board (FAB) which is responsible for
approval of all specifications published by FIPA.
Show full document text