- From: Simon Cox via GitHub <sysbot+gh@w3.org>
- Date: Thu, 17 Jan 2019 04:08:20 +0000
- To: public-dxwg-wg@w3.org
The point about a DDS is that its functionality is limited to enabling download of 'existing' discrete datasets, or extracts/subsets of them. It doesn't usually do any other processing, such as re-sampling or interpolation or combination (though it is easy to imagine specializations that could). This is such a common case of DS that we thought it merited its own class on that ground alone. Would the addition of the word 'existing' in the definition do the trick for you? In the majority of cases, a DDS is bound to one or more known datasets. However, there are federated services for which the served datasets are only known transitively, though the operation signature is otherwise that of a 'normal' DDS. I suppose we could put a cardinality constraint that there is at least one `dcat:servesDataset`. Yes - the DiscoveryService had been included in earlier drafts. In today's DCAT meeting we decided to drop it, but there were still some remnants in the document - I think I've removed them all now. -- GitHub Notification of comment by dr-shorthair Please view or discuss this issue at https://github.com/w3c/dxwg/issues/432#issuecomment-455035562 using your GitHub account
Received on Thursday, 17 January 2019 04:08:22 UTC