Here's what I think happened.  At one point I created a copy of your spin.owl 
ontology so I could edit it for our purposes (ostensibly to use it without 
using your sp.owl ontology since I was just going to use text representations 
of the SPARQL Queries themselves), and gave it a URL of 
http://www.boeing.com/IVHM/spin.owl

I then decided to go back and use sp.owl as I learned more about templates and 
functions.  Anyway, I deleted the import of http://www.boeing.com/IVHM/spin.owl 
and then added an import to your spin.owl ontology (or I may have done it in 
the other order - add then delete).  After doing that, for some reason I had 
two namespaces defined for spin in my ontology.  Apparently removing an import 
didn't delete namespaces defined for the removed ontology.  

Note that I never explicitly added or deleted any namespaces myself.  This is 
just what TBC did for me automatically.
 
jeff

-----Original Message-----
From: Scott Henninger [mailto:[email protected]] 
Sent: Wednesday, January 07, 2009 2:43 PM
To: TopBraid Composer Users
Subject: Re: FIXED RE: [tbc-users] Re: SPARQL Query on spin:constraint weirdness


Jeff;  Exactly how was it defined twice?  The same prefix to different URIs or 
the same namespace to different prefixes?  Just trying to get an idea of what 
happened.

A couple of additional notes.  In general a SPARQL query that matches a bnode 
will return the bnode.  Some are recognized by Composer (restrictions, SPIN, 
etc.).  Others will display the anonymous id.

FailureRate was misspelled in the FILTER of your ASK query.  A small thing that 
can drive you crazy - command completion helps me a lot in this respect.

-- Scott

On Jan 7, 2:18 pm, "Schmitz, Jeffrey A" <[email protected]>
wrote:
> Nevermind, it was a namespace clash.  I had "spin" defined twice in my 
> ontology.  Perhaps an error check you could add in future versions?
> Can't think of a reason it would ever be good to do that.
>
> Thanks!
> Jeff


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TopBraid Composer Users" group.
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-composer-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to