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
Proposal for relaxing domain of dcat:contactPoint #95
Comments
Also, is the range right? While vcard:Kind is an RDF encoding of a commonly used contact data structure, there are other options ... |
I agree that the use of only vCard for contact information is too restrictive. If the range were :ContactInformation, vCard could be one possible expression of that class, while allowing other ways of specifying contact details. |
Proposal accepted https://www.w3.org/2018/02/07-dxwgdcat-minutes |
Document also updated. Resolved by #97 |
This proposal is about relaxing the domain of
dcat:contactPoint
, to allow its use not only for datasets (as it is in the current version of DCAT), but also for other resources (e.g., catalogues, catalogue records).This issue popped up during the development of GeoDCAT-AP, since all the agent roles (
dcat:contactPoint
included) supported in ISO 19115 can be specified for any resource.Besides this, the "contact point" is probably the most important role for data consumers, not only for datasets. For instance, for a
dcat:Catalog
it is possible to specify thedct:publisher
, but if I need to ask questions and/or report issues about the catalogue I need to get in touch with the publisher's dedicated contact point.The text was updated successfully, but these errors were encountered: