Yes we have TriG support on our JIRA bug tracker for a future version.
It would be indeed very hard to align it with our file-based graph
representation assumptions, but for importing/exporting databases it
should be useful. As of 4.4 a single SDB connection can contain an
unlimited number of named graphs, assuming they all start with the same
URI part. As of 4.5 this will be extended to TDB, so opening a TriG file
could result in creating an internal TDB.
Holger
On 4/3/2014 7:36, Irene Polikoff wrote:
Simon,
Just from a superficial scan of it, I see TriG as targeted for mostly
for exchange of RDF Datasets for loading:
“A TriG document allows writing down an RDF Dataset in a compact
textual form. It consists of a sequence of directives, triple
statements, graph statements which contain triple-generating
statements and optional blank lines.”
As you say, RDF Dataset is not equal to a named graph. It can contain
multiple graphs. Thus, TriG provides an way to write down a named
graph’s identifier within a Dataset, but it does not seem to offer
anything new for the identity of the individual textual files, e.g.,
Dataset’s themselves. Then, there is a way to say which triples belong
to a default graph.
In TopBraid, each file (or each connector) is an individual named
graph. Base URIs are used to store identity of these graphs for use in
runtime. So, there is quite a bit of a difference between TriG use
case and what TopBraid is using base URIs for.
I can see RDF databases (named graph stores) implementing TriG as an
export/import format. Internally, at runtime, they will continue to
store and provide named graph identity in whatever way they are
already doing it. And we will probably support something along those
lines as well.
Regards,
Irene
*From:*[email protected]
[mailto:[email protected]] *On Behalf Of *Simon Cox
*Sent:* Wednesday, April 02, 2014 4:11 PM
*To:* [email protected]
*Subject:* Re: [topbraid-users] Base URI in TopBraid
> To the extent that RDF 1.1 specifies different ways of specifying
named graph, and RDF files comply, we will adopt those standards in
due time.
TriG has been issued as a W3C recommendation, as part of the RDF 1.1
suite.
This allows graph names (note the plural!) to be included in a TTL file.
What plans to implement this in TopBraid?
I can see it will be a big job, because currently TopBraid uses the
ontology URI as the graph name internally (and usually expects it to
correspond with the file name) so supporting named graphs properly
would undermine this, or at least require you to call it 'context'
rather than 'graph-name' or something similar ...
On Wednesday, 23 January 2013 04:34:25 UTC, Scott Henninger wrote:
Peter; I think that explains it pretty well. TopBraid has always had
a named graph architecture, just like triple stores. But a problem is
that text serializations don't have a way to define the graph name,
except for the base URI, which turns out to work nicely and
transparently.
To the extent that RDF 1.1 specifies different ways of specifying
named graph, and RDF files comply, we will adopt those standards in
due time.
-- Scott
On 1/22/2013 11:20 PM, Peter Ansell wrote:
On 23 January 2013 14:07, Simon Cox<[email protected]> <javascript:>
wrote:
While trying to move RDF data between systems, we have found that
TopBraid
appears to use a non-standard way to specify the base URI in its Turtle
mode.
The documentation is clear: on the Help page
TopBraid Composer > RDF and TopBraid > Named Graphs and Base URIs
in
TopBraid
it says
base URI that identifies a graph is saved within a file using one of the
following types of statements:
Hi Simon,
That almost sounds like it identifies a graph, in the same way as
SPARQL Graph's, which are going to be in RDF-1.1, but are not in
RDF-1.0. A graph is separate to the normal interpretation of base URI,
as it encompasses a set of statements, but does not provide a base for
relative URIs.
To fully support graphs you would need to move to using a quads
format, with either TriX (RDF/XML+Graphs), TriG (Turtle+Graphs) or
N-Quads (N-Triples+Graphs) as possible alternatives.
Cheers,
Peter
--
-- 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] <mailto:[email protected]>
To unsubscribe from this group, send email to
[email protected]
<mailto:[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]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
-- 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]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
-- 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/d/optout.
