Re: [dxwg] Create a use case that explains the meta modelling requirement for domain/range restrictions on the dcat:contactPoint & other DCAT properties

s/weaking/weakening/
s/a property a part of guidance/a property, some of the guidance/
s/compensated by apporpiate/compensated for by appropriate/

Since there is a UC draft, all I can think to do now is to expand it with examples as follows:

* demoing the use of `dcat:contactPoint` with a relaxed domain:
    * The use of `dcat:contactPoint` for a catalogue is obviously appropriate and given that there are many circumstances within which people would want to contact the catalog maintainers rather than the maintainers of a specific dataset. The data.gov.au catalog (a CKAN instance able to export DCAT) has a non-semantically-described web page "About" with "Contact Us" information including the main catalogue team email address data@digital.gov.au. This should be able to be represented, legally, as follows:

```
:Catalog_x a dcat:Catalog ;
    dct:title "data.gov.au" ;
    dcat:contactPoint <data@digital.gov.au>
.
```


-- 
GitHub Notification of comment by nicholascar
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/130#issuecomment-374158213 using your GitHub account

Received on Monday, 19 March 2018 09:58:43 UTC