bs:QuantityValue
rdf:type owl:Class ;
rdfs:subClassOf owl:Thing ;
rdfs:subClassOf [
rdf:type owl:Restriction ;
owl:onClass xsd:decimal ;
owl:onProperty rdf:value ;
owl:qualifiedCardinality "1"^^xsd:nonNegativeInteger ;
] ;
skos:prefLabel "kwantiteitwaarde"@nl ;
skos:prefLabel "quantity value"@en ;
.
Someone said: red should be owl:onDatatype but when I do that I get error missing class:
???
|
|||||||||||||||||
|
This OWL 2 feature is only superficially supported by TopBraid
and will not be supported in the future.
Holger
--
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/f7c585569482452db12ab76a4ed8614d%40tno.nl.
Ahhhh, ok!
The next question would than be: why is that?
Isn’t the example a valid case?
In the primer I see only qualifiedCardinality examples with “onClass”.....maybe this simply should not work for qualified datatype properties?
Any other way to say that my class has exactly one attribute with type xsd:decimal?
Like normal cardinality + some or all valuesfrom?
Thx a lot,
Michel
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/967752e4-a1d4-10b0-cb98-be91a3486c7c%40topquadrant.com.
Hi Michel,
we have (long) moved away from OWL 2 and suggest to use SHACL for
these use cases. The example with rdf:value looks like sh:minCount
1; sh:maxCount 1; sh:datatype xsd:decimal.
Holger
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/e971ce4c42f84094a0ecda6e9d8338f4%40tno.nl.
I know, the question was specifically for OWL.
Some of the involved parties have tools that do not support SHACL.
We cannot force them (now) to SHACL-only mode.
Can I do:
bs:QuantityValue
rdf:type owl:Class ;
rdfs:subClassOf owl:Thing ;
rdfs:subClassOf [
rdf:type owl:Restriction ;
owl:allValuesFrom xsd:decimal ;
owl:onProperty rdf:value ;
] ;
rdfs:subClassOf [
rdf:type owl:Restriction ;
owl:cardinality "1"^^xsd:nonNegativeInteger ;
owl:onProperty rdf:value ;
] ;
skos:prefLabel "kwantiteitwaarde"@nl ;
skos:prefLabel "quantity value"@en ;
.
With same effect?
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/4fd71ad0-a41c-2019-4139-d15751837963%40topquadrant.com.
This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. TNO accepts no liability for the content of this e-mail, for the manner in which you use it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages.
Van: topbrai...@googlegroups.com <topbrai...@googlegroups.com> Namens Holger Knublauch
Verzonden: Wednesday, March 25, 2020 8:47 AM
Aan: topbrai...@googlegroups.com
Onderwerp: Re: [topbraid-users] question on restrictionHi Michel,
we have (long) moved away from OWL 2 and suggest to use SHACL for these use cases. The example with rdf:value looks like sh:minCount 1; sh:maxCount 1; sh:datatype xsd:decimal.
Holger
On 25/03/2020 17:25, 'Bohms, H.M. (Michel)' via TopBraid Suite Users wrote:
Ahhhh, ok!The next question would than be: why is that?Isn’t the example a valid case?In the primer I see only qualifiedCardinality examples with “onClass”.....maybe this simply should not work for qualified datatype properties?Any other way to say that my class has exactly one attribute with type xsd:decimal?Like normal cardinality + some or all valuesfrom?Thx a lot,Michel
Dr. ir. H.M. (Michel) Böhms
Senior Data Scientist
This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. TNO accepts no liability for the content of this e-mail, for the manner in which you use it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages.
Van: topbrai...@googlegroups.com <topbrai...@googlegroups.com> Namens Holger Knublauch
Verzonden: Tuesday, March 24, 2020 11:09 PM
Aan: topbrai...@googlegroups.com
Onderwerp: Re: [topbraid-users] question on restrictionThis OWL 2 feature is only superficially supported by TopBraid and will not be supported in the future.
Holger
On 25/03/2020 05:07, 'Bohms, H.M. (Michel)' via TopBraid Suite Users wrote:
bs:QuantityValuerdf:type owl:Class ;rdfs:subClassOf owl:Thing ;rdfs:subClassOf [rdf:type owl:Restriction ;owl:onClass xsd:decimal ;owl:onProperty rdf:value ;owl:qualifiedCardinality "1"^^xsd:nonNegativeInteger ;] ;skos:prefLabel "kwantiteitwaarde"@nl ;skos:prefLabel "quantity value"@en ;.Someone said: red should be owl:onDatatype but when I do that I get error missing class:
<image002.png>???
Dr. ir. H.M. (Michel) Böhms
Senior Data Scientist
This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. TNO accepts no liability for the content of this e-mail, for the manner in which you use it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages.
--
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/f7c585569482452db12ab76a4ed8614d%40tno.nl.
--
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/967752e4-a1d4-10b0-cb98-be91a3486c7c%40topquadrant.com.--
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/e971ce4c42f84094a0ecda6e9d8338f4%40tno.nl.
--
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/4fd71ad0-a41c-2019-4139-d15751837963%40topquadrant.com.
--
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/959124700eab4a68bd0ad350e973965e%40tno.nl.
Also, in OWL, constraints are constraints on classification, not constraints on specifying values of properties. It is often precisely the people who are slow in starting with SHACL that are not fully aware of this.
Even with simple cardinality specified to exactly 1, a resource can have none or many values for the property. It just falls outside the definition of the class. Violations are not violations of a constraint, but contradictions between two or more propositions, neither of which is contested. Therefore, in standards that intend to express data constraints, SHACL should be used and not OWL. -j
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/11A9C901-19FB-4E7D-A6B5-359ACF1ADA97%40topquadrant.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/DB8PR03MB597715C34CDC0337546F3EC2E9CE0%40DB8PR03MB5977.eurprd03.prod.outlook.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/CALGFikevYAVMQUMmL%3D_czZoYmgC06LpUgpnSgMwCPixxYa9utg%40mail.gmail.com.
Thank you Michael for your feedback! I have the same inhibitions as Irene, and yet we need to keep spreading the word. Best, -j
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/ABE47EBB-9FE9-4E9A-BA79-0E373EE1D085%40topquadrant.com.
On 25 Mar 2020, at 22:34, 'Bohms, H.M. (Michel)' via TopBraid Suite Users <topbrai...@googlegroups.com> wrote:Think the benefits of shacl over owl are clear.Still there are owl users with owl tools using owl reasoning that are not 100% sure they can do all their owl things in shacl (given their tools have the capability of handling shacl at all).
Eg when they use inference like autoclassification based on necessary&sufficient owl restrictions....can they still do that with shacl?
Do they need ..not yet recommendation status...shacl AF for that?
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/66e78a6e-142b-4a17-b24e-9577a068ff68%40email.android.com.