redirect with fragid (was Re: Draft TAG telcon minutes of 2010-09-02 available)

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

What I find odd about the particular example we discussed is that the
URI in the redirection
  
 http://dublincore.org/2008/01/14/dcterms.rdf#title

doesn't make _any_ sense on its own.  That is, presented with just
that URI, I don't think you can find out anything.  None of the nodes
in the RDF graph corresponding to

 http://dublincore.org/2008/01/14/dcterms.rdf

are labelled with any variant of that URI, as far as I can see.

So it's _only_ if you know that you are following a redirection from

 http://purl.org/dc/terms/title

that the ...#title URI makes any sense.  I don't think that's
consistent with the way URIs are meant to work, and I wouldn't want
whatever ends up being said in HTTPbis, supposing some form of change
does in fact happen in this area, to suggest that it is.

ht
- -- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
      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 from me _always_ has a .sig like this -- mail without it is forged spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFMhLBgkjnJixAXWBoRAr6TAJ9G34OHSGPTYaiZ5cTsobocCDG6gACePPY1
BQ+93IwiukQu1tn4ElH3YLU=
=zsIi
-----END PGP SIGNATURE-----

Received on Monday, 6 September 2010 09:12:31 UTC