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]> 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 Ensemble, 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
 
 

Reply via email to