-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is dpv:Relation
a Class or a Property?
#112
Comments
Hi.
Regarding its modelling: Tbh, I don't like the messy implementation with 3 different semantics because implementation is a pain, but if it helps people fit DPV into their implementations then it is needed. The DPV modelling concepts (concept, relation) help produce the relevant RDFS/OWL class and property declarations in the other two semantic implementations. A solution to keep it clean might be to get rid of all "DPV" modelling concepts and just use SKOS. The additional value of separating DPV stuff from other SKOS-defined information doesn't seem to be worth the effort. |
On further thought, I think it would be best to drop this DPV defined concept modelling altogether, make RDFS+SKOS the default semantic implementation, and OWL as an alternative implementation. |
Hiya Harsh,
>> *I think it would be best to drop this DPV defined concept modelling
altogether*
Yeah, I totally agree.
>> *make RDFS+SKOS the default semantic implementation*
Yep, I totally agree with this too!
Cheers,
Pat.
…On Tue, Sep 19, 2023 at 10:38 AM Harshvardhan Pandit < ***@***.***> wrote:
On further thought, I think it would be best to drop this DPV defined
concept modelling altogether, make RDFS+SKOS the default semantic
implementation, and OWL as an alternative implementation.
—
Reply to this email directly, view it on GitHub
<#112 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHKXJLIIFMSF6NOUXO5I4LX3FKZBANCNFSM6AAAAAA45YMOQY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Thanks. I have sent an email for the change to the DPV's mailing list: https://lists.w3.org/Archives/Public/public-dpvcg/2023Sep/0024.html. Let's keep the issue open for discussion for now, and I will open a new issue for using RDFS+SKOS as default serialisation if the proposal is to be implemented. |
RDFS+SKOS is the default model now with OWL as an additional alternative serialisation. |
I notice that
dpv:Relation
is currently defined as:...but since it's a Property (specifically a
rdfs:subPropertyOf
ofskos:semanticRelation
), and not a Class, should it not be nameddpv:hasRelation
(as all properties should start with a lowercase character)...?But then I notice that it's used as the
rdf:type
of 91 terms in DPV - meaning it's considered a Class, e.g.,:Hence my confusion. So is
dpv:Relation
really intended to be a Property or a Class?(Note: The use of
dpv:isSubTypeOf dpv:hasRepresentative
above also appears strange (i.e., a Property being a sub-Class/Type of another Property?). Should DPV define a new propertydpv:isSubPropertyOf
, and use that in cases like this...?)(Also note: tiny typo in the
skos:definition
value above too - i.e., 'Specifices' should be 'Specifies'.)The text was updated successfully, but these errors were encountered: