dat range question

[Michel Böhms]

 

Suppose I have defined height as owl objectproperty with range QuantityValue having a rdf:value with datatype xsd:decimal.

 

How can I now specify in OWL for a certain class that this height has a min and max value?

 

So looking for a data restriction on ex:height.rdf:value

 

Or otherwise can I do it for the object property in general?

 

Thx Michel

[Holger Knublauch]

See https://www.w3.org/TR/owl2-primer/#Advanced_Use_of_Datatypes (There are buttons to switch from the Functional Syntax to Turtle or RDF/XML).

Note that TopBraid doesn't really support those OWL 2 restriction types. Alternative is sh:minExclusive etc.

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/CAPB9pOwmZTVF6stoZmtPso974jwOOUQ%3DNdrccJ4hhnT%3Df%3D_zVw%40mail.gmail.com.

[Bohms, H.M. (Michel)]

Thx

Will have look at teenager ex in turtle....

Op 26 feb. 2020 00:10 schreef Holger Knublauch <hol...@topquadrant.com>:

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/b6eee44d-81d5-f420-364c-f7de7c62911c%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.

[Bohms, H.M. (Michel)]

- hi holger

Some more on this

- would tbc syntactically handle this constraint type?

- would onDatatype not be double since range is already xsd:double?

- would i need propertychaining first since 2 steps? ex:height.rdf:value...

Thx again! Michel

Op 26 feb. 2020 00:10 schreef Holger Knublauch <hol...@topquadrant.com>:

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/b6eee44d-81d5-f420-364c-f7de7c62911c%40topquadrant.com.

[Holger Knublauch]

On 27/02/2020 21:27, 'Bohms, H.M. (Michel)' via TopBraid Suite Users wrote:
> - hi holger
>
> Some more on this
>
> - would tbc syntactically handle this constraint type?

Not really. You could enter the definitions using source code.

> - would onDatatype not be double since range is already xsd:double?
> - would i need propertychaining first since 2 steps?
> ex:height.rdf:value...

There may be better mailing lists for support of these more obscure
features of OWL 2, e.g. the Protege list.

Holger

[Bohms, H.M. (Michel)]

Just to be sure, in tbc-owl no way to infer problem for:

ex:Bridge
rdf:type owl:Class ;
rdfs:subClassOf owl:Thing ;
rdfs:subClassOf [
rdf:type owl:Restriction ;
owl:allValuesFrom [
rdf:type rdfs:Datatype ;
owl:onDatatype xsd:decimal ;
owl:withRestrictions (
[
xsd:minExclusive 12 ;
]
[
xsd:maxInclusive 19 ;
]
) ;
] ;
owl:onProperty ex:heightValue ;
] ;
.
ex:heightValue
rdf:type owl:DatatypeProperty ;
owl:propertyChainAxiom (
ex:height
rdf:value
) ;
.
ex:Bridge_1
rdf:type ex:Bridge ;
ex:height [
rdf:value 50.0 ;
] ;
.

I HAVE to revert to shacl first, right?
thx

 
Dr. ir. H.M. (Michel) Böhms
Senior Data Scientist

T +31888663107
M +31630381220
E michel...@tno.nl
Location

 

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.

-----Oorspronkelijk bericht-----
Van: topbrai...@googlegroups.com <topbrai...@googlegroups.com> Namens Holger Knublauch
Verzonden: Thursday, February 27, 2020 11:24 PM
Aan: topbrai...@googlegroups.com
Onderwerp: Re: [topbraid-users] dat range question

--
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/078b224b-e51b-07fc-5a07-fdb6962ff35f%40topquadrant.com.

[dprice]

Hi Michel,

First, WRT terminology: OWL DL reasoner do not “infer problems". OWL DL reasoners infers triples and as a separate feature they can report inconsistencies within the limits of the open world assumption. 

Due to issues discussed many times in this forum, Composer does not come integrated with an OWL DL reasoner. Instead, since many of our customers found the open world assumption and OWL DL inferencing inadequate, and TopQuadrant create SPIN and then helped push SHACL through the W3C.

Composer can infer RDFS and OWL RL profile triples using TopSPIN engine.

Composer can generate SHACL from OWL where their semantics overlap, and customers can extend that converter as it’s delivered largely as SHACL SPARQL rules rather than as compiled code. 

Composer can identify errors in data using the SHACL language and engine under a closed world assumption.

For more complex data constraints, customers can write SHACL shapes using Composer. 

There’s a lot of SHACL overview and explanation at https://www.topquadrant.com/technology/shacl/

Hope that clarifies the situation.

Cheers,

David

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/48e81b57ba12440ea95f93dec10d2eb3%40tno.nl.

UK +44 (0) 7788 561308

US +1 (336) 283-0808‬

[Irene Polikoff]

Correct. These OWL axioms are outside of the standard OWL-RL profile. 

Thus, only OWL-DL reasoner will be able to identify inconsistencies “out of the box” - without some change in the ontology or rules. TopBraid does not include OWL DL reasoner and OWL DL, in general, due to its performance characteristics is not recommended for working with data of any scale.

In TopBraid, you have the following options:

1. Use SHACL equivalent of these statements
2. Extend rules defining OWL-RL profile to support working with these patterns

We recommend #1.

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/1693C82E-DF32-4D77-96F8-31AC65707D0F%40topquadrant.com.

[Bohms, H.M. (Michel)]

David, Irene

Thx.

Will keep owl code for representation only and only expect logical inconsistency checking ...indeed better term than 'infer problem'....from derived/extended shacl variants.

Gr michel

Op 1 mrt. 2020 15:49 schreef Irene Polikoff <ir...@topquadrant.com>:

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/581C2045-EDEA-44B4-9D5C-134319E14BE7%40topquadrant.com.