Re: [topbraid-users] property graph using graph identifier

[Scott Henninger]

Yes, TriG will appear in RDF 1.1, which is currently in working draft form (i.e. premature, as the syntax may change).  See http://www.w3.org/TR/2013/WD-trig-20130409/ -- Scott On 9/2/2013 4:51 AM, PaulZH wrote: Hi Scott and Kevin, Thanks for all this input. I do some more research as you suggested. BTW. This is a snippet in TriG of what the way of thinking was. @prefix  : <htt://test.be/e/>. @prefix  xsd: <http://www.w3.org/2001/XMLSchema#> . :g1 {:a1  :pays  :a2.} :g2 {:a2  :pays  :a3.} :g3 {:a3  :pays  :a4.} :g4 {:a4  :pays  :a1.} {:g1   :time  "2013-12-12T09:00:00"^^xsd:dateTime . :g1   :location <http://dbpedia.org/resource/Keerbergen> . :g1   :amount 5600 .} {:g2   :time  "2013-08-08T09:00:00"^^xsd:dateTime . :g2   :location <http://dbpedia.org/resource/Mechelen> . :g2   :amount 2400 .} {:g3   :time  "2013-06-06T09:00:00"^^xsd:dateTime . :g3   :location <http://dbpedia.org/resource/Aarschot> . :g3   :amount  1200 .} {:g4   :time  "2013-04-04T09:00:00"^^xsd:dateTime . :g4   :location <http://dbpedia.org/resource/Aarschot> . :g4   :amount  12000 .} On Saturday, August 31, 2013 7:15:23 PM UTC+2, Scott Henninger wrote: 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.  http://www.w3.org/TR/prov-o/ 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 On Aug 31, 2013, at 9:12 AM, PaulZH <p...@proxml.be> wrote: 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 topbrai...@googlegroups.com To unsubscribe from this group, send email to topbraid-user...@googlegroups.com 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 topbraid-user...@googlegroups.com. 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 topbraid-users@googlegroups.com To unsubscribe from this group, send email to topbraid-users+unsubscribe@googlegroups.com 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 topbraid-users+unsubscribe@googlegroups.com. 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 topbraid-users@googlegroups.com To unsubscribe from this group, send email to topbraid-users+unsubscribe@googlegroups.com 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 topbraid-users+unsubscribe@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- Kevin P. Tyson kevin...@gmail.com -- -- 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 topbrai...@googlegroups.com To unsubscribe from this group, send email to topbraid-user...@googlegroups.com 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 topbraid-user...@googlegroups.com. 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 topbraid-users@googlegroups.com To unsubscribe from this group, send email to topbraid-users+unsubscr...@googlegroups.com 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 topbraid-users+unsubscr...@googlegroups.com. 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 topbraid-users@googlegroups.com To unsubscribe from this group, send email to topbraid-users+unsubscr...@googlegroups.com 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 topbraid-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.