Hi Irene, The blog did not answer my question as it did not mention mininclusive, minExlclusive maxinclusive MaxExclusive for datatype restrictions, only minimum and maximum. I tried to do what that suggests, but it did not work. Using 'only won't get one inclusive or exclusive max/mins. Here is the W3C tidbit again. Maybe that will clarify what I mean.
DatatypeRestriction also makes it possible to specify restrictions on datatypes by means of constraining facets that constrain the range of values allowed for a given datataype, by length (for strings) e.g., minLength, maxLength, and minimum/maximum value, e.g., minInclusive, maxInclusive. Extended datatypes are allowed in many description logics and are supported by several reasoners. Normative Syntax Direct Semantics RDF-Based Semantics DatatypeRestriction( DT F1 lt1 ... Fn ltn ) where DT is a unary datatype and ⟨ Fi lti ⟩, 1 ≤ i ≤ n are pairs of constraining facet and literal. HCLS Functional-Style Syntax:DatatypeRestriction(xsd:integer minInclusive 18) (UC#9) new datatype with a lower bound of 18 on the XML Schema datatype xsd:integer RDF:_:x rdf:type rdfs:Datatype . _:x owl:onDatatype xsd:integer . _:x owl:withRestrictions ( _:y ) . _:y xsd:minInclusive "5"^^xsd:integer . (UC#9) new datatype with a lower bound of 18 on the XML Schema datatype xsd:integer This datatype is needed for example to define patients under 18 (children) who depend on a hospital's pediatric services while those over 18 (adults) depend on adult services. Best, Leonard On Fri, Mar 18, 2011 at 4:49 PM, Gokhan Soydan <gsoy...@topquadrant.com>wrote: > Hello Leonard, > > You could use "user-defined datatypes" in OWL 2 and express them in > Manchaster Syntax in TopBraid Composer. So, if you build a restriction using > those, it will look something like: > > :count only xsd:double[> 8.4, <10.0] > > where the literals specified in this restriction could be between 8.4 and > 10. > > More information about how OWL 2 user-defined datatype properties can be > created in TopBraid Composer can be found here: > > > http://composing-the-semantic-web.blogspot.com/2009/10/owl-2-support-in-topbraid-composer.html > > More information on OWL 2 user-defined datatypes can be found here. For > easier reading, please click on "Show Turtle Syntax" or "Show Manchaster > Syntax" close to the top of the page: > http://www.w3.org/TR/owl2-primer/#Advanced_Use_of_Datatypes > > Gokhan > > > > On 3/18/2011 11:50 AM, Leonard Jacuzzo wrote: > > Thanks Irene, > Any thoughts on the first part of my question? > Best, > Leonard > > On Fri, Mar 18, 2011 at 2:47 PM, Irene Polikoff <ir...@topquadrant.com>wrote: > >> Leonard, >> >> >> >> To do qualified cardinality restriction, type "HasPart min 8 X" where 'X' >> is a class. Or max or exactly depending on the cardinality type. >> >> >> >> Regards, >> >> >> >> Irene >> >> >> >> *From:* topbraid-users@googlegroups.com [mailto: >> topbraid-users@googlegroups.com] *On Behalf Of *Leonard Jacuzzo >> *Sent:* Friday, March 18, 2011 2:09 PM >> *To:* topbraid-users@googlegroups.com >> *Subject:* [topbraid-users] DatatypeRestriction in TBC. >> >> >> >> Hello, >> >> I would like to be able to use OWL2 datatype restrictions, but cannot >> figure out how to do this with TBC. For example, I would like to have a >> value like '8.4' count as a minimum exclusive value while defining a class >> as equivalent to the class having this minimal inclusive value for the >> datatype property in question. I have pasted the W3C explanation of this >> below. It is from Owl2 New Features and Rationale. >> >> >> >> I would also like to be sure that I understand how one can do qualified >> cardinalites as restrictions on a property. It seems to allow me to type >> that in, but there is no icon for it in the dropdown via rightclick while >> formulating the restrictions. >> >> is it simply enough to type "HasPart 8 X" where 'X' is a class? >> >> >> >> Any help will be greatly appreciate. >> >> Best wishes, >> >> Leonard >> >> >> >> >> >> >> >> DatatypeRestriction also makes it possible to specify restrictions on >> datatypes by means of constraining >> *facets*<http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Datatype_Maps>that >> constrain the range of values allowed for a given datataype, by length >> (for strings) e.g., minLength, maxLength, and minimum/maximum value, e.g., >> minInclusive, maxInclusive. Extended datatypes are allowed in many >> description logics and are supported by several reasoners. Normative >> Syntax<http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Datatype_Restrictions> >> Direct >> Semantics<http://www.w3.org/TR/2009/REC-owl2-direct-semantics-20091027/#Data_Ranges> >> RDF-Based >> Semantics<http://www.w3.org/TR/2009/REC-owl2-rdf-based-semantics-20091027/#Semantic_Conditions_for_Datatype_Restrictions> >> >> DatatypeRestriction( DT F1 lt1 ... Fn ltn ) where DT is a unary datatype >> and ⟨ Fi lti ⟩, 1 ≤ i ≤ n are pairs of constraining facet and literal. >> >> - HCLS >> >> Functional-Style Syntax: >> >> DatatypeRestriction(xsd:integer minInclusive 18) (*UC#9*) >> >> new datatype with a lower bound of 18 on the XML Schema datatype >> xsd:integer >> >> >> >> RDF: >> >> _:x *rdf:type* *rdfs:Datatype* . >> _:x *owl:onDatatype* *xsd:integer* . >> _:x *owl:withRestrictions* ( _:y ) . >> _:y *xsd:minInclusive* "5"^^*xsd:integer* . (*UC#9*) >> >> new datatype with a lower bound of 18 on the XML Schema datatype >> xsd:integer >> >> This datatype is needed for example to define patients under 18 (children) >> who depend on a hospital's pediatric services while those over 18 (adults) >> depend on adult services. >> >> -- >> 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 >> topbraid-users@googlegroups.com >> To unsubscribe from this group, send email to >> topbraid-users+unsubscr...@googlegroups.com >> 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 >> topbraid-users@googlegroups.com >> To unsubscribe from this group, send email to >> topbraid-users+unsubscr...@googlegroups.com >> 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 > topbraid-users@googlegroups.com > To unsubscribe from this group, send email to > topbraid-users+unsubscr...@googlegroups.com > 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 > topbraid-users@googlegroups.com > To unsubscribe from this group, send email to > topbraid-users+unsubscr...@googlegroups.com > 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 topbraid-users@googlegroups.com To unsubscribe from this group, send email to topbraid-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en
