Thanks a lot Irene. That clarifies things for me. I'll re-state it in my
words to check I've got it right:
1. the set of graphs in the workspace is determined by the <import>
statements in the ontologies
2. the baseURI is used as the graph name for each import.
AFAICT the issue that I raised comes about because
owl:import rdfs:range owl:Ontology .
rather than _graph_ . So even though the specs do not require any specific
correspondence between ontology name and baseURI, because it makes sense to
interpret an import as operating on a _graph_ we end up in the situation
that works best if the ontology name is a graph name, which is easiest if
it is the context or baseURI.
The issue is really that range of owl:import is not really right.
On Fri, Dec 20, 2013 at 3:38 PM, Irene Polikoff <[email protected]>wrote:
> Simon,
>
>
>
> TopBraid workspace implements graphs as specified by the relevant W3C
> specifications. A TopBraid workspace defines a dataset consisting of
> multiple named graphs. Each file in the workspace that either directly
> contains RDF triples (such as a .TTL file) or is a connector to an external
> data source (such as SPARQL Endpoint, RDFa site or external database) is a
> named graph.
>
>
>
> Each graph needs an identity and TopBraid uses baseURI as graphs’
> identity. Without having a way to identify graphs, it would not be possible
> to act on owl:import statements as there would be no way to identify what
> is being imported. Nor would it be possible to say which graph is being
> queried in a SPARQL query.
>
>
>
> For more information, please refer to Help -> TopBraid
> Composer<http://127.0.0.1:60574/help/nav/3>> RDF
> and TopBraid <http://127.0.0.1:60574/help/nav/3_11> >Named Graphs and
> Base URIs in TopBraid
>
>
>
> Regards,
>
>
>
> Irene
>
>
>
>
>
>
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Simon Cox
> *Sent:* Thursday, December 19, 2013 10:39 PM
> *To:* [email protected]
> *Subject:* Re: [topbraid-users] Re: Ontology URI assumption in TopBraid
>
>
>
> The baseURI is only required it there are partial URIs.
>
> If every URI in a document is either a either fully qualified URI, or a
> namespace-abbreviated URI, including the Ontology declaration, then any
> definition of or assumptions about the baseURI is superfluous. Everything
> is explicit. That should be enough for any application. So I guess I don't
> understand the question
>
>
>
> "how could TopBraid possibly make sense of it"
>
>
>
> My other point is that if TB is relying on extra information being
> smuggled in comments, then we are well out on a limb here.
>
>
>
> On Fri, Dec 20, 2013 at 1:57 PM, Holger Knublauch <[email protected]>
> wrote:
>
> I really don't think there is a problem in TBC. If the physical file
> (imported from somewhere else) does not contain baseURI information then
> how could TopBraid possibly make sense of it. That's why we add the #
> baseURI comment: it makes managing the files in the workspace much more
> efficient than having to pre-load them all.
>
>
>
> I remain of the position that the ontology authors should follow the
> convention used almost everywhere else - that the owl:Ontology does not end
> with a #.
>
>
>
> Holger
>
>
>
>
>
> On Dec 20, 2013, at 12:38 PM, Simon Cox wrote:
>
>
>
> Thanks Holger -
>
>
>
> OK - I saved the imported ontology like you said.
>
> Inspecting the contents, I find the only difference from what I got by
> downloading the TTL file directly from W3C was the insertion of
>
>
>
> # baseURI: http://www.w3.org/ns/locn
>
>
>
> This is a comment! http://www.w3.org/TR/turtle/#sec-grammar-comments
>
> But I guess it is important to TopBraid.
>
> I've previously noticed similar comments used to indicate imports as well.
>
> Hmmm. Now we are getting into (black) magic?
>
>
>
> Furthermore, when I put a copy of this saved file in a place where I could
> open it, then TopBraid automatically created a second Ontology resource
> whose URI is the baseURI, in addition to the explicit one already in the
> file.
>
> So clearly TopBraid insists on having an Ontology present whose URI is the
> baseURI declared in the file (graph).
>
> If you make any changes to the file and then save it, you end up with two
> ontologies in the file, which in turn confuses some other tools.
>
>
>
> One of my colleagues has pointed out that this may be coming from OWLAPI
>
>
>
> "the automatic ontology IRI mapping tools in OWLAPI assume that the base
> URI is the ontology IRI. As far as I know this should be just a
> convention."
>
>
>
> Is this the source of the problem in TB?
>
>
>
>
>
> --
> -- 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 a topic in the
> Google Groups "TopBraid Suite Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/topbraid-users/975Tv5ukhog/unsubscribe.
> To unsubscribe from this group and all its topics, 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.
>
> --
> -- 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 a topic in the
> Google Groups "TopBraid Suite Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/topbraid-users/975Tv5ukhog/unsubscribe.
> To unsubscribe from this group and all its topics, 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.
