Thank you, Kevin. This may indeed lie at the root of the problem. We
have observed that Turtle and N-Triples are better for moving between
ontology editors. Using the Triples View is one sure-fire way to find
out whether Composer is reading the triples at all.
We do not support OWL/XML and we will add an issue report to detect
this when trying to open such a file and let the user know quicker.
In terms of "...offering you imports for your untyped resources..."
the correct answer depends on the data you have:
- Answer 'No' if you have raw RDF data, i.e. resources whose type
definition isn't necessary in the file
- Answer "Yes" if you have strongly typed data and you need to make
sure all imports are found
Answering 'No' is by far the most common. To explain, TBC will look
to import any URL resource. So if you have:
{<http://topbraid.org/examples/kennedys#College> skos:broader
<http://fiddlestyx.com/universities>}
...then Composer will go looking for http://fiddlestyx.com, if you say
"Yes". As of 3.6.2, the default is now to not look for "missing
imports", which should cause fewer problems. You can change this at
Preferences > TopBraid Composer > Input/Output > Check for missing
imports after loading
-- Scott
On Oct 29, 2:52 pm, Kevin Tyson <[email protected]> wrote:
> Bruce,
> I think the problem is that Protege encodes the base uri one way and TBC
> encodes it another way due to their use of different underlying toolsets
> (OWLAPI vs JENA). The differences between OWLAPI and Jena are smaller if
> you use turtle encoding. I was able to create ontologies in Protege using
> Turtle that opened correctly using ttl. When I tried owl/xml encodings of
> the same ontology TBC displayed a modal dialog box saying "Checking for
> imports..." which never terminated (for a two class one property file).
> Try saving in turtle format from Protege and then opening in TBC. The next
> thing you may encounter is a message offering you imports for your untyped
> resources. If you answer "yes" to this prompt, you should end up with what
> you're looking for, your classes and properties displayed in the
> appropriate panes without recourse to SPARQL queries or other special
> purpose panes.
> HTH,
> Kevin
>
> On Mon, Oct 29, 2012 at 3:15 PM, Scott Henninger <[email protected]
>
>
>
>
>
>
>
>
>
> > wrote:
> > On 10/28/2012 11:21 PM, Bruce Whealton wrote:
>
> > I mentioned the problem I had opening up an existing ontology inside TBC
> > and you asked what did I see and what did I expect to see. I expected to
> > see a nice hierarchy of classes and properties. That was exactly what I
> > saw in Protege. In TBC, I couldn't find any of the classes or properties
> > that I knew existed in the ontology.
> > See my comments again and your question: > I was
> > > able to do this in Protege editor but I did something wrong in TBC. I
> > > created a project for this first then I put the ontology into the
> > project
> > > folder and then I opened it by double clicking on it in TBC.
>
> > ...and? Was there an error? What didn't happen that you expected?
>
> > Unfortunately, I'm still not sure what I can do to help you. I can state
> > the rules for viewing a class hierarchy, which is the same for any ontology
> > editor:
> > - any resource of type owl:Class will appear as a subclass of owl:Thing
> > - any resource of type rdfs:Class will appear as a subclass of r
> > dfs:Resource
>
> > I cannot state whether Protégé does this faithfully or what it may have
> > done with your data model.
>
> > As stated, there are a couple of ways of viewing your data other than
> > from the class hierarchy - see
> >http://www.topquadrant.com/products/TBS_FAQ.html#TBC6
>
> > 1) Use the Triples View: Window > Show View > Triples to see all triples
> > in the file
>
> > 2) Use the SPARQL View and query the data. For example, the following
> > will find all OWL class definitions:
>
> > SELECT *
> > WHERE
> > { ?s a owl:Class .
> > }
>
> > Beyond that, you may need to send screen shots or examples of your data
> > for us to be able to help you any further.
>
> > -- Scott
>
> > --
> > -- 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
>
> --
> 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 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
