Browse Prior Art Database

A Uniform Resource Name (URN) Namespace for Federated Content (RFC4198)

IP.com Disclosure Number: IPCOM000131703D
Original Publication Date: 2005-Nov-01
Included in the Prior Art Database: 2005-Nov-16
Document File: 8 page(s) / 12K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

D. Tessman: AUTHOR

Abstract

This document describes a URN (Uniform Resource Name) namespace for identifying content resources within federated content collections. A federated content collection often does not have a strong centralized authority but relies upon shared naming, metadata, and access conventions to provide interoperability among its members.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 23% of the total text.

Network Working Group                                         D. Tessman
Request for Comments: 4198                                      Zelestra
Category: Informational                                    November 2005


     A Uniform Resource Name (URN) Namespace for Federated Content

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 (2005).

Abstract

   This document describes a URN (Uniform Resource Name) namespace for
   identifying content resources within federated content collections.
   A federated content collection often does not have a strong
   centralized authority but relies upon shared naming, metadata, and
   access conventions to provide interoperability among its members.

1.  Introduction

   Federated content collections are often loose constructs of both
   small and large content providers, with an active community, but
   without significant central authority.  Members are bound together by
   shared purpose and interoperate through shared naming, metadata, and
   access conventions.  Federations may also consist of other
   federations, creating complex associations and dependencies.

   A content provider may join or leave a federation at any time and may
   be part of more than one federation at the same time.  Content
   providers may also cease as organizations altogether, freeing their
   domain names for use by others.  In addition, content identifiers are
   spread throughout the members of a federation.  These identifiers are
   stored on various media, sometimes for long durations before being
   used.  Therefore, although they work well in situations without a
   strong content naming authority, URLs are insufficient as content
   identifiers within a federation because they cannot be uniquely and
   permanently tied to a specific content resource.

Tessman                      Informational                      [Page 1]
RFC 4198          URN Namespace for Federated Content      November 2005


   This URN namespace provides a mechanism whereby a central naming
   authority is not required.  Providers maintain naming authority over
   their own content within guidelines that guarantee URNs to be unique
   and permanent.

   A simple identifier resolution convention is also recommended to
   provide a consistent URN resolver interface across all providers.

   This namespace specification is for a formal namespace.

2.  Terminology

   In this document, the key words "MUST", "MUST NOT", "REQUIRED",
   "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
   and "OPTIONAL" ar...