- markup (76)
- xml (11)
- xslt (23)
- pipelines (8)
- atom (9)
- overlapping markup (6)
- schema (11)
- creole (5)
- dtll (1)
- xforms (1)
- xpath (1)
- xquery (2)
- coding (2)
- datagovuk (1)
- genealogy (4)
- hardware (1)
- linked data (16)
- modelling (1)
- named graphs (1)
- opendata (1)
- provenance (1)
- psi (3)
- skos (1)
- sparql (4)
- Talis (7)
- unicode (1)
- uri (4)
- versioning (1)
- visualisation (6)
- web (78)
- google (4)
- html5 (5)
- jQuery (2)
- rdf (46)
- ontologies (2)
- rdfa (8)
- rdfQuery (5)
- rest (6)
- wikis (1)
- work (3)
- legislation (2)
- xmlsummerschool09 (2)
- life (28)
- children (5)
- equality (6)
- gtd (1)
- environment (4)
- gadgets (5)
- software (3)
- xlinq (2)
- conferences (11)
- ukgc09 (1)
- xtech (9)
- xtech2008 (3)
- blog (8)
- drupal (3)
Content negotiation for getting meta data.
"...a set of URIs that are explicitly intended to be used as unique identifiers..."
"If you request one of these URIs, ..., you will get some information about that bit of legislation..."
Sorry, I realise this is, at best, very tangential to your main point but I really think doing a request on a URI should either return a representation of the resource or should redirect to information about the resource. It shouldn't return a representation of something else (e.g., information about the original resource). I think it's an abuse of the content negotiation mechanism to use it to distinguish between a request for a resource and a request for metadata about that resource.
On the other hand, I don't have a better suggestion. I first asked the TAG about this a while ago:
http://lists.w3.org/Archives/Public/www-tag/2007Aug/0075.html
and they seem to have recently decided it's something worth talking about:
http://www.w3.org/2001/tag/group/track/issues/62
Still, I'm not going to hold my breath.