ok, according to Holger: "yes there is (or rather: was until 2.6.2) a special handling of rdfs:labels in SPARQL queries, but only if the subject is a blank node. This was very obscure and confusing so I have just removed it. "
So it looks like the next version of TBC will be handling this better. thanks Holger! On Oct 27, 12:27 pm, donundeen <[EMAIL PROTECTED]> wrote: > Here's some more > information:http://www.daml.org/2002/06/webont/owl-ref-proposed#Annotations > > one of the points: > Annotation properties must not be used in property axioms (e.g., no > subproperties are allowed). > > So that means I can't make sxml:text a subProperty of rdfs:label? > > can i go the other way around, and make rdfs:label a subProperty of > sxml:text ? > > On Oct 23, 3:55 pm, donundeen <[EMAIL PROTECTED]> wrote: > > > well, to get around this issue, I ran inferencing, then asserted the > > triples arising from subproperties, > > and ran the same query again. This time, the query worked. > > not sure what to make of that. > > > On Oct 23, 11:51 am, donundeen <[EMAIL PROTECTED]> wrote: > > > > hm, not sure if this is relevent, > > > but my subProperty, sxml:text > > > has > > > domain sxml:TextNode > > > range xsd:string > > > > whereasrdfs:labelhas > > > domain: rdfs:Resource > > > range : rdfs:Literal > > > > could those values be conflicting with eachother in any way? > > > I wouldn't think so, based on my understanding of what domain and > > > range do, > > > but I'm having trouble locating what else could be going on. > > > > also, my main ontology file has a lot of imports; the definitions of > > >rdfs:labeland sxml:text, as well as the various instances are in > > > different places. that's another difference between my case and the > > > example. > > > > On Oct 23, 10:43 am, donundeen <[EMAIL PROTECTED]> wrote: > > > > > yes, your example works. > > > > will have to figure out what I'm doing wrong with my ontology. > > > > > On Oct 22, 10:44 pm, Scott Henninger <[EMAIL PROTECTED]> > > > > wrote: > > > > > > Don; I'm not sure what is happening in your case, but subPropertyOf > > > > > works as you outline. I've attached a min-ontology to demonstrate > > > > > this. Run the following query with and without inferencing and you > > > > > will see that turning on inferences invokes the subPropertyOf > > > > > relationship. > > > > > SELECT ?lbl > > > > > WHERE { > > > > > ?thing a :Thing_1 . > > > > > ?thingrdfs:label?lbl . > > > > > } > > > > > -- Scott > > > > > donundeen wrote:Hi, I'm working some queries using subproperties. my > > > > > understanding is that IF sp subPropertyOf s AND x sp y THEN x s y For > > > > > example, I've made sxml:text a subproperty ofrdfs:labeltherefore, > > > > > shouldn't the queries: CONSTRUCT { ?node sxml:text ?found . }WHERE{ > > > > > ?node sxml:text ?found . } and CONSTRUCT { ?node sxml:text ?found . > > > > > }WHERE{ ?node sxml:text ?found . ?noderdfs:label?found . } return the > > > > > same thing, if inferencing is turned on when you do the query? Right > > > > > now, I've got my inferencing configured to just do SwiftOWLIM. It > > > > > seems as though inferencing isnt' doing anything with subProperties. > > > > > When I run inferencing alone, I also don't see any new properties > > > > > being added based on subproperties. > > > > > > unnamed0.owl > > > > > 1KViewDownload --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
