On 9/04/2021 6:31 pm, 'Bohms, H.M. (Michel)' via TopBraid Suite Users wrote:
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.
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 [email protected] <mailto:[email protected]>
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:* [email protected]
<[email protected]> *Namens *Holger Knublauch
*Verzonden:* dinsdag 6 april 2021 13:22
*Aan:* [email protected]
*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 <[email protected]
<mailto:[email protected]>> 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
<https://w3id.org/def/nen2660-rdfs>
But I got the comment that just:
# baseURI:https://w3id.org/def/nen2660 <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 [email protected] <mailto:[email protected]>
Location <http://www.tno.nl/locations/DTS>
<image001.gif> <http://www.tno.nl/>
This message may contain information that is not intended for you.
If you are not the addressee or if this message was sent to you by
mistake, you are requested to inform the sender and delete the
message. TNO accepts no liability for the content of this e-mail,
for the manner in which you use it and for damage of any kind
resulting from the risks inherent to the electronic transmission
of messages.
--
You received this message because you are subscribed to the Google
Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it,
send an email [email protected]
<mailto:[email protected]>.
To view this discussion on the web
visithttps://groups.google.com/d/msgid/topbraid-users/8c5728fd3b8b45cd8ca17055b8df9688%40tno.nl
<https://groups.google.com/d/msgid/topbraid-users/8c5728fd3b8b45cd8ca17055b8df9688%40tno.nl?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google
Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
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&utm_source=footer>.
--
You received this message because you are subscribed to the Google
Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/2d7063d8c78e4ceeacf219a6efcd5ae5%40tno.nl
<https://groups.google.com/d/msgid/topbraid-users/2d7063d8c78e4ceeacf219a6efcd5ae5%40tno.nl?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups "TopBraid
Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/88c0b9e2-43a1-8896-8014-eb9c6076748d%40topquadrant.com.
