- 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: Temporal Scope for RDF Triples
I'm a bit hesitant about serializing Named Graphs in everyday Web documents. I heavily use Named Graphs to track provenance, by loading each document into its own Named Graph internally. If I would allow documents to contain several Named Graphs, then essentially someone could fool my store by claiming that this is the graph representing some other document. Does this mean I need to move to Quintuples for my internal data model?
That's why I prefer solutions that remain within the standard RDF data model, and I advocate the solution of creating classes representing the time-scoped relationship in your vocabulary.
Jiri Prochazka and I have written up a little draft RDFS extension that might help with mapping such relationship classes into the pure triple form: Property Reification Vocabulary.
But anyway, this is an important and interesting topic and it's good to see this well thought out proposal.