RFC 3616

RFC 3616: A Uniform Resource Name (URN) Namespace for Foundation for Intelligent Physical Agents (FIPA) 🦋

okay bestie, the title block is giving organized. It's an Informational RFC from the Network Working Group, dated September 2003. The authors are Fabio Bellifemine (Telecom Italia Lab), Ion Constantinescu (EPFL), and Steven Willmott (UPC). It doesn't list anything it obsoletes or updates, so it's a fresh start 🌸

Status of this Memo 📜

This memo gives information to the Internet community. It is not an Internet standard of any kind, and distribution of this memo is unlimited ✨

Copyright Notice ©️

Copyright (C) The Internet Society (2003). All Rights Reserved.

Abstract 💜

okay so this document describes a Uniform Resource Name Namespace Identification (URN NID) for the Foundation for Intelligent Physical Agents (FIPA). FIPA's URN NID is going to be used to identify 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

1. Introduction 🎀

The Foundation for Intelligent Physical Agents (FIPA) was established in 1996 in Geneva, Switzerland. It's an international non-profit association of companies and organizations, and it's dedicated to promoting the intelligent agents industry by openly developing specifications that support interoperability among agents and agent-based applications 💅

Its core mission is to help agents and agent systems work together across multiple vendors' platforms. Since it started, FIPA has counted more than 60 member companies from over 20 different countries worldwide. That's a whole international glow-up 🌍✨

FIPA publishes technical specifications, schemas, diagrams, and other documentation about Agent technology. It wants to create and manage globally unique, persistent, location-independent identifiers for these resources, and that is what this namespace is for 🔥

2. Specification Template 🧚

Here's the official template, bestie. Every field is a little piece of the puzzle 🧩

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 like this 🌳

urn:<assigned number>:{subspace-id1}:{subspace-id2}:...

The subspace-ids can be any US-ASCII string that follows URI syntax, as long as it doesn't contain the ":" character. The subspaces are used to split the assigned namespace along one or more logical schemes. Lowkey genius 🧠

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 is managed by the FIPA Architecture Board (FAB), which makes sure that the URNs assigned in the requested namespace are unique. Main character energy 👑

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 is managed by the FIPA Architecture Board (FAB), which is responsible for approving all specifications published by FIPA.

Process for identifier resolution:

FIPA maintains published lists of assigned identifiers on its web pages at http://www.fipa.org.

Rules for Lexical Equivalence:

URNs are lexically equivalent if they are lexically identical. Simple, clean, iconic 💜

Conformance with URN Syntax:

• No special considerations.

Validation mechanism:

• None specified.

Scope:

• Global.

---

9. Full Copyright Statement 💅

Copyright (C) The Internet Society (2003). All Rights Reserved. 🌸

okay so the vibe here is: you can copy this doc and share it with literally anyone, and you can make derivative works that comment on it, explain it, or help people implement it. You can publish and distribute all of that, in whole or in part, with no restrictions of any kind 🎀. The one condition is that the copyright notice and this paragraph have to be included on every copy and every derivative work.

The one thing you can't do is change this document itself. You can't remove the copyright notice, and you can't take out the references to the Internet Society or other Internet organizations. The exceptions are when you need it for developing Internet standards, in which case you have to follow the copyright procedures in the Internet Standards process, or when you need to translate it into a language other than English 🌈.

The limited permissions above are perpetual. The Internet Society and its successors or assignees will never revoke them ♾️💖.

This document and the information in it 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 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE 💀.

---

Acknowledgement 🫶

Funding for the RFC Editor function is currently provided by the Internet Society ✨.