W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > July to September 1998

New Advanced Collection Requirements Draft

From: Slein, Judith A <JSlein@crt.xerox.com>
Date: Fri, 24 Jul 1998 10:51:28 -0400
Message-ID: <201BB34B3A73D1118C1F00805F1582E8B76BE9@x-wb-0128-nt8.wrc.xerox.com>
To: "'w3c-dist-auth@w3.org'" <w3c-dist-auth@w3.org>
A new revision of the Advanced Collection Requirements draft is now
available on the Internet-Drafts directory:


This revision reflects the discussions at Redmond:

1. The "internal member" (directly contained) terminology has been
References are contrasted with ordinary resources that have content,
not with internal collection members.  

2. State explicitly that the requirements are silent on how the server
maintains referential integrity.

3. State explicitly that there is no requirement that references be

4. The notion of referencing has been separated from the notion of
collections as far as possible.  There are still a few requirements that
relate to references only in the context of collections, but for the
most part the requirements for referencing can be states without mention
of collections.  

5. Ordered Collection Requirements -- No Changes.  Ordered collection
requirements were uncontroversial at Redmond.  The restriction to a
single ordering per collection was revisited and confirmed.  If
additional orderings are desired, they can be achieved by created
separate collections with those orderings (though this would be a
maintenance headache) or on the client side. The suggestion that there
be a requirement relating to scalability and performance was rejected on
the grounds that this is motherhood and can be assumed for any protocol
specification, and that metrics are too difficult to define.

In addition, this revision of the requirements introduces the concepts
of direct vs. indirect references, based on suggestions from Jim Davis
and Roy Fielding.  It tries to state clearly which requirements apply to
direct references, and which to indirect references.

The distinction between strong and weak references also stayed in the

The requirements say, however, that the initial collections protocol is
not expected to support either strong references or direct references.

Judith A. Slein
Xerox Corporation
800 Phillips Road 105/50C
Webster, NY 14580
Received on Friday, 24 July 1998 10:52:52 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:17 UTC