- From: Christopher B Ferris <chrisfer@us.ibm.com>
- Date: Fri, 19 Jul 2002 08:12:14 -0400
- To: Tim Bray <tbray@textuality.com>
- Cc: www-tag@w3.org
Tim,
Looking good. Some comments.
Nit in section 1.1: "The representations of a resource may vary as a
function of factors including time, place, and the
identity of the agent accessing the representation"
Seems to me that the agent accesses the 'resource' not the 'representation'
Then, further in that paragraph it says: "The representations of this
resource depend on (at least) time, the expressed
preference of the user for Fahrenheit or Celsius, and the identity of the
user-agent software requesting the
representation.".
which I do think is probably accurate. I think that one 'access a resource'
to 'retrieve a representation'.
Then, in section 1.1.1.2: "On the other hand, the URN scheme [RFC 2141]
does not have a built-in dereference
mechanism, and does not guarantee that a dereference procedure is provided
for any given URN."
What is a ' built-in' dereference mechanism? Built-in to what? Given that
work on DDDS[1] continues, I might offer
the following:
On the other hand, the URN scheme [RFC 2141] does not yet have a
widely deployed dereference
mechanism, and does not guarantee that a dereference procedure
is provided for any given URN.
Cheers,
Christopher Ferris
Architect, Emerging e-business Industry Architecture
email: chrisfer@us.ibm.com
phone: +1 508 234 3624
[1] http://www.ietf.org/internet-drafts/draft-ietf-urn-ddds-toc-03.txt
Tim Bray
<tbray@textuality To: www-tag@w3.org
.com> cc:
Sent by: Subject: Fixed Section 1.1 language
www-tag-request@w
3.org
07/16/2002 06:47
PM
Per my action item I updated the language in my draft of section 1.1 to
remove the special favor given to time among the many things on which
the representation of a resource can depend. Also I added an example
(something no section of the arch doc should be without).
At http://www.textuality.com/tag/s1.1.html -Tim
Received on Friday, 19 July 2002 08:19:30 UTC