Closed riccardoAlbertoni closed 2 years ago
rdfs:member
is a pretty obscure element from RDFS.
In fact if you read the documentation it is not fully clear if it should be subclassed, and I'm not sure that I've seen it done anywhere else. for example skos:member
is not a sub-property.
Probably remove it.
@dr-shorthair said:
rdfs:member
is a pretty obscure element from RDFS. In fact if you read the documentation it is not fully clear if it should be subclassed, and I'm not sure that I've seen it done anywhere else. for exampleskos:member
is not a sub-property.Probably remove it.
I concur. Let's remove it.
I also agree with removing this restriction, note that there was a previous issue about relaxing the constraints on dcat:service
(https://github.com/w3c/dxwg/issues/1363) and there was also a suggestion (by @dr-shorthair ) on removing the subproperty constraint with rdfs:member
https://github.com/w3c/dxwg/issues/1363#issuecomment-844806375
Statements making dcat:catalog
, dcat:dataset
, and dcat:service
sub-properties of rdfs:member
have been removed via PR https://github.com/w3c/dxwg/pull/1482
I have noticed that
dcat:catalog
,dcat:service
, anddcat:dataset
are all defined as subproperties ofrdfs:member
in the TTL. The recently addeddcat:resource
which is the super-property of the above is not.Should we define
dcat:resource
subproperty ofrdfs:member
?rdfs:member
is never mentioned in the DCAT HTML, should we add it todcat:catalog
,dcat:service
, anddcat:dataset
anddcat:resource
or delete its occurences from the RDF?