Re: [dxwg] Extending DCAT for services

1. I opened a separate issue to discuss the type and range of *URL properties #249 - let's have the conversation there. 
2. `DataService` is probably the most conservative option. Can we accept it for now and consider again later?

I also moved all the classes and properties that were already marked 'deprecated' in DCAT-2014 into the RDF document dcat-2014.ttl, where we are gathering all the axioms removed in the DCAT-rev process. That allows the dcat.ttl document to reflect the current state without any noise. 

I'm concerned that merging becomes difficult if we have too many branches open. This one covers what is likely to be the main refactor that we will make in this DCAT revision. It introduces the class `dcat:Resource` interpolated above `dcat:Dataset`, and also includes `dcat:DataService` and sub-classes, and a small number of new properties - `dcat:service`, `dcat:catalog`, `dcat:endpointURL`, `dcat:endpointDescription`, `dcat:accessService` and  `dcat:servesDataset`. The overall shape of these has been accepted by the team, with the explicit understanding that we can and should tidy up details later. My view is that we need to move this material into the gh-branch now so that we can get the necessary community scrutiny of the editor's draft. Nothing is final until we publish a rec in a year or so, but it would be helpful to expose this material. 

GitHub Notification of comment by dr-shorthair
Please view or discuss this issue at using your GitHub account

Received on Wednesday, 6 June 2018 02:48:01 UTC