Review of "Usage Patterns For Client-Side URL parameters" 2008-03-20

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Further to Action-119, herewith a brief review of "Usage Patterns For
Client-Side URL parameters", version dated 20 March 2008 [1].

This draft is intended only to make a start at the problem of
non-traditional usages of fragment-identifiers as client-side
parameters, by cataloguing existing usages.  As such it is very
valuable, although I'm not well placed to comment on the extent to
which it actually covers the space of such usages.

Some minor comments:

 1) At the end of section 2.1.3, the question about error processing
    doesn't make sense to me -- too many implicit steps left unspoken?

 2) In section 2.4, an example from the cited document would be
    helpful.

 3) I could use a tiny bit more detail, perhaps a trivial example, in
    section 2.6.

And one more substantial one: Section 2.1 has an extended analysis of
the pattern it describes, in the form of concluding subsections named
"Things to Note", "Extrapolating from this Pattern" and "Architectural
Questions".  Sections 2.2 through 2.6 would greatly benefit from the
same detail.

ht

[1] http://www.w3.org/2001/tag/doc/hash-in-url
- -- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
                         Half-time member of W3C Team
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 651-1426, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFIv+gFkjnJixAXWBoRAp3EAJ0YrrMUN7wBoZ/rG2PVnsfb0mgICgCdHeeB
po0h1/rarsK93CtsENt5/mk=
=eBR/
-----END PGP SIGNATURE-----

Received on Thursday, 4 September 2008 13:52:44 UTC