- 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)
Re: Your Website is Your API: Quick Wins for Government Data
Thanks Jeni, for a very helpful post. It prompts a couple of questions which are probably well-trodden ground, but unclear to me still:
1) whatever happened to URNS - don’t we want something like urn:ukco:00445790 to refer to the company itself, rather than use the URI http://www.companieshouse.gov.uk/id/company/00445790 which is really an identifier of Company House’s ‘view’ of that company. How would a URN scheme be used or retrofitted if it was available?
2) if URIs are supposed to be “short, clean, readable, hackable”, why isn’t the representation hackable too, best practice requiring content negotiation instead of a suffix?
Chris