Hi Paul, have a look at the OWL 2 RDF mapping document:
http://www.w3.org/TR/owl2-mapping-to-rdf/ and see that the DatatypeRestrictions are mapped to _:x blank nodes. DatatypeRestriction( DT F1 lt1 ... Fn ltn ) _:x rdf:type rdfs:Datatype . _:x owl:onDatatype T(DT) . _:x owl:withRestrictions T(SEQ _:y1 ... _:yn) . _:y1 F1 lt1 . ... _:yn Fn ltn . _:x And then owl:equivalentClass is used to link that blank node with a named datatype: DatatypeDefinition( DT DR ) T(DT) owl:equivalentClass T(DR) . This means that it is not legal to directly attach datatype restrictions to a named datatype. That's also why there is no UI support in TBC. Regards, Holger On Jun 30, 2010, at 4:47 AM, PaulZH wrote: > Scott, > > On Jun 29, 6:30 pm, Scott Henninger <[email protected]> > wrote: >> Paul; I don't think this can be avoided, as user-defined datatypes >> define an unnamed class. When you then name the datatype with >> owl:equivalentClass, another type statement is created. (Note the two >> instances of {?rsc a rdfs:Datatype} in each of your graph >> specifications.) >> > > I think you can avoid this by doing: > > foo:test > a rdfs:Datatype ; > rdfs:label "Datatype_1"^^xsd:string ; > owl:onDatatype xsd:int ; > owl:withRestrictions > ([ xsd:minInclusive "65"^^<xsd:integer> > ]) . > > However I couldn't figure out how to edit this via the user interface, > which was my initial question. > >> I found the OWL 2 Language Primer (http://www.w3.org/TR/2009/REC-owl2- >> primer-20091027) to be useful for understanding how datatypes are >> defined. Be sure to click the button on the page that shows the >> turtle syntax. >> > > I'll do that. > > Paul >> -- Scott >> >> On Jun 29, 9:56 am, PaulZH <[email protected]> wrote: >> >>> On Jun 29, 4:10 pm, Scott Henninger <[email protected]> >>> wrote: >> >>>> Hello Paul; The XML schema datatypes Composer supports can be turned >>>> on via the Classes View preference. Choose which data types you need >>>> to display. >> >>> OK, I see. Thanks. It would be handy though if I could select all xsd >>> datatypes in one action. >> >>>> <<If I use owl:equivalentClass with the Manchester Syntax the number >>>> of my datatypes double. >>>> I was trying to avoid this. >> >> >>>> Can you provide a specific example of this? >> >>> :test >>> a rdfs:Datatype ; >>> owl:equivalentClass >>> [ a rdfs:Datatype ; >>> owl:onDatatype xsd:int ; >>> owl:withRestrictions >>> ([ xsd:minInclusive 65 >>> ]) >>> ] . >> >>> and >> >>> :union >>> a rdfs:Datatype ; >>> owl:equivalentClass >>> [ a rdfs:Datatype ; >>> owl:unionOf (xsd:date xsd:dateTime) >>> ] . >> >>> lead to 4 datatypes in my instances overview. >> >>> Paul >> >>>> -- Scott >> >>>> On Jun 29, 7:07 am, PaulZH <[email protected]> wrote: >> >>>>> Hi Holger, >> >>>>> On Jun 29, 12:44 pm, Holger Knublauch <[email protected]> wrote: >> >>>>>> Hi Paul, >> >>>>>> On Jun 29, 2010, at 3:40 PM, PaulZH wrote: >> >>>>>>> a) When creating a new instance of class rdfs:Datatype, I expected to >>>>>>> get when using "add existing ..." on property owl:onDatatype the list >>>>>>> of xsd datatypes, but I see none. Is this influenced by a setting? >> >>>>>> Seems to work for me, see screenshot. What exactly are you doing? >> >>>>> I was talking specifically about the whole list of the XML Schema >>>>> (xsd) datatypes, which I do not seem to find. >> >>>>>>> b) What is the syntax to be used in the value of owl:withRestrictions? >> >>>>>> Did you read this >>>>>> http://composing-the-semantic-web.blogspot.com/2009/10/owl-2-support-... >>>>>> which shows examples of how to enter user-defined datatypes with >>>>>> restrictions on the TBC forms? >> >>>>> Yes, I did. >> >>>>>> Typically, I would not expect people to enter the low-level properties >>>>>> such as owl:withRestrictions manually. >>>>>> Could you clarify why you are attempting this, and why the inline text >>>>>> notation (Manchester Syntax) would not work? >> >>>>> If I use owl:equivalentClass with the Manchester Syntax the number of >>>>> my datatypes double. >>>>> I was trying to avoid this. >> >>>>> Paul > > -- > You received this message because you are subscribed to the Google > Group "TopBraid Suite Users", the topics of which include TopBraid Composer, > TopBraid Live, TopBraid Ensemble, SPARQLMotion 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 Group "TopBraid Suite Users", the topics of which include TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion 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
