- From: Andrea Perego via GitHub <sysbot+gh@w3.org>
- Date: Tue, 05 Jun 2018 12:40:46 +0000
- To: public-dxwg-wg@w3.org
@dr-shorthair said: > 1. I'm OK calling it `endpointURL` _provided_ that for all the properties `*URL`, they are corrected to owl:DatatypeProperty with range xsd:anyURI I have to disagree here. It would break existing implementations, and I don't think we have any use cases supporting this revision. Moreover, having them as object properties would enable cross-linking of related resources (as services and distributions). Using "URL" in the property name is consistent with similar DCAT properties (`dcat:accessURL` and `dcat:downloadURL`, which are object properties), and DCAT users will recognise the pattern. So, I don't see the need of requiring a term to be a datatype property just because it includes "URL" in its name. > 2. Service was renamed DataService following the discussion in the F2F - @kcoyle seemed to feel quite strongly about that, and also with @danbri in the room we wanted to be clear that we were talking about web- and data-oriented services not hairdressers. I tend to agree that we should not allow any type of service, but I don't think we have currently a clear idea of what should be in or out. An option, already discussed, and recently suggested by @pwin [in his mail](http://lists.w3.org/Archives/Public/public-dxwg-wg/2018Jun/0058.html), is to say that the scope is limited to online (Web?) services. On the other hand, we have the example of the Core Public Service vocabulary, which is used to describe a (not necessarily online) service delivered by a public institution, and such descriptions are meant to be available in catalogues. I cannot find a strong case to say that we cannot use DCAT for describing these catalogues. -- GitHub Notification of comment by andrea-perego Please view or discuss this issue at https://github.com/w3c/dxwg/pull/241#issuecomment-394694028 using your GitHub account
Received on Tuesday, 5 June 2018 12:40:50 UTC