Thx will adapt (import out at rdfs & copy preflabel/definition also to rdfs)
isDefinedBy can as I see the definition also be used for elements of ontologies
(domain and ranges are resource in general). It feels a bit more semantic then
seeAlso… 😊
but now that part of that definition is copied to
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 isDefinedB
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 specific
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):
s
> On 29 Jun 2021, at 08:46, 'Bohms, H.M. (Michel)' via TopBraid Suite Users
> 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 happenin
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 s
