- From: Norman Walsh <Norman.Walsh@Sun.COM>
- Date: Fri, 19 Sep 2003 18:19:05 -0400
- To: www-tag@w3.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Technical comments through section 2.
In section 2.6, I don't much like the ambiguity example immediately
after the "URI ambiguity" good practice. It feels to me like it's
trying to demonstrate not only the ambiguity problem, but it's also
trying to prejudice the httpRange-14 question by hinting that the
problem is using the HTTP URIs of the corporations to identify the
corporations.
The Moby Dick paragraph that follows also seems a little stranded. It
makes a bunch of statements about what the URI might identify, but
doesn't go on to say anything about what those statements mean or what
the creator should do about it.
Everything else through Section 2 looks ok. Fantastic.
Be seeing you,
norm
- --
Norman.Walsh@Sun.COM | The shoe that fits one person pinches
XML Standards Architect | another; there is no recipe for living that
Web Tech. and Standards | suits all cases.--Jung
Sun Microsystems, Inc. |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iD8DBQE/a4DZOyltUcwYWjsRAhMUAJ445TLaN3rnawm+hfPTHGcBYU8d4ACgonJg
LWsmAoAbxY993vO45jyS51k=
=cnO7
-----END PGP SIGNATURE-----
Received on Friday, 19 September 2003 18:22:20 UTC