Attributes should only be there if part of the name/address space
Tim Berners-Lee <timbl@w3.org> Tue, 18 February 1997 21:08 UTC
Received: from cnri by ietf.org id aa18639; 18 Feb 97 16:08 EST
Received: from services.Bunyip.Com by CNRI.Reston.VA.US id aa12719; 18 Feb 97 16:08 EST
Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id PAA18261 for uri-out; Tue, 18 Feb 1997 15:16:41 -0500 (EST)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.8.5/8.8.5) with SMTP id PAA18256 for <uri@services.bunyip.com>; Tue, 18 Feb 1997 15:16:39 -0500 (EST)
Received: from www10.w3.org by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA01012 (mail destined for uri@services.bunyip.com); Tue, 18 Feb 97 15:16:36 -0500
Received: from peak.w3.org (mountain.w3.org [18.29.0.122]) by www10.w3.org (8.7.5/8.7.3) with SMTP id PAA15956; Tue, 18 Feb 1997 15:15:33 -0500 (EST)
Message-Id: <3.0.32.19970218151607.0080d4d0@hq.lcs.mit.edu>
X-Sender: timbl@hq.lcs.mit.edu
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Tue, 18 Feb 1997 15:16:08 -0500
To: Erik Guttman <eguttman@ns.incog.com>, uri@bunyip.com
From: Tim Berners-Lee <timbl@w3.org>
Subject: Attributes should only be there if part of the name/address space
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-uri@bunyip.com
Precedence: bulk
At 04:25 PM 2/6/97 -0800, Erik Guttman wrote: >I am working on the Service Location Protocol (SLP). >We associate attributes with services. The services are >identified using a service: URL scheme. Since these >attributes have multiple values and may be quite extensive >in number and size we include a mechanism in SLP to register >and transfer them in replies outside of the URL. It may be >useful to include SLP attributes in the service: URL, >for small numbers of reasonably sized attributes. If I understand this correctly (if not correct me), the attributes are not needed in order to identify the services. The services have these attributed juts as web documents have titles and expiry dates. If this is the case, then under no circumstances should any information other than those needed to identify an object be included in the URL. If the information *is* needed to identify the object, then it must (clearly) be included in the URL. >The discussion makes it clear that attributes can be used >quite effectively in URLs, but only discusses single valued >attributes. I assume we are all happy with a single value being a list with some allowed delimiter. Tim Berners-Lee http://www.w3.org/People/Berners-Lee Director, World Wide Web Consortium http://www.w3.org MIT Laboratory for Computer Science, 545 Technology Square, Cambridge MA 02139 USA phone://1/617/253 5702 fax://1/617/258/5999
- Attributes should only be there if part of the na… Tim Berners-Lee
- Attributes should only be there if part of the na… Daniel LaLiberte
- Re: Attributes should only be there if part of th… Dan Connolly
- Re: Attributes should only be there if part of th… Larry Masinter
- Re: Attributes should only be there if part of th… Daniel LaLiberte
- Re: Attributes should only be there if part of th… Dan Connolly
- Re: Attributes should only be there if part of th… Larry Masinter
- Re: Attributes should only be there if part of th… Dan Connolly
- Re: Resources and Identifiers Dan Connolly
- Re: Resources and Identifiers Michael Mealling
- Resources and Identifiers Daniel LaLiberte
- Re: Resources and Identifiers Daniel LaLiberte