Hi David
That is what I suspected (getting lost in shacl-mapping).
I also tried:
sainput:bpsWeg
rdf:type owl:DatatypeProperty ;
rdfs:domain [
rdf:type owl:Class ;
owl:unionOf (
sainput:OntwerpSpecificatie
sainput:MonsterLaag
sainput:MonitoringMeting
) ;
] ;
rdfs:label "bpsWeg" ;
rdfs:range xsd:integer ;
.
But I guess not treated by shacl-mapping since not
Guess I will differentiate them in the inputontology (per sheet).
I can have them one time in the target ontologie.
Thx Michel
Dr. ir. H.M. (Michel) Bohms
Scientist Specialist
Structural Reliability
T +31 (0)88 866 31 07
M +31 (0)63 038 12 20
E [email protected]<mailto:[email protected]>
Location<http://www.tno.nl/locations/DTS>
[cid:[email protected]]<http://www.tno.nl/>
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.
From: [email protected] <[email protected]> On
Behalf Of David Price
Sent: Tuesday, October 19, 2021 11:26 AM
To: [email protected]
Subject: Re: [topbraid-users] spreadsheet import by pattern, no-domain target
props issue
On 19 Oct 2021, at 09:58, 'Bohms, H.M. (Michel)' via TopBraid Suite Users
<[email protected]<mailto:[email protected]>> wrote:
Properties in the input ontology not having a domain cannot be chosen as target:
<image004.png>
(where the dashes are)
Is this intended?
Yes.
See if you can create an instance of the thing in the EDG UI, and if so see
what property shapes are visible. That’s what you have to work with. The
importer, like all of EDG, is based on the SHACL Shapes, not the initial OWL.
So, if a property does not appear in the SHACL as being relevant for the
selected Class/Nodeshape then you cannot pattern map into it. I cannot remember
what OWL2SHACL does in this case, but as always you can extend it to do
whatever you want. I *think* the property shapes may be there, just not
connected to a NodeShape.
(these properties are valid for multiple sheets so they have multiple domains)
I can understand they are not automatically proposed but why can I not choose
them manually from the list?
Should I indicate union of relevant domains?
Thx Michel
Ps
Missing target props are defined as:
sainput:bpsWeg
a owl:DatatypeProperty ;
rdfs:label "bpsWeg" ;
rdfs:range xsd:integer ;
.
sainput:bpsStartKilometrering
a owl:DatatypeProperty ;
rdfs:label "bpsStartKilometrering" ;
rdfs:range xsd:integer ;
.
sainput:bpsEindKilometrering
a owl:DatatypeProperty ;
rdfs:label "bpsEindKilometrering" ;
rdfs:range xsd:integer ;
.
sainput:bpsBaan
a owl:DatatypeProperty ;
rdfs:label "bpsBaan" ;
rdfs:range xsd:integer ;
.
sainput:bpsStrook
a owl:DatatypeProperty ;
rdfs:label "bpsStrook" ;
rdfs:range xsd:integer ;
.
As you say, these specific properties cleary DO have some reasonable but
unstated domain in the ontology. I imagine what would happen if you ran a DL
reasoner on this is that it would infer owl:Thing as the domain of the property
which is clearly wrong. bpsStartKilometrering is clearly not a property of
Person, for example.
As far as SHACL/EDG is concerned, this is an under specificed (i.e. incomplete)
ontology wrt doing any kind of sensible data validation/UI generation/etc. EDG
Data Graphs are based on SHACL Shapes Graphs (i.e. not trying to be a generic,
OWL-based collection type).
Probably better to make an abstract superclass and tie these with a domain to
that class. If you make a complex OWL structure, you may have to do an
extension to OWL2SHACL to get what you want.
Cheers,
David
Dr. ir. H.M. (Michel) Bohms
Scientist Specialist
Structural Reliability
T +31 (0)88 866 31 07
M +31 (0)63 038 12 20
E [email protected]<mailto:[email protected]>
Location<http://www.tno.nl/locations/DTS>
<image005.gif><http://www.tno.nl/>
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
[email protected]<mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/9f044c442f7f4a9591b29cb8b421f974%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/9f044c442f7f4a9591b29cb8b421f974%40tno.nl?utm_medium=email&utm_source=footer>.
UK +44 (0) 7788 561308
US +1 (336) 283-0808
--
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
[email protected]<mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/5B0F1709-C447-4FD9-AA46-BA7E4C373BCE%40topquadrant.com<https://groups.google.com/d/msgid/topbraid-users/5B0F1709-C447-4FD9-AA46-BA7E4C373BCE%40topquadrant.com?utm_medium=email&utm_source=footer>.
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/67da6c77b2dd463091c6fbedb5e90366%40tno.nl.
