- 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: Versioning URIs
Is there some parallel to the DNS here? www.example.net is really 123.456.789.123, right now. It might be some other IP later. So id.example.org/124/78 might be found from id.example.org/school/78 right now, but from id.example.org/academy/78 some other day. Since /124/78 is meaningless, there’s no reason ever to change it. What it is doesn’t change, but the context we assign it certainly will.
If we wish to put human-readable meaning in the URI, then it should be a temporary condition. Versioning should be built in, but in a meaningless way. /124/78 might be /school/10Nov2009 right now, but /academy/archival_only/10Nov2009 some day.