[dxwg] cardinality constraint for dcat:endpointURL (restrictions in dcat.ttl which are not visible in html) (#1394)

bertvannuffelen has just created a new issue for https://github.com/w3c/dxwg:

== cardinality constraint for dcat:endpointURL (restrictions in dcat.ttl which are not visible in html) ==
The specification on dcat:endpointURL: https://www.w3.org/TR/2020/REC-vocab-dcat-2-20200204/#Property:data_service_endpoint_url does not provide an indication of a cardinality constraint.

However https://www.w3.org/ns/dcat2.ttl contains a maxCardinality constraint. 

What is here the expected behaviour? Adding constraints in the machine readable syntax should be best reflected in the html representation. 

Similary the following restriction for dcat:Catalog
```
  rdfs:subClassOf [
      a owl:Restriction ;
      owl:allValuesFrom dcat:Resource ;
      owl:onProperty dct:hasPart ;
    ] ;
```
If I am not mistaken that states that every dcat:Catalog is a dcat:Resource which has a dct:hasPart relation. 
I doubt this is the always the case.

The problem with these restrictions is that they are not visible. They are only discovered when people start reading the ttl file and interpreting the OWL statements. This adds a lot of conditionals in the interpretation of the DCAT specification. When discussing with others I am not sure if they take the html spec, the RDF ttl file or the OWL interpretation of the RDF ttl file as their interpretation of the DCAT specification.  

proposal: 
remove all restrictions from the dcat.ttl unless these are explicitely part of the html specification. 


Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1394 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 26 August 2021 13:29:59 UTC