from:"'Bohms, H.M. \(Michel\)' via TopBraid Suite Users"

[topbraid-users] RE: simple shacl question

2021-06-23 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

And then similar question for:

ex:heightShape
  a sh:NodeShape ;
  sh:targetObjectsOf ex:height ;
  sh:class sml:QuantityValue ;
.

Can it be:

ex:height
  a sh:NodeShape ;
  sh:class sml:QuantityValue ;
.



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 michel.bo...@tno.nl

Location



[cid:image001.gif@01D76812.0DAEF9B0]

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: Bohms, H.M. (Michel)
Verzonden: woensdag 23 juni 2021 09:25
Aan: topbraid-users@googlegroups.com
Onderwerp: simple shacl question

Just checking...

Instead of:

ex:BridgeShape
  a sh:NodeShape ;
  sh:targetClass ex:Bridge ;
  sh:property [
sh:path ex:height ;
sh:minCount 1 ;
] ;
  sh:property [
sh:path sml:hasPart ;
sh:minCount 1 ;
sh:maxCount 1 ;
sh:class ex:Deck ;
] ;
.

I can say:

ex:Bridge
  a sh:NodeShape ;
  sh:property [
sh:path ex:height ;
sh:minCount 1 ;
] ;
  sh:property [
sh:path sml:hasPart ;
sh:minCount 1 ;
sh:maxCount 1 ;
sh:class ex:Deck ;
] ;
.

Right?
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 michel.bo...@tno.nl

Location



[cid:image001.gif@01D76812.0DAEF9B0]

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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/e9de0317a39a47fd822f2b35b3a6d25c%40tno.nl.

RE: [topbraid-users] simple shacl question

2021-06-23 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Right, see previous (its there imported from other graph (same ns))



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D76813.EAF23C50]<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.




Van: topbraid-users@googlegroups.com  Namens 
Holger Knublauch
Verzonden: woensdag 23 juni 2021 09:30
Aan: topbraid-users@googlegroups.com
Onderwerp: Re: [topbraid-users] simple shacl question



On 2021-06-23 5:25 pm, 'Bohms, H.M. (Michel)' via TopBraid Suite Users wrote:
Just checking…

Instead of:

ex:BridgeShape
  a sh:NodeShape ;
  sh:targetClass ex:Bridge ;
  sh:property [
sh:path ex:height ;
sh:minCount 1 ;
] ;
  sh:property [
sh:path sml:hasPart ;
sh:minCount 1 ;
sh:maxCount 1 ;
sh:class ex:Deck ;
] ;
.

I can say:

ex:Bridge
  a sh:NodeShape ;
  sh:property [
sh:path ex:height ;
sh:minCount 1 ;
] ;
  sh:property [
sh:path sml:hasPart ;
sh:minCount 1 ;
sh:maxCount 1 ;
sh:class ex:Deck ;
] ;
.

... only if you also say ex:Bridge rdf:type owl:Class (or rdfs:Class). If a 
class is also a node shape then you don't need a targetClass statement. See

https://www.w3.org/TR/shacl/#implicit-targetClass

Holger



Right?
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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D76813.EAF23C50]<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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/165cca5ae08e4e088d45585a8994b992%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/165cca5ae08e4e088d45585a8994b992%40tno.nl?utm_medium=email_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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/31cd5804-8b2e-82da-78ed-ac0880bbc9b4%40topquadrant.com<https://groups.google.com/d/msgid/topbraid-users/31cd5804-8b2e-82da-78ed-ac0880bbc9b4%40topquadrant.com?utm_medium=email_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 topbraid-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/7de6fea0c9894792b01d8c833976a621%40tno.nl.

RE: [topbraid-users] simple shacl question

2021-06-23 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Yes, ok

The ex:Bridge a rdfs:Class is in the imported RDFS ontology!



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D76813.D1567310]<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.




Van: topbraid-users@googlegroups.com  Namens 
Irene Polikoff
Verzonden: woensdag 23 juni 2021 09:29
Aan: topbraid-users@googlegroups.com
Onderwerp: Re: [topbraid-users] simple shacl question


ex:Bridge
  a sh:NodeShape, owl:Class ; (or rdfs:Class)
  sh:property [
sh:path ex:height ;
sh:minCount 1 ;
] ;
  sh:property [
sh:path sml:hasPart ;
sh:minCount 1 ;
sh:maxCount 1 ;
sh:class ex:Deck ;
] ;
.


This is necessary to establish the target.


On Jun 23, 2021, at 3:25 AM, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Just checking…

Instead of:

ex:BridgeShape
  a sh:NodeShape ;
  sh:targetClass ex:Bridge ;
  sh:property [
sh:path ex:height ;
sh:minCount 1 ;
] ;
  sh:property [
sh:path sml:hasPart ;
sh:minCount 1 ;
sh:maxCount 1 ;
sh:class ex:Deck ;
] ;
.

I can say:

ex:Bridge
  a sh:NodeShape ;
  sh:property [
sh:path ex:height ;
sh:minCount 1 ;
] ;
  sh:property [
sh:path sml:hasPart ;
sh:minCount 1 ;
sh:maxCount 1 ;
sh:class ex:Deck ;
] ;
.

Right?
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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/165cca5ae08e4e088d45585a8994b992%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/165cca5ae08e4e088d45585a8994b992%40tno.nl?utm_medium=email_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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/813D5CF6-DCB7-493B-B4BE-271AD2D6635A%40topquadrant.com<https://groups.google.com/d/msgid/topbraid-users/813D5CF6-DCB7-493B-B4BE-271AD2D6635A%40topquadrant.com?utm_medium=email_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 topbraid-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/d144fda7254f480bad747644fe5bf584%40tno.nl.

[topbraid-users] no individuals

2021-06-23 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Please advice, why i do not see individuals (like Bridge_1) when opening 
sml-example.ttl

This data file, imports all others from skos, rdfs, owl and shacl that all open 
fine by themselves.

Turtle seems fine too in validator.



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 michel.bo...@tno.nl

Location



[cid:image001.gif@01D76853.D2D94E70]

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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/bac74a1d58a14ab7872e14f54e7fdbd6%40tno.nl.


sml-skos.ttl
Description: sml-skos.ttl

[topbraid-users] sh import?

2021-06-23 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Is it needed to explicitly import sh?

Or is it like rdfs, rdfs, owl, xsd etc.

(I used to import dash but given that issue...etc.)



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 michel.bo...@tno.nl

Location



[cid:image001.gif@01D7682C.77839200]

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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/95be0c36c3e644c1ae06f717771a7b90%40tno.nl.

RE: [topbraid-users] sh import?

2021-06-23 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

More like:

Is sh in the league of xsd/rdf/rdfs/owl (not imported)

Or in the league of others being imported explicitly

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>

[cid:image001.gif@01D76883.4D995D60]<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.

Van: topbraid-users@googlegroups.com Namens
Holger Knublauch
Verzonden: woensdag 23 juni 2021 22:03
Aan: topbraid-users@googlegroups.com
Onderwerp: Re: [topbraid-users] sh import?

On 23/06/2021 8:37 pm, 'Bohms, H.M. (Michel)' via TopBraid Suite Users wrote:
Is it needed to explicitly import sh?

For what application?

In general, owl:imports are a good thing. They make the semantics of the used
resources more explicit and transparent. If we skip them here, where would this
end: use skos:Concept without importing SKOS Core? Makes no sense to me.

Holger

Or is it like rdfs, rdfs, owl, xsd etc.

(I used to import dash but given that issue…etc.)

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>

[cid:image001.gif@01D76883.4D995D60]<http://www.tno.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-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/95be0c36c3e644c1ae06f717771a7b90%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/95be0c36c3e644c1ae06f717771a7b90%40tno.nl?utm_medium=email_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
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/75ee91b7-1367-e1ac-a716-4c098ce156d5%40topquadrant.com<https://groups.google.com/d/msgid/topbraid-users/75ee91b7-1367-e1ac-a716-4c098ce156d5%40topquadrant.com?utm_medium=email_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 topbraid-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/79cec119271a4ef5b44239d2eff46a47%40tno.nl.

RE: [topbraid-users] sh import?

2021-06-23 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

My view…sh would fit well in that list of languages (xsd, rdf, rdfs, owl, …) 
that are handled without explicit import…

???

Counterargument?



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D76884.1F9A59E0]<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.




Van: 'Bohms, H.M. (Michel)' via TopBraid Suite Users 

Verzonden: woensdag 23 juni 2021 22:59
Aan: topbraid-users@googlegroups.com
Onderwerp: RE: [topbraid-users] sh import?

More like:

Is sh in the league of xsd/rdf/rdfs/owl (not imported)

Or in the league of others being imported explicitly



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D76884.1F9A59E0]<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.




Van: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com> 
mailto:topbraid-users@googlegroups.com>> 
Namens Holger Knublauch
Verzonden: woensdag 23 juni 2021 22:03
Aan: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com>
Onderwerp: Re: [topbraid-users] sh import?



On 23/06/2021 8:37 pm, 'Bohms, H.M. (Michel)' via TopBraid Suite Users wrote:
Is it needed to explicitly import sh?

For what application?

In general, owl:imports are a good thing. They make the semantics of the used 
resources more explicit and transparent. If we skip them here, where would this 
end: use skos:Concept without importing SKOS Core? Makes no sense to me.

Holger



Or is it like rdfs, rdfs, owl, xsd etc.

(I used to import dash but given that issue…etc.)



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D76884.1F9A59E0]<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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/95be0c36c3e644c1ae06f717771a7b90%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/95be0c36c3e644c1ae06f717771a7b90%40tno.nl?utm_medium=email_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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/75ee91b7-1367-e1ac-a716-4c098ce156d5%40topquadrant.com<https://groups.google.com/d/msgid/topbraid-users/75ee91b7-1367-e1ac-a716-4c098ce156d5%40topquadrant.com?utm_medium=email_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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/79cec119271a4ef5b44239d2eff46a47%40tno.nl<https://groups.google.com/d/msg

[topbraid-users] RE: no individuals

2021-06-23 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Solved: i had to introduce another graph uri for the data (since other ns
uri...).
Could not be both "ex:"

@prefix exdata: .
@prefix ex: .

Now fine...

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 michel.bo...@tno.nl

Location

[cid:image001.gif@01D76885.56434FF0]

Van: Bohms, H.M. (Michel)
Verzonden: woensdag 23 juni 2021 17:19
Aan: 'topbraid-users@googlegroups.com'
Onderwerp: no individuals

Please advice, why i do not see individuals (like Bridge_1) when opening
sml-example.ttl

This data file, imports all others from skos, rdfs, owl and shacl that all open
fine by themselves.

Turtle seems fine too in validator.

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 michel.bo...@tno.nl

Location

[cid:image001.gif@01D76885.56434FF0]

--
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/5901440c2aa44bb6b17c5a1cade0ece2%40tno.nl.

[topbraid-users] RE: no individuals

2021-06-23 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Correction, should be:

Solved: i had to introduce another prefix for the data (since other ns uri…).
Could not be both “ex:”

@prefix exdata: <https://w3id.org/sml-example/id#> .
@prefix ex: <https://w3id.org/sml-example/def#> .

Now fine…





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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D76885.DA01D050]<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.




Van: 'Bohms, H.M. (Michel)' via TopBraid Suite Users 

Verzonden: woensdag 23 juni 2021 23:13
Aan: topbraid-users@googlegroups.com
Onderwerp: [topbraid-users] RE: no individuals

Solved: i had to introduce another graph uri for the data (since other ns uri…).
Could not be both “ex:”

@prefix exdata: <https://w3id.org/sml-example/id#> .
@prefix ex: <https://w3id.org/sml-example/def#> .

Now fine…



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D76885.DA01D050]<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.




Van: Bohms, H.M. (Michel)
Verzonden: woensdag 23 juni 2021 17:19
Aan: 'topbraid-users@googlegroups.com' 
mailto:topbraid-users@googlegroups.com>>
Onderwerp: no individuals

Please advice, why i do not see individuals (like Bridge_1) when opening 
sml-example.ttl

This data file, imports all others from skos, rdfs, owl and shacl that all open 
fine by themselves.

Turtle seems fine too in validator.



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D76885.DA01D050]<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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/5901440c2aa44bb6b17c5a1cade0ece2%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/5901440c2aa44bb6b17c5a1cade0ece2%40tno.nl?utm_medium=email_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 topbraid-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/92b6e65c9b0d40b9a77ad3febfc800a5%40tno.nl.

RE: [topbraid-users] Staying with official SHACL

2021-06-22 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Thx, good to know (we sometimes use free version in webinars)



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D76744.57E23AC0]<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.




Van: topbraid-users@googlegroups.com  Namens 
Holger Knublauch
Verzonden: dinsdag 22 juni 2021 01:26
Aan: topbraid-users@googlegroups.com
Onderwerp: Re: [topbraid-users] Staying with official SHACL



On 22/06/2021 9:10 am, Steve Ray wrote:
Hi Holger,
Things are looking good on my end using TBC 7.0.1 and only importing the SHACL 
URI and not dash or tosh. Running SHACL reasoning and SHACL validation both 
seem to work reliably. I'm assuming that, as you mentioned, dash and/or tosh 
are brought in automatically if needed.

The only exception is a summer student working on the standards project who is 
using the TBC Free edition (which seems to have moved backwards to 6.0.1). It 
seems to choke when validating because it isn't finding some tosh objects.
(Caused by: java.lang.IllegalArgumentException: Shapes graph does not include 
tosh:http://datashapes.org/dash#DefaultValueTypeRule)

The workaround for the student is just to have him explicitly import dash.ttl 
whenever he wants to run the validator, but remove it before doing his git 
push. I know that you all aren't supporting TBC Free any more, but I just 
wanted to confirm that this is expected behavior.

Yes this sounds plausible. The SHACL engine in that version was different.

Holger



Steve



On Sun, Jun 20, 2021 at 3:58 PM Holger Knublauch 
mailto:hol...@topquadrant.com>> wrote:

In addition to the extra constraint components

http://datashapes.org/constraints.html

the dash namespace also imports the tosh namespace, which contains constraints 
on the SHACL metamodel and therefore is used to drive the forms in EDG.

What you do with the files generated with TopBraid outside of TopBraid is of 
course your own decision. I assume all standards-compliant SHACL validation 
engines will support at least SHACL Core without any mandatory owl:imports. In 
the SHACL API that I wrote, the code uses dash and tosh internally to identify 
the constraint components, so they are internally added in case they don't 
exist in the provided shapes graph. But this happens automatically.

Holger


On 2021-06-20 7:48 am, Steve Ray wrote:
Very cool! With bated breath, I tried it, and nothing blew up!

It would be good to know at some point what functionality I lose by directly 
importing
owl:imports <http://www.w3.org/ns/shacl#<http://www.w3.org/ns/shacl>> ;
instead of
  owl:imports <http://datashapes.org/dash> ;
Steve



On Sat, Jun 19, 2021 at 3:36 AM David Price 
mailto:dpr...@topquadrant.com>> wrote:
Hi Steve and Michel

I’m not near my computer so cannot do it for you, but suggest replacing dash 
import with SHACL import and trying it. I think that’s ok.
Cheers,
David


On 19 Jun 2021, at 08:44, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

I have exactly the same issue in CEN TC442/WG4/TG3 ….

I now have:

# baseURI: https://w3id.org/sml/shacl/def
# imports: https://w3id.org/sml/rdfs/def
# imports: http://datashapes.org/dash
# imports: http://qudt.org/schema/qudt
# imports: http://qudt.org/vocab/quantitykind
# imports: http://qudt.org/vocab/unit
# imports: http://www.w3.org/2004/02/skos/core
# imports: https://www.w3.org/2006/time
# prefix: sml

@prefix dash: <http://datashapes.org/dash#<http://datashapes.org/dash>> .
@prefix sml: <https://w3id.org/sml/def#<https://w3id.org/sml/def>> .
@prefix owl: <http://www.w3.org/2002/07/owl#<http://www.w3.org/2002/07/owl>> .
@prefix quantitykind: <http://qudt.org/vocab/quantitykind/> .
@prefix qudt: <http://qudt.org/schema/qudt/> .
@prefix rdf: 
<http://www.w3.org/1999/02/22-rdf-syntax-ns#<http://www.w3.org/1999/02/22-rdf-syntax-ns>>
 .
@prefix rdfs: 
<http://www.w3.org/2000/01/rdf-schema#<http://www.w3.org/2000/01/rdf-schema>> .
@prefix sh: <http://www.w3.org/ns/shacl#<http://www.w3.org/ns/shacl>> .
@prefix skos: 
<http://www.w3.org/2004/02/skos/core#<http://www.w3.org/2004/02/skos/core>> .
@prefix time: <http://www.w3.org/2006/time#<http://www.w3.org/2006/time>> .
@prefix unit: <http://qudt.org/vocab/unit/> .
@prefix xsd: 
<http://www.w3.org/2001/XMLSchema#<http:

[topbraid-users] imports

2021-06-24 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Assume I have:


(3/4)  SKOS concepten schema;

(3/4)  RDFS ontologie (importeert het SKOS schema);

(3/4)  OWL ontologie (importeert de RDFS ontologie);

(3/4)  SHACL ontologie (importeert de RDFS ontologie[1]).


All addressing complementary aspects...



  1.  How needed is the RDFS import by OWL? (guess not)
  2.  Idem for RDFS import by SHACL? (or OWL ignoring the owl-stuff)

Think 1. Can be out, but I doubt about 2. (does the shalcl shape need the class 
working with implicit shapes so no target classes)



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 michel.bo...@tno.nl

Location



[cid:image001.gif@01D76924.BB0009C0]

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.







[1] Kan eventueel ook de OWL ontologie zijn omdat SHACL de OWL-aspecten 
simpelweg negeert. Dit geldt niet andersom: de OWL ontologie moet niet de SHACL 
graaf importeren want OWL is strikter.

-- 
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/3a102dfc871a4cec8218efd56ca6745f%40tno.nl.

[topbraid-users] rdfs using owl

2021-06-15 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Dear Irene, David

We got the following question on our EU standard proposal:

Why are you using owl in your rdfs spec (for owl:Ontology and owl:imports).

Isn't this simply best practice?
Could you do without ie be RDFS pure?

But how then do you specify the graph uri and how to deal with imports??

Thx for your views, 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 michel.bo...@tno.nl

Location



[cid:image001.gif@01D761F2.11844520]

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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/16aed2c420a14a8eae0a9fc7db8b772a%40tno.nl.

RE: [topbraid-users] rdfs using owl

2021-06-15 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Thank you Holger, David

Very useful arguments we can use in our justification for choices,
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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D7620B.89133A60]<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.




Van: topbraid-users@googlegroups.com  Namens 
David Price
Verzonden: dinsdag 15 juni 2021 15:30
Aan: topbraid-users@googlegroups.com
Onderwerp: Re: [topbraid-users] rdfs using owl




On 15 Jun 2021, at 14:07, Holger Knublauch 
mailto:hol...@topquadrant.com>> wrote:

owl:imports is the only feature of OWL that even SHACL mentions because there 
is no real alternative, and it is quite harmless.
Holger

I was writing something which I guess explains Holger's “no real alternative” 
statement. Modularization of RDF-based ontologies and data is the business use 
case being supported and it cannot be done in formally defined, not 
implementation-specific way using only RDF and RDFS.

TBC uses owl:import to define the graph closure for a domain of interest.

RDFS says zero about named graphs, depending on RDF. RDF talks about RDF 
Datasets and the default graph which is the union of everything visible to the 
RDF tool (as far as I can interpret it) but the spec says nothing about how the 
“collection of RDF graphs” is defined or located. It also says nothing about 
how the “set of RDF Triples” that constitute the RDF Graph is defined or 
located.

Give that neither the “set of triples” or “collection of graphs” is formally 
defined, it’s easy to argue that the SPARQL GRAPH keyword actually has little 
or no formal meaning (does one graph need another and if so how is that 
relation specified?).

OWL introduces a more powerful way to manage and relate named graphs and TBC 
takes advantage of that so users can control what triples are visible where. 
Technically I think that is what the RDF spec means by “RDF source” and I think 
that equates to the Ontology Document idea in the OWL2 spec.

Anyway … RDFS purists can simply ignore (or remove) anything in the OWL 
namespace if they have some other way to build RDF Datasets and Named Graphs 
and graph relations in their tooling. In a way the OWL simply provides hints 
about what the graph URIs are and how they are related to other graphs for 
humans when ignored by the tool. In your standards case, you started with OWL 
and “dumbed down" everything you could into RDFS leaving only what formally 
defines the named graph closure.  Note that the OSLC which produces RDFS 
standard ontologies uses owl:Ontology to manage named graphs, so TBC is also 
just following industry usage patterns (as are you).

WRT “best practice” I do sometimes find RDFS that has nothing defining how the 
named graphs relate, sometimes with multiple named graphs in the same RDF/XML 
or TTL file. Usually what you find is that the developers of that content 
actually manage everything separately and then concatenate it into a singe TTL 
at the end. It seems they assume whatever triples they produce is *all* the 
triples and/or can be concatenated with anything else - IMO very odd indeed and 
not nearly as useful to others as having the original separate files.

Not sure if that helps the EU, but explains how TBC works and why.

Cheers,
David



On 15/06/2021 10:23 pm, 'Bohms, H.M. (Michel)' via TopBraid Suite Users wrote:
Dear Irene, David

We got the following question on our EU standard proposal:

Why are you using owl in your rdfs spec (for owl:Ontology and owl:imports).

Isn’t this simply best practice?
Could you do without ie be RDFS pure?

But how then do you specify the graph uri and how to deal with imports??

Thx for your views, 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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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 U

RE: [topbraid-users] render issue in case of uuid code as name

2021-06-02 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Hi Holger,
Are you sure? latest Turtle says:

[168s]

PN_LOCAL

::=

(PN_CHARS_U<https://www.w3.org/TR/turtle/#grammar-production-PN_CHARS_U> | ':' 
| [0-9] | PLX<https://www.w3.org/TR/turtle/#grammar-production-PLX>) 
((PN_CHARS<https://www.w3.org/TR/turtle/#grammar-production-PN_CHARS> | '.' | 
':' | PLX<https://www.w3.org/TR/turtle/#grammar-production-PLX>)* 
(PN_CHARS<https://www.w3.org/TR/turtle/#grammar-production-PN_CHARS> | ':' | 
PLX<https://www.w3.org/TR/turtle/#grammar-production-PLX>))?



It was not allowed in the 2008 variant hence (see red):

D.4 Changes from January 2008 Team 
Submission<http://www.w3.org/TeamSubmission/2008/SUBM-turtle-20080114/> to 
First Public Working Draft<http://www.w3.org/TR/2011/WD-turtle-20110809/>

  *   Adopted three additional string syntaxes from SPARQL: 
STRING_LITERAL2<http://www.w3.org/TR/2013/REC-sparql11-query-20130321/#rSTRING_LITERAL2>,
 
STRING_LITERAL_LONG1<http://www.w3.org/TR/2013/REC-sparql11-query-20130321/#rSTRING_LITERAL_LONG1>,
 
STRING_LITERAL_LONG2<http://www.w3.org/TR/2013/REC-sparql11-query-20130321/#rSTRING_LITERAL_LONG2>
  *   Adopted SPARQL's syntax for prefixed names (see editor's 
draft<http://www.w3.org/TR/sparql11-query/#rPrefixedName>):
 *   '.'s in names in all positions of a local name apart from the first or 
last, e.g. ex:first.name.
 *   digits in the first character of the 
PN_LOCAL<http://www.w3.org/TR/rdf-sparql-query/#rPN_LOCAL> lexical token, e.g. 
ex:7tm.
  *   adopted SPARQL's IRI resolution and prefix substitution text.
  *   explicitly allowed re-use of the same prefix.
  *   Added parsing rules<https://www.w3.org/TR/turtle/#sec-parsing>.

GR 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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D75796.77E9A230]<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.




Van: topbraid-users@googlegroups.com  Namens 
Holger Knublauch
Verzonden: woensdag 2 juni 2021 03:40
Aan: topbraid-users@googlegroups.com
Onderwerp: Re: [topbraid-users] render issue in case of uuid code as name


We use slightly different serialization algorithms across tools but local names 
cannot start with digits so writing the full URI is correct.

If you just export "Turtle" from EDG or save to Turtle from TBC you'll get 
test_uuid:675d0ae5-d8eb-49b7-867f-80ba8c0b09e9 while Sorted Turtle will produce 
<http://example.org/ontologies/test_uuid#675d0ae5-d8eb-49b7-867f-80ba8c0b09e9><http://example.org/ontologies/test_uuid#675d0ae5-d8eb-49b7-867f-80ba8c0b09e9>
 which is more correct AFAIK. Both can be parsed though, so it shouldn't matter 
too much.

Holger


On 2021-06-01 10:14 pm, 'Bohms, H.M. (Michel)' via TopBraid Suite Users wrote:
Dear tq
I have asked earlier but I could not refind….

I have:

https://w3id.org/cbnl/skos/term#048B3010-0BD1-4A89-9F49-FE6D825DA799
  rdf:type skos:Concept ;
  dct:source "IMBOR2021beta"@NL-nl ;
  skos:broader nen2660-term:InformationObject ;
  skos:definition "Informatieobject voor het registreren en koppelen van 
documenten aan 
objecttypes."@NL-nl<mailto:%22Informatieobject%20voor%20het%20registreren%20en%20koppelen%20van%20documenten%20aan%20objecttypes.%22@NL-nl>
 ;
  skos:prefLabel "Document"@NL-nl ;
.

So name is UUID code.

Despite prefixes are fine TBC does not use prefix in interface now.
Think I reported earlier.

(when I change uuid number into “Document” things render fine again)

Gr 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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D75796.77E9A230]<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

RE: [topbraid-users] render issue in case of uuid code as name

2021-06-03 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Super Holger, thx!

Ps
And thx Redmer, for pinpointing.



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D75855.047FFC80]<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.




Van: topbraid-users@googlegroups.com  Namens 
Holger Knublauch
Verzonden: donderdag 3 juni 2021 00:52
Aan: topbraid-users@googlegroups.com
Onderwerp: Re: [topbraid-users] render issue in case of uuid code as name


Apologies, you are right. I even found a ticket in our Jira system from 2017 
where we wanted to update this but it fell through the cracks. The problem is 
that the Sorted Turtle writer uses an outdated base library that we cloned from 
an earlier Jena version. We'll try to fix that for 7.1.

Holger


On 2021-06-02 6:03 pm, 'Bohms, H.M. (Michel)' via TopBraid Suite Users wrote:
Hi Holger,
Are you sure? latest Turtle says:

[168s]

PN_LOCAL

::=

(PN_CHARS_U<https://www.w3.org/TR/turtle/#grammar-production-PN_CHARS_U> | ':' 
| [0-9] | PLX<https://www.w3.org/TR/turtle/#grammar-production-PLX>) 
((PN_CHARS<https://www.w3.org/TR/turtle/#grammar-production-PN_CHARS> | '.' | 
':' | PLX<https://www.w3.org/TR/turtle/#grammar-production-PLX>)* 
(PN_CHARS<https://www.w3.org/TR/turtle/#grammar-production-PN_CHARS> | ':' | 
PLX<https://www.w3.org/TR/turtle/#grammar-production-PLX>))?



It was not allowed in the 2008 variant hence (see red):

D.4 Changes from January 2008 Team 
Submission<http://www.w3.org/TeamSubmission/2008/SUBM-turtle-20080114/> to 
First Public Working Draft<http://www.w3.org/TR/2011/WD-turtle-20110809/>

  1.  Adopted three additional string syntaxes from SPARQL: 
STRING_LITERAL2<http://www.w3.org/TR/2013/REC-sparql11-query-20130321/#rSTRING_LITERAL2>,
 
STRING_LITERAL_LONG1<http://www.w3.org/TR/2013/REC-sparql11-query-20130321/#rSTRING_LITERAL_LONG1>,
 
STRING_LITERAL_LONG2<http://www.w3.org/TR/2013/REC-sparql11-query-20130321/#rSTRING_LITERAL_LONG2>
  2.  Adopted SPARQL's syntax for prefixed names (see editor's 
draft<http://www.w3.org/TR/sparql11-query/#rPrefixedName>):

 *   '.'s in names in all positions of a local name apart from the first or 
last, e.g. ex:first.name.
 *   digits in the first character of the 
PN_LOCAL<http://www.w3.org/TR/rdf-sparql-query/#rPN_LOCAL> lexical token, e.g. 
ex:7tm.

  1.  adopted SPARQL's IRI resolution and prefix substitution text.
  2.  explicitly allowed re-use of the same prefix.
  3.  Added parsing rules<https://www.w3.org/TR/turtle/#sec-parsing>.

GR 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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D75855.047FFC80]<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.




Van: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com> 
<mailto:topbraid-users@googlegroups.com> 
Namens Holger Knublauch
Verzonden: woensdag 2 juni 2021 03:40
Aan: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com>
Onderwerp: Re: [topbraid-users] render issue in case of uuid code as name


We use slightly different serialization algorithms across tools but local names 
cannot start with digits so writing the full URI is correct.

If you just export "Turtle" from EDG or save to Turtle from TBC you'll get 
test_uuid:675d0ae5-d8eb-49b7-867f-80ba8c0b09e9 while Sorted Turtle will produce 
<http://example.org/ontologies/test_uuid#675d0ae5-d8eb-49b7-867f-80ba8c0b09e9><http://example.org/ontologies/test_uuid#675d0ae5-d8eb-49b7-867f-80ba8c0b09e9>
 which is more correct AFAIK. Both can be parsed though, so it shouldn't matter 
too much.

Holger


On 2021-06-01 10:14 pm, 'Bohms, H.M. (Michel)' via TopBraid Suite Users wrote:
Dear tq
I have asked earlier but I could not refind….

I have:

https://w3id.org/cbnl/skos/term#048B3010-0BD1-4A89-9F49-FE6D825DA799
  rdf:type skos:Concept

[topbraid-users] render issue in case of uuid code as name

2021-06-01 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Dear tq
I have asked earlier but I could not refind

I have:

https://w3id.org/cbnl/skos/term#048B3010-0BD1-4A89-9F49-FE6D825DA799
rdf:type skos:Concept ;
dct:source "IMBOR2021beta"@NL-nl ;
skos:broader nen2660-term:InformationObject ;
skos:definition "Informatieobject voor het registreren en koppelen van
documenten aan
objecttypes."@NL-nl
;
skos:prefLabel "Document"@NL-nl ;
.

So name is UUID code.

Despite prefixes are fine TBC does not use prefix in interface now.
Think I reported earlier.

(when I change uuid number into "Document" things render fine again)

Gr 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 michel.bo...@tno.nl

Location

[cid:image001.gif@01D756EF.83196110]

--
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/2329b36a509f49ee83b4571bf7b18330%40tno.nl.

RE: [topbraid-users] sh import?

2021-06-24 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Hi Holger

I see the issue.

So reformulated my question is:

Is shacl import also automated now (like eg rdf)?
(It seems not, since deleting the import also deletes the shacl tab)

If not, should be it be? (consistently, since it is also a basic language vocab)
Or not, because it is not that essential like rdf(s) etc. ie not breaking code 
etc.)


But generalizing I see you point that ‘being essential’ depends in the end on 
what you want to do with it….(forms etc.)
(and explicit import only works if the stuff imported is perfect…)

All in all, I think, shacl getting more and more important, it would be best to 
automatically load it.
(in other words: TBBC being by default a RDF/RDFS/OWL/SHACL-tool).

For now, I’ll keep the sh imports explicitly in…..

Gr 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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D768D0.93819BB0]<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.




Van: topbraid-users@googlegroups.com  Namens 
Holger Knublauch
Verzonden: donderdag 24 juni 2021 00:58
Aan: topbraid-users@googlegroups.com
Onderwerp: Re: [topbraid-users] sh import?



On 2021-06-24 7:04 am, 'Bohms, H.M. (Michel)' via TopBraid Suite Users wrote:
My view…sh would fit well in that list of languages (xsd, rdf, rdfs, owl, …) 
that are handled without explicit import…

What does it even mean to be "handled". In all TopBraid tools, there is a 
hidden automated import of system triples including XSD, RDF etc. Without that, 
no forms and other algorithms would work. Algorithms wouldn't even know that 
owl:Class rdfs:subClassOf rdfs:Class. The design of OWL in this respect is a 
failure, and I believe they don't want people to import the metamodel because 
it broke some OWL DL algorithms with the introduction of metaclasses. Having to 
implement some special hidden graph is ugly.

Holger



???

Counterargument?



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D768D0.93819BB0]<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.




Van: 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
<mailto:topbraid-users@googlegroups.com>
Verzonden: woensdag 23 juni 2021 22:59
Aan: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com>
Onderwerp: RE: [topbraid-users] sh import?

More like:

Is sh in the league of xsd/rdf/rdfs/owl (not imported)

Or in the league of others being imported explicitly



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D768D0.93819BB0]<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.




Van: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com> 
mailto:topbraid-users@googlegroups.com>> 
Namens Holger Knublauch
Verzonden: woensdag 23 juni 2021 22:03
Aan: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com>
Onderwerp: Re: [topbraid-users] sh import?



On 23/06/2021 8:37 pm, 'Bohms, H.M. (Michel)' via TopBraid Suite Users wrote:
Is it needed to explicitly import sh?

For what application?

In general, owl:imports are a good thing. They make the semantics of the used 
resources more explicit and transparent. If we skip them here, where would this 
end: use skos:Concept without importing SKOS Core? Makes no sense to me.

Holger



Or is it like rdfs, rdfs, owl, xsd etc.

(I used to import dash but giv

RE: [topbraid-users] sh import?

2021-06-24 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Yes in case of ‘choice’ checkbox is fine
However we also have scenarios where both OWL and SHACL are relevant (say for 
use cases involving inference and verification).
Or in future where we might want to go shacl-only (blog irene…).

Those scenarios would benefit from automatic shacl import….



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D768E1.030616E0]<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.




Van: topbraid-users@googlegroups.com  Namens 
David Price
Verzonden: donderdag 24 juni 2021 09:25
Aan: topbraid-users@googlegroups.com
Onderwerp: Re: [topbraid-users] sh import?


On 24 Jun 2021, at 07:21, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Hi Holger

I see the issue.

So reformulated my question is:

Is shacl import also automated now (like eg rdf)?
(It seems not, since deleting the import also deletes the shacl tab)

If not, should be it be? (consistently, since it is also a basic language vocab)
Or not, because it is not that essential like rdf(s) etc. ie not breaking code 
etc.)

But generalizing I see you point that ‘being essential’ depends in the end on 
what you want to do with it….(forms etc.)
(and explicit import only works if the stuff imported is perfect…)

All in all, I think, shacl getting more and more important, it would be best to 
automatically load it.
(in other words: TBBC being by default a RDF/RDFS/OWL/SHACL-tool).

Hi Michel,

If users want SHACL then in TBC use File, New, SHACL Shapes file and there’s a 
checkbox to decide initial imports of dash or pure SHACL.

If users want RDFS/OWL then use File, New, RDF File.

TBC users have control.

Cheers,
David





For now, I’ll keep the sh imports explicitly in…..

Gr 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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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.




Van: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com> 
mailto:topbraid-users@googlegroups.com>> 
Namens Holger Knublauch
Verzonden: donderdag 24 juni 2021 00:58
Aan: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com>
Onderwerp: Re: [topbraid-users] sh import?


On 2021-06-24 7:04 am, 'Bohms, H.M. (Michel)' via TopBraid Suite Users wrote:
My view…sh would fit well in that list of languages (xsd, rdf, rdfs, owl, …) 
that are handled without explicit import…
What does it even mean to be "handled". In all TopBraid tools, there is a 
hidden automated import of system triples including XSD, RDF etc. Without that, 
no forms and other algorithms would work. Algorithms wouldn't even know that 
owl:Class rdfs:subClassOf rdfs:Class. The design of OWL in this respect is a 
failure, and I believe they don't want people to import the metamodel because 
it broke some OWL DL algorithms with the introduction of metaclasses. Having to 
implement some special hidden graph is ugly.
Holger


???

Counterargument?



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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.




Van: 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
<mailto:topbraid-users@googlegroups.com>
Verzonden: woensdag 23 juni 2021 22:59
Aan: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com>
Onderwerp: RE: [topbraid-use

RE: [topbraid-users] label position

2021-06-29 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Thx Irene

Following offline discussion with David I guess we better split the 2 worlds 
(skos versus non-skos (ie rdfs/owl/shacl)):

  *   No import of skos scheme in rdfs ont
  *   Copy prefLabel, altLabel, definition also to rdfs items (satisfying your 
note in the end)
  *   Keep the isDefinedBy, doing no harm, expecting no special semantics just 
a common way to be able to navigate from rdfs to skos where there could be more 
(more languages, broaders, groupings, examples, …)
Gr michel

From: topbraid-users@googlegroups.com  On 
Behalf Of Irene Polikoff
Sent: dinsdag 29 juni 2021 15:54
To: topbraid-users@googlegroups.com
Cc: benno.koeho...@rws.nl; Sander Stolk 
Subject: Re: [topbraid-users] label position

I will answer this question from two perspectives:

1. Standards
2. TopBraid EDG

1. From the standards perspective, rdfs:isDefinedBy is a utility property that 
has no standard semantics.

It is typically used to connect a resource to its “home” vocabulary (a graph). 
This is the use case specifically mentioned by the RDFS specification and this 
is how it is typically used in practice.

Not having standard semantics means that users are generally free to use it in 
any way they want - with an understanding that there is no standard treatment 
of it by tools. A tool could decide to do something special when they see this 
property - or not. Most (all?) tools don’t.

Thus, if your intended semantics (meaning) is that the object of a triple with 
rdfs:isDefinedBy predicate carries a label and a definition for the subject of 
that triple, it is up to you to implement software that will understand this 
semantics and will act on it. You can’t expect that a standards compliant tools 
will understand this.

2. How TopBraid EDG will treat this information

As per above, by default, TopBraid EDG will simply treat a triple with 
rdfs:isDefinedBy predicate the same ass any other triple. It will not mean 
anything special to EDG - unless you tell EDG that it has a special meaning.

You can define inference rules to give rdfs:isDefinedBy a special meaning. For 
example, the property value rule below will automatically infer skos:definition 
for sml:Activity from sml-term:Activity.

Or, more generally, for any class from any concept connected to it by 
rdfs:isDefinedBy.




owl:Class
  sh:property owl:Class-definition ;
sh:property owl:Class-isDefinedBy ;
.



owl:Class-isDefinedBy
  a sh:PropertyShape ;
  sh:path rdfs:isDefinedBy ;
  sh:class skos:Concept ;


owl:Class-definition
  a sh:PropertyShape ;
  sh:path skos:definition ;
  sh:values [
  sh:path skos:definition ;
  sh:nodes [
  sh:path rdfs:isDefinedBy ;
] ;
] ;
.


Note: You can do this for any property except for the 
rdfs:label/skos:prefLabel. EDG uses special indexing and algorithms for these 
labels and their values need to be asserted directly for each resource.


On Jun 29, 2021, at 3:46 AM, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:


Dear All,

We use the pattern:



sml-term:Activity

  a skos:Concept ;

  skos:broader sml-term:Entity ;

  skos:definition "An activity is something possibly or actually happening in 
space and time"@en ;

  skos:prefLabel "Activity"@en ;

.



sml:Activity

  a rdfs:Class ;

  rdfs:isDefinedBy sml-term:Activity ;

  rdfs:subClassOf sml:Entity ;

.

But this means that the label is only indirectly available for sml:Activity 
(via “isDefinedBy.prefLabel”)

Is this an issue? (many tools like to have a direct label for their classes)
Better solutions?
(I’d like to define only once, not double; label feels naturally close to 
definition; maybe only prefLabel to rdfs-variant and leave altLabel/definition 
at skos?)

Thx for advice,
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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/65077d500edc4a6bb4f8289d08326df2%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/65077d500edc4a6bb4f8289d0832

RE: [topbraid-users] label position

2021-06-30 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

pe ;
sh:path skos:definition ;
sh:values [
sh:path skos:definition ;
sh:nodes [
sh:path rdfs:isDefinedBy ;
] ;
] ;
.

Note: You can do this for any property except for the
rdfs:label/skos:prefLabel. EDG uses special indexing and algorithms for these
labels and their values need to be asserted directly for each resource.

On Jun 29, 2021, at 3:46 AM, 'Bohms, H.M. (Michel)' via TopBraid Suite Users
mailto:topbraid-users@googlegroups.com>> wrote:

Dear All,

We use the pattern:

sml-term:Activity

a skos:Concept ;

skos:broader sml-term:Entity ;

skos:definition "An activity is something possibly or actually happening in
space and time"@en ;

skos:prefLabel "Activity"@en ;

sml:Activity

a rdfs:Class ;

rdfs:isDefinedBy sml-term:Activity ;

rdfs:subClassOf sml:Entity ;

But this means that the label is only indirectly available for sml:Activity
(via “isDefinedBy.prefLabel”)

Is this an issue? (many tools like to have a direct label for their classes)
Better solutions?
(I’d like to define only once, not double; label feels naturally close to
definition; maybe only prefLabel to rdfs-variant and leave altLabel/definition
at skos?)

Thx for advice,
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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>

<http://www.tno.nl/>

T
M
W

Sander Stolk
Head of Innovation

In office on Monday, Tuesday, Friday
+316 142 750 66
sanderst...@semmtech.com<mailto://sanderst...@semmtech.com>
www.semmtech.com<https://www.semmtech.com/>

[cid:image002.png@01D76D8D.242BDE30]

The information in this message is private and confidential, and only intended
for the addressee. Should you receive this message by mistake, you are hereby
notified that any disclosure, reproduction, distribution or use of this message
is strictly prohibited. Please inform the sender by reply transmission and
delete the message without copying or opening it.

--
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/51e1877d24e64f88b6e2a2e7a149ec18%40tno.nl.

[topbraid-users] label position

2021-06-29 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Dear All,

We use the pattern:

sml-term:Activity

a skos:Concept ;

skos:broader sml-term:Entity ;

skos:definition "An activity is something possibly or actually happening in
space and time"@en ;

skos:prefLabel "Activity"@en ;

sml:Activity

a rdfs:Class ;

rdfs:isDefinedBy sml-term:Activity ;

rdfs:subClassOf sml:Entity ;

But this means that the label is only indirectly available for sml:Activity
(via "isDefinedBy.prefLabel")

Is this an issue? (many tools like to have a direct label for their classes)
Better solutions?
(I'd like to define only once, not double; label feels naturally close to
definition; maybe only prefLabel to rdfs-variant and leave altLabel/definition
at skos?)

Thx for advice,
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 michel.bo...@tno.nl

Location

[cid:image001.gif@01D76CCB.A2FB2D50]

--
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/65077d500edc4a6bb4f8289d08326df2%40tno.nl.

RE: [topbraid-users] label position

2021-06-29 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Hi David

I see your point: “better use skos only separate from rdfs/owl/shacl”

But ok we said it would be handy to combine (many parties already did in NL 
like Cadastre).

But then it seems we have to double….which goes a bit against the principle of 
separation of concerns….

Ie also (red):


sml:Activity

  a rdfs:Class ;

  rdfs:isDefinedBy sml-term:Activity ;

  rdfs:subClassOf sml:Entity ;

  skos:definition "An activity is something possibly or actually happening in 
space and time"@en ;

  skos:prefLabel "Activity"@en ;

.

I hoped for less doubling like:


sml:Activity

  a rdfs:Class ;

  rdfs:isDefinedBy sml-term:Activity ;

  rdfs:subClassOf sml:Entity ;

  skos:prefLabel "Activity"@en ;

.

Isn’t the skos:definition also for human interpretation only so that it can 
stays at skos-side?

Wrt tools expecting labels..if I rember right edg also likes/needs labels right?

If edg has no issue I might stay with the current approach (only having 
uris/names) for rdfs/owl/shacl side.

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D76CEC.13AA5290]<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.




Van: topbraid-users@googlegroups.com  Namens 
David Price
Verzonden: dinsdag 29 juni 2021 12:37
Aan: topbraid-users@googlegroups.com
CC: Benno Koehorst ; Sander Stolk 

Onderwerp: Re: [topbraid-users] label position




On 29 Jun 2021, at 08:46, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:


Dear All,

We use the pattern:



sml-term:Activity

  a skos:Concept ;

  skos:broader sml-term:Entity ;

  skos:definition "An activity is something possibly or actually happening in 
space and time"@en ;

  skos:prefLabel "Activity"@en ;

.



sml:Activity

  a rdfs:Class ;

  rdfs:isDefinedBy sml-term:Activity ;

  rdfs:subClassOf sml:Entity ;

.

But this means that the label is only indirectly available for sml:Activity 
(via “isDefinedBy.prefLabel”)

Is this an issue? (many tools like to have a direct label for their classes)

I imagine tools will use one of the local name or perhaps URI or perhaps 
prefixed name. Being an issue depends on use case (i.e. no problem at all if 
for data exchange but perhaps for a human looking at a UI).


Better solutions?
(I’d like to define only once, not double;

Not possible.


label feels naturally close to definition; maybe only prefLabel to rdfs-variant 
and leave altLabel/definition at skos?)

There are two different things with different URIs. They do not “share” 
properties. That’s just how RDF and RDFS/OWL and SKOS work, so will not 
surprise anyone or any tool. It’s unclear if you expect them to ever be used 
together, but as SKOS is an OWL ontology and the other seems RDFS I imagine not.

A Concept and a Class are not the same thing at all. An RDFS Class (data 
modelling artefact) has members/class extension that are resources, while a 
SKOS Concept (e.g. a library science artefact) does not as it’s main purpose is 
as the Web identifier for the variety of labels/definitions in multiple 
languages and flexible, not-formally-defined relations that it holds.

Note that the SKOS crew do want it used in a manner like this, but not with the 
specific approach being taken above:

Looking to the future, SKOS occupies a position between the exploitation and 
analysis of unstructured information, the informal and socially-mediated 
organization of information on a large scale, and the formal representation of 
knowledge. By making the accumulated experience and wisdom of knowledge 
organization in the library and information sciences accessible, applicable and 
transferable to the technological context of the Semantic Web, in a way that is 
complementary to existing Semantic Web technology (and in particular formal 
systems of knowledge representation such as OWL), it is hoped that SKOS will 
enable many new and valuable applications, and will also lead to new 
integrative lines of research and development in both technology and practice.

Every class and property should have its own label and more importantly its own 
local definition. Note that formal class definitions often place the class in 
the class hierarchy (i.e. a  is a  that  ) whereas a 
concept definition would not do so. Concept labels/defs are for all humans, and 
those for Classes are aimed at software developer

RE: [topbraid-users] class name?

2021-02-10 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Van: topbraid-users@googlegroups.com Namens
David Price
Verzonden: woensdag 10 februari 2021 13:29
Aan: topbraid-users@googlegroups.com
Onderwerp: Re: [topbraid-users] class name?

I assume by “class name” you mean the local name part of the URI following the
hash or final slash. If not, then ask again and be more clear.

Øyes

If I remember correctly, there is or was some issue with the local name part of
a URI starting with a number wrt being 100% valid following the underlying
standards for such things (and I mean down int the lower level standards, not
in SHACL or OWL/RDFS).

ØI assume its an rdf-level issue indeed

I do remember odd/occasional cases where the maybe the encoding into TTL or
viewing in the UI didn’t correctly use prefixes. If it’s a concern, what I’ve
done in the past was always have the URI-building-function include something
for the local name that like “ID_” + to make sure and avoid those
cases.

That said, I’ve also worked on projects using TBC and EDG where numbers were
used and everything important works. In fact, in some projects the whole local
name was an integer cast into a string for use in building the URI.

So, “2L-14” should be fine even if you occasionally see something a bit odd in
a TBC UI, etc.

ØThe actual issue I have now:

wn:TL-ZOAB-dl
rdf:type owl:Class ;
rdfs:subClassOf wn:TL-PA ;
.

Client wants:

wn:1L-ZOAB-dl
rdf:type owl:Class ;
rdfs:subClassOf wn:TL-PA ;
.

(being a subclass of asphalt)

In TBC:
When I change to 2nd option I get:

[cid:image001.png@01D6FFB9.C5115B50]

So the name space (“wn”) disappears…

Cheers,
David

On 10 Feb 2021, at 10:16, 'Bohms, H.M. (Michel)' via TopBraid Suite Users
mailto:topbraid-users@googlegroups.com>> wrote:

Is it possible that a classname starts with a number?
“2L-14”

(I experienced an issue in TBC)

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>

<http://www.tno.nl/>

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 topbraid-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/8afe3731a37c4eea81e0bd5a7f2fc022%40tno.nl.

[topbraid-users] class name?

2021-02-10 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Is it possible that a classname starts with a number?
"2L-14"

(I experienced an issue in TBC)



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 michel.bo...@tno.nl

Location



[cid:image001.gif@01D6FF9E.1BFCDB40]

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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/15b453a21f0449378912b26d837380ba%40tno.nl.

RE: [topbraid-users] class name?

2021-02-10 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

It is not just an interface issue

Also in the file after save it gives:

<https://w3id.org/def//wegennetwerk#1L-ZOAB-dl>
  a owl:Class ;
  rdfs:subClassOf wn:TL-PA ;
.

Instead of:

wn::1L-ZOAB-dl
  a owl:Class ;
  rdfs:subClassOf wn:TL-PA ;
.

So if the spec allows I would just see it as an TBC issue that could be fixed….

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>

[cid:image002.gif@01D6FFBE.B9CFA2B0]<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.

Van: topbraid-users@googlegroups.com  Namens 
David Price
Verzonden: woensdag 10 februari 2021 14:54
Aan: topbraid-users@googlegroups.com
Onderwerp: Re: [topbraid-users] class name?

On 10 Feb 2021, at 13:34, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Van: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com> 
mailto:topbraid-users@googlegroups.com>> 
Namens David Price
Verzonden: woensdag 10 februari 2021 13:29
Aan: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com>
Onderwerp: Re: [topbraid-users] class name?

I assume by “class name” you mean the local name part of the URI following the 
hash or final slash. If not, then ask again and be more clear.

>yes

If I remember correctly, there is or was some issue with the local name part of 
a URI starting with a number wrt being 100% valid following the underlying 
standards for such things (and I mean down int the lower level standards, not 
in SHACL or OWL/RDFS).

>I assume its an rdf-level issue indeed

I do remember odd/occasional cases where the maybe the encoding into TTL or 
viewing in the UI didn’t correctly use prefixes. If it’s a concern, what I’ve 
done in the past was always have the URI-building-function include something 
for the local name that like “ID_” +  to make sure and avoid those 
cases.

That said, I’ve also worked on projects using TBC and EDG where numbers were 
used and everything important works. In fact, in some projects the whole local 
name was an integer cast into a string for use in building the URI.

So, “2L-14” should be fine even if you occasionally see something a bit odd in 
a TBC UI, etc.

>The actual issue I have now:

wn:TL-ZOAB-dl
  rdf:type owl:Class ;
  rdfs:subClassOf wn:TL-PA ;
.

Client wants:

wn:1L-ZOAB-dl
  rdf:type owl:Class ;
  rdfs:subClassOf wn:TL-PA ;
.

(being a subclass of asphalt)

In TBC:
When I change to 2nd option I get:

[cid:image003.png@01D6FFBE.B9CFA2B0]

So the name space (“wn”) disappears…

Yes, as I mentioned I did remember this wrt TBC form and prefixes in this case. 
I cannot remember the underlying issue but as I said I think there was a time 
when these were not “valid” wrt some standard.

In any case, everything “works” as far as the semantics are concerned.  If that 
form is a problem for you/client, then I suggest using the “human label” UI 
mode (person icon next to Home icon) in Composer where it will show the 
rdfs:label instead of the local name of the URI. That means you also get the 
much cleaner looking use of spaces in the UI wrt class and property names.

FWIW Composer is an IDE intended for developers, and there is the human label 
view mode, so these corner cases are not something likely to ever be “fixed” in 
Composer.

Cheers,
David

On 10 Feb 2021, at 10:16, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Is it possible that a classname starts with a number?
“2L-14”

(I experienced an issue in TBC)

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>

<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, se

[topbraid-users] best practise name space in multiple languages?

2021-04-06 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

In case I have the same specification on different modelling levels:

* Skos
* Rdfs
* Rdfs+owl
* Rdfs+shacl

Is there some best practice for the name space?

(compare same name space for different serializations but now for different
languages used...).

I now have ie:

# baseURI: https://w3id.org/def/nen2660-rdfs

But I got the comment that just:
# baseURI: https://w3id.org/def/nen2660

was preferred.

But then I have 4 variants (actually 12: all in rdf/xml, turtle and json-ld)
specifying for the same name space.

Thx for advice,
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 michel.bo...@tno.nl

Location

[cid:image001.gif@01D72ACE.6D3A5D10]

--
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/8c5728fd3b8b45cd8ca17055b8df9688%40tno.nl.

[topbraid-users] rdfs+shacl issue

2021-03-26 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

I now have often:

[cid:image001.png@01D72226.14A5C9B0]


But I want to be more strict SHACL: RDFS+SHACL only using owl for 
owl:ontology/owl:import actually.

What can happen to the owl:unionOf within sh:class in that case?

Can I use some shacl counterpart?
Or if not, do I have to delete this constraint?

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 michel.bo...@tno.nl

Location



[cid:image002.gif@01D72226.14A5C9B0]

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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/b17aabc432484d1287c5fefa499698d7%40tno.nl.

Re: [topbraid-users] TBCME 7 multiple errors on opening

2021-03-26 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

I had it yesterday again having thought i undoubled...wiil recheck and send log
for info.
Michel

Op 26 mrt. 2021 00:13 schreef Holger Knublauch :

I suspect this is the same error that Michel Bohms had reported on the same
mailing list a few days ago. This is a regression in TBC that we will fix ASAP.

Meanwhile, if your existing workspace contains more than one graph/file with
the same base URI, it would crash at start-up and produce these many alarming
errors. Please go through the workspace and check whether two files have the
same base URI. This may for example happen if you have copied the same file
with two names, or saved the same graph both as Turtle and RDF/XML.

Holger

On 2021-03-26 12:01 am, Tim Jones wrote:
Hi

Have just installed TBCME 7, but when I open it I get a stream of error in the
UI:
e.g.
Plug-in org.topbraidcomposer.navigation was unable to load class
org.topbraidcomposer.navigation.subclassestree.SubClassesTreeView.

Plug-in "org.topbraidcomposer.navigation" was unable to instantiate class
"org.topbraidcomposer.navigation.propertiestree.PropertiesTreeView".

and in the log:
[javaw_gXRaDzPucf.png]

I unzipped the distribution into a clean folder and used my existing workspace
folder (from the previous version), which warned me that it would be upgraded.

Is there something that I have missed or done wrong?

Thanks,

--
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/37ac326e-5a0d-1a8f-13a8-7019b2945ae1%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.

--
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/7d013b48-6a78-4de5-86da-018801db526b%40email.android.com.

RE: [topbraid-users] TBCME 7 multiple errors on opening

2021-03-26 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

It was indeed some leftover doubling on my side:
[cid:image001.png@01D7221D.D49A7FD0]

Often the case when you have alternative serialisations for the same ontology.

For the time being I’ll use the 7beta which starts ok.

Gr 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 michel.bo...@tno.nl

Location

[cid:image002.gif@01D7221D.D49A7FD0]

Van: topbraid-users@googlegroups.com Namens
Holger Knublauch
Verzonden: vrijdag 26 maart 2021 00:13
Aan: topbraid-users@googlegroups.com
Onderwerp: Re: [topbraid-users] TBCME 7 multiple errors on opening

I suspect this is the same error that Michel Bohms had reported on the same
mailing list a few days ago. This is a regression in TBC that we will fix ASAP.

Holger

On 2021-03-26 12:01 am, Tim Jones wrote:
Hi

Plug-in "org.topbraidcomposer.navigation" was unable to instantiate class
"org.topbraidcomposer.navigation.propertiestree.PropertiesTreeView".

and in the log:

I unzipped the distribution into a clean folder and used my existing workspace
folder (from the previous version), which warned me that it would be upgraded.

Is there something that I have missed or done wrong?

Thanks,

Tim
--
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/8200b155-a0e4-4c17-a146-841ab6742a3en%40googlegroups.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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/37ac326e-5a0d-1a8f-13a8-7019b2945ae1%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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/9c8bbe5ab9f146ae902306b4e883e50c%40tno.nl.

RE: [topbraid-users] best practise name space in multiple languages?

2021-04-06 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

ed across 
files, and therefore don’t risk running out of sync, e.g. if someone changes 
the RDFS classes only in one file.


Exactly! Maintenance is always a concern - and most people ignore it until it 
causes a huge problem later in life (unfortunately, too often in someone else’s 
life).


I don’t know enough about how the SKOS version is different to comment on that. 
I would find it rather confusing if a resource is a class in one graph but a 
SKOS concept in another.

The case where I regularly see this is if the artefact being defined is “master 
data” or a “reference data library”. If the OWL is really just a large 
hierarchy of classes with annotation properties and no restrictions, then I 
have seen those be published as OWL and as SKOS with the same URIs. That does 
mean you should not mix the two, of course.


ØHmmm not mixt: aren they just multiple typed: ie something is a skos 
concept, an rdfs class and a shack shape at the same time…or will that result 
in problems..?

Scenarios where either language might be used include supporting 
semantic/faceted search and where a class in an ontology has a property like 
“external classification” or “_ category” or “_group” (e.g. the property 
range is almost just an enumeration).



The topic of RDF/XML vs Turtle etc is another dimension, typically solved using 
HTTP content negotiation. All serialisations would be accessible from the same 
server URLs yet the server would return different results depending on what 
accept header the client requests.

Holger



On 6 Apr 2021, at 6:20 pm, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

In case I have the same specification on different modelling levels:

  *   Skos
  *   Rdfs
  *   Rdfs+owl
  *   Rdfs+shacl

Is there some best practice  for the name space?

Question - Does the RDFS/OWL import and build on the RDFS? That seems logical 
to me so just wondering. Even the SHACL could import and build on the RDFS (and 
perhaps even the RDFS/OWL). That way the “class” would have the same URI all 
the time and you’d just be saying more/different things about it as the 
languages allow more to be said and the rationale for the different namespaces 
might be clarified a bit.


ØYES, that is what I would like….

ØPeople start in skos

ØExtend the skost concept in rdfs

ØExtend further in shacl for the constraints

ØAll about the same bridge

ØSo if I want that…what name space do I need for the concepts, classes and 
shapes (for the same thing)

Cheers,
David



(compare same name space for different serializations but now for different 
languages used…).

I now have ie:

# baseURI: https://w3id.org/def/nen2660-rdfs

But I got the comment that just:
# baseURI: https://w3id.org/def/nen2660

was preferred.

But then I have 4 variants (actually 12: all in rdf/xml, turtle and json-ld) 
specifying for the same name space.

Thx for advice,
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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/8c5728fd3b8b45cd8ca17055b8df9688%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/8c5728fd3b8b45cd8ca17055b8df9688%40tno.nl?utm_medium=email_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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/9C404919-EDE6-4E6A-B1EA-98AB888E8E03%40topquadrant.com<https://groups.google.com/d/msgid/topbraid-users/9C404919-EDE6-4E6A-B1EA-98AB888E8E03%40topquadrant.com?utm_medium=email_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

[topbraid-users] json-ld question

2021-03-18 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Not really TBC questions but I guess you can give the best answer.

I see popularity of json-ld rising a lot (as optimal compromise between webdev
and ld/sw world) where people might just forget about the (for them) complex
RDF conceptuals above….

In that sense I see more and more projects that go json-ld (iso rdf/xml, turtle
etc.) also involving storage options like mongodb iso triple/quad stores. At
the same time people like graphql(-ld) over sparql.

These trends gives rise for me to some issues:

1.
If RDF* evolves bringing us better metadata options (treating statements as
objects again) on LD side would that also give rise to a JSON-LD* next to
Turtle*?
Or is json-ld already by itself more flexible here so that no change is needed?
(ie is the current use of json-ld as RDF serialization an already restricted
usage?)

I am trying to find out if turtle and hence Turtle* will have advantages over
json-ld…

2.
I know graphQL-LD approach as defined/demonstrated etc. by Ghent university
(https://comunica.github.io/Article-ISWC2018-Demo-GraphQlLD/).
Is your prefixes graphql schema extension doing (functionaly) the same?
If so isn’t there room for a standard graph-ql-ld variant having those
extensions in a standard way?
Or… is such a GraphQL update already in the making (much a like json to
json-ld)?

3.
What will happen in future: shacl or graphql schema or both?
(knowing slide no. 20 from:
https://www.topquadrant.com/project/graphql_json_rdf/)

4.
Why is there a graphql schema language anyway? Why not use json-ld schema
definitions for that (because it is not powerful enough)?
(like in schema.org if I am right)

Sorry if these questions are out of scope.
It’s just that I need some story when people ask “why do we have shacl/sparql,
graphql schema/graphql, json-ld for schemas (and also json schema)….can’t you
make up your mind?”

Thx for your views
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 michel.bo...@tno.nl

Location

[cid:image001.gif@01D71BFD.AE8CFC30]

--
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/5402dc770eb948068fe971f523d7879e%40tno.nl.

RE: [topbraid-users] json-ld question

2021-03-18 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Thx David, all clear!


Wrt the red below, the editor things differently in: 
http://manu.sporny.org/2014/json-ld-origins-2/

Where he says:

“
I’ve heard many people say that JSON-LD is primarily about the Semantic Web, 
but I disagree, it’s not about that at all. JSON-LD was created for Web 
Developers that are working with data that is important to other people and 
must interoperate across the Web. The Semantic Web was near the bottom of my 
list of “things to care about” when working on JSON-LD, and anyone that tells 
you otherwise is wrong. []
TL;DR: The desire for better Web APIs is what motivated the creation of 
JSON-LD, not the Semantic Web. If you want to make the Semantic Web a reality, 
stop making the case for it and spend your time doing something more useful, 
like actually making machines smarter or helping people publish data in a way 
that’s useful to them.
"

For someone with an RDF-hat that sees JSON-LD as “just” a RDF serialization 
(like turtle, drf/xml, nriples etc.)  I can see your point.
But we have to be aware of people with other heads.

And yes, I know RDFS/OWL/SHACL are providing features not in json-ld (when used 
on schema level), JSON Schema or  graphql schema.

So indeed as you say the truth will be in the middle (of webdev & LD) depending 
on the specific use cases.
Its more that we are promoting LD so much but at the same time and we encounter 
people  that like manu sporny want to do things simpler, webdev-based, etc. and 
then we need a good story.
Sometimes wished we good look 5 /10 years ahead 

THX Michel


On 18 Mar 2021, at 13:01, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Not really TBC questions but I guess you can give the best answer.

I see popularity of json-ld rising a lot (as optimal compromise between webdev 
and ld/sw world) where people might just forget about the (for them) complex 
RDF conceptuals above….

JSON-LD does nothing to reduce the complex concepts that might be defined in 
RDFS, OWL or SHACL data models.  JSON-LD is an implementation format for 
RDF-based data. Without the underlying RDF-based model there is no JSON-LD.

It makes sense for Web developers to use anything making Javascript development 
easier (e.g. eliminating having to learn a new format/syntax) . So, for that 
scenario JSON-LD may very well be their preference.

However, most folks think TTL is easier to read and write in a text editor, for 
example vs JSON-LD or RDF/XML. Also, if you don’t know/prefer Javascript and 
JSON you may not going to prefer JSON-LD or if your application is not 
browser-based then it may actually be a Con, not a Pro.



In that sense I see more and more projects that go json-ld (iso rdf/xml, turtle 
etc.) also involving storage options like mongodb iso triple/quad stores. At 
the same time people like graphql(-ld) over sparql.

Probably depends on if you come from a database vs. Web developer background as 
much as anything else.



These trends gives rise for me to some issues:

1.
If RDF* evolves bringing us better metadata options (treating statements as 
objects again) on LD side would that also give rise to a JSON-LD* next to 
Turtle*?
Or is json-ld already by itself more flexible here so that no change is needed? 
(ie is the current use of json-ld as RDF serialization an already restricted 
usage?)

I am trying to find out if turtle and hence Turtle* will have advantages over 
json-ld…


Until we see the final “standards” we cannot be 100% sure, but it seems 
unlikely one will be better than the other wrt this question. I imagine the 
criteria for choosing between them in a specific scenario is unlikely to 
change. Again, we’ll have to wait and see though as nobody knows right now.


2.
I know graphQL-LD approach as defined/demonstrated etc. by Ghent university 
(https://comunica.github.io/Article-ISWC2018-Demo-GraphQlLD/).
Is your prefixes graphql schema extension doing (functionaly) the same?

Our Web site says:

Query schemas for use with GraphQL are automatically generated from the data 
models. This includes powerful features to select, filter, aggregate, 
dynamically compute and page results. For even more power, full support for 
SPARQL expressions is available from GraphQL queries. Data updates are 
automatically validated using SHACL shapes.

So I’ll guess not exactly the same as what Ghent is doing.


If so isn’t there room for a standard graph-ql-ld variant having those 
extensions in a standard way?
Or… is such a GraphQL update already in the making (much a like json to 
json-ld)?

There is a working draft next release of GraphQL online but it does not mention 
this topic as far as I can tell. I’m not a GraphQL expert though.



3.
What will happen in future: shacl or graphql schema or both?
(knowing slide no. 20 from: 
https://www.topquadrant.com/project/graphql_json_rdf/)

If you mean in EDG for the next few years, then “both”. Cannot say for ot

RE: [topbraid-users] json-ld question

2021-03-18 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Wrt my first issue I just came across:

https://json-ld.github.io/json-ld-star/



Which was exactly I was looking for !

(This NOTE explores an extension of JSON-LD which can allow the value of an @id 
property to be an embedded 
node<https://json-ld.github.io/json-ld-star/#dfn-embedded-node>, and the 
description of an annotation 
object<https://json-ld.github.io/json-ld-star/#dfn-annotation-object> which 
serves as a short-hand when the annotated value also is described directly in 
the graph.)

{
 "@context": {
"@base": "http://example.org/;,
"@vocab": "http://example.org/;
 },
 "@id": {
"@id": "bob",
"age": 42
 },
 "certainty": 0.8
}

Gr 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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D71C13.1265D960]<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.




Van: topbraid-users@googlegroups.com  Namens 
David Price
Verzonden: donderdag 18 maart 2021 15:22
Aan: topbraid-users@googlegroups.com
Onderwerp: Re: [topbraid-users] json-ld question




On 18 Mar 2021, at 13:01, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Not really TBC questions but I guess you can give the best answer.

I see popularity of json-ld rising a lot (as optimal compromise between webdev 
and ld/sw world) where people might just forget about the (for them) complex 
RDF conceptuals above….

JSON-LD does nothing to reduce the complex concepts that might be defined in 
RDFS, OWL or SHACL data models.  JSON-LD is an implementation format for 
RDF-based data. Without the underlying RDF-based model there is no JSON-LD.

It makes sense for Web developers to use anything making Javascript development 
easier (e.g. eliminating having to learn a new format/syntax) . So, for that 
scenario JSON-LD may very well be their preference.

However, most folks think TTL is easier to read and write in a text editor, for 
example vs JSON-LD or RDF/XML. Also, if you don’t know/prefer Javascript and 
JSON you may not going to prefer JSON-LD or if your application is not 
browser-based then it may actually be a Con, not a Pro.



In that sense I see more and more projects that go json-ld (iso rdf/xml, turtle 
etc.) also involving storage options like mongodb iso triple/quad stores. At 
the same time people like graphql(-ld) over sparql.

Probably depends on if you come from a database vs. Web developer background as 
much as anything else.



These trends gives rise for me to some issues:

1.
If RDF* evolves bringing us better metadata options (treating statements as 
objects again) on LD side would that also give rise to a JSON-LD* next to 
Turtle*?
Or is json-ld already by itself more flexible here so that no change is needed? 
(ie is the current use of json-ld as RDF serialization an already restricted 
usage?)

I am trying to find out if turtle and hence Turtle* will have advantages over 
json-ld…


Until we see the final “standards” we cannot be 100% sure, but it seems 
unlikely one will be better than the other wrt this question. I imagine the 
criteria for choosing between them in a specific scenario is unlikely to 
change. Again, we’ll have to wait and see though as nobody knows right now.


2.
I know graphQL-LD approach as defined/demonstrated etc. by Ghent university 
(https://comunica.github.io/Article-ISWC2018-Demo-GraphQlLD/).
Is your prefixes graphql schema extension doing (functionaly) the same?

Our Web site says:

Query schemas for use with GraphQL are automatically generated from the data 
models. This includes powerful features to select, filter, aggregate, 
dynamically compute and page results. For even more power, full support for 
SPARQL expressions is available from GraphQL queries. Data updates are 
automatically validated using SHACL shapes.

So I’ll guess not exactly the same as what Ghent is doing.


If so isn’t there room for a standard graph-ql-ld variant having those 
extensions in a standard way?
Or… is such a GraphQL update already in the making (much a like json to 
json-ld)?

There is a working draft next release of GraphQL online but it does not mention 
this topic as far as I can tell. I’m not a GraphQL expert though.



3.
What will happen in future: shacl or graphql schema or both?
(knowing slide no. 20 from: 
https://www.topquadrant.com/project/graphql_json_rdf/

RE: [topbraid-users] json-ld question

2021-03-18 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Right!

I see indeed that the “webdev world only” data modelling capabilities (graphql
schema, json/json-ld, json schema, …) are limited compared to
RDFS/OWL/SHACL/SHACL-AF.

I wonder how the “LD-haters” would deal with that….guess they just code it.

Avro was new to me…( https://en.wikipedia.org/wiki/Apache_Avro, yet another
data language)
Thx for the paper!

I see also the advantages of your ‘graphql-ld’ approach over Ghent keeping the
GraphQL Schema in the picture.

I was more wondering whether graphql (and graphql schema) could use json-ld
treatment more as first class citizen in some official GraphQL-LD (GraphQL
Schema-LD) instead of just as being a special version of json… (in a sense
standardizing the kind of extensions you did)
(I see this discussion in their lists without clear answers though)

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>

[cid:image001.gif@01D71C1A.BE1ABDF0]<http://www.tno.nl/>

Van: topbraid-users@googlegroups.com Namens
Irene Polikoff
Verzonden: donderdag 18 maart 2021 16:45
Aan: topbraid-users@googlegroups.com
Onderwerp: Re: [topbraid-users] json-ld question

On Mar 18, 2021, at 10:21 AM, David Price
mailto:dpr...@topquadrant.com>> wrote:

On 18 Mar 2021, at 13:01, 'Bohms, H.M. (Michel)' via TopBraid Suite Users
mailto:topbraid-users@googlegroups.com>> wrote:

Not really TBC questions but I guess you can give the best answer.

I see popularity of json-ld rising a lot (as optimal compromise between webdev
and ld/sw world) where people might just forget about the (for them) complex
RDF conceptuals above….

JSON-LD does nothing to reduce the complex concepts that might be defined in
RDFS, OWL or SHACL data models. JSON-LD is an implementation format for
RDF-based data. Without the underlying RDF-based model there is no JSON-LD.

I interpreted Michel’s words to be about complexity of understanding/using RDF
data structures and technologies when developing applications vs making it
possible for developers to stay in the JSON word. I did not think he was
talking about data models. If one stays solely within the JSON stack, the need
for data models is addressed by things like GraphQL Schema, JSON Schema and
Avro. They are pretty simple schema languages with minimal expressivity.

I am attaching a presentation that may be useful in understanding why we
believe the combination of SHACL with GraphQL is more powerful than just
GraphQL Schema and GraphQL.

GraphQL tools and infrastructure rely on having GraphQL Schema. I am referring
to tools such as GraphiQL which we integrated into EDG to provide interactive,
syntax directed query development and she documentation capabilities expected
by the GraphQL query developers. This is why EDG autogenerates GraphQL Schema
to enable GraphQL query.

Our approach is different from Ghent University:

Ghent University implementation translates GraphQL queries into SPARQL, then
runs SPARQL over RDF data. So, this is something that could potentially sit in
front of any SPARQL endpoint. I would, however, expect the (necessary to this
approach) heavy use of OPTIONAL in the generated SPARQL to create performance
problems for SPARQL endpoints. Their use of JSON-LD is about taking advantage
of JSON-LD context to map textual ids in GraphQL e.g., “prefLabel” to the full
URI.

In this approach, there is no GraphQL Schema to drive GraphQL tools or to
provide documentation to GraphQL developers as to what they could actually
query for. The GraphQL capabilities are limited to vanilla GraphQL. GraphQL is
a small and simple language for APIs with the built-in ability to extend it and
most GraphQL implementations add such extensions. There is no way to define or
provide extended GraphQL query capabilities or to query the

RE: [topbraid-users] json-ld question

2021-03-19 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Thx, VERY interesting
Quite strong statements (ora) from a semantic web principal….
At the same time I think he is not very clear in arguments why he thinks that 
way (json just being next xml)

I am more in the Newres/Gregg camp I think…

When ora says: It is never just JSON, ever”

Does he mean: people are making mistakes (like your next feedback there) or 
“there is much more non-json out there”?

And he also repeats all the time: syntax is not the issue…ok, semantics is 
bigger issue but isn’t that possible for json-ld then in rdfs/owl/shacl/json 
schema/json-ld/graphql schema… etc. (so I do not get the point)

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D71C98.97C277F0]<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.




Van: topbraid-users@googlegroups.com  Namens 
Holger Knublauch
Verzonden: vrijdag 19 maart 2021 00:06
Aan: topbraid-users@googlegroups.com
Onderwerp: Re: [topbraid-users] json-ld question



On 2021-03-19 2:28 am, 'Bohms, H.M. (Michel)' via TopBraid Suite Users wrote:
Right!

I see indeed that the “webdev world only” data modelling capabilities (graphql 
schema, json/json-ld, json schema, …) are limited compared to 
RDFS/OWL/SHACL/SHACL-AF.

I wonder how the “LD-haters”

https://twitter.com/oralassila/status/1364946776252420103

Holger


would deal with that….guess they just code it.

Avro was new to me…( https://en.wikipedia.org/wiki/Apache_Avro, yet another 
data language)
Thx for the paper!

I see also the advantages of your ‘graphql-ld’ approach over Ghent keeping the  
GraphQL Schema in the picture.

I was more wondering whether graphql (and graphql schema) could use json-ld 
treatment more as first class citizen in some official GraphQL-LD (GraphQL 
Schema-LD)  instead of just as being a special version of json… (in a sense 
standardizing the kind of extensions you did)
(I see this discussion in their lists without clear answers though)

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D71C98.97C277F0]<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.




Van: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com> 
<mailto:topbraid-users@googlegroups.com> 
Namens Irene Polikoff
Verzonden: donderdag 18 maart 2021 16:45
Aan: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com>
Onderwerp: Re: [topbraid-users] json-ld question





On Mar 18, 2021, at 10:21 AM, David Price 
mailto:dpr...@topquadrant.com>> wrote:





On 18 Mar 2021, at 13:01, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Not really TBC questions but I guess you can give the best answer.

I see popularity of json-ld rising a lot (as optimal compromise between webdev 
and ld/sw world) where people might just forget about the (for them) complex 
RDF conceptuals above….

JSON-LD does nothing to reduce the complex concepts that might be defined in 
RDFS, OWL or SHACL data models.  JSON-LD is an implementation format for 
RDF-based data. Without the underlying RDF-based model there is no JSON-LD.

I interpreted Michel’s words to be about complexity of understanding/using RDF 
data structures and technologies when developing applications vs making it 
possible for developers to stay in the JSON word. I did not think he was 
talking about data models. If one stays solely within the JSON stack, the need 
for data models is addressed by things like GraphQL Schema, JSON Schema and 
Avro. They are pretty simple schema languages with minimal expressivity.

I am attaching a presentation that may be useful in understanding why we 
believe the combination of SHACL with GraphQL is more powerful than just 
GraphQL Schema and GraphQL.

--
You received this message because you are subscribed to the Google Groups 
"TopBraid Suite Users" g

RE: [topbraid-users] json-ld question

2021-03-19 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Thx David and Holger

Your views really put things in perspective!

My conclusion at least like:
worlds come together syntactically but this is only a practical issue.
Semantically they are (and probably will stay) worlds apart with LD having the 
compat. Edge (basis in math/logic/grpahs)

In that sense I can now more clearly see TQ following the best path…

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D71CA5.E6905840]<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.




Van: topbraid-users@googlegroups.com  Namens 
David Price
Verzonden: vrijdag 19 maart 2021 09:29
Aan: topbraid-users@googlegroups.com
Onderwerp: Re: [topbraid-users] json-ld question




On 19 Mar 2021, at 07:25, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Thx, VERY interesting
Quite strong statements (ora) from a semantic web principal….
At the same time I think he is not very clear in arguments why he thinks that 
way (json just being next xml)

I imagine it is because they are both only modelling *data structures* in a 
narrow context. People think they are doing “data modelling” or even modelling 
semantics, but they are not. JSON schema is modelling JSON data structures, so 
JSON Schema is like using XSDs. For XSDs, people used to get very confused 
because their tools produced nice diagrams that looked at bit like UML, for 
example. However, they were actually *nothing* like UML because all they 
modelled was the structure of XML and the only “meaning” they conveyed was 
containment, attribute, ID and data value. I would get dragged into consulting 
engagements in a previous job to explain this to them - Model your data using 
better languages (e.g. UML) and then implement it in some technology (e.g. 
XML/XSDs). If you do otherwise it will often eventually come back and bite you.



I am more in the Newres/Gregg camp I think…

When ora says: It is never just JSON, ever”

Does he mean: people are making mistakes (like your next feedback there) or 
“there is much more non-json out there”?

And he also repeats all the time: syntax is not the issue…ok, semantics is 
bigger issue but isn’t that possible for json-ld then in rdfs/owl/shacl/json 
schema/json-ld/graphql schema… etc. (so I do not get the point)

I imagine something like this:

In the LD world, OWL has an underlying theory (sets and logic) and SHACL has an 
underlying theory (Graph Theory). JSON-LD has Javascript under it, on its own 
what it specifies are Javascript data structures with some RDF-based patterns 
so you can simulate say RDFS with it. It’s not better or worse than Python, 
Java, etc. on that front. It’s big advantage is that it’s great for 
browser-based apps. However, that does not mean it’s great for anything else on 
its own.

Technologists who support a “data centric” view are trying to make data an 
“asset” that organisations own and manage. If you are smart about that then 
data => knowledge. Supporting that means getting data out of any app or 
programming language. They argue that JSON-LD on its own doesn’t really do that.

Cheers,
David



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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.




Van: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com> 
mailto:topbraid-users@googlegroups.com>> 
Namens Holger Knublauch
Verzonden: vrijdag 19 maart 2021 00:06
Aan: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com>
Onderwerp: Re: [topbraid-users] json-ld question


On 2021-03-19 2:28 am, 'Bohms, H.M. (Michel)' via TopBraid Suite Users wrote:
Right!

I see indeed that the “webdev world only” data modelling capabilities (graphql 
schema, json/json-ld, json schema, …) are limited compared to 
RDFS/OWL/SHACL/SHACL-AF.

I wonder how the “LD-haters”
h

RE: [topbraid-users] json-ld question

2021-03-19 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Final remark:

If you have some good refs on the difference between structure & semantics, 
very welcome!

Personally I do not see this as two poles really…both deal with defining 
possibilities and impossibilities in your data. In that sense an XSD also 
covers semantics. And a json-ld spec on schema level also covers semantics. 
Clearly math/logic/graph-based SW-semantics in RDF/RDFS/OWL/SHACL-covers much 
MORE semantics.
In that sense I think the discussions on this aspect are a bit unnecessary 
polarized…..it feels more like different degrees of semantics….

But maybe there are some other essential differences that I do not see yet…..



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D71CAF.D9886C50]<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.




Van: 'Bohms, H.M. (Michel)' via TopBraid Suite Users 

Verzonden: vrijdag 19 maart 2021 09:58
Aan: topbraid-users@googlegroups.com
Onderwerp: RE: [topbraid-users] json-ld question

Thx David and Holger

Your views really put things in perspective!

My conclusion at least like:
worlds come together syntactically but this is only a practical issue.
Semantically they are (and probably will stay) worlds apart with LD having the 
compat. Edge (basis in math/logic/grpahs)

In that sense I can now more clearly see TQ following the best path…

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D71CAF.D9886C50]<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.




Van: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com> 
mailto:topbraid-users@googlegroups.com>> 
Namens David Price
Verzonden: vrijdag 19 maart 2021 09:29
Aan: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com>
Onderwerp: Re: [topbraid-users] json-ld question



On 19 Mar 2021, at 07:25, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Thx, VERY interesting
Quite strong statements (ora) from a semantic web principal….
At the same time I think he is not very clear in arguments why he thinks that 
way (json just being next xml)

I imagine it is because they are both only modelling *data structures* in a 
narrow context. People think they are doing “data modelling” or even modelling 
semantics, but they are not. JSON schema is modelling JSON data structures, so 
JSON Schema is like using XSDs. For XSDs, people used to get very confused 
because their tools produced nice diagrams that looked at bit like UML, for 
example. However, they were actually *nothing* like UML because all they 
modelled was the structure of XML and the only “meaning” they conveyed was 
containment, attribute, ID and data value. I would get dragged into consulting 
engagements in a previous job to explain this to them - Model your data using 
better languages (e.g. UML) and then implement it in some technology (e.g. 
XML/XSDs). If you do otherwise it will often eventually come back and bite you.


I am more in the Newres/Gregg camp I think…

When ora says: It is never just JSON, ever”

Does he mean: people are making mistakes (like your next feedback there) or 
“there is much more non-json out there”?

And he also repeats all the time: syntax is not the issue…ok, semantics is 
bigger issue but isn’t that possible for json-ld then in rdfs/owl/shacl/json 
schema/json-ld/graphql schema… etc. (so I do not get the point)

I imagine something like this:

In the LD world, OWL has an underlying theory (sets and logic) and SHACL has an 
underlying theory (Graph Theory). JSON-LD has Javascript under it, on its own 
what it specifies are Javascript data structures with some RDF-based patterns 
so you can simulate say RDFS with it. It’s not better or worse than Python, 
Java, etc. on that front. It’s big advantage is that it’s great for 
browser-based apps. Howe

RE: [topbraid-users] json-ld question

2021-03-19 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

I fully agree that adding generic upper ontologies increase semantic meaning of 
the stuff below specialized.
(we do that ourselves in our cen European Semantic Modelling & Linking standard 
by providing a “top level model” covering PhysicalObject, Event, State, 
Activity etcetc.)

(But..) here I just wanted to focus on the language level

So say: XSD versus OWL or, graphql schema versus shacl

The second seems quite semantically compatible (given your 1-to-1 link in your 
tooling).

Lets focus on the first.

What does an OWL ontology provide essentially more than an XSD schema.

Yes owl defines semantics and xsd defines ‘just’ structure following defs below 
but…what does it mean exactly?

When I define a elementtype in xsd or class in owl..both indicate a declaration 
of a thing of interest.
Attributes and subelements in xsd give further meaning like datatype props and 
object props in owl.

Is it the fact that owl defines the restrictions and xsd cannot that is 
distinguishing the “structure” from the “semantics”?
(guess not because datatypes also limit values and they are on both sides…)

Or is it the fact that xsd misses the underlying logic entailment?

Or …. ???

THAT are the kind of arguments I am looking for…….

(of course Wikipedia is a high level source here but not really giving precise 
answers…)





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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D71CC0.7BC14040]<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.




Van: topbraid-users@googlegroups.com  Namens 
David Price
Verzonden: vrijdag 19 maart 2021 12:26
Aan: topbraid-users@googlegroups.com
Onderwerp: Re: [topbraid-users] json-ld question




On 19 Mar 2021, at 10:06, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Final remark:

If you have some good refs on the difference between structure & semantics, 
very welcome!

Even Wikipedia is your friend and then just read the specs themselves  - see 
below.



Personally I do not see this as two poles really…both deal with defining 
possibilities and impossibilities in your data. In that sense an XSD also 
covers semantics.
And a json-ld spec on schema level also covers semantics. Clearly 
math/logic/graph-based SW-semantics in RDF/RDFS/OWL/SHACL-covers much MORE 
semantics.
In that sense I think the discussions on this aspect are a bit unnecessary 
polarized…..it feels more like different degrees of semantics….

But maybe there are some other essential differences that I do not see yet…..


XML & XSDs are syntax/structure, that’s different from semantics.  Using your 
phrasing - one says what’s possible wrt storing your data, the other says what 
data is possible and how that data is to be interpreted.

Syntax: the set of rules that defines the combinations of symbols that are 
considered to be correctly structured statements or expressions in that language

Semantics:

  *   (general) is the study of meaning, reference, or truth;
  *   (logic) the study of the interpretations of formal and natural languages;
  *   (programming) is the field concerned with the rigorous mathematical study 
of the meaning of programming languages. It does so by evaluating the meaning 
of syntactically valid strings defined by a specific programming language, 
showing the computation involved.

XML/XSD:

The first sentence on the W3C XML Schema page says “An XML Schema is a language 
for expressing constraints about XML documents.”

XML says: Extensible Markup Language describes a class of data objects called 
XML documents and partially describes the behavior of computer programs which 
process them. XML is an application profile or restricted form of SGML, the 
Standard Generalized Markup Language [ISO 8879]. By construction, XML documents 
are conforming SGML documents.

XML documents are made up of storage units called entities, which contain 
either parsed or unparsed data. Parsed data is made up of characters, some of 
which form character data, and some of which form markup. Markup encodes a 
description of the document's storage layout and logical structure. XML 
provides a mechanism to impose constraints on the storage layout and logical 
structure.

Clearly, XSDs specify exactly zero semantics as it’s about “constraints” on 
“storage units” and “markup of storage layout”.  I’m sure there are blogs 
claiming XSDs have “meaning” aka semantics, but those blogs

RE: [topbraid-users] best practise name space in multiple languages?

2021-04-09 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users


Dear Holger

One more question on this.


  *   Indeed serialization is other dimension related to server negotiation etc.
  *   Skos variant is special: totally different beasts (instance versus class 
etc.) so indeed separate namespace/prefix (we dicided for rdfs:isDefinedBy to 
make links between them; in practice you see many other relations used).
  *   Lets focus on name spaces for rdfs/owl/shacl variants, let’s assume 
variant: owl & shacl both importing rdfs (not: shacl importing owl)
  *   Even more focus: rdfs & shacl only (forget about owl for now)
Below you propose a different prefix/ns for the shacl-variant (nen2660-shacl).

Now the question. Would it be somehow possible to use the same name space for 
both rdfs and shacl?
(think you state that too below…)

So having two files/graphs having the same name space, one stating the rdfs 
stuff, the other the shacl.

Then I guess you need a mechanism to merge the two files/graphs other then 
owl:import (imports does not make sense since it is logical and the ontology 
would import itself)?

Thx again (for your patience…),
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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D72D2B.828002B0]<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.




Van: topbraid-users@googlegroups.com  Namens 
Holger Knublauch
Verzonden: dinsdag 6 april 2021 13:22
Aan: topbraid-users@googlegroups.com
Onderwerp: Re: [topbraid-users] best practise name space in multiple languages?

Hi Michel,

First we should make sure that the users of your models understand the 
distinction between namespaces and graph URIs. You can of course use the same 
namespace (e.g., https://w3id.org/def/nen2660#<https://w3id.org/def/nen2660>) 
in multiple graphs. What you are probably referring to is the Graph URI under 
which the models will be downloaded from on the Web.

For the RDFS part, assuming this merely declares classes, properties and their 
relationships, I suggest they should be found at the URI that is like the 
namespace (except maybe without the #). Then, the OWL version could be at a URI 
ending with nen2660-owl and the SHACL version could be at nen2660-shacl, and 
both would have owl:imports statements to the RDFS Graph URI. OWL is typically 
pretty strict about what is allowed in the models, e.g. to preserve the OWL DL 
logic. On the other hand, SHACL is quite relaxed if a graph also contains OWL 
axioms - they will simply be ignored. So in theory the SHACL graph may 
owl:import the OWL version too.

Using owl:imports will make sure that declarations are not repeated across 
files, and therefore don’t risk running out of sync, e.g. if someone changes 
the RDFS classes only in one file.

I don’t know enough about how the SKOS version is different to comment on that. 
I would find it rather confusing if a resource is a class in one graph but a 
SKOS concept in another.

The topic of RDF/XML vs Turtle etc is another dimension, typically solved using 
HTTP content negotiation. All serialisations would be accessible from the same 
server URLs yet the server would return different results depending on what 
accept header the client requests.

Holger



On 6 Apr 2021, at 6:20 pm, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

In case I have the same specification on different modelling levels:

  *   Skos
  *   Rdfs
  *   Rdfs+owl
  *   Rdfs+shacl

Is there some best practice  for the name space?

(compare same name space for different serializations but now for different 
languages used…).

I now have ie:

# baseURI: https://w3id.org/def/nen2660-rdfs

But I got the comment that just:
# baseURI: https://w3id.org/def/nen2660

was preferred.

But then I have 4 variants (actually 12: all in rdf/xml, turtle and json-ld) 
specifying for the same name space.

Thx for advice,
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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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 f

RE: [topbraid-users] best practise name space in multiple languages?

2021-04-09 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Ok,….my misunderstanding becomes clearer…

Typically i used up till now owl:imports referencing other name spaces

Do I understand now that the import can also be a (sub)graph/file saying 
something about a name space?

If both rdfs and shacl variant have name space say https://w3id.org/nen2660/def 
, what would the owl:imports statement look like in the shacl variant file?


Guess I used up till now some assumptions on name space uri versus graph uri 
that I now better have to differentiate….




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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D72D2E.6CEDFA80]<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.




Van: topbraid-users@googlegroups.com  Namens 
Holger Knublauch
Verzonden: vrijdag 9 april 2021 10:42
Aan: topbraid-users@googlegroups.com
Onderwerp: Re: [topbraid-users] best practise name space in multiple languages?



On 9/04/2021 6:31 pm, 'Bohms, H.M. (Michel)' via TopBraid Suite Users wrote:

Dear Holger

One more question on this.


  1.  Indeed serialization is other dimension related to server negotiation etc.
  2.  Skos variant is special: totally different beasts (instance versus class 
etc.) so indeed separate namespace/prefix (we dicided for rdfs:isDefinedBy to 
make links between them; in practice you see many other relations used).
  3.  Lets focus on name spaces for rdfs/owl/shacl variants, let’s assume 
variant: owl & shacl both importing rdfs (not: shacl importing owl)
  4.  Even more focus: rdfs & shacl only (forget about owl for now)
Below you propose a different prefix/ns for the shacl-variant (nen2660-shacl).

Now the question. Would it be somehow possible to use the same name space for 
both rdfs and shacl?
(think you state that too below…)

So having two files/graphs having the same name space, one stating the rdfs 
stuff, the other the shacl.
Yes we do this in our EDG namespace, which is split across dozens of files, but 
they all declare resources from the edg: namespace. Namespaces and graph URIs 
are relatively separate topics, so any graph can declare resources from any 
namespace.


Then I guess you need a mechanism to merge the two files/graphs other then 
owl:import (imports does not make sense since it is logical and the ontology 
would import itself)?

I don't understand this argument - we use owl:imports between the edg: files 
without problems.

Holger



Thx again (for your patience…),
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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D72D2E.6CEDFA80]<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.




Van: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com> 
<mailto:topbraid-users@googlegroups.com> 
Namens Holger Knublauch
Verzonden: dinsdag 6 april 2021 13:22
Aan: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com>
Onderwerp: Re: [topbraid-users] best practise name space in multiple languages?

Hi Michel,

First we should make sure that the users of your models understand the 
distinction between namespaces and graph URIs. You can of course use the same 
namespace (e.g., https://w3id.org/def/nen2660#<https://w3id.org/def/nen2660>) 
in multiple graphs. What you are probably referring to is the Graph URI under 
which the models will be downloaded from on the Web.

For the RDFS part, assuming this merely declares classes, properties and their 
relationships, I suggest they should be found at the URI that is like the 
namespace (except maybe without the #). Then, the OWL version could be at a URI 
ending with nen2660-owl and the SHACL version could be at nen2660-shacl, and 
both would have owl:imports statements to the RDFS Graph URI. OWL is typically 
pretty strict about what is allowed in the models, e.g. to preserve the OWL DL 
logic. On the other hand, SHACL is quite relaxed if a graph also contains OWL 
axioms - they will sim

RE: [topbraid-users] best practise name space in multiple languages?

2021-04-12 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Correction:

I forgot, one more subissue wrt the naming of the different graph uri’s 
involved:

https://w3id.org/nen2660/rdfs

versus

https://w3id.org/nen2660-rdfs
the latter also corresponding to the filename: nen2660-rdfs.ttl

any principle difference/pros/cons?

thx




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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D72F94.0D4DB260]<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.




Van: 'Bohms, H.M. (Michel)' via TopBraid Suite Users 

Verzonden: maandag 12 april 2021 11:36
Aan: topbraid-users@googlegroups.com
Onderwerp: RE: [topbraid-users] best practise name space in multiple languages?

I forgot, one more subissue wrt the naming of the different graph uri’s 
involved:

https://w3id.org/nen2660/rdfs

versus

https://w3id.org/nen2660-rdfs
the latter also corresponding to the filename: nen2660-schema.ttl

any principle difference/pros/cons?

thx



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D72F94.0D4DB260]<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.




Van: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com> 
mailto:topbraid-users@googlegroups.com>> 
Namens David Price
Verzonden: vrijdag 9 april 2021 12:33
Aan: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com>
Onderwerp: Re: [topbraid-users] best practise name space in multiple languages?

Hi Michel,

I

On 9 Apr 2021, at 09:52, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Ok,….my misunderstanding becomes clearer…

Typically i used up till now owl:imports referencing other name spaces

Do I understand now that the import can also be a (sub)graph/file saying 
something about a name space?

If both rdfs and shacl variant have name space say https://w3id.org/nen2660/def 
, what would the owl:imports statement look like in the shacl variant file?

Guess I used up till now some assumptions on name space uri versus graph uri 
that I now better have to differentiate….


I’ll simply a bit, but a good way to think about it is that the concept of the 
named graph (with name being a Graph URI) is actually what owl:imports 
references.  A named graph may define classes/properties that use any number of 
namespaces, made simpler by using prefixes for the namespaces.

A named graph with Graph URI like https://w3id.org/nen2660/shapes is not the 
same thing as a concept of Namespace URI like 
https://w3id.org/nen2660#<https://w3id.org/nen2660>.   From the Turtle Primer:

prefix rdfs:, namespace URI: 
http://www.w3.org/2000/01/rdf-schema#<http://www.w3.org/2000/01/rdf-schema>

Note that it calls the non-local name of a full URI a "namespace URI” so I 
should probably be doing that too.

Technically, there is zero relationship between the graph URI and namespace 
URI. The named graph can be http://anything.at.all and define classes and 
properties using http://michel.com#<http://michel.com> as the namespace URI. 
That much difference may confuse people, so it’s not usually recommended but 
it’s fine technically.

All the classes/properties of interest can then use the same namespace URI, 
even if they are managed in different named graphs

So,  
https://w3id.org/nen2660<https://w3id.org/nen2660/Thing1>#Class1<https://w3id.org/nen2660/Thing1>
 an rdfs:Class can be in  https://w3id.org/nen2660/schema graph and  
https://w3id.org/nen2660<https://w3id.org/nen2660/Thing2>#NodeShape2<https://w3id.org/nen2660/Thing2>
 a SHACL NodeShape can be in  https://w3id.org/nen2660/shapes graph.

Both graphs as TTL would state

@prefix nen2660: <https://w3id.org/nen2660#<https://w3id.org/nen2660>> .

so you’d see nen2660:Class1 and nen2660:NodeShape2 and so things are is 
consistent wrt writing SPARQL queries, for example, over the schema/shapes and

RE: [topbraid-users] best practise name space in multiple languages?

2021-04-12 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Thx David /Irene for the explanations…

I never had the need to clearly differentiate the 2 types of uri’s.

An important ‘exception’ seems indeed when you want to somehow combine 
complementary rdfs/owl/shacl stuff for the same logical thing in different 
graphs (sep. of concerns).

I am writing a small piece of text on this for our nen2660 spec (that will be 
reused for cen tc442 SML).
I hope you can have a quick look soon to see if I understood you right.

Thx a lot! 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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D72F88.E8CB3C10]<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.




Van: topbraid-users@googlegroups.com  Namens 
Irene Polikoff
Verzonden: vrijdag 9 april 2021 14:13
Aan: topbraid-users@googlegroups.com
Onderwerp: Re: [topbraid-users] best practise name space in multiple languages?

Yes, exactly.

To simplify it even more:


  *   There are graphs and they have identity - graph URI. owl:imports 
statements refer to the graph URIs.
  *   A graph contains a set of triple statements about some resources. These 
resources also have identity - URIs of resources.
  *   URIs are formed by combining some namespace with a local name.
  *   There is no requirement for the namespace used to form the URI of a graph 
to be the same as the namespace(s) used to form URIs of resources that 
participate in the triple statements in a graph.

 *   In many cases, it is a good practice for resources to use the same 
namespace as the graph - at least resources that are subjects in the triples 
contained in a graph.
 *   However, there are also significant exceptions and you can see 
examples of this all over the place.


On Apr 9, 2021, at 6:32 AM, David Price 
mailto:dpr...@topquadrant.com>> wrote:

Hi Michel,

I


On 9 Apr 2021, at 09:52, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Ok,….my misunderstanding becomes clearer…

Typically i used up till now owl:imports referencing other name spaces

Do I understand now that the import can also be a (sub)graph/file saying 
something about a name space?

If both rdfs and shacl variant have name space say https://w3id.org/nen2660/def 
, what would the owl:imports statement look like in the shacl variant file?

Guess I used up till now some assumptions on name space uri versus graph uri 
that I now better have to differentiate….


I’ll simply a bit, but a good way to think about it is that the concept of the 
named graph (with name being a Graph URI) is actually what owl:imports 
references.  A named graph may define classes/properties that use any number of 
namespaces, made simpler by using prefixes for the namespaces.

A named graph with Graph URI like https://w3id.org/nen2660/shapes is not the 
same thing as a concept of Namespace URI like 
https://w3id.org/nen2660#<https://w3id.org/nen2660>.   From the Turtle Primer:

prefix rdfs:, namespace URI: 
http://www.w3.org/2000/01/rdf-schema#<http://www.w3.org/2000/01/rdf-schema>

Note that it calls the non-local name of a full URI a "namespace URI” so I 
should probably be doing that too.

Technically, there is zero relationship between the graph URI and namespace 
URI. The named graph can be http://anything.at.all<http://anything.at.all/> and 
define classes and properties using http://michel.com#<http://michel.com/> as 
the namespace URI. That much difference may confuse people, so it’s not usually 
recommended but it’s fine technically.

All the classes/properties of interest can then use the same namespace URI, 
even if they are managed in different named graphs

So,  
https://w3id.org/nen2660<https://w3id.org/nen2660/Thing1>#Class1<https://w3id.org/nen2660/Thing1>
 an rdfs:Class can be in  https://w3id.org/nen2660/schema graph and  
https://w3id.org/nen2660<https://w3id.org/nen2660/Thing2>#NodeShape2<https://w3id.org/nen2660/Thing2>
 a SHACL NodeShape can be in  https://w3id.org/nen2660/shapes graph.

Both graphs as TTL would state

@prefix nen2660: <https://w3id.org/nen2660#<https://w3id.org/nen2660>> .

so you’d see nen2660:Class1 and nen2660:NodeShape2 and so things are is 
consistent wrt writing SPARQL queries, for example, over the schema/shapes and 
over the data.

Then https://w3id.org/nen2660/shapes owl:imports  
https://w3id.org/nen2660/schema  so NodeShape2 can refer to Class1

RE: [topbraid-users] best practise name space in multiple languages?

2021-04-12 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

I forgot, one more subissue wrt the naming of the different graph uri’s 
involved:

https://w3id.org/nen2660/rdfs

versus

https://w3id.org/nen2660-rdfs
the latter also corresponding to the filename: nen2660-schema.ttl

any principle difference/pros/cons?

thx



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D72F90.0F899570]<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.




Van: topbraid-users@googlegroups.com  Namens 
David Price
Verzonden: vrijdag 9 april 2021 12:33
Aan: topbraid-users@googlegroups.com
Onderwerp: Re: [topbraid-users] best practise name space in multiple languages?

Hi Michel,

I


On 9 Apr 2021, at 09:52, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Ok,….my misunderstanding becomes clearer…

Typically i used up till now owl:imports referencing other name spaces

Do I understand now that the import can also be a (sub)graph/file saying 
something about a name space?

If both rdfs and shacl variant have name space say https://w3id.org/nen2660/def 
, what would the owl:imports statement look like in the shacl variant file?

Guess I used up till now some assumptions on name space uri versus graph uri 
that I now better have to differentiate….


I’ll simply a bit, but a good way to think about it is that the concept of the 
named graph (with name being a Graph URI) is actually what owl:imports 
references.  A named graph may define classes/properties that use any number of 
namespaces, made simpler by using prefixes for the namespaces.

A named graph with Graph URI like https://w3id.org/nen2660/shapes is not the 
same thing as a concept of Namespace URI like 
https://w3id.org/nen2660#<https://w3id.org/nen2660>.   From the Turtle Primer:

prefix rdfs:, namespace URI: 
http://www.w3.org/2000/01/rdf-schema#<http://www.w3.org/2000/01/rdf-schema>

Note that it calls the non-local name of a full URI a "namespace URI” so I 
should probably be doing that too.

Technically, there is zero relationship between the graph URI and namespace 
URI. The named graph can be http://anything.at.all and define classes and 
properties using http://michel.com#<http://michel.com> as the namespace URI. 
That much difference may confuse people, so it’s not usually recommended but 
it’s fine technically.

All the classes/properties of interest can then use the same namespace URI, 
even if they are managed in different named graphs

So,  
https://w3id.org/nen2660<https://w3id.org/nen2660/Thing1>#Class1<https://w3id.org/nen2660/Thing1>
 an rdfs:Class can be in  https://w3id.org/nen2660/schema graph and  
https://w3id.org/nen2660<https://w3id.org/nen2660/Thing2>#NodeShape2<https://w3id.org/nen2660/Thing2>
 a SHACL NodeShape can be in  https://w3id.org/nen2660/shapes graph.

Both graphs as TTL would state

@prefix nen2660: <https://w3id.org/nen2660#<https://w3id.org/nen2660>> .

so you’d see nen2660:Class1 and nen2660:NodeShape2 and so things are is 
consistent wrt writing SPARQL queries, for example, over the schema/shapes and 
over the data.

Then https://w3id.org/nen2660/shapes owl:imports  
https://w3id.org/nen2660/schema  so NodeShape2 can refer to Class1.

Tooling often supports a “Default Namespace” for a graph exactly to simplify 
the separation of the Graph URI from the namespace URI.

This separation also supports versions of ontologies. So, for example named 
graphs http://standard.iso.org/mystandard/edition1 and 
http://standard.iso.org/mystandard/edition2
can both contain

http://standard.iso.org/mystandard/<http://standard.iso.org/mystandard/MyClass>MyClass<http://standard.iso.org/mystandard/MyClass>
 a rdfs:Class .

with no problem.

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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

RE: [topbraid-users] best practise name space in multiple languages?

2021-04-14 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Ok, thx, changed to:



De gehanteerde prefixen & ‘name space URI’s’:

¾nen2660-vocab   
https://w3id.org/nen2660/vocab#<https://w3id.org/nen2660/vocab>

¾nen2660 
https://w3id.org/def/nen2660/def#<https://w3id.org/def/nen2660/def>
Met ‘graaf URI’s’ (default voor vocab, 3 subgrafen voor def):

¾https://w3id.org/nen2660/vocab# (bestand: nen2660-skos.ttl)

¾https://w3id.org/nen2660-rdfs/def# (bestand: nen2660-rdfs.ttl)

¾https://w3id.org/nen2660-owl/def# (bestand: nen2660-owl.ttl)

¾https://w3id.org/nen2660-shacl/def# (bestand: 
nen2660-shacl.ttl)




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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D73124.3D65BBA0]<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.




Van: topbraid-users@googlegroups.com  Namens 
David Price
Verzonden: woensdag 14 april 2021 11:41
Aan: topbraid-users@googlegroups.com
CC: Opgenoort, Rik ; Kronemeijer, Redmer 
; Bart Bink 
Onderwerp: Re: [topbraid-users] best practise name space in multiple languages?




On 14 Apr 2021, at 10:28, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

I thought the / or # only came in with the porefix independent of the uri 
itself…..

No, the # or / is part of the Namespace URI.

>From the Turtle Primer:

The full triples notation requires that URI references be written out 
completely, in angle brackets, which, as the example above illustrates, can 
result in very long lines on a page. For convenience, the Primer uses a 
shorthand way of writing triples (the same shorthand is also used in other RDF 
specifications). This shorthand substitutes a qualified name (or QName) without 
angle brackets as an abbreviation for a full URI reference . A QName contains a 
prefix that has been assigned to a namespace URI, followed by a colon, and then 
a local name. The full URIref is formed from the QName by appending the local 
name to the namespace URI assigned to the prefix. So, for example, if the QName 
prefix foo is assigned to the namespace URI http://example.org/somewhere/, then 
the QName foo:bar is shorthand for the URIref http://example.org/somewhere/bar. 
Primer examples will also use several "well-known" QName prefixes (without 
explicitly specifying them each time), defined as follows:

prefix rdf:, namespace URI: 
http://www.w3.org/1999/02/22-rdf-syntax-ns#<http://www.w3.org/1999/02/22-rdf-syntax-ns>
prefix rdfs:, namespace URI: 
http://www.w3.org/2000/01/rdf-schema#<http://www.w3.org/2000/01/rdf-schema>
prefix dc:, namespace URI: http://purl.org/dc/elements/1.1/
prefix owl:, namespace URI: 
http://www.w3.org/2002/07/owl#<http://www.w3.org/2002/07/owl>
prefix ex:, namespace URI: http://www.example.org/ (or http://www.example.com/)
prefix xsd:, namespace URI: 
http://www.w3.org/2001/XMLSchema#<http://www.w3.org/2001/XMLSchema>

Cheers,
David


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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/71D1477B-766D-4035-8730-90B7E5FF27CB%40topquadrant.com<https://groups.google.com/d/msgid/topbraid-users/71D1477B-766D-4035-8730-90B7E5FF27CB%40topquadrant.com?utm_medium=email_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 topbraid-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/be42ca7c28bb4be3aeb984164725ebcd%40tno.nl.

RE: Why SKOS in ontologies? Was Re: [topbraid-users] best practise name space in multiple languages?

2021-04-14 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

In NL we have eg:

https://bp4mc2.org/profiles/#skos-toepassingsprofiel-voor-begrippenkaders

a profile for LD application for the government.
(you have to follow or explain why not…)

It has an integral role for skos.

[cid:image002.jpg@01D73123.705935B0]

Small fragment (google) translation:

2. SKOS Application profile for conceptual frameworks

Concepts make it clear which "topics of conversation" there are. In a system 
catalog terms are formally defined, each definition being built up according to 
strict rules. The essence is that every concept in a particular domain is 
explained in terms of other concepts. Those concepts are also limited until 
every concept that needs explanation has been defined. Ultimately, the concepts 
remain, the meaning of which is assumed to be automatic. In a logical model 
these are called axioms. This creates an axiomatic conceptual framework for 
each domain. This conceptual framework can be regarded as a more-less specified 
description of the institutional reality of the domain.

SKOS is used to describe concepts. SKOS is on the apply or explain list in the 
Netherlands.

Each concept is represented by a skos: concept.
Each domain has its own conceptual framework. The conceptual framework for a 
particular domain is represented by a skos: ConceptScheme.
Concepts can be organized in collections. A collection is represented by a 
skos: collection.
Concepts in different domains can be linked through appropriate mechanisms. 
This connection of concepts between domains creates a cohesion of coherent 
conceptual frameworks. This system of coherent conceptual frameworks can be 
seen as the knowledge base for a system catalog.




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 michel.bo...@tno.nl

Location



[cid:image005.gif@01D73123.2F918000]

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: topbraid-users@googlegroups.com  Namens 
David Price
Verzonden: woensdag 14 april 2021 11:25
Aan: topbraid-users@googlegroups.com
Onderwerp: Why SKOS in ontologies? Was Re: [topbraid-users] best practise name 
space in multiple languages?

Hi TB users,

The discussion with Michel caused a question to pop into my mind and I hope to 
get some customer feedback here.

I see customers/bodies use SKOS to define what turn out to be simple lists of 
standard class instances that are then used in an ontology. My question is - 
Why?

OWL enumerated classes provide the same standard-instance capability, but 
without the added “clutter” in your ontology when you import SKOS. The number 
of completely empty, never-to-be-used cases of Collection, Concept Scheme, etc. 
appearing as classes in ontologies has become surprising to me.

Can anyone who’s been part of making this kind of decision in your ontologies 
please explain Why?  Among other possible reasons, a few I could think of might 
be:

  *   Is it that the UI for creating them is simpler?
  *   Is it that these standard instances are seen as being somehow improved by 
having a not-well-defined tree structure available via broader/narrower?
  *   Is it that you’re using a standard that’s done this and you’d be happy 
with any solution that supports defining standard instances? i.e. perhaps a 
SKOS-to-enumerated-class importer for these situations would be a useful tool?
  *   Is that you really have use cases like described here: 
https://www.w3.org/2006/07/SWD/SKOS/skos-and-owl/master.html. ?
  *   Is it really just that you prefer/need the SKOS annotation properties, 
even for classes, instances, etc? (I like them and have local a 
skos-annotations-only.ttl I reuse)
We are always looking for real-world user scenarios wrt improving EDG, and so 
you can also think of this as a requirements gathering/feature request exercise.

It may be there are some EDG feature or UI changes we could make. It may be 
that a How-To video on our Web site explaining this approach and how to best 
execute it in EDG would be useful. I don’t know but thought it worth asking the 
requirements question to see how prevalent this is and why it happens.

Cheers,
David



“
x.y  Combination of language bindings

In practice, there will often be a need for a combination of language bindings. 
In the most extensive case, this concerns (always 1 or more):

  *   SKOS concept scheme;
  *   RDFS (basic) ontology (imports the SKOS concept scheme);
  *   OWL ontology (imports the RDFS ontology);
  *   SHACL graph (imports the RDFS ontology).
Since the semantic

RE: [topbraid-users] best practise name space in multiple languages?

2021-04-14 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Thx and indeed we might want versioned graph uri’s!

Now:

De gehanteerde prefixen & ‘name space URI’s’:

¾nen2660-vocab   
https://w3id.org/nen2660/vocab#<https://w3id.org/nen2660/vocab>

¾nen2660  
https://w3id.org/def/nen2660/def#<https://w3id.org/def/nen2660/def>
Met ‘graaf URI’s’ (default voor vocab, 3 subgrafen voor def):

¾https://w3id.org/nen2660/vocab (bestand: nen2660-skos.ttl)

¾https://w3id.org/nen2660-rdfs/def (bestand: nen2660-rdfs.ttl)

¾https://w3id.org/nen2660-owl/def (bestand: nen2660-owl.ttl)

¾https://w3id.org/nen2660-shacl/def (bestand: nen2660-shacl.ttl)

happy with that “solution” for now, let’s see what the use case question brings 
us as “problem” 

One more:
>From the above the process of obtaining a default name space uri from the 
>graph uri would be:
ns-uri := g-uri + #

and I know see that is exactly what happens in tbc when you click the chain….:

[cid:image001.png@01D7312B.5913E5F0]

thx

gr 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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>

[cid:image003.gif@01D7312A.E9D8B580]<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.

Van: topbraid-users@googlegroups.com  Namens 
David Price
Verzonden: woensdag 14 april 2021 12:16
Aan: topbraid-users@googlegroups.com
CC: Opgenoort, Rik ; Kronemeijer, Redmer 
; Bart Bink 
Onderwerp: Re: [topbraid-users] best practise name space in multiple languages?

On 14 Apr 2021, at 10:49, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Ok, thx, changed to:

De gehanteerde prefixen & ‘name space URI’s’:
•nen2660-vocab   
https://w3id.org/nen2660/vocab#<https://w3id.org/nen2660/vocab>

•nen2660 
https://w3id.org/def/nen2660/def#<https://w3id.org/def/nen2660/def>
Met ‘graaf URI’s’ (default voor vocab, 3 subgrafen voor def):
•https://w3id.org/nen2660/vocab# (bestand: nen2660-skos.ttl)
•
https://w3id.org/nen2660-rdfs/def#<https://w3id.org/nen2660-rdfs/def> (bestand: 
nen2660-rdfs.ttl)
•
https://w3id.org/nen2660-owl/def#<https://w3id.org/nen2660-owl/def> (bestand: 
nen2660-owl.ttl)

•
https://w3id.org/nen2660-shacl/def#<https://w3id.org/nen2660-shacl/def> 
(bestand: nen2660-shacl.ttl)
IMO the Graph URI and the Namespace URI are best kept different so nobody gets 
confused. It is also the case that you may define constructs in any namespace 
in a graph and so there is really zero relation required between them.

So, I’d suggest this for your Graph URIs (no #):

Met ‘graaf URI’s’ (default voor vocab, 3 subgrafen voor def):
•https://w3id.org/nen2660/vocab (bestand: nen2660-skos.ttl)
•https://w3id.org/nen2660-rdfs/def (bestand: nen2660-rdfs.ttl)
•https://w3id.org/nen2660-owl/def (bestand: nen2660-owl.ttl)

•https://w3id.org/nen2660-shacl/def (bestand: nen2660-shacl.ttl)
As I explained earlier there are cases supporting versions of ontologies with 
the same classes defined - you may eventually need  
https://w3id.org/nen2660/v1/vocab and https://w3id.org/nen2660/v2/vocab to both 
contain https://w3id.org/nen2660/vocab/PhysicalObject concept. In the 
engineering world where apps are audited (e.g. Aircraft design and 
manufacture), there are situations where there is a hard requirement for very 
strictly managed change to all apps, so versions are needed in the ontologies 
Graph URIs. The ontology provider can offer both a versioned release with v1, 
v2, etc. in the Graph URI and an un-versioned release with no v1, etc. in the 
Graph URI that is always the latest-and-greatest. That way implementors can 
choose “always the latest” or “a specific version”.

The main point is to separate the Graph URI from Namespace URI in your 
thinking, and maintain that separation in the artefacts themselves.

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>

<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

[topbraid-users] prefix suggestions

2021-02-12 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

When instantiating a class in wegennetwerken, tbc always suggeste the prefix 
quantitykind.
Cant find out why (why not its own prefix being wn)

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 michel.bo...@tno.nl

Location



[cid:image001.gif@01D70131.D573A470]

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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/72b9f76860c1498a860686d84b87e0c0%40tno.nl.


wegennetwerk.ttl
Description: wegennetwerk.ttl


nen2660.ttl
Description: nen2660.ttl

RE: [topbraid-users] prefix suggestions

2021-02-12 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Aarrgghh
Sometimes one can be blind for these things
How stupid…

Thx!!



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D70134.CF4F8020]<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.




Van: topbraid-users@googlegroups.com  Namens 
David Price
Verzonden: vrijdag 12 februari 2021 11:45
Aan: topbraid-users@googlegroups.com
Onderwerp: Re: [topbraid-users] prefix suggestions

Hi Michel,

The wn prefix is not defined correctly (extra "/" after "def"):

@prefix wn: <https://w3id.org/def//wegennetwerk#> .

Cheers,
David



On 12 Feb 2021, at 10:25, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

When instantiating a class in wegennetwerken, tbc always suggeste the prefix 
quantitykind.
Cant find out why (why not its own prefix being wn)

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/72b9f76860c1498a860686d84b87e0c0%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/72b9f76860c1498a860686d84b87e0c0%40tno.nl?utm_medium=email_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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/9318F050-12CE-46BF-853A-B9119A89DC36%40topquadrant.com<https://groups.google.com/d/msgid/topbraid-users/9318F050-12CE-46BF-853A-B9119A89DC36%40topquadrant.com?utm_medium=email_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 topbraid-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/32ac5295bad64ab2afa05f911d1fb102%40tno.nl.

Re: [topbraid-users] RE: property chains

2021-02-20 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Thx

Wasnt there a way to not do the remove of redundant inferences?

Op 20 feb. 2021 07:43 schreef Holger Knublauch :

FWIW on my machine this took 96 seconds to infer 272152 triples. Then another
minute or two to remove redundant inferences.

Our OWL-RL implementation is what it is. The design it a pretty simplistic
implementation of the spec. To take more control of performance, use SPARQL
CONSTRUCT queries?

Holger

On 2021-02-19 11:24 pm, 'Bohms, H.M. (Michel)' via TopBraid Suite Users wrote:
It seems it just took a long time….
Result is there when patient enough

Can this be speeded up ?

It’s removing redundant stuff for a long time I see now…

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>

[cid:part3.270389F3.FAC2FD10@topquadrant.com]<http://www.tno.nl/>

Van: 'Bohms, H.M. (Michel)' via TopBraid Suite Users
<mailto:topbraid-users@googlegroups.com>
Verzonden: vrijdag 19 februari 2021 09:46
Aan: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com>
Onderwerp: [topbraid-users] property chains

Wondering why my property chain is not inferred?
(I ticked the owl-rl profile)

I try to bring the valued properties from type-level to instance level.

Thx for any tip, 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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>

[cid:part3.270389F3.FAC2FD10@topquadrant.com]<http://www.tno.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-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/a30e48c6db1344caa7cc286e202bece4%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/a30e48c6db1344caa7cc286e202bece4%40tno.nl?utm_medium=email_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
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/78b41397ffe64c5aa7a848df72b2725c%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/78b41397ffe64c5aa7a848df72b2725c%40tno.nl?utm_medium=email_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 topbraid-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/2ab8478e-cf2c-4a5d-9dfb-7f90f2309baf%40email.android.com.

[topbraid-users] RE: property chains

2021-02-19 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

It seems it just took a long time….
Result is there when patient enough

Can this be speeded up ?

It’s removing redundant stuff for a long time I see now…

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>

[cid:image001.gif@01D706CA.E350E910]<http://www.tno.nl/>

Van: 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Verzonden: vrijdag 19 februari 2021 09:46
Aan: topbraid-users@googlegroups.com
Onderwerp: [topbraid-users] property chains

Wondering why my property chain is not inferred?
(I ticked the owl-rl profile)

I try to bring the valued properties from type-level to instance level.

Thx for any tip, 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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>

[cid:image001.gif@01D706CA.E350E910]<http://www.tno.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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/78b41397ffe64c5aa7a848df72b2725c%40tno.nl.

[topbraid-users] property chains

2021-02-19 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Wondering why my property chain is not inferred?
(I ticked the owl-rl profile)

I try to bring the valued properties from type-level to instance level.

Thx for any tip, 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 michel.bo...@tno.nl

Location



[cid:image001.gif@01D706A4.096A8CE0]

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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/a30e48c6db1344caa7cc286e202bece4%40tno.nl.


producttype-3_and_property_chain_axiom.ttl
Description: producttype-3_and_property_chain_axiom.ttl


producttype-3_and_property_chain_axiom.ttl.tbc
Description: producttype-3_and_property_chain_axiom.ttl.tbc


nen2660.ttl
Description: nen2660.ttl

[topbraid-users] right owl2shacl-mapping?

2021-08-31 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

(we were looking for an approach not needing rdfs-entailment)

sml:AllDisjointClasses_1
  a owl:AllDisjointClasses ;
  owl:members (
  sml:PhysicalObject
  sml:InformationObject
  sml:Activity
  sml:Event
  sml:State
) ;
.

In shacl (?):

sml:DisjointClassesShape_1 a sh:NodeShape ;
  sh:targetSubjectsOf rdf:type ;
  sh:property [
sh:path ( rdf:type [ sh:zeroOrMorePath rdfs:subClassOf ] ) ;
sh:qualifiedValueShape [
  sh:in (
sml:PhysicalObject
sml:InformationObject
sml:State
sml:Event
sml:Activity
  ) ;
] ;
sh:qualifiedMaxCount 1 ;
  ] ;
.

Any issues with this mapping?

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 michel.bo...@tno.nl

Location



[cid:image001.gif@01D79E74.69501590]

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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/9eedba7e10534409ac1eec4e3d3704b1%40tno.nl.

RE: [topbraid-users] right owl2shacl-mapping?

2021-08-31 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Hi David

Your solution (as generated) needs quite some code in case of more than two 
items and also in a distributed way.
We hoped to cover it with more generic template code…

Wrt shacl AF: if we can do it in shacl core (being a recommendation) that would 
be preferred. Furthermore I would not quickly see how to define a triple rule 
that does the same as the shacl core nodeshape proposal.

(I do see your visibility issue though…)

Gr 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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D79E80.866A87D0]<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.




Van: topbraid-users@googlegroups.com  Namens 
David Price
Verzonden: dinsdag 31 augustus 2021 15:46
Aan: topbraid-users@googlegroups.com
Onderwerp: Re: [topbraid-users] right owl2shacl-mapping?

I don’t like creating a separate instance to control disjointedness as it’s not 
immediately visible in the relevant class form. The NodeShape being proposed 
has the same issue.

I usually use a pattern like this:

unnamed:Thing_1
  rdf:type owl:Class ;
  rdfs:subClassOf owl:Thing ;
  owl:disjointWith unnamed:Thing_2 ;
  owl:disjointWith unnamed:Thing_3 ;

and then EDG owl2shacl does this: For each owl:disjointWith from class A to B, 
create one constraint at A with the pattern sh:not [ sh:class B ].

You could generate sh:not from the approach you mention too, of course. I did 
not test the mentioned approach but it does appear that it or something similar 
would work.

Also, if Advanced SHACL is supported in your tools a TripleRule could likely 
handle this need.

https://w3c.github.io/shacl/shacl-af/#TripleRule

Cheers,
David


On 31 Aug 2021, at 13:28, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

(we were looking for an approach not needing rdfs-entailment)

sml:AllDisjointClasses_1
  a owl:AllDisjointClasses ;
  owl:members (
  sml:PhysicalObject
  sml:InformationObject
  sml:Activity
  sml:Event
  sml:State
) ;
.

In shacl (?):

sml:DisjointClassesShape_1 a sh:NodeShape ;
  sh:targetSubjectsOf rdf:type ;
  sh:property [
sh:path ( rdf:type [ sh:zeroOrMorePath rdfs:subClassOf ] ) ;
sh:qualifiedValueShape [
  sh:in (
sml:PhysicalObject
sml:InformationObject
sml:State
sml:Event
sml:Activity
  ) ;
] ;
sh:qualifiedMaxCount 1 ;
  ] ;
.

Any issues with this mapping?

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/9eedba7e10534409ac1eec4e3d3704b1%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/9eedba7e10534409ac1eec4e3d3704b1%40tno.nl?utm_medium=email_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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/642FE359-E3CF-4FF8-881E-26AC0C1D201B%40topquadrant.com<https://groups.google.com/d/msgid/topbraid-users/642FE359-E3CF-4FF8-881E-26AC0C1D201B%40topquadrant.com?utm_medium=email_source=footer>.

-- 
You received this message because you are subscribed to the Google Groups 
"TopBraid Suite Users" gro

RE: [topbraid-users] right owl2shacl-mapping?

2021-09-01 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Hi Holger

The pattern I showed is a proposal by someone as a replacement for our current:

sml:AllDisjointClassesShape_1
  a sh:NodeShape ;
  sh:targetSubjectsOf rdf:type ;
  sh:property [
sh:path rdf:type ;
sh:qualifiedValueShape [
  sh:zeroOrMorePath rdfs:subClassOf ;
  sh:in (
sml:PhysicalObject
sml:InformationObject
sml:State
sml:Event
sml:Activity
  ) ;
] ;
sh:qualifiedMaxCount 1 ;
  ] ;
.

Would the current way be less cumbersome to check?

How applied? In our current CEN SML ontology we have one such dimension for the 
main archetypes (as above) and for some of them some orthogonal dimensions with 
less items (#2): planned/realized, space/object, functional/technical).

That is also the reason multiple typing is always relevant and cannot be closed 
(ie ‘maxcard rdf:type being 1’ is not possible).

dash:allDisjoint would be an interesting  but ‘limited standard’ option I 
guess…isn’t there room in the evolving (in future more standard) shacl-af for 
such a construct?

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D79F0E.7E987C40]<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.




Van: topbraid-users@googlegroups.com  Namens 
Holger Knublauch
Verzonden: woensdag 1 september 2021 01:58
Aan: topbraid-users@googlegroups.com
Onderwerp: Re: [topbraid-users] right owl2shacl-mapping?


This (interesting) design may work technically, but it can be very slow because 
it will traverse all rdf:type triples everywhere and use a rather complex 
algorithm with nested (qualified) shapes. A better solution would indeed start 
with exactly the instances of one of those classes. The solution that David 
mentioned certainly works OK if you have few disjoint classes each, but for 
long lists even the OWL 2 standard introduced a more compact syntax, using 
owl:AllDisjointClasses.

I guess the syntactically ideal replacement would be to declare a reusable 
constraint component using SHACL-SPARQL (which is part of the SHACL standard 
1.0). You could even leave the existing owl:DisjointClasses in place, but I 
don't like that they are using rdf:Lists which would need to be traversed 
repeatedly and that is very slow too. owl:members here should simply point at 
the classes IMHO.

But something like that should be fine:

sml:AllDisjointClasses_1
a sh:NodeShape ;
sh:targetClass sml:PhysicalObject, sml:InformationObject, sml:Activity, 
sml:Event, sml:State ;
dash:allDisjoint true .

where dash:allDisjoint would be a constraint component that would walk through 
the targetClasses of $currentShape in $shapesGraph.

How many such cases (of large disjointness clusters) do you actually have? Is 
this even a sensible concept... I mean how would this exclude anyone else from 
adding more classes that you don't know about yet. If you want to close off 
your instances, just give them a sh:maxCount 1 on rdf:type.

Holger


On 2021-08-31 10:28 pm, 'Bohms, H.M. (Michel)' via TopBraid Suite Users wrote:
(we were looking for an approach not needing rdfs-entailment)

sml:AllDisjointClasses_1
  a owl:AllDisjointClasses ;
  owl:members (
  sml:PhysicalObject
  sml:InformationObject
  sml:Activity
  sml:Event
  sml:State
) ;
.

In shacl (?):

sml:DisjointClassesShape_1 a sh:NodeShape ;
  sh:targetSubjectsOf rdf:type ;
  sh:property [
sh:path ( rdf:type [ sh:zeroOrMorePath rdfs:subClassOf ] ) ;
sh:qualifiedValueShape [
  sh:in (
sml:PhysicalObject
sml:InformationObject
sml:State
sml:Event
sml:Activity
  ) ;
] ;
sh:qualifiedMaxCount 1 ;
  ] ;
.

Any issues with this mapping?

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D79F0E.7E987C40]<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.




--
Y

RE: [topbraid-users] right owl2shacl-mapping?

2021-09-02 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Thx clear!

So…how could we define the dash:allDisjoint …. ?



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D79FDB.99CAD4E0]<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.




Van: topbraid-users@googlegroups.com  Namens 
Holger Knublauch
Verzonden: donderdag 2 september 2021 05:09
Aan: topbraid-users@googlegroups.com
CC: Miltos Gatzios ; Lucas Verhelst 

Onderwerp: Re: [topbraid-users] right owl2shacl-mapping?



On 2021-09-01 4:51 pm, 'Bohms, H.M. (Michel)' via TopBraid Suite Users wrote:
Hi Holger

The pattern I showed is a proposal by someone as a replacement for our current:

sml:AllDisjointClassesShape_1
  a sh:NodeShape ;
  sh:targetSubjectsOf rdf:type ;
  sh:property [
sh:path rdf:type ;
sh:qualifiedValueShape [
  sh:zeroOrMorePath rdfs:subClassOf ;
  sh:in (
sml:PhysicalObject
sml:InformationObject
sml:State
sml:Event
sml:Activity
  ) ;
] ;
sh:qualifiedMaxCount 1 ;
  ] ;
.

Would the current way be less cumbersome to check?
That looks equally slow as it applies to all rdf:type triples. Better to target 
exactly the instances of the classes in question, and the sh:targetClass 
approach that I outlined would do that.


How applied? In our current CEN SML ontology we have one such dimension for the 
main archetypes (as above) and for some of them some orthogonal dimensions with 
less items (#2): planned/realized, space/object, functional/technical).

That is also the reason multiple typing is always relevant and cannot be closed 
(ie ‘maxcard rdf:type being 1’ is not possible).

dash:allDisjoint would be an interesting  but ‘limited standard’ option I 
guess…isn’t there room in the evolving (in future more standard) shacl-af for 
such a construct?

dash:allDisjoint can already be expressed in SHACL 1.0 but not in Core but 
SHACL-SPARQL.

There is no point in waiting for a SHACL 1.1 or SHACL-AF becoming official as 
W3C would require multi-year processes for that and nobody has even started 
those processes.

Holger



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D79FDB.99CAD4E0]<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.




Van: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com> 
<mailto:topbraid-users@googlegroups.com> 
Namens Holger Knublauch
Verzonden: woensdag 1 september 2021 01:58
Aan: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com>
Onderwerp: Re: [topbraid-users] right owl2shacl-mapping?


This (interesting) design may work technically, but it can be very slow because 
it will traverse all rdf:type triples everywhere and use a rather complex 
algorithm with nested (qualified) shapes. A better solution would indeed start 
with exactly the instances of one of those classes. The solution that David 
mentioned certainly works OK if you have few disjoint classes each, but for 
long lists even the OWL 2 standard introduced a more compact syntax, using 
owl:AllDisjointClasses.

I guess the syntactically ideal replacement would be to declare a reusable 
constraint component using SHACL-SPARQL (which is part of the SHACL standard 
1.0). You could even leave the existing owl:DisjointClasses in place, but I 
don't like that they are using rdf:Lists which would need to be traversed 
repeatedly and that is very slow too. owl:members here should simply point at 
the classes IMHO.

But something like that should be fine:

sml:AllDisjointClasses_1
a sh:NodeShape ;
sh:targetClass sml:PhysicalObject, sml:InformationObject, sml:Activity, 
sml:Event, sml:State ;
dash:allDisjoint true .

where dash:allDisjoint would be a constraint component that would walk through 
the targetClasses of $currentShape in $shapesGraph.

How many such cases (of large disjointness clusters) do you actually have? Is 
this ev

[topbraid-users] semantic sheet datatypes

2021-09-16 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

When using the semantic spreadsheet option I see that numbers are mapped to xsd 
doubles.

But...in the spreadsheet people are using comma's... so I get:
[cid:image001.png@01D7AADE.5D44A380]

But a double should have a point in the end.

So wouldn't the heuristic not be a string when comma stuff is encountered?

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 michel.bo...@tno.nl

Location



[cid:image002.gif@01D7AADE.5D44A380]

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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/0f20078c7b184de595c10fc04650c8f7%40tno.nl.

RE: [topbraid-users] RE: third issue sheet import

2021-09-16 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Ok, I put some fake data in this yet to fill sheet ….



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D7AB20.0FA31C50]<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.




Van: topbraid-users@googlegroups.com  Namens 
Irene Polikoff
Verzonden: Thursday, September 16, 2021 5:26 PM
Aan: topbraid-users@googlegroups.com
Onderwerp: Re: [topbraid-users] RE: third issue sheet import

Yes, index starts with 0


On Sep 16, 2021, at 10:23 AM, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

More info:
It only goes wrong when the first sheet is empty
If there is data classification is fine.



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<http://www.tno.nl/>
<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.




Van: 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>>
Verzonden: Thursday, September 16, 2021 12:54 PM
Aan: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com>
Onderwerp: [topbraid-users] third issue sheet import

In excel i have 3 sheets
1 en 3 are empty, 2 is filled:



Result:
Data from sheet 2 is classified as sheet no 1 ..



Is this expected?

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<http://www.tno.nl/>
<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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/d0148d90da724fd2889e6100f25fa6b2%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/d0148d90da724fd2889e6100f25fa6b2%40tno.nl?utm_medium=email_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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/d4e75bb24ee0414db65532e6a77e375a%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/d4e75bb24ee0414db65532e6a77e375a%40tno.nl?utm_medium=email_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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/8DBF0191-FD21-4AEE-B9D0-9464CF9EBBA5%40topquadrant.com<https://groups.google.com/d/msgid/topbraid-users/8DBF0191-FD21-4AEE-B9D0-9464CF9EBBA5%40topquadrant.com?utm_medium=email_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 fr

[topbraid-users] RE: third issue sheet import

2021-09-16 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

More info:
It only goes wrong when the first sheet is empty
If there is data classification is fine.

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>

[cid:image003.gif@01D7AB17.329CBFD0]<http://www.tno.nl/>

Van: 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Verzonden: Thursday, September 16, 2021 12:54 PM
Aan: topbraid-users@googlegroups.com
Onderwerp: [topbraid-users] third issue sheet import

In excel i have 3 sheets
1 en 3 are empty, 2 is filled:

[cid:image004.png@01D7AB17.329CBFD0]

Result:
Data from sheet 2 is classified as sheet no 1 ..

[cid:image005.png@01D7AB17.329CBFD0]

Is this expected?

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>

[cid:image003.gif@01D7AB17.329CBFD0]<http://www.tno.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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/d4e75bb24ee0414db65532e6a77e375a%40tno.nl.

[topbraid-users] mu

2021-09-16 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

I noticed that:

zanddriehoek_180_µm_63_µm

did not result in a prefixed name

because of 'µ'...was that to be expected?

(can change to micro )



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 michel.bo...@tno.nl

Location



[cid:image001.gif@01D7AB20.4C683580]

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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/66ca887829244dbda2133e228f0acd9d%40tno.nl.

RE: [topbraid-users] RE: third issue sheet import

2021-09-16 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Hi Irene

Well the semantic import is working quite well for me.
(we generate standard/simple spreadsheets from existing PDFs)

The only two import-issues left now are:


·   Dots in numbers become commas

·   Dashes and underscores in attribute names disappear



Hope I can resolve/work around then then…….



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D7AB23.0DAF3430]<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.




Van: topbraid-users@googlegroups.com  Namens 
Irene Polikoff
Verzonden: Thursday, September 16, 2021 5:40 PM
Aan: topbraid-users@googlegroups.com
Onderwerp: Re: [topbraid-users] RE: third issue sheet import

Just noticed your message that the 1st sheet is empty.

This may be a reason as well. In some importers index starts with zero. In 
some, it starts with 1.

Overtime, several different spreadsheet importers were built. Based on our and 
customer’s experience with them, we are no longer actively maintaining 
spreadsheet import options unique to TBC. We discovered that no matter how much 
one tries, there will always be cases when a canned spreadsheet import does not 
do exactly what a user needs - because of how a particular spreadsheet is 
structured and the data in it  and/or because a canned import is not fully 
aligned with the user’s unique needs.

Spreadsheet importer available in EDG is under active maintenance. This is the 
only pre-canned option under active maintenance. All other options are as-is. 
For use cases that are outside of the current capabilities of that importer, we 
recommend and made available facilities for scripting a custom import as 
explained in https://www.datashapes.org/active/import.html#spreadsheets

Also see the video 
https://www.topquadrant.com/project/importing-data-using-active-data-shapes/


On Sep 16, 2021, at 11:25 AM, Irene Polikoff 
mailto:ir...@topquadrant.com>> wrote:
Yes, index starts with 0


On Sep 16, 2021, at 10:23 AM, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

More info:
It only goes wrong when the first sheet is empty
If there is data classification is fine.



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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.




Van: 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>>
Verzonden: Thursday, September 16, 2021 12:54 PM
Aan: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com>
Onderwerp: [topbraid-users] third issue sheet import

In excel i have 3 sheets
1 en 3 are empty, 2 is filled:



Result:
Data from sheet 2 is classified as sheet no 1 ..



Is this expected?

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/d0148d90da724fd2889e6100f25fa6b2%40tno.nl<https://groups.google.com/d/msgid

[topbraid-users] RE: semantic sheet datatypes

2021-09-16 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users


By explicitly formatting cells as Number this seems solved…. (they become 
xsd:double)


Only now my dotsin the values become comma’s in TBC! 

[cid:image001.png@01D7AB07.27DB8E60]



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image002.gif@01D7AB07.27DB8E60]<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.




Van: 'Bohms, H.M. (Michel)' via TopBraid Suite Users 

Verzonden: donderdag 16 september 2021 12:51
Aan: topbraid-users@googlegroups.com
Onderwerp: [topbraid-users] RE: semantic sheet datatypes

Now i changed my system setting (as also used by excel) to . as separator.

But now my . values in the sheet become strings!

H?

[cid:image004.png@01D7AB07.27DB8E60]



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image002.gif@01D7AB07.27DB8E60]<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.




Van: 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>>
Verzonden: donderdag 16 september 2021 09:37
Aan: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com>
Onderwerp: [topbraid-users] semantic sheet datatypes

When using the semantic spreadsheet option I see that numbers are mapped to xsd 
doubles.

But…in the spreadsheet people are using comma’s… so I get:
[cid:image006.png@01D7AB07.27DB8E60]

But a double should have a point in the end.

So wouldn’t the heuristic not be a string when comma stuff is encountered?

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image002.gif@01D7AB07.27DB8E60]<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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/0f20078c7b184de595c10fc04650c8f7%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/0f20078c7b184de595c10fc04650c8f7%40tno.nl?utm_medium=email_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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/3055a08a30474f0b83a05faa4463c86a%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/3055a08a30474f0b83a05faa4463c86a%40tno.nl?utm_medium=email_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 topbraid-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/fb399760342046c183502a06114465bb%40tno.nl.

RE: [topbraid-users] RE: third issue sheet import

2021-09-16 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Also in edg/import I see:

[cid:image001.png@01D7AB30.C6A43870]

Why are the underscores deleted?  Some special reason?

And here the mu is also replaced by an M:

[cid:image002.png@01D7AB30.C6A43870]

Some my issues seems more universal than just tbc-import 



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image003.gif@01D7AB30.C6A43870]<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.




Van: topbraid-users@googlegroups.com  Namens 
Irene Polikoff
Verzonden: Thursday, September 16, 2021 5:40 PM
Aan: topbraid-users@googlegroups.com
Onderwerp: Re: [topbraid-users] RE: third issue sheet import

Just noticed your message that the 1st sheet is empty.

This may be a reason as well. In some importers index starts with zero. In 
some, it starts with 1.

Overtime, several different spreadsheet importers were built. Based on our and 
customer’s experience with them, we are no longer actively maintaining 
spreadsheet import options unique to TBC. We discovered that no matter how much 
one tries, there will always be cases when a canned spreadsheet import does not 
do exactly what a user needs - because of how a particular spreadsheet is 
structured and the data in it  and/or because a canned import is not fully 
aligned with the user’s unique needs.

Spreadsheet importer available in EDG is under active maintenance. This is the 
only pre-canned option under active maintenance. All other options are as-is. 
For use cases that are outside of the current capabilities of that importer, we 
recommend and made available facilities for scripting a custom import as 
explained in https://www.datashapes.org/active/import.html#spreadsheets

Also see the video 
https://www.topquadrant.com/project/importing-data-using-active-data-shapes/


On Sep 16, 2021, at 11:25 AM, Irene Polikoff 
mailto:ir...@topquadrant.com>> wrote:
Yes, index starts with 0


On Sep 16, 2021, at 10:23 AM, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

More info:
It only goes wrong when the first sheet is empty
If there is data classification is fine.



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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.




Van: 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>>
Verzonden: Thursday, September 16, 2021 12:54 PM
Aan: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com>
Onderwerp: [topbraid-users] third issue sheet import

In excel i have 3 sheets
1 en 3 are empty, 2 is filled:



Result:
Data from sheet 2 is classified as sheet no 1 ..



Is this expected?

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/d0148d90da724fd2889e6100f25fa6b2%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/d0148d90da724fd2889e6100f25fa6b2%40tno.nl?utm_medium=e

[topbraid-users] third issue sheet import

2021-09-16 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

In excel i have 3 sheets
1 en 3 are empty, 2 is filled:

[cid:image001.png@01D7AAF9.EAE2F500]

Result:
Data from sheet 2 is classified as sheet no 1 ..

[cid:image002.png@01D7AAF9.EAE2F500]

Is this expected?

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 michel.bo...@tno.nl

Location



[cid:image003.gif@01D7AAF9.EAE2F500]

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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/d0148d90da724fd2889e6100f25fa6b2%40tno.nl.

[topbraid-users] special characters in atr. names

2021-09-16 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

It seems that dashes and underscores from attribute names disappear in de 
semantic sheet conversion.
Please advice, thx Michel

[cid:image001.png@01D7AAF8.6B815B90]

Results in:

[cid:image002.png@01D7AAF8.6B815B90]



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 michel.bo...@tno.nl

Location



[cid:image003.gif@01D7AAF8.6B815B90]

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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/ed86413647a54cfb8746654fd36b0af6%40tno.nl.

[topbraid-users] RE: semantic sheet datatypes

2021-09-16 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Now i changed my system setting (as also used by excel) to . as separator.

But now my . values in the sheet become strings!

[cid:image003.png@01D7AAF9.90120E40]

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>

[cid:image004.gif@01D7AAF9.90120E40]<http://www.tno.nl/>

Van: 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Verzonden: donderdag 16 september 2021 09:37
Aan: topbraid-users@googlegroups.com
Onderwerp: [topbraid-users] semantic sheet datatypes

When using the semantic spreadsheet option I see that numbers are mapped to xsd
doubles.

But…in the spreadsheet people are using comma’s… so I get:
[cid:image005.png@01D7AAF9.90120E40]

But a double should have a point in the end.

So wouldn’t the heuristic not be a string when comma stuff is encountered?

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>

[cid:image004.gif@01D7AAF9.90120E40]<http://www.tno.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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/3055a08a30474f0b83a05faa4463c86a%40tno.nl.

RE: [topbraid-users] define transform rule

2021-09-23 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

  Ahh, ok, so in my case I would add to the source class 
sa-input:Monsterlaag :

sh:rule [
a sh:TripleRule ;
sh:subject (sh:this ATTRIBUTE projectName as URI) ;
sh:predicate rdf:type ;
sh:object sa:Project ;
  ] .

Apart from the yellow I can also think of putting the rule at the target:

sa:ProjectShape
  a sh:NodeShape ;
  sh:targetClass sa:Project ;
  sh:rule [
a sh:SPARQLRule ;
sh:prefixes sa: ;
sh:construct """
  CONSTRUCT {
 ?uri rdf:type 
sa:Project .
  }
  WHERE {
 ?someproject 
sa-input:projectNaam ?projectNaam .
 ? Uri = ….( 
projectNaam)
  }
  """ ;
  ] ;
.

Again having a similar yellow part I have to find the right predefined function 
for…

???



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D7B07D.20F337D0]<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: topbraid-users@googlegroups.com  On 
Behalf Of David Price
Sent: Thursday, September 23, 2021 1:02 PM
To: topbraid-users@googlegroups.com
Subject: Re: [topbraid-users] define transform rule

SHACL rules are defined here:

https://w3c.github.io/shacl/shacl-af/#rules

What I typically do is make a separate graph for the rules and edit it in 
Composer, in the new Files feature or in Source Code editor. You can then 
include that graph and then remove it when the conversion is finished.

You define the rules (via sh:rule referencing a sh:SPARQLRule) on the “source” 
classes, and in the WHERE clause $this is instances of that classs, and then 
CONSTRUCT instances of “target" classes.

Cheers,
David


On 23 Sep 2021, at 11:01, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Hi David

In my input data from big excel I now have for instance the triple:


 sa-input:projectOmschrijving "bestekk 1654, N317 , Dieren - Hoog Keppel" ;

I want to use this info to instantiate a separate Project class.

I understand that here:


I have to add someway a shacl-af rule doing:
Insert triple: " 
rdf:type sa:Project

(actually I have to do that for all rows and because they are all in same 
project I will get duplicate triples that are only 1 in the end, I hope)

I have to do that for all classes (and for all other classes then the first: 
add also triple relating them)

Can you give my a hint how/where to best define these insert rule?

Thx a lot, 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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/f994e032f1c4487c8b99e264295c6142%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/f994e032f1c4487c8b99e264295c6142%40tno.nl?utm_medium=email_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 u

[topbraid-users] prefix use in edg

2021-09-23 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

When importing an ontology in EDG (in an existing ontology)
I see the prefix is not used.

In the imported file it says:
@prefix sa: https://w3id.org/sa/def# .

In the edg/settings tab taken over:
PREFIX sa: https://w3id.org/sa/def#

But I see in the ontology:

[cid:image002.png@01D7B06E.E30FBEB0]

So no prefixes for the 4 subclasses...

Thx for help, 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 michel.bo...@tno.nl

Location



[cid:image003.gif@01D7B06E.E30FBEB0]

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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/17e5f04bbda34910ad94ea87b746f0e4%40tno.nl.

RE: [topbraid-users] edg import xlsx

2021-09-23 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Worked perfectly. Thx.
So my translation (you call conversion) is now working fine.
I can read all spreadsheet data acc. to the defined simple spreadsheet ontology.

Next step is the data transformation to the target ontology ….
Involving the URI creation etc.
Guess will need some study/advice ….



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D7B06F.5664E430]<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: topbraid-users@googlegroups.com  On 
Behalf Of David Price
Sent: Wednesday, September 22, 2021 2:49 PM
To: topbraid-users@googlegroups.com
Subject: Re: [topbraid-users] edg import xlsx

I’ve never tried that, but may work.

Cheers,
David


On 22 Sep 2021, at 13:44, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Ok my idea:

In TBC i import the xlsx (semantic table variant)
Then I export a ttl for it

I strip the data off, leaving only the one class and column properties

I import this one in edg

Then I can do import by by pattern

Selecting the one class (and prob. the attributes in the mapping…).

Strange idea?



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com> 
mailto:topbraid-users@googlegroups.com>> On 
Behalf Of David Price
Sent: Wednesday, September 22, 2021 2:39 PM
To: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com>
Subject: Re: [topbraid-users] edg import xlsx

The entity type is the class in the ontology that the importer will make 
instances of. The current EDG graph must have an ontology in its 
settings/includes. That’s what the documentation means:

The Entity type for the imported data field identifies what type of assets you 
will be importing. Each row in the spreadsheet will be brought into EDG as an 
instance of the selected class and you will be able to map spreadsheet columns 
to the declared properties of the class.

FWIW if you create an EDG Ontologies first, you will find this which does 
generate the properties required, just not the class itself:

If you do not yet have a suitable target class: To import property definitions 
from a spreadsheet, create or select a class in the Ontology editor, then use 
Modify > Add property shapes from Spreadsheet columns...

Cheers,
David



On 22 Sep 2021, at 13:26, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Ok, I tried Import by Pattern

But then I get:



So, it does not takes, as with TBC, the worksheet name as enity type, but it 
expects a type already available…

AS I would like the system to generate the ontology from the first row…what is 
the minimum I have to do now?


Is it true that there is no ontology generation here because:
“ Each row in the spreadsheet will be brought into EDG as an instance of the 
selected class “

So:

  1.  Each row….also the first rows typically having the attribute names
  2.  Selected class, so there should be one to select already……

It feels like:
You have to define the ontology yourself now. And just import the DATA rows….
Please confirm, thx



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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 electron

[topbraid-users] define transform rule

2021-09-23 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Hi David

In my input data from big excel I now have for instance the triple:

sa-input:projectOmschrijving "bestekk 1654, N317 , Dieren - Hoog Keppel" ;

I want to use this info to instantiate a separate Project class.

I understand that here:
[cid:image002.png@01D7B072.B1296780]

I have to add someway a shacl-af rule doing:
Insert triple: "
rdf:type sa:Project

(actually I have to do that for all rows and because they are all in same
project I will get duplicate triples that are only 1 in the end, I hope)

I have to do that for all classes (and for all other classes then the first:
add also triple relating them)

Can you give my a hint how/where to best define these insert rule?

Thx a lot, 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 michel.bo...@tno.nl

Location

[cid:image003.gif@01D7B072.B1296780]

--
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/f994e032f1c4487c8b99e264295c6142%40tno.nl.

Re: [topbraid-users] define transform rule

2021-09-23 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Thx David
I'l try that.

Op 23 sep. 2021 15:08 schreef David Price :


On 23 Sep 2021, at 13:44, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Think you did not confuse me with target. I meant target class being the class 
i want to transform to...in the target ontology sa.

I think the below pattern does not do the job for me.
I have to create new instances of sa:Project etc. based on the existing 
MonsterLaag instance.

Based on!

Yes, I understood that.


That is...i use an attribute value of that instance to create an new target 
instance. Being projectNaam.

This transformation will in a sense normalise my original excel relation 
splitting it into subtables.

I just need to find again the way to create such an instance.

Some swp function i used to use in spin in the past.. and bind the result 
in a where clause i think...
???

SPARQL functions probably. BIND, IRI, CONCAT are usually enough.

See https://www.w3.org/TR/sparql11-query/#func-iri

Cheers,
David



Op 23 sep. 2021 13:50 schreef David Price 
mailto:dpr...@topquadrant.com>>:
Not quite and I think I confused you by mentioning “target” by which I did NOT 
mean sh:targetClass.

Put the actual SPARQLRule against the source class so that $this refers to 
instances of that class. There is no need for TripleRule. More like this but 
using $this in the WHERE rule to iterate through the instances of the class:

add to the source class sa-input:Monsterlaag :

 sh:rule [
a sh:SPARQLRule ;
sh:prefixes sa: ;
sh:construct """
  CONSTRUCT {
 ?uri rdf:type 
sa:Project .
  }
  WHERE {
 ?someproject 
sa-input:projectNaam ?projectNaam .
 ? Uri = ….( 
projectNaam)
  }
  """ ;
  ] ;
.

but

WHERE {
$this sa-input:SomeAttrOf Monsterlaag ?value .
$this sa-input:SomeOtherAttrOf Monsterlaag ?valueother .
Etc

Cheers,
David



On 23 Sep 2021, at 12:22, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

  Ahh, ok, so in my case I would add to the source class 
sa-input:Monsterlaag :

sh:rule [
a sh:TripleRule ;
sh:subject (sh:this ATTRIBUTE projectName as URI) ;
sh:predicate rdf:type ;
sh:object sa:Project ;
  ] .

Apart from the yellow I can also think of putting the rule at the target:

sa:ProjectShape
  a sh:NodeShape ;
  sh:targetClass sa:Project ;
  sh:rule [
a sh:SPARQLRule ;
sh:prefixes sa: ;
sh:construct """
  CONSTRUCT {
 ?uri rdf:type 
sa:Project .
  }
  WHERE {
 ?someproject 
sa-input:projectNaam ?projectNaam .
 ? Uri = ….( 
projectNaam)
  }
  """ ;
  ] ;
.

Again having a similar yellow part I have to find the right predefined function 
for…

???



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com> 
mailto:topbraid-users@googlegroups.com>> On 
Behalf Of David Price
Sent: Thursday, September 23, 2021 1:02 PM
To: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com>
Subject: Re: [topbraid-users] define transform rule

SHACL rules are defined here:

https://w3c.github.io/shacl/shacl-af/#rules

What I typically do is make a separate graph for the rules and edit it in 
Composer, in the n

Re: [topbraid-users] define transform rule

2021-09-23 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Think you did not confuse me with target. I meant target class being the class 
i want to transform to...in the target ontology sa.

I think the below pattern does not do the job for me.
I have to create new instances of sa:Project etc. based on the existing 
MonsterLaag instance.

Based on!

That is...i use an attribute value of that instance to create an new target 
instance. Being projectNaam.

This transformation will in a sense normalise my original excel relation 
splitting it into subtables.

I just need to find again the way to create such an instance.

Some swp function i used to use in spin in the past.. and bind the result 
in a where clause i think...
???


Op 23 sep. 2021 13:50 schreef David Price :
Not quite and I think I confused you by mentioning “target” by which I did NOT 
mean sh:targetClass.

Put the actual SPARQLRule against the source class so that $this refers to 
instances of that class. There is no need for TripleRule. More like this but 
using $this in the WHERE rule to iterate through the instances of the class:

add to the source class sa-input:Monsterlaag :

 sh:rule [
a sh:SPARQLRule ;
sh:prefixes sa: ;
sh:construct """
  CONSTRUCT {
 ?uri rdf:type 
sa:Project .
  }
  WHERE {
 ?someproject 
sa-input:projectNaam ?projectNaam .
 ? Uri = ….( 
projectNaam)
  }
  """ ;
  ] ;
.

but

WHERE {
$this sa-input:SomeAttrOf Monsterlaag ?value .
$this sa-input:SomeOtherAttrOf Monsterlaag ?valueother .
Etc

Cheers,
David



On 23 Sep 2021, at 12:22, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

  Ahh, ok, so in my case I would add to the source class 
sa-input:Monsterlaag :

sh:rule [
a sh:TripleRule ;
sh:subject (sh:this ATTRIBUTE projectName as URI) ;
sh:predicate rdf:type ;
sh:object sa:Project ;
  ] .

Apart from the yellow I can also think of putting the rule at the target:

sa:ProjectShape
  a sh:NodeShape ;
  sh:targetClass sa:Project ;
  sh:rule [
a sh:SPARQLRule ;
sh:prefixes sa: ;
sh:construct """
  CONSTRUCT {
 ?uri rdf:type 
sa:Project .
  }
  WHERE {
 ?someproject 
sa-input:projectNaam ?projectNaam .
 ? Uri = ….( 
projectNaam)
  }
  """ ;
  ] ;
.

Again having a similar yellow part I have to find the right predefined function 
for…

???



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com> 
mailto:topbraid-users@googlegroups.com>> On 
Behalf Of David Price
Sent: Thursday, September 23, 2021 1:02 PM
To: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com>
Subject: Re: [topbraid-users] define transform rule

SHACL rules are defined here:

https://w3c.github.io/shacl/shacl-af/#rules

What I typically do is make a separate graph for the rules and edit it in 
Composer, in the new Files feature or in Source Code editor. You can then 
include that graph and then remove it when the conversion is finished.

You define the rules (via sh:rule referencing a sh:SPARQLRule) on the “source” 
classes, and in the WHERE clause $this is instances of that classs, and then 
CONSTRUCT instances of “target" classes.

Cheers,
David


On 23 Sep 2021, at 11:01, 'Bohms, H.M. (Michel)'

[topbraid-users] malformed shacl

2021-09-24 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Hi David, Irene

Tbc says maformed shacl for:

[cid:image002.png@01D7B186.829E37A0]
Any tip welcome, 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 michel.bo...@tno.nl

Location



[cid:image001.gif@01D7B184.1F1D6AE0]

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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/6a93f92fda784aaf98b0bc4773ce7e71%40tno.nl.

[topbraid-users] import issue by pattern

2021-09-24 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

When I import my spreadsheet in an ontology that has to variants of MonsterLaag
One with prefix sainput
One with prefix sa

And I select MonsterLaag (the right one in the panel):

I get:
[cid:image001.png@01D7B181.D61F6C00]

No more full uri of prefix there (for MonsterLaag).

Also in the next mapping table you cannot check anymore the right Monsterlaag
and its properties are used...

Wouldn't it be handy to show the prefix here?

(endresult is fine though, instances are under the right sainput:MonsterLaag)

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 michel.bo...@tno.nl

Location

[cid:image004.gif@01D7B181.4F466530]

--
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/95f903ea50cb47159094dcf321c269c8%40tno.nl.

[topbraid-users] prefix

2021-09-23 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

And moreover:

[cid:image001.png@01D7B0BC.5C6349B0]

I thought i had to declare all used prefixes...
But this second one stays red




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 michel.bo...@tno.nl

Location



[cid:image002.gif@01D7B0BC.5C6349B0]

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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/dc34ac9629644a55b6d2f2820cedecef%40tno.nl.

RE: [topbraid-users] prefix use in edg

2021-09-23 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Hi David

There seems to be no duplicate prefix.
I checked the imported files (1xsa, 1xsa-input).

And the name space settings say:

PREFIX dash: http://datashapes.org/dash#
PREFIX dc: http://purl.org/dc/elements/1.1/
PREFIX dct: http://purl.org/dc/terms/
PREFIX edg: http://edg.topbraid.solutions/model/
PREFIX graphql: http://datashapes.org/graphql#
PREFIX metadata: http://topbraid.org/metadata#
PREFIX nen2660: https://w3id.org/nen2660/def#
PREFIX nen2660-term: https://w3id.org/nen2660/term#
PREFIX owl: http://www.w3.org/2002/07/owl#
PREFIX quantitykind: http://qudt.org/vocab/quantitykind/
PREFIX qudt: http://qudt.org/schema/qudt/
PREFIX rdf: http://www.w3.org/1999/02/22-rdf-syntax-ns#
PREFIX rdfs: http://www.w3.org/2000/01/rdf-schema#
PREFIX sa: https://w3id.org/sa/def#
PREFIX sh: http://www.w3.org/ns/shacl#
PREFIX skos: http://www.w3.org/2004/02/skos/core#
PREFIX skosxl: http://www.w3.org/2008/05/skos-xl#
PREFIX teamwork: http://topbraid.org/teamwork#
PREFIX time: http://www.w3.org/2006/time#
PREFIX unit: http://qudt.org/vocab/unit/
PREFIX xsd: http://www.w3.org/2001/XMLSchema#

“sa”  is there only once…

But….

I look again and:

[cid:image001.png@01D7B0B6.0A64E5C0]

So I guess, somewhere some refresh issue 
Maybe solved by switching tabs….

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image002.gif@01D7B0B6.0A64E5C0]<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: topbraid-users@googlegroups.com  On 
Behalf Of David Price
Sent: Thursday, September 23, 2021 4:30 PM
To: topbraid-users@googlegroups.com
Subject: Re: [topbraid-users] prefix use in edg

Sounds like duplicate prefix is consuing EDG. Choose one or the other and 
delete the duplicate and see if that fixed things.

Cheers,
David


On 23 Sep 2021, at 10:33, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

When importing an ontology in EDG (in an existing ontology)
I see the prefix is not used.

In the imported file it says:
@prefix sa: https://w3id.org/sa/def#<https://w3id.org/sa/def> .

In the edg/settings tab taken over:
PREFIX sa: https://w3id.org/sa/def#<https://w3id.org/sa/def>

But I see in the ontology:



So no prefixes for the 4 subclasses…

Thx for help, 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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/17e5f04bbda34910ad94ea87b746f0e4%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/17e5f04bbda34910ad94ea87b746f0e4%40tno.nl?utm_medium=email_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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/20441DDF-FE43-424E-9478-72A8229ED0E2%40topquadrant.com<https://groups.google.com/d/msgid/topbraid-users/20441DDF-FE43-424E-9478-72A8229ED0E2%40topquadrant.com?utm_medium=email_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 topbraid-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/cb0c9313db694ff187bc3c4499fd6f5d%40tno.nl.

RE: [topbraid-users] define transform rule

2021-09-23 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Ok, i tried:

[cid:image001.png@01D7B0BB.B6965F40]

But the query stays red….




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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image002.gif@01D7B0BB.B6965F40]<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: topbraid-users@googlegroups.com  On 
Behalf Of David Price
Sent: Thursday, September 23, 2021 3:08 PM
To: topbraid-users@googlegroups.com
Subject: Re: [topbraid-users] define transform rule




On 23 Sep 2021, at 13:44, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Think you did not confuse me with target. I meant target class being the class 
i want to transform to...in the target ontology sa.

I think the below pattern does not do the job for me.
I have to create new instances of sa:Project etc. based on the existing 
MonsterLaag instance.

Based on!

Yes, I understood that.



That is...i use an attribute value of that instance to create an new target 
instance. Being projectNaam.

This transformation will in a sense normalise my original excel relation 
splitting it into subtables.

I just need to find again the way to create such an instance.

Some swp function i used to use in spin in the past.. and bind the result 
in a where clause i think...
???

SPARQL functions probably. BIND, IRI, CONCAT are usually enough.

See https://www.w3.org/TR/sparql11-query/#func-iri

Cheers,
David




Op 23 sep. 2021 13:50 schreef David Price 
mailto:dpr...@topquadrant.com>>:
Not quite and I think I confused you by mentioning “target” by which I did NOT 
mean sh:targetClass.

Put the actual SPARQLRule against the source class so that $this refers to 
instances of that class. There is no need for TripleRule. More like this but 
using $this in the WHERE rule to iterate through the instances of the class:

add to the source class sa-input:Monsterlaag :

 sh:rule [
a sh:SPARQLRule ;
sh:prefixes sa: ;
sh:construct """
  CONSTRUCT {
 ?uri rdf:type 
sa:Project .
  }
  WHERE {
 ?someproject 
sa-input:projectNaam ?projectNaam .
 ? Uri = ….( 
projectNaam)
  }
  """ ;
  ] ;
.

but

WHERE {
$this sa-input:SomeAttrOf Monsterlaag ?value .
$this sa-input:SomeOtherAttrOf Monsterlaag ?valueother .
Etc

Cheers,
David



On 23 Sep 2021, at 12:22, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

  Ahh, ok, so in my case I would add to the source class 
sa-input:Monsterlaag :

sh:rule [
a sh:TripleRule ;
sh:subject (sh:this ATTRIBUTE projectName as URI) ;
sh:predicate rdf:type ;
sh:object sa:Project ;
  ] .

Apart from the yellow I can also think of putting the rule at the target:

sa:ProjectShape
  a sh:NodeShape ;
  sh:targetClass sa:Project ;
  sh:rule [
a sh:SPARQLRule ;
sh:prefixes sa: ;
sh:construct """
  CONSTRUCT {
 ?uri rdf:type 
sa:Project .
  }
  WHERE {
 ?someproject 
sa-input:projectNaam ?projectNaam .
 ? Uri = ….( 
projectNaam)
  }
  """ ;
  ] ;
.

Again having a similar yellow part I have to find the right predefined function 
for…

???



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<http://www.tno.nl/>

T

[topbraid-users] edg search results for classes

2021-09-23 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

In:

[cid:image001.png@01D7B0B6.98D26260]

When I type sa:Project in the quick search no results are shown...
As you can see it IS there ...

Normal or full text search, same issue

Gr 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 michel.bo...@tno.nl

Location



[cid:image002.gif@01D7B0B6.98D26260]

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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/92b286afa3424ae2b2270bbaa519c118%40tno.nl.

RE: [topbraid-users] owl restrictions for individuals?

2021-10-13 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Hi David

Thx for your view.

Personally I think the rdfs containers captures at least some generic 
"grouping" semantics.
I would not like to redefine that myself (own group classes, member relations 
etc.).

On the other hand we might misuse this way a mechanism meant for explicit 
grouping for implicit grouping.

In any case the practical need is really there in asset mngt. People do not 
want to model (in their view) all the details from others.
In the example: they want to be able to model the groups of things having 
typical properties and the group having properties like an amount of members, 
total cost, etc. without the need to be able to explicitly point to the members.

In that sense our pattern could fulfil those needs: we have a group 
(container), we do not model explicit members, but add other properties to the 
group (like total cost) and are able to put restrictions on their members (like 
'all should be yellow'). So we capture the typical member data in a restriction 
without having the (explicit) members themselvesthat might be special 
too

Anyway, we'll consider, thx



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D7C017.1A8D5610]<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: topbraid-users@googlegroups.com  On 
Behalf Of David Price
Sent: Monday, October 11, 2021 5:34 PM
To: topbraid-users@googlegroups.com
Subject: Re: [topbraid-users] owl restrictions for individuals?

The following is just my opinion:

RDFS collections have zero semantics, so using them for a purpose like this 
sounds like a bad idea. I have never used them in any ontology for any customer.

Calling something an "implicit group" and then trying to use semantics to 
define it does not make any sense to me. So, it's hard to really understand 
your requirements, but if there is a need to "group" things then :

- perhaps make a class called Groups and make instances of that class be 
your groups. Then a simple object property member ofGroup can relate any 
instance to that group.
- a second approach is to define a datatype property but give it anyURI as its 
datatype. This is often how models relate to external reference data libraries 
not actually imported into the current graph - i.e. they have a property called 
something like "external classification" with a URI value that usually 
dereferences to something in a giant online RDL.

Both of are easy in OWL and SHACL.

Cheers,
David

On 11 Oct 2021, at 15:46, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Hereby also the actual code example for modelling implicit groups of assets.
(via a nested constraint for an individual)

Example: a road  crash barrier having associated an implicit group of 300 
yellow km-signs.

No complaints from TBC.
Still special way of modelling, comments welcome.

# baseURI: https://w3id.org/igtest/owl/def
# imports: https://w3id.org/nen2660/owl/def

@prefix nen2660: https://w3id.org/nen2660/def#<https://w3id.org/nen2660/def> .
@prefix owl: http://www.w3.org/2002/07/owl#<http://www.w3.org/2002/07/owl> .
@prefix quantitykind: http://qudt.org/vocab/quantitykind/ .
@prefix qudt: http://qudt.org/schema/qudt/ .
@prefix rdf: 
http://www.w3.org/1999/02/22-rdf-syntax-ns#<http://www.w3.org/1999/02/22-rdf-syntax-ns>
 .
@prefix rdfs: 
http://www.w3.org/2000/01/rdf-schema#<http://www.w3.org/2000/01/rdf-schema> .
@prefix skos: 
http://www.w3.org/2004/02/skos/core#<http://www.w3.org/2004/02/skos/core> .
@prefix unit: http://qudt.org/vocab/unit/ .
@prefix wn: 
https://w3id.org/wegennetwerk/def#<https://w3id.org/wegennetwerk/def> .
@prefix xsd: 
http://www.w3.org/2001/XMLSchema#<http://www.w3.org/2001/XMLSchema> .
@prefix ig: https://w3id.org/igtest/def#<https://w3id.org/igtest/def> .

https://w3id.org/igtest/owl/def
  a owl:Ontology ;
  owl:imports https://w3id.org/nen2660/owl/def ;
.
ig:GeleideConstructie a owl:Class ;
.
ig:HectometerPaal a owl:Class ;
.
ig:GCnoorderZijberm-hm15dot-hm25dot3 a ig:GeleideConstructie ;
  ig:hasGroupedParts ig:HMPgroup_1 ;
.
ig:HMPgroup_1 a rdfs:Container ;
  a [a owl:Restriction ;
 owl:onProperty rdfs:member;
 owl:qualifiedCardinality 300 ;
 owl:onClass [ rdfs:subClassOf ig:HectometerPaal;
   rdfs:subClassOf [
 a owl:Restriction;

[topbraid-users] RE: owl restrictions for individuals?

2021-10-11 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Hereby also the actual code example for modelling implicit groups of assets.
(via a nested constraint for an individual)

Example: a road  crash barrier having associated an implicit group of 300 
yellow km-signs.

No complaints from TBC.
Still special way of modelling, comments welcome.

# baseURI: https://w3id.org/igtest/owl/def
# imports: https://w3id.org/nen2660/owl/def

@prefix nen2660: https://w3id.org/nen2660/def# .
@prefix owl: http://www.w3.org/2002/07/owl# .
@prefix quantitykind: http://qudt.org/vocab/quantitykind/ .
@prefix qudt: http://qudt.org/schema/qudt/ .
@prefix rdf: http://www.w3.org/1999/02/22-rdf-syntax-ns# .
@prefix rdfs: http://www.w3.org/2000/01/rdf-schema# .
@prefix skos: http://www.w3.org/2004/02/skos/core# .
@prefix unit: http://qudt.org/vocab/unit/ .
@prefix wn: https://w3id.org/wegennetwerk/def# .
@prefix xsd: http://www.w3.org/2001/XMLSchema# .
@prefix ig: https://w3id.org/igtest/def# .

https://w3id.org/igtest/owl/def
  a owl:Ontology ;
  owl:imports https://w3id.org/nen2660/owl/def ;
.
ig:GeleideConstructie a owl:Class ;
.
ig:HectometerPaal a owl:Class ;
.
ig:GCnoorderZijberm-hm15dot-hm25dot3 a ig:GeleideConstructie ;
  ig:hasGroupedParts ig:HMPgroup_1 ;
.
ig:HMPgroup_1 a rdfs:Container ;
  a [a owl:Restriction ;
 owl:onProperty rdfs:member;
 owl:qualifiedCardinality 300 ;
 owl:onClass [ rdfs:subClassOf ig:HectometerPaal;
   rdfs:subClassOf [
 a owl:Restriction;
 owl:hasvalue "Geel";
 owl:onProperty ig:kleur] ] ] ;
.
ig:hasGroupedParts a owl:ObjectProperty ;
  rdfs:range rdfs:Container ;
.
ig:kleur a owl:DatatypeProperty ;
  rdfs:range xsd:string ;
.





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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D7BEBF.7B5D1DD0]<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: 'Bohms, H.M. (Michel)' via TopBraid Suite Users 

Sent: Friday, October 8, 2021 12:52 PM
To: topbraid-users@googlegroups.com
Subject: [topbraid-users] owl restrictions for individuals?

In asset management/modelling we often see the need  to define groups of (many) 
things that are not (yet) fully explicitly modelled.
Ie a rdfs:Bag instance where not all rdfs:member’ s are known explicitly.

Such ‘implicit groups’ as we call them, we would like to represent using OWL 
restriction classes in owl (and later also shacl shapes) that are used to 
classify such group instances.
Typically all examples we see is using such restriction classes for subclassing 
on class-level.
So now the idea is to use them for classifying instances.

Would that be possible within TBC/EDG?

In my perception, such instance-level constraint was only a shacl-benefit.
But now one of my partners says that this can be done with owl restrictions too.

Here is a sketch of the proposal:
[cid:image002.png@01D7BEBF.7B5D1DD0]
Not that the restriction R (left side) is related to the instance of the group 
#1 working on its member property.
Note also its is a nested restriction: onClass has further subrestrictions.

If allowed (owl full?) and practically working in TBC/EDG, it would be a very 
nice language-level approach, better than own inventions like an own 
hasReferenceIndividual relationship etc.

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D7BEBF.7B5D1DD0]<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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/8dcd808efee34cb7aac43463f7051a2c%40tno.nl<https://groups.google.com

[topbraid-users] owl restrictions for individuals?

2021-10-08 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

In asset management/modelling we often see the need to define groups of (many)
things that are not (yet) fully explicitly modelled.
Ie a rdfs:Bag instance where not all rdfs:member' s are known explicitly.

Such 'implicit groups' as we call them, we would like to represent using OWL
restriction classes in owl (and later also shacl shapes) that are used to
classify such group instances.
Typically all examples we see is using such restriction classes for subclassing
on class-level.
So now the idea is to use them for classifying instances.

Would that be possible within TBC/EDG?

In my perception, such instance-level constraint was only a shacl-benefit.
But now one of my partners says that this can be done with owl restrictions too.

Here is a sketch of the proposal:
[cid:image003.png@01D7BC43.412E19D0]
Not that the restriction R (left side) is related to the instance of the group
#1 working on its member property.
Note also its is a nested restriction: onClass has further subrestrictions.

If allowed (owl full?) and practically working in TBC/EDG, it would be a very
nice language-level approach, better than own inventions like an own
hasReferenceIndividual relationship etc.

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 michel.bo...@tno.nl

Location

[cid:image004.gif@01D7BC41.08076F00]

--
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/8dcd808efee34cb7aac43463f7051a2c%40tno.nl.

RE: [topbraid-users] spreadsheet import by pattern, no-domain target props issue

2021-10-19 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Solved by first converting ‘owl to shacl’ before the spreadsheet import (after 
ontology import)

It seems the simple domains are directly taken into account (without this 
conversion), where the domain-unions need this explicit conversion first…..



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D7C4E8.865DA5E0]<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: topbraid-users@googlegroups.com  On 
Behalf Of David Price
Sent: Tuesday, October 19, 2021 12:37 PM
To: topbraid-users@googlegroups.com
Subject: Re: [topbraid-users] spreadsheet import by pattern, no-domain target 
props issue

As I said, go look at the Class/Nodeshape in a Data Graph and see if the 
properties are there for you to fill into an instance. If not, then you may 
need to look a SHACL source code to understand.

Also, after adding relevant domains did you go to Transforms and run the 
OWL2SHACL again?

Cheers,
David


On 19 Oct 2021, at 11:14, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

That would be good news….

I added union domains for the relevant columns (5x).

However ‘spreadsheet import by pattern’ does not provide the mapping, nor does 
it allow me to select myself.

(for the five union-based domains):



Using EDG started from Windows TBC ME 7.0.3.



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com> 
mailto:topbraid-users@googlegroups.com>> On 
Behalf Of David Price
Sent: Tuesday, October 19, 2021 12:01 PM
To: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com>
Subject: Re: [topbraid-users] spreadsheet import by pattern, no-domain target 
props issue

Actually, OWL2SHACL handles that case (just tested in Composer 6.4). Something 
else must be “wrong”.

On 19 Oct 2021, at 10:44, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

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 ;
.

 I just did this:

# baseURI: http://example.org/unnamed
# prefix: unnamed

@prefix owl: <http://www.w3.org/2002/07/owl#<http://www.w3.org/2002/07/owl>> .
@prefix rdf: 
<http://www.w3.org/1999/02/22-rdf-syntax-ns#<http://www.w3.org/1999/02/22-rdf-syntax-ns>>
 .
@prefix rdfs: 
<http://www.w3.org/2000/01/rdf-schema#<http://www.w3.org/2000/01/rdf-schema>> .
@prefix unnamed: <http://example.org/unnamed#<http://example.org/unnamed>> .
@prefix xsd: 
<http://www.w3.org/2001/XMLSchema#<http://www.w3.org/2001/XMLSchema>> .

<http://example.org/unnamed>
  a owl:Ontology ;
  owl:versionInfo "Created with TopBraid Composer" ;
.
unnamed:DatatypeProperty_1
  a owl:DatatypeProperty ;
  rdfs:domain [
  a owl:Class ;
  owl:unionOf (
  unnamed:Thing_1
  unnamed:Thing_2
) ;
] ;
  rdfs:label "Datatype property 1" ;
  rdfs:range xsd:integer ;
.
unnamed:Thing_1
  a owl:Class ;
  rdfs:label "Thing 1" ;
  rdfs:subClassOf owl:Thing ;
.
unnamed:Thing_2
  a owl:Class ;
  rdfs:label "Thing 2" ;
  rdfs:subClassOf owl:Thing ;
.

and get this:

# baseURI: http://example.org/unnamed.shapes
# imports: http://datashapes.org/dash
# imports: http://example.org/unnamed

@prefix dash: <http://datashapes.org/dash#<http://datashapes.org/dash>> .
@prefix owl: <http://www.w3.org/2002/07/owl#<http://w

RE: [topbraid-users] spreadsheet import by pattern, no-domain target props issue

2021-10-19 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

That would be good news….

I added union domains for the relevant columns (5x).

However ‘spreadsheet import by pattern’ does not provide the mapping, nor does 
it allow me to select myself.

(for the five union-based domains):

[cid:image004.png@01D7C4E2.D027EF10]

Using EDG started from Windows TBC ME 7.0.3.



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image005.gif@01D7C4E2.D027EF10]<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: topbraid-users@googlegroups.com  On 
Behalf Of David Price
Sent: Tuesday, October 19, 2021 12:01 PM
To: topbraid-users@googlegroups.com
Subject: Re: [topbraid-users] spreadsheet import by pattern, no-domain target 
props issue

Actually, OWL2SHACL handles that case (just tested in Composer 6.4). Something 
else must be “wrong”.

On 19 Oct 2021, at 10:44, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

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 ;
.

 I just did this:

# baseURI: http://example.org/unnamed
# prefix: unnamed

@prefix owl: <http://www.w3.org/2002/07/owl#<http://www.w3.org/2002/07/owl>> .
@prefix rdf: 
<http://www.w3.org/1999/02/22-rdf-syntax-ns#<http://www.w3.org/1999/02/22-rdf-syntax-ns>>
 .
@prefix rdfs: 
<http://www.w3.org/2000/01/rdf-schema#<http://www.w3.org/2000/01/rdf-schema>> .
@prefix unnamed: <http://example.org/unnamed#<http://example.org/unnamed>> .
@prefix xsd: 
<http://www.w3.org/2001/XMLSchema#<http://www.w3.org/2001/XMLSchema>> .

<http://example.org/unnamed>
  a owl:Ontology ;
  owl:versionInfo "Created with TopBraid Composer" ;
.
unnamed:DatatypeProperty_1
  a owl:DatatypeProperty ;
  rdfs:domain [
  a owl:Class ;
  owl:unionOf (
  unnamed:Thing_1
  unnamed:Thing_2
) ;
] ;
  rdfs:label "Datatype property 1" ;
  rdfs:range xsd:integer ;
.
unnamed:Thing_1
  a owl:Class ;
  rdfs:label "Thing 1" ;
  rdfs:subClassOf owl:Thing ;
.
unnamed:Thing_2
  a owl:Class ;
  rdfs:label "Thing 2" ;
  rdfs:subClassOf owl:Thing ;
.

and get this:

# baseURI: http://example.org/unnamed.shapes
# imports: http://datashapes.org/dash
# imports: http://example.org/unnamed

@prefix dash: <http://datashapes.org/dash#<http://datashapes.org/dash>> .
@prefix owl: <http://www.w3.org/2002/07/owl#<http://www.w3.org/2002/07/owl>> .
@prefix rdf: 
<http://www.w3.org/1999/02/22-rdf-syntax-ns#<http://www.w3.org/1999/02/22-rdf-syntax-ns>>
 .
@prefix rdfs: 
<http://www.w3.org/2000/01/rdf-schema#<http://www.w3.org/2000/01/rdf-schema>> .
@prefix sh: <http://www.w3.org/ns/shacl#<http://www.w3.org/ns/shacl>> .
@prefix unnamed: <http://example.org/unnamed#<http://example.org/unnamed>> .
@prefix xsd: 
<http://www.w3.org/2001/XMLSchema#<http://www.w3.org/2001/XMLSchema>> .

unnamed:Thing_1
  a sh:NodeShape ;
  sh:property unnamed:Thing_1-DatatypeProperty_1 ;
.
unnamed:Thing_1-DatatypeProperty_1
  a sh:PropertyShape ;
  sh:path unnamed:DatatypeProperty_1 ;
  sh:datatype xsd:integer ;
.
unnamed:Thing_2
  a sh:NodeShape ;
  sh:property unnamed:Thing_2-DatatypeProperty_1 ;
.
unnamed:Thing_2-DatatypeProperty_1
  a sh:PropertyShape ;
  sh:path unnamed:DatatypeProperty_1 ;
  sh:datatype xsd:integer ;
.
<http://example.org/unnamed.shapes>
  a owl:Ontology ;
  owl:imports <http://datashapes.org/dash> ;
  owl:imports <http://example.org/unnamed> ;
.


Cheers,
David



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<http://www.tno.nl/>

This message may contain information that is not intended for you. If you are 
not the addressee or if

[topbraid-users] include question

2021-10-20 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Everytime I cretae an ontology in EDG it seems somehow it is included in 
itself: example ontology 'sma':

[cid:image001.png@01D7C59A.678B5920]

So everytime I have to delete it I first have to delete this include first.
At what point in time is this selfinclude added?

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 michel.bo...@tno.nl

Location



[cid:image002.gif@01D7C59A.678B5920]

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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/b9cdafbf28c846b89824f2f9200bb482%40tno.nl.

RE: [topbraid-users] include question

2021-10-20 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Hmmm, not circular…

What i do:

Create new ontology in edg called sma (https://w3id.org/sma/def)

Import my sainput ontology (this one is only importing sh) for the excel inport

Next I import the sa target ontology (this one imports sainput, and also 
nen2660 but this cannot cause issue I think, there is no link to sma)

After this action I see the sma selfinclude…..



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D7C59E.92193870]<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: topbraid-users@googlegroups.com  On 
Behalf Of David Price
Sent: Wednesday, October 20, 2021 10:20 AM
To: topbraid-users@googlegroups.com
Subject: Re: [topbraid-users] include question

EDG ontologies do not include themselves.  I expect there is a circular import 
in your ontologies set.
Cheers,
David


On 20 Oct 2021, at 09:08, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Everytime I cretae an ontology in EDG it seems somehow it is included in 
itself: example ontology ‘sma’:



So everytime I have to delete it I first have to delete this include first.
At what point in time is this selfinclude added?

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<http://www.tno.nl/>
<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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/b9cdafbf28c846b89824f2f9200bb482%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/b9cdafbf28c846b89824f2f9200bb482%40tno.nl?utm_medium=email_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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/B754DE7D-AAF0-42CB-8AB3-1F52B721D490%40topquadrant.com<https://groups.google.com/d/msgid/topbraid-users/B754DE7D-AAF0-42CB-8AB3-1F52B721D490%40topquadrant.com?utm_medium=email_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 topbraid-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/a099fb3b236646a08ae3764cec094f8d%40tno.nl.


sa.ttl
Description: sa.ttl


sainput.ttl
Description: sainput.ttl

RE: [topbraid-users] include question

2021-10-20 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Thx I will try the last option.



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D7C5AC.FF6784A0]<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: topbraid-users@googlegroups.com  On 
Behalf Of David Price
Sent: Wednesday, October 20, 2021 12:10 PM
To: topbraid-users@googlegroups.com
Subject: Re: [topbraid-users] include question

Hi Michel,

I can only repeat what I said - the EDG app does not do this. I’ve made 
hundreds of ontologies, and other staff and customers have made thousands, 
without seeing this behaviour.

I occasionally see odd behaviour running EDG from TBC (i.e. eclipse) where 
cleanup/restart is needed though. Maybe there’s something leftover in TBC cache 
or workspace - suggest re-starting TBC. Maybe the TBC workspace is somehow 
corrupted and you should create a new one.

Cheers,
David


On 20 Oct 2021, at 09:38, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Hmmm, not circular…

What i do:

Create new ontology in edg called sma (https://w3id.org/sma/def)

Import my sainput ontology (this one is only importing sh) for the excel inport

Next I import the sa target ontology (this one imports sainput, and also 
nen2660 but this cannot cause issue I think, there is no link to sma)

After this action I see the sma selfinclude…..



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com> 
mailto:topbraid-users@googlegroups.com>> On 
Behalf Of David Price
Sent: Wednesday, October 20, 2021 10:20 AM
To: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com>
Subject: Re: [topbraid-users] include question

EDG ontologies do not include themselves.  I expect there is a circular import 
in your ontologies set.
Cheers,
David



On 20 Oct 2021, at 09:08, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Everytime I cretae an ontology in EDG it seems somehow it is included in 
itself: example ontology ‘sma’:



So everytime I have to delete it I first have to delete this include first.
At what point in time is this selfinclude added?

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/b9cdafbf28c846b89824f2f9200bb482%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/b9cdafbf28c846b89824f2f9200bb482%40tno.nl?utm_medium=email_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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on th

[topbraid-users] spreadsheet import by pattern, no-domain target props issue

2021-10-19 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Properties in the input ontology not having a domain cannot be chosen as target:

[cid:image004.png@01D7C4D8.437AF2B0]
(where the dashes are)

Is this intended?

(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 ;
.

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 michel.bo...@tno.nl

Location

[cid:image005.gif@01D7C4D8.437AF2B0]

--
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/9f044c442f7f4a9591b29cb8b421f974%40tno.nl.

RE: [topbraid-users] spreadsheet import by pattern, no-domain target props issue

2021-10-19 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D7C4DE.9EF81040]<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: topbraid-users@googlegroups.com  On 
Behalf Of David Price
Sent: Tuesday, October 19, 2021 11:26 AM
To: topbraid-users@googlegroups.com
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 
mailto:topbraid-users@googlegroups.com>> wrote:

Properties in the input ontology not having a domain cannot be chosen as target:


(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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubs

RE: [topbraid-users] multi-sheet import by pattern

2021-10-18 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Ok, thx, I will do the sheets one by one…

Gr 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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D7C404.41B42FC0]<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: topbraid-users@googlegroups.com  On 
Behalf Of David Price
Sent: Thursday, October 7, 2021 11:30 AM
To: topbraid-users@googlegroups.com
Subject: Re: [topbraid-users] multi-sheet import by pattern




On 7 Oct 2021, at 10:21, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Is it possible to do a multi-sheet import?


Leaving index open delivers a java-level error…..(which is strange since its 
says ‘ optional’ )

Maybe something like “1-2”?

Multi-sheet import is not supported by the "as pattern/as template” EDG 
importer.

If that is your requirement, then I’d suggest using an external tool that 
generates RDF and then import that into EDG.

Cheers,
David



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/398bb3ac997d4f988467b89b049d9344%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/398bb3ac997d4f988467b89b049d9344%40tno.nl?utm_medium=email_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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/A68B0FBF-F4A7-4328-9749-AEBCBF5FE2DD%40topquadrant.com<https://groups.google.com/d/msgid/topbraid-users/A68B0FBF-F4A7-4328-9749-AEBCBF5FE2DD%40topquadrant.com?utm_medium=email_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 topbraid-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/d09560003be84c72843c074780bf136e%40tno.nl.

Re: [topbraid-users] owl restrictions for individuals?

2021-10-13 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Thx david, much appreciated
I will experiment both owa owl and cwa shacl variants. Lets see if i can bring 
the pattern correctly to shacl first...
The results will indeed help us to decide
Gr michel


Op 13 okt. 2021 15:04 schreef David Price :
Hi Michel,

A final question … Have you run any OWL reasoner over this and produced any 
inconsistency e.g. in the case of 301 members of your Container saying only 300 
are allowed?

I’m not sure the “semantics” you think exist in this setup are actually there. 
Maybe I’m wrong as I’ve not tried it, but it looks questionable to me and 
actually using a tool such as a DL reasoner is the only way to be sure.  Does 
it at least not complain about these structures as it’s possible the customers 
of your ontology might use these tools.  FWIW I’ve not used any OWL Full 
reasoners so not sure how you’d test what you propose otherwise.

Also, as always note that OWL is OWA so missing data such as min card = 1 
cannot not be reported as an error.

Anyway, in answer to your “Would that be possible within TBC/EDG?":

TBC will probably let you view that structure but not 100% sure the form-based 
editing supports it. I did not try it myself.

EDG = not out-of-the-box but perhaps with some configuration. The EDG UI is 
driven by SHACL and the out-of-the-box OWL2SHACL feature does not cover the 
restriction structures you sent. It’s not hard to extend the OWL2SHACL within 
EDG so you could add whatever SHACL generation you wanted to see appear taking 
that OWL structure as input.  EDG 7.1 will support the SHACL qualified value 
shapes and it does report violations … I’ve actually tested that and the CWA 
helps make that so.

Cheers,
David

On 13 Oct 2021, at 13:00, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Hi David

Thx for your view.

Personally I think the rdfs containers captures at least some generic 
“grouping” semantics.
I would not like to redefine that myself (own group classes, member relations 
etc.).

On the other hand we might misuse this way a mechanism meant for explicit 
grouping for implicit grouping.

In any case the practical need is really there in asset mngt. People do not 
want to model (in their view) all the details from others.
In the example: they want to be able to model the groups of things having 
typical properties and the group having properties like an amount of members, 
total cost, etc. without the need to be able to explicitly point to the members.

In that sense our pattern could fulfil those needs: we have a group 
(container), we do not model explicit members, but add other properties to the 
group (like total cost) and are able to put restrictions on their members (like 
‘all should be yellow’). So we capture the typical member data in a restriction 
without having the (explicit) members themselves….that might be special too….

Anyway, we’ll consider, thx



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com> 
mailto:topbraid-users@googlegroups.com>> On 
Behalf Of David Price
Sent: Monday, October 11, 2021 5:34 PM
To: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com>
Subject: Re: [topbraid-users] owl restrictions for individuals?

The following is just my opinion:

RDFS collections have zero semantics, so using them for a purpose like this 
sounds like a bad idea. I have never used them in any ontology for any customer.

Calling something an “implicit group” and then trying to use semantics to 
define it does not make any sense to me. So, it’s hard to really understand 
your requirements, but if there is a need to “group” things then :

- perhaps make a class called Groups and make instances of that class be 
your groups. Then a simple object property member ofGroup can relate any 
instance to that group.
- a second approach is to define a datatype property but give it anyURI as its 
datatype. This is often how models relate to external reference data libraries 
not actually imported into the current graph - i.e. they have a property called 
something like “external classification” with a URI value that usually 
dereferences to something in a giant online RDL.

Both of are easy in OWL and SHACL.

Cheers,
David

On 11 Oct 2021, at 15:46,

Re: [topbraid-users] Better formulated potential sh:declare issues

2021-09-28 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Dear David
Please reread our issues.
This is exactly the point in our two subissues.

Issue1...recommended does not mean obliged. It also says optional owl:Ontology 
in the spec.
But indeed metalanguage is much stronger ... domain is owl:Ontology...

Issue 2
The file attached delivers rule results
If modelled the strict way...it does not


Thx Michel


Op 28 sep. 2021 19:38 schreef David Price :
Hi Michel,

I did not test anything but it looks to me like you’re having problems reading 
the W3C spec. I see this in your file:

rdf:
  sh:declare [
  sh:namespace "http://www.w3.org/1999/02/22-rdf-syntax-ns#"^^xsd:anyURI ;
  sh:prefix "rdf" ;
] ;
.

when the spec clearly says “The recommended subject for values of sh:declare is 
the IRI of the named graph containing the shapes that use the prefixes."

rdf: graph does not contain any shapes.

I expoect rdf: above should instead be

<https://w3id.org/sainput/owl/def>
  sh:declare [
  sh:namespace "http://www.w3.org/1999/02/22-rdf-syntax-ns#"^^xsd:anyURI ;
  sh:prefix "rdf" ;
] ;
.

Cheers,
David

P.S. If you have an issue with a W3C spec, please report it to the W3C rather 
than the TB user forum.


On 28 Sep 2021, at 16:12, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Together with our partner, BIM-Connected, Miltos Gatzios, we tried to better 
formulate the actual issue we see with sh:declare.

Issue 1 (not tbc issue, but general shacl issue)

Metalanguage (https://www.w3.org/ns/shacl.ttl):

sh:declare
a rdf:Property ;
rdfs:label "declare"@en ;
rdfs:comment "Links a resource with its namespace prefix 
declarations."@en<mailto:%22Links%20a%20resource%20with%20its%20namespace%20prefix%20declarations.%22@en>
 ;
rdfs:domain owl:Ontology ;
rdfs:range sh:PrefixDeclaration ;
rdfs:isDefinedBy sh: .

Specification (Shapes Constraint Language (SHACL) 
(w3.org)<https://www.w3.org/TR/shacl/#sparql-prefixes>):

“ The recommended subject<https://www.w3.org/TR/shacl/#dfn-subject> for values 
of sh:declare is the IRI of the named graph containing the shapes that use the 
prefixes. These IRIs are often declared as an instance of owl:Ontology, but 
this is not required.”


So the spec is flexible but the metalanguage makes a choice that it actually IS 
the named graph using the prefixes AND that it IS at an instance of 
owl:Ontology.

Issue 2 (the actual tbc/edg issue)

The implementation in tbc/edg seems to use the more strict way as recommended 
(we assume since that sh name space is used).
But that one seems not to work while the flexible way DOES seem to work …

Greetings, Michel

Ps
Attached the file where the shacl-rule does work (but we think now all prefixes 
become of type owl:Ontology…)
In case the declare’s are all attached to sainput: (the graph/ontology-prefix), 
the rule does not result in results.




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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/fd20239d403743a8a9aa80d4e96828ef%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/fd20239d403743a8a9aa80d4e96828ef%40tno.nl?utm_medium=email_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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/B62F7DC9-15DC-4F01-B91D-2D569505A82C%40topquadrant.com<https://groups.google.com/d/msgid/topbraid-users/B62F7DC9-15DC-4F01-B91D-2D569505A82C%40topquadrant.com?utm_medium=email_source=footer>.

-- 
You received this message because you are subscribed to the Google Groups 
"TopBraid Suite User

Re: [topbraid-users] Better formulated potential sh:declare issues

2021-09-28 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Wrt your ps

I think it is quite obvious that I mention this issue 1 here since it is so 
much related to the actual tbc issue being issue 2.

Op 28 sep. 2021 19:38 schreef David Price :
Hi Michel,

I did not test anything but it looks to me like you’re having problems reading 
the W3C spec. I see this in your file:

rdf:
  sh:declare [
  sh:namespace "http://www.w3.org/1999/02/22-rdf-syntax-ns#"^^xsd:anyURI ;
  sh:prefix "rdf" ;
] ;
.

when the spec clearly says “The recommended subject for values of sh:declare is 
the IRI of the named graph containing the shapes that use the prefixes."

rdf: graph does not contain any shapes.

I expoect rdf: above should instead be

<https://w3id.org/sainput/owl/def>
  sh:declare [
  sh:namespace "http://www.w3.org/1999/02/22-rdf-syntax-ns#"^^xsd:anyURI ;
  sh:prefix "rdf" ;
] ;
.

Cheers,
David

P.S. If you have an issue with a W3C spec, please report it to the W3C rather 
than the TB user forum.


On 28 Sep 2021, at 16:12, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Together with our partner, BIM-Connected, Miltos Gatzios, we tried to better 
formulate the actual issue we see with sh:declare.

Issue 1 (not tbc issue, but general shacl issue)

Metalanguage (https://www.w3.org/ns/shacl.ttl):

sh:declare
a rdf:Property ;
rdfs:label "declare"@en ;
rdfs:comment "Links a resource with its namespace prefix 
declarations."@en<mailto:%22Links%20a%20resource%20with%20its%20namespace%20prefix%20declarations.%22@en>
 ;
rdfs:domain owl:Ontology ;
rdfs:range sh:PrefixDeclaration ;
rdfs:isDefinedBy sh: .

Specification (Shapes Constraint Language (SHACL) 
(w3.org)<https://www.w3.org/TR/shacl/#sparql-prefixes>):

“ The recommended subject<https://www.w3.org/TR/shacl/#dfn-subject> for values 
of sh:declare is the IRI of the named graph containing the shapes that use the 
prefixes. These IRIs are often declared as an instance of owl:Ontology, but 
this is not required.”


So the spec is flexible but the metalanguage makes a choice that it actually IS 
the named graph using the prefixes AND that it IS at an instance of 
owl:Ontology.

Issue 2 (the actual tbc/edg issue)

The implementation in tbc/edg seems to use the more strict way as recommended 
(we assume since that sh name space is used).
But that one seems not to work while the flexible way DOES seem to work …

Greetings, Michel

Ps
Attached the file where the shacl-rule does work (but we think now all prefixes 
become of type owl:Ontology…)
In case the declare’s are all attached to sainput: (the graph/ontology-prefix), 
the rule does not result in results.




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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/fd20239d403743a8a9aa80d4e96828ef%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/fd20239d403743a8a9aa80d4e96828ef%40tno.nl?utm_medium=email_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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/B62F7DC9-15DC-4F01-B91D-2D569505A82C%40topquadrant.com<https://groups.google.com/d/msgid/topbraid-users/B62F7DC9-15DC-4F01-B91D-2D569505A82C%40topquadrant.com?utm_medium=email_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 topbraid-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/3e3294b8-6744-41b9-8586-fc9c2ee04548%40email.android.com.

[topbraid-users] Better formulated potential sh:declare issues

2021-09-28 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Together with our partner, BIM-Connected, Miltos Gatzios, we tried to better
formulate the actual issue we see with sh:declare.

Issue 1 (not tbc issue, but general shacl issue)

Metalanguage (https://www.w3.org/ns/shacl.ttl):

sh:declare
a rdf:Property ;
rdfs:label "declare"@en ;
rdfs:comment "Links a resource with its namespace prefix
declarations."@en
;
rdfs:domain owl:Ontology ;
rdfs:range sh:PrefixDeclaration ;
rdfs:isDefinedBy sh: .

Specification (Shapes Constraint Language (SHACL)
(w3.org)):

" The recommended subject for values
of sh:declare is the IRI of the named graph containing the shapes that use the
prefixes. These IRIs are often declared as an instance of owl:Ontology, but
this is not required."

So the spec is flexible but the metalanguage makes a choice that it actually IS
the named graph using the prefixes AND that it IS at an instance of
owl:Ontology.

Issue 2 (the actual tbc/edg issue)

The implementation in tbc/edg seems to use the more strict way as recommended
(we assume since that sh name space is used).
But that one seems not to work while the flexible way DOES seem to work ...

Greetings, Michel

Ps
Attached the file where the shacl-rule does work (but we think now all prefixes
become of type owl:Ontology...)
In case the declare's are all attached to sainput: (the graph/ontology-prefix),
the rule does not result in results.

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 michel.bo...@tno.nl

Location

[cid:image001.gif@01D7B48C.0D3EF590]

--
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/fd20239d403743a8a9aa80d4e96828ef%40tno.nl.

sainput.ttl
Description: sainput.ttl

Re: [topbraid-users] Better formulated potential sh:declare issues

2021-09-28 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Hi David

Miltos cracked my problem finally based on your example.

1. The shacl issue1 wrt domain is still there but lets forget...lets assume 
domain should be always ontology.

2. Issue2 was never in the sh:declare

3. It was in the prefixes that should have target owl ontology hence base uri 
not name space uri

4. In many examples in spec etc no problem where often base uri == ns uri
5. But not in our case!
6. I used ns uri but should be different base uri including owl fragment etc. 
So i should write full uri like you did...not the prefix only valid for ns uri 
here.

Sigh...thx for your patience as usual, greetings and thx michel/miltos

Op 28 sep. 2021 21:47 schreef David Price :
Hi Michel,

I did the following from your example but following the W3C spec and it works 
fine in Composer:

<https://w3id.org/sainput/owl/def>
  sh:declare [
  sh:namespace "http://www.w3.org/1999/02/22-rdf-syntax-ns#"^^xsd:anyURI ;
  sh:prefix "rdf" ;
] ;
  sh:declare [
  sh:namespace "https://w3id.org/sa/def#"^^xsd:anyURI ;
  sh:prefix "sa" ;
] ;
  sh:declare [
  sh:namespace "https://w3id.org/sainput/def#"^^xsd:anyURI ;
  sh:prefix "sainput" ;
] ;
.
sainput:MonsterLaag
  a owl:Class ;
  a sh:NodeShape ;
  rdfs:label "MonsterLaag" ;
  sh:rule [
  a sh:SPARQLRule ;
  sh:construct """
   CONSTRUCT {
 ?project rdf:type sa:Project .
   }
   WHERE {
 ?this sainput:projectOmschrijving ?omschrijving .
 BIND (IRI (CONCAT (\"https://w3id.org/sa/def#\;, encode_for_uri 
(?omschrijving))) AS ?project) .
   }
   """ ;
  sh:prefixes <https://w3id.org/sainput/owl/def> ;
] ;
.


Please see SHACL spec

5.1 An Example SPARQL-based Constraint - see 
https://www.w3.org/TR/shacl/#sparql-constraints

and

5.2.1  https://www.w3.org/TR/shacl/#sparql-prefixes

Cheers,
David


On 28 Sep 2021, at 19:54, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Wrt your ps

I think it is quite obvious that I mention this issue 1 here since it is so 
much related to the actual tbc issue being issue 2.

Op 28 sep. 2021 19:38 schreef David Price 
mailto:dpr...@topquadrant.com>>:
Hi Michel,

I did not test anything but it looks to me like you’re having problems reading 
the W3C spec. I see this in your file:

rdf:
  sh:declare [
  sh:namespace "http://www.w3.org/1999/02/22-rdf-syntax-ns#"^^xsd:anyURI ;
  sh:prefix "rdf" ;
] ;
.

when the spec clearly says “The recommended subject for values of sh:declare is 
the IRI of the named graph containing the shapes that use the prefixes."

rdf: graph does not contain any shapes.

I expoect rdf: above should instead be

<https://w3id.org/sainput/owl/def>
  sh:declare [
  sh:namespace "http://www.w3.org/1999/02/22-rdf-syntax-ns#"^^xsd:anyURI ;
  sh:prefix "rdf" ;
    ] ;
.

Cheers,
David

P.S. If you have an issue with a W3C spec, please report it to the W3C rather 
than the TB user forum.


On 28 Sep 2021, at 16:12, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Together with our partner, BIM-Connected, Miltos Gatzios, we tried to better 
formulate the actual issue we see with sh:declare.

Issue 1 (not tbc issue, but general shacl issue)

Metalanguage (https://www.w3.org/ns/shacl.ttl):

sh:declare
a rdf:Property ;
rdfs:label "declare"@en ;
rdfs:comment "Links a resource with its namespace prefix 
declarations."@en<mailto:%22Links%20a%20resource%20with%20its%20namespace%20prefix%20declarations.%22@en>
 ;
rdfs:domain owl:Ontology ;
rdfs:range sh:PrefixDeclaration ;
rdfs:isDefinedBy sh: .

Specification (Shapes Constraint Language (SHACL) 
(w3.org)<https://www.w3.org/TR/shacl/#sparql-prefixes>):

“ The recommended subject<https://www.w3.org/TR/shacl/#dfn-subject> for values 
of sh:declare is the IRI of the named graph containing the shapes that use the 
prefixes. These IRIs are often declared as an instance of owl:Ontology, but 
this is not required.”


So the spec is flexible but the metalanguage makes a choice that it actually IS 
the named graph using the prefixes AND that it IS at an instance of 
owl:Ontology.

Issue 2 (the actual tbc/edg issue)

The implementation in tbc/edg seems to use the more strict way as recommended 
(we assume since that sh name space is used).
But that one seems not to work while the flexible way DOES seem to work …

Greetings, Michel

Ps
Attached the file where the shacl-rule does work (but we think now all prefixes 
become of type owl:Ontology…)
In case the declare’s are all attached to sainput: (the graph/ontology-prefix), 
the rule does not result in results.




Dr. ir. H.M. (Michel) Bohms
Scienti

Re: [topbraid-users] Better formulated potential sh:declare issues

2021-09-28 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Hi David
This did not work for me earlier starting the whole issue but i will retry 
again tomorrow.

The spec I know and copied earlier.
The issue is that in that paragraph ...the link you copy below...it says 
"recommended" and "optional" where looking at the rdfs def of sh:declare it is 
much stronger since the domain there specifies owl:Ontology.

So to be consistent the spec should say something like..."the declare shall 
always be for an ontology graph".

Anyway that is a shacl issue indeed...

I will focus first on the second issuelet you know outcome...

Thx michel


Op 28 sep. 2021 21:47 schreef David Price :
Hi Michel,

I did the following from your example but following the W3C spec and it works 
fine in Composer:

<https://w3id.org/sainput/owl/def>
  sh:declare [
  sh:namespace "http://www.w3.org/1999/02/22-rdf-syntax-ns#"^^xsd:anyURI ;
  sh:prefix "rdf" ;
] ;
  sh:declare [
  sh:namespace "https://w3id.org/sa/def#"^^xsd:anyURI ;
  sh:prefix "sa" ;
] ;
  sh:declare [
  sh:namespace "https://w3id.org/sainput/def#"^^xsd:anyURI ;
  sh:prefix "sainput" ;
] ;
.
sainput:MonsterLaag
  a owl:Class ;
  a sh:NodeShape ;
  rdfs:label "MonsterLaag" ;
  sh:rule [
  a sh:SPARQLRule ;
  sh:construct """
   CONSTRUCT {
 ?project rdf:type sa:Project .
   }
   WHERE {
 ?this sainput:projectOmschrijving ?omschrijving .
 BIND (IRI (CONCAT (\"https://w3id.org/sa/def#\;, encode_for_uri 
(?omschrijving))) AS ?project) .
   }
   """ ;
  sh:prefixes <https://w3id.org/sainput/owl/def> ;
] ;
.


Please see SHACL spec

5.1 An Example SPARQL-based Constraint - see 
https://www.w3.org/TR/shacl/#sparql-constraints

and

5.2.1  https://www.w3.org/TR/shacl/#sparql-prefixes

Cheers,
David


On 28 Sep 2021, at 19:54, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Wrt your ps

I think it is quite obvious that I mention this issue 1 here since it is so 
much related to the actual tbc issue being issue 2.

Op 28 sep. 2021 19:38 schreef David Price 
mailto:dpr...@topquadrant.com>>:
Hi Michel,

I did not test anything but it looks to me like you’re having problems reading 
the W3C spec. I see this in your file:

rdf:
  sh:declare [
  sh:namespace "http://www.w3.org/1999/02/22-rdf-syntax-ns#"^^xsd:anyURI ;
  sh:prefix "rdf" ;
] ;
.

when the spec clearly says “The recommended subject for values of sh:declare is 
the IRI of the named graph containing the shapes that use the prefixes."

rdf: graph does not contain any shapes.

I expoect rdf: above should instead be

<https://w3id.org/sainput/owl/def>
  sh:declare [
  sh:namespace "http://www.w3.org/1999/02/22-rdf-syntax-ns#"^^xsd:anyURI ;
      sh:prefix "rdf" ;
] ;
.

Cheers,
David

P.S. If you have an issue with a W3C spec, please report it to the W3C rather 
than the TB user forum.


On 28 Sep 2021, at 16:12, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Together with our partner, BIM-Connected, Miltos Gatzios, we tried to better 
formulate the actual issue we see with sh:declare.

Issue 1 (not tbc issue, but general shacl issue)

Metalanguage (https://www.w3.org/ns/shacl.ttl):

sh:declare
a rdf:Property ;
rdfs:label "declare"@en ;
rdfs:comment "Links a resource with its namespace prefix 
declarations."@en<mailto:%22Links%20a%20resource%20with%20its%20namespace%20prefix%20declarations.%22@en>
 ;
rdfs:domain owl:Ontology ;
rdfs:range sh:PrefixDeclaration ;
rdfs:isDefinedBy sh: .

Specification (Shapes Constraint Language (SHACL) 
(w3.org)<https://www.w3.org/TR/shacl/#sparql-prefixes>):

“ The recommended subject<https://www.w3.org/TR/shacl/#dfn-subject> for values 
of sh:declare is the IRI of the named graph containing the shapes that use the 
prefixes. These IRIs are often declared as an instance of owl:Ontology, but 
this is not required.”


So the spec is flexible but the metalanguage makes a choice that it actually IS 
the named graph using the prefixes AND that it IS at an instance of 
owl:Ontology.

Issue 2 (the actual tbc/edg issue)

The implementation in tbc/edg seems to use the more strict way as recommended 
(we assume since that sh name space is used).
But that one seems not to work while the flexible way DOES seem to work …

Greetings, Michel

Ps
Attached the file where the shacl-rule does work (but we think now all prefixes 
become of type owl:Ontology…)
In case the declare’s are all attached to sainput: (the graph/ontology-prefix), 
the rule does not result in results.




Dr. ir. H.M. (Michel) Bohms
Scientist Specialist
Structural Reliability

T +3

[topbraid-users] edg undo transform?

2021-09-30 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Is there any option in EDG to undo a Transform?
When experimenting in TBC you can just infer without actual assertion.
In EDG directly asserted.

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 michel.bo...@tno.nl

Location



[cid:image001.gif@01D7B5F2.48A6C100]

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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/384c3f80515b462baf457bbd44c732ad%40tno.nl.

[topbraid-users] edg class tree

2021-09-30 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Why are classes shown in tree AND in the list:
[cid:image004.png@01D7B5EF.731387F0]
Activity as subclass of Entity is also shown in the list.

Same in TBC only shows tree:
[cid:image005.png@01D7B5EF.731387F0]

Is that an edg setting?

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 michel.bo...@tno.nl

Location



[cid:image006.gif@01D7B5EF.731387F0]

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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/ad24c9e1defc40ecb58e599e0f206c68%40tno.nl.

RE: [topbraid-users] edg class tree

2021-09-30 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Ahhh
I now see, the owl:Thing seems automatically added when importing to edg?
Can that be switched of?



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D7B5FA.13FDF1A0]<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: topbraid-users@googlegroups.com  On 
Behalf Of David Price
Sent: Thursday, September 30, 2021 12:47 PM
To: topbraid-users@googlegroups.com
Subject: Re: [topbraid-users] edg class tree

The tree is showing exactly what the source code says:

[image004.png]


Activity is a subclass of Thing too, so the EDG UI shows that - it’s case of 
multiple superclasses. Remove subClassOf Thing if that’s not desired,

Cheers,
David


On 30 Sep 2021, at 10:36, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Why are classes shown in tree AND in the list:

Activity as subclass of Entity is also shown in the list.

Same in TBC only shows tree:


Is that an edg setting?

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/ad24c9e1defc40ecb58e599e0f206c68%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/ad24c9e1defc40ecb58e599e0f206c68%40tno.nl?utm_medium=email_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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/6E42A573-4721-4C3F-8A5C-9B400A456E75%40topquadrant.com<https://groups.google.com/d/msgid/topbraid-users/6E42A573-4721-4C3F-8A5C-9B400A456E75%40topquadrant.com?utm_medium=email_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 topbraid-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/c19e4f6713ae43efb67bd4c208a6a228%40tno.nl.

RE: [topbraid-users] edg class tree

2021-09-30 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Ok thx
I was a bit scared because of the for manager’s only warning there 



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



[cid:image001.gif@01D7B5FA.D333D580]<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: topbraid-users@googlegroups.com  On 
Behalf Of David Price
Sent: Thursday, September 30, 2021 12:55 PM
To: topbraid-users@googlegroups.com
Subject: Re: [topbraid-users] edg class tree

Import RDF has a streaming option if you look under Imports.

Cheers,
David


On 30 Sep 2021, at 11:52, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Ahhh
I now see, the owl:Thing seems automatically added when importing to edg?
Can that be switched of?



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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com> 
mailto:topbraid-users@googlegroups.com>> On 
Behalf Of David Price
Sent: Thursday, September 30, 2021 12:47 PM
To: topbraid-users@googlegroups.com<mailto:topbraid-users@googlegroups.com>
Subject: Re: [topbraid-users] edg class tree

The tree is showing exactly what the source code says:




Activity is a subclass of Thing too, so the EDG UI shows that - it’s case of 
multiple superclasses. Remove subClassOf Thing if that’s not desired,

Cheers,
David



On 30 Sep 2021, at 10:36, 'Bohms, H.M. (Michel)' via TopBraid Suite Users 
mailto:topbraid-users@googlegroups.com>> wrote:

Why are classes shown in tree AND in the list:

Activity as subclass of Entity is also shown in the list.

Same in TBC only shows tree:


Is that an edg setting?

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 michel.bo...@tno.nl<mailto:michel.bo...@tno.nl>

Location<http://www.tno.nl/locations/DTS>



<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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/ad24c9e1defc40ecb58e599e0f206c68%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/ad24c9e1defc40ecb58e599e0f206c68%40tno.nl?utm_medium=email_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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/6E42A573-4721-4C3F-8A5C-9B400A456E75%40topquadrant.com<https://groups.google.com/d/msgid/topbraid-users/6E42A573-4721-4C3F-8A5C-9B400A456E75%40topquadrant.com?utm_medium=email_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 
topbraid-users+unsubscr...@googlegroups.com<mailto:topbraid-users+unsubscr...@googlegroups.com

[topbraid-users] multi-sheet import by pattern

2021-10-07 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Is it possible to do a multi-sheet import?

[cid:image004.png@01D7BB6D.89666EE0]
Leaving index open delivers a java-level error.(which is strange since its 
says ' optional' )

Maybe something like "1-2"?

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 michel.bo...@tno.nl

Location



[cid:image005.gif@01D7BB6D.89666EE0]

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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/398bb3ac997d4f988467b89b049d9344%40tno.nl.

[topbraid-users] edg import xlsx

2021-09-22 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users

Trying to find my way in edg wrt the excel stuff

I imported by target (multiclass) ontology and now wanted to import the one 
table sheet:
[cid:image001.png@01D7AFA7.5FD8EC50]

Why can I not click " Finish"?

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 michel.bo...@tno.nl

Location



[cid:image002.gif@01D7AFA7.5FD8EC50]

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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/a52355aeac7442a99686b4c12628cf14%40tno.nl.

< 1 2 3 4 5 >

301 - 400 of 484 matches

Mail list logo