It's here in the OWL 2 spec
http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Minimum_Cardinality
Make sure to activate display of RDF in examples.
Holger
On Jun 1, 2011, at 6:37 PM, Bohms, H.M. (Michel) wrote:
> very interesting!, we never used that....is this because of a change in spec
> or tbc or...did we always do it the wrong way ? :)
>
> we always did:
>
> <rdfs:subClassOf>
>
> <owl:Restriction>
>
> <owl:onProperty
> rdf:resource="http://www.bimtoolset.org/ontologies/pmo.owl#hasPart_directly"/>
>
> <owl:onClass
> rdf:resource="http://www.bimtoolset.org/ontologies/Sensor.owl#Room"/>
>
> <owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#integer";
>
> >1</owl:minCardinality>
>
> </owl:Restriction>
>
> </rdfs:subClassOf>
>
> I read about a change of syntax at:
> http://www.w3.org/2007/OWL/wiki/FullSemanticsQCRs
>
> but I cant find quickly when the syntax was actually changed in the specs...
>
> ths for more info, Michel
>
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Holger Knublauch
> Sent: Wednesday, June 01, 2011 9:47 AM
> To: [email protected]
> Cc: Bonsma, P. (Peter)
> Subject: Re: [topbraid-users] QCR display in form view
>
> Hi Michel,
>
> you need to use owl:minQualifiedCardinality instead of owl:minCardinality :)
>
> The best way to figure such things out is to enter what you want manually in
> TBC and look at the triples with the small + button over the icon.
>
> Cheers,
> Holger
>
>
> On Jun 1, 2011, at 5:37 PM, Bohms, H.M. (Michel) wrote:
>
>> Hi Scott,
>>
>> After adapting the generator, the errors non-total-uri xsd type
>> resources/datatypes are gone.
>> But I still don't see in the form view the QCR constraints fully.
>>
>> I attached the file. If you go to sensor:Building, you see in the form view:
>> pmo:hasPart_directly min 1
>>
>> where I hoped to see someting like:
>>
>> pmo:hasPart_directly min 1 sesnor:Room
>>
>> any idea what I still do wrong?
>>
>> thx Michel
>>
>>
>>
>>
>>
>>
>> Dr. ir. H.M. (Michel) Böhms
>> sr. Research Scientist
>> Building Innovation T +31 (0)888663107
>> M +31 (0)630381220
>> E [email protected] Location
>> Disclaimer
>>
>> <logo_signature.gif>
>>
>>
>>
>>
>>
>> This e-mail and its contents are subject to the DISCLAIMER at
>> http://www.tno.nl/emaildisclaimer
>> <Sensor.owl>--
>> 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
>
> --
> 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
