- From: Fadi Maali <fadi.maali@deri.org>
- Date: Wed, 30 Oct 2013 16:43:19 +1100
- To: Johan De Smedt <johan.de-smedt@tenforce.com>
- Cc: <public-gld-comments@w3.org>
Hello Johan, Thanks for the following up. Some comments inline... On 29 Oct 2013, at 16:58, Johan De Smedt <johan.de-smedt@tenforce.com> wrote: > Hi Sandro, Fadi, > > 1) Thanks for following up. > > The reply classifies our request as being out of scope of DCAT - so any application seeing the use of declaring a conforming standard as relevant will require a custom extension. This could be done by: > - an extra custom property, > - a void property in case the set is available as RDF, > - using a dedicated theme, > - … > Many ways to get around. > > > 2) In case there is still room for amending some text, I would suggest: > a) Replace all references to the deprecated vcard:VCard by the replacing vcard:Kind or any of its sub-classes. +1 thanks for pointing that out. The two classes (card:VCard and card:Kind) are equivalent but as you pointed out card:VCard is deprecated. > b) To make the usage note on dcat:mediaType more explicit. > Add to usage note: “Best practice for retrieving a data using dcat:downloadURL is to set the HTTP header ‘Accept’ to a value of dcat:mediaType.” While this sounds right to be recommended, my personal opinion is that the vocabulary specification should not include this recommendation as it relates to the deployment… thoughts on this? > c) Add note that dcat:accessURL and dcat:landingPage are of type html or xhtml dcat:accessURL is also used when the publisher knows that the URL can be used to access the dataset but has no information what exactly the result of accessing the URL. Therefore it is not always HTML... > d) It is not clear how a multilingual dataset can be registered that has different distributions per language > either -d.1- using a different dcat:downloadURL > With the current model, this situation can be handled unambiguously by having multiple (further unrelated) data sets. > If this is considered best practice, this could be clarified in a usage note on dataset dcat:language > or -d.2- using the same downloadURL but with different values for the HTTP header Accept-Language > With the current model this could be handled by adding a usage note on the dataset dct:language and on the distribution dcat:downloadURL What about different distributions (each with its own downloadURL) for the same dataset? Regards, Fadi Maali > Sorry for these late results on an implementation exercise we made with the EU Publication Office CELLAR platform. > > Kind Regards, > > Johan De Smedt > Chief Technology Officer > > mail: johan.de-smedt@tenforce.com > mobile: +32 477 475934 > <image002.jpg>
Received on Wednesday, 30 October 2013 05:43:49 UTC