- 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: Linked Open Data in a Changing World
If you treat every document containing RDF data as an OWL ontology (which just happens to only contain instance data) then you can use some of OWL’s vocab for exactly that. And it will make the DL reasoners happy I guess. ;-) For example owl:priorVersion and its sub-properties might be useful. And in OWL 2 you can even keep the ontology URI the same and just change its version IRI (a new property) so it’s all connected through the ontology URI. It doesn’t have anything for deprecating ontologies though. To express the temporal validity of a document you can use dcterms:valid although it doesn’t specify a format for how to express such a range. I guess you’d do that with OWL Time.