Kevin; This is a good reference and outline an approach I did not talk about
earlier, which is to use properties instead of statement reification (caveat: some like to talk about
multiple type of "reification", though I tend to use it
for statement reification only).
So I would second your recommendation to look at the PROV Ontology.
The computational approaches are
different in this case. PROV assumes a
reasoner is being used and I was assuming manipulation of the RDF
triples. Many ways to work at this (all of
which are beyond the scope
of this forum) and the key is probably to
choose one that fits your needs best and is
computationally feasible. Your
miles will vary...
--Scott
On 8/31/2013 11:51 AM, Kevin Tyson
wrote:
The W3C Provenance ontology does a very good job of
associating time with properties that represent causal
relationships by employing the qualified relations
pattern.
This allows the ordering
information to be considered during inference which I don't
think would work with reification.
On Saturday, August 31, 2013, Scott Henninger wrote:
Paul; No, that's not the implication. Currently you
need a file for each graph (RDF 1.1 will likely change
this).
So the quad structure you refer to is already there.
All triples live within a graph, and graphs are named -
with a URI, the base URI for TopBraid - and can be
accessed through SPARQL GRAPH.
To add a fifth dimension to the triple for time would
not be a standards-based solution and therefore of
marginal interest to vendors, such as TopQuadrant.
Not sure why reification is ruled out - you can always
represent the triple metadata, such as time, in
reification in the back-end and generate the non-reified
triples in memory when needed. I.e. given an epoch of time
that needs to be queried (displayed, etc.), compute the
triples for the epoch using the reified metadata. It's
fairly simple to do computationally, and is essentially
what EVN does with Working Copies. Generally speaking,
reification is not such a bad solution.
Named Graphs could be manipulated in a similar way for
time, but I'm sketchier on the details. One thought is to
represent the timed data in a graph, one per epoch. Then
import the desired epoch graph into the rest of the data.
Beyond those sketchy details, this is an active area
for a number of standards bodies, and I'd suggest looking
into some of those approaches.
-- Scott
Scott,
Do I understand this well that for every triple that
gets a (graph) id which can then be used to attach
time related data on it, needs to have its own file?
We are ending up with zillions of files then.
Paul
On Friday, August 30, 2013 4:56:17 PM UTC+2, Scott
Henninger wrote:
Paul; TopBraid does use a named graph architecture. Each file, be they a text serialization or a
back-end connector, contains a graph identifier
using the base URI.
So you may be able
to manipulate this though multiple files
and import them using
owl:imports. A file can be
imported anywhere
and in multiple places, so I think that
will get you close to your
use case.
-- Scott
On 8/30/2013 3:14 AM, PaulZH
wrote:
Hi,
I would like some advice on
this requirement.
Context.
Time info should be added to
certain statements/triples
(e.g. when valid in the
real world)).
Choices made:
- not to use reification
- not to use the Qualified
Relation pattern
but to use the graph id (4th
slot) for adding this info to
mimic property graphs in graph
databases such as Neo4J.
What I do not see for the
moment is an easy workflow to
do this in TBC as editing
environment.
Any input on this is
appreciated.
Paul
--
-- You received this message
because you are subscribed to
the Google
Group "TopBraid Suite Users",
the topics of which include
Enterprise Vocabulary Network
(EVN), TopBraid Composer,
TopBraid Live, TopBraid Insight,
SPARQLMotion, SPARQL Web Pages
and SPIN.
To post to this group, send
email to
[email protected]
To unsubscribe from this group,
send email to
[email protected]
For more options, visit this
group at
http://groups.google.com/group/topbraid-users?hl=en
---
You received this message
because you are subscribed to
the Google Groups "TopBraid
Suite Users" group.
To unsubscribe from this group
and stop receiving emails from
it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
--
-- You received this message because you are subscribed
to the Google
Group "TopBraid Suite Users", the topics of which
include Enterprise Vocabulary Network (EVN), TopBraid
Composer, TopBraid Live, TopBraid Insight, SPARQLMotion,
SPARQL Web Pages and SPIN.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
---
You received this message because you are subscribed to
the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails
from it, send an email to [email protected].
For more options, visit
--
-- You received this message because you are subscribed to the
Google
Group "TopBraid Suite Users", the topics of which include
Enterprise Vocabulary Network (EVN), TopBraid Composer,
TopBraid Live, TopBraid Insight, SPARQLMotion, SPARQL Web
Pages and SPIN.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
---
You received this message because you are subscribed to the
Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from
it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
--
Kevin P. Tyson
[email protected]
--
-- You received this message because you are subscribed to the
Google
Group "TopBraid Suite Users", the topics of which include
Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid
Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
---
You received this message because you are subscribed to the Google
Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
--
-- You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
---
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
|
