Browse Prior Art Database

Definition of an X.500 Attribute Type and an Object Class to Hold Uniform Resource Identifiers (URIs) (RFC2079)

IP.com Disclosure Number: IPCOM000002631D
Original Publication Date: 1997-Jan-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 4 page(s) / 8K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Smith: AUTHOR

Abstract

Uniform Resource Locators (URLs) are being widely used to specify the location of Internet resources. There is an urgent need to be able to include URLs in directories that conform to the LDAP and X.500 information models, and a desire to include other types of Uniform Resource Identifiers (URIs) as they are defined. A number of independent groups are already experimenting with the inclusion of URLs in LDAP and X.500 directories. This document builds on the experimentation to date and defines a new attribute type and an auxiliary object class to allow URIs, including URLs, to be stored in directory entries in a standard way.

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 37% of the total text.

Network Working Group M. Smith

Request for Comments: 2079 Netscape Communications

Category: Standards Track January 1997

Definition of an X.500 Attribute Type and an Object Class to Hold

Uniform Resource Identifiers (URIs)

Status of this Memo

This document specifies an Internet standards track protocol for the

Internet community, and requests discussion and suggestions for

improvements. Please refer to the current edition of the "Internet

Official Protocol Standards" (STD 1) for the standardization state

and status of this protocol. Distribution of this memo is unlimited.

Abstract

Uniform Resource Locators (URLs) are being widely used to specify the

location of Internet resources. There is an urgent need to be able

to include URLs in directories that conform to the LDAP and X.500

information models, and a desire to include other types of Uniform

Resource Identifiers (URIs) as they are defined. A number of

independent groups are already experimenting with the inclusion of

URLs in LDAP and X.500 directories. This document builds on the

experimentation to date and defines a new attribute type and an

auxiliary object class to allow URIs, including URLs, to be stored in

directory entries in a standard way.

Background and Intended Usage

Uniform Resource Locators (URLs) as defined by [1] are the first of

several types of Uniform Resource Identifiers (URIs) being defined by

the IETF. URIs are widely used on the Internet, most notably within

Hypertext Markup Language [2] documents. This document defines an

X.500 [3,4] attribute type called labeledURI and an auxiliary object

class called labeledURIObject to hold all types of URIs, including

URLs. These definitions are designed for use in LDAP and X.500

directories, and may be used in other contexts as well.

Schema Definition of the labeledURI Attribute Type

Name: labeledURI

ShortName: None

Description: Uniform Resource Identifier with optional label

OID: umichAttributeType.57 (1.3.6.1.4.1.250.1.57)

Syntax: caseExactString

SizeRestriction: None

SingleValued: False

Discussion of the labeledURI Attribute Type

The labeledURI attribute type has the caseExactString syntax (since

URIs are case-sensitive) and it is multivalued. Values placed in the

attribute should consist of a URI (at the present time, a URL)

optionally followed by one or more space characters and a label.

Since space characters are not allowed to appear un-encoded in URIs,

there is no ambiguity about where the label begins. At the present

time, the URI portion must comply with the URL specification [1].

Multiple labeledURI values will generally indicate different

resources that are all related to the X.500 object, but may indicate

different locations for the same resource.

The label is used to descri...