Andreas Kuckartz

i18n of metadata

As noted in https://joinup.ec.europa.eu/asset/ogd2_0/issue/cardinality-title-and-be… the specification draft does not support i18n of metadata: No Sorbian metadata! It is not…

Comment by "Some One"

This comment was posted https://joinup.ec.europa.eu/catalogue/distribution/specification-docume… by "Some One" on June 14, 2016. Unfortunately the commenter did not create…

Transparency and requirements

The slides Deutschland auf dem Weg zum neuen Metadatenstandard by Christian Horn from June 16, 2016, indicate that there exists material regarding requirements which was not made available to the…

Language code

1. The proposed tag encoding of languages is not used in established web standards and therefore not technically compatible with them. ISO 639-2 consists of three letter codes such as "ger" (and "deu"…

"kategorie" versus "unterkategorie"

In the draft specification both "kategorie" and "unterkategorie" (subcategory) have a cardinality "0..*". That implies that when there is more than one category it is unknown to which of them a…

W3C Workshop regarding DCAT

A workshop regarding the future of DCAT has been announced by the W3C (30 November - 1 December, CWI, Amsterdam Science Park). The OGD2 project should provide input and take part in the discussions…

License restrictions / "Codelist of specific licenses"

An issue raised against DCAT-AP: Not existing vocabularies: 15: Codelist of specific licenses, as compiled by Govdata.de Raised in https://joinup.ec.europa.eu/discussion/dcat-ap#comment-18465…

Codelists of German Länder for DCAT

One alleged issue with DCAT was: Not existing vocabularies: 13: Codelist of German Länder ... Raised in comment https://joinup.ec.europa.eu/asset/ogd2_0/issue/dcat-ap#comment-18465 But even if no such…

Technical interoperability

The draft specification does not guarantee technical interoperability. A serialisation based on DCAT-AP (and therefore RDF) and JSON would help. This can be done using JSON-LD. Component Documentation…

Frequency / "AenderungshaeufigkeitCode" / ISO 19115 / ISO 8601

Instead of using terms from a German translation of ISO 19115 please consider technical compatibility using an international standard. Maybe a "temporal" property with ISO 8601 values is an…