- From: Johan De Smedt <johan.de-smedt@tenforce.com>
- Date: Tue, 29 Oct 2013 06:58:56 +0100
- To: <public-gld-comments@w3.org>
- Message-ID: <011201ced46b$f48a8130$dd9f8390$@tenforce.com>
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.
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.”
c) Add note that dcat:accessURL and dcat:landingPage are of type html or xhtml
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
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: <mailto:johan.de-smedt@tenforce.com> johan.de-smedt@tenforce.com
mobile: +32 477 475934
mail-TenForce
Attachments
- image/jpeg attachment: image002.jpg
Received on Tuesday, 29 October 2013 05:59:28 UTC