We have a light-weight collection of such SPIN constraints at
http://topbraid.org/spin/spinowl
This defines closed-world constraints of common OWL restrictions
including owl:cardinality. Just import this into your model and
activate constraint checking.
But as Scott says, this will work better in the upcoming TBE version.
Holger
On Jul 13, 2009, at 9:55 AM, Scott Henninger wrote:
>
> <Is there any plan to link the SPIN-check on the cardinality
> restrictions to the owl-properties? >
>
> All OWL constructs are defined in RDF triples. Therefore, SPARQL
> queries can be created to define the restrictions you need, regardless
> whether OWL constructs are used or not.
>
> For example, the following will get you close to what you might want:
>
> SELECT ?prop ?cardVal
> WHERE
> { ?cls a owl:Class .
> ?cls rdfs:subClassOf ?restr .
> ?restr owl:onProperty ?prop .
> ?restr owl:cardinality ?cardVal
> }
>
> -- Scott
>
>> The idea would be to determine in owl the min, max or exact number of
>> properties with a reference from the SPIN-function to the owl-
>> property.
>> <owl:Restriction>
>> <owl:onProperty rdf:resource="parties#hasName"/>
>> <owl:cardinality rdf:datatype="http://www.w3.org/2001/
>> XMLSchema#int"
>> >1</owl:cardinality>
>> </owl:Restriction>
>> Perhaps there is already now a way to refer to that property but we
>> don't know how to perform this.
>
> >
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
