Author: GDI-DE AK Metadaten (betriff das ganze Dokument) Das SAGA-Dokument besagt in Kapitel 4.3, dass rdf-Metadaten und Dublin Core (DCES) zu verwenden sind. Component Documentation Category task
eGovernment
Last activity: 27/07/2017, 16:16
i18n of metadata
As noted in https://joinup.ec.europa.eu/asset/ogd2_0/issue/cardinality-title-and-beschreibung#comment-18596 the specification draft does not support i18n of metadata: No Sorbian metadata! It is not even possible to have English and German at the same time. Worse: the language of a metadata string is unknown! Please replace the draft by DCAT-AP which supports i18n. Component Documentation Category bug
eGovernment
Last activity: 27/07/2017, 16:14
Missing size indicator for resources
There is no field for the size of the resource. Where it is not always appropriate, in many cases this could be very helpful. So I would propose an optional field similar to dcat:byteSize of DCAT-AP. Component Code Category improvement
eGovernment
Last activity: 27/07/2017, 16:16
Cardinality of 'title' and 'beschreibung'
What is the reason to allow more than one e.g. 'titel' and 'beschreibung'? If this for different languages this should be stated explicitly somewhere in the specification. Component Documentation Category improvement
eGovernment
Last activity: 25/07/2016, 10:09
Comment by "Some One"
This comment was posted https://joinup.ec.europa.eu/catalogue/distribution/specification-document-ogd-20-pdf#comment-18438 by "Some One" on June 14, 2016. Unfortunately the commenter did not create separate issues, but most of the listed issues meanwhile have there own formal issue: Just some thoughts: non international: introduces german terms (umlauts!) and make it impossible to recycle the definitions in an international way overengeniering: introduces a lot of namespaces (esp. in JSON schema) instead of relying on default primitive types. introduces helper classes instead of flat…
eGovernment
Last activity: 25/07/2016, 09:44
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 public (including reviewers of the specification). That makes it impossible to verify or evaluate the origin or validity of requirements and how features in the draft specification are linked to such requirements. Also other relevant documents of the "Fachgruppe" GovData relating to the draft seem to exist which were not made available. Component Documentation Category bug
eGovernment
Last activity: 27/07/2017, 16:05
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") for German or "hsb" for Upper Sorbian language (Sorbian is an official minority language spoken and written in a small part of Germany near Poland). Please use the IETF standard BCP47 for language tags instead. The main difference is that German is encoded "de" using ISO 639-1. Upper Sorbian is not contained in ISO 639-1 and therefore the encoding "hsb" is taken from ISO 639-2 in BCP47. 2. "Code…
eGovernment
Last activity: 27/07/2017, 16:10
Markup languages for freetext fields
It seems that the current draft of OGD-2.0 does not talk about the usage of markup languages for freetext fields at all. CKAN, for example, allows you to use Markdown for the descriptions of datasets, resources, etc. This is very useful, for example to add emphasis or links to such texts. However, although Markdown and other lightweight markup languages are designed to be human-readable in their plain text form readability benefits greatly from an appropriate rendering in HTML. For example, here is a plain text Markdown description of one of our own datasets: Die [Landesanstalt für Umwelt…
eGovernment
Last activity: 27/07/2017, 16:12
"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 subcategory belongs. I also question the concept of category plus subcategory due to the redundancy of the information (subcategory implies category). Using SKOS (as DCAT and DCAT-AP do) can help to solve this. Component Documentation Category bug
eGovernment
Last activity: 02/10/2017, 23:17
Rights Statement Nutzungsbestimmung
As in DCAT-AP the precise relation between the rights statement and the licence remains unclear. The ODI (https://theodi.org/guides/publishers-guide-to-the-open-data-rights-statement-vocabulary) explains the rights statement as a resource that describes the relationship between a dataset and its licence(s) , and which can also be used to describe additional contextual information that applies to the reuse of a dataset. While the description of a licence remains unchanged, no matter how it is used by an organisation when publishing data, the Rights Statement captures the context of the use of a…
To be interoperable with DCAT-AP MDR Frequency Named Authority List (http://publications.europa.eu/mdr/authority/frequency) should be used instead. Um mit DCAT-AP interoperabel zu sein sollte stattdessen die MDR Frequency Named Authority List (http://publications.europa.eu/mdr/authority/frequency) benutzt werden Component Documentation Category improvement
eGovernment
Last activity: 02/10/2017, 23:17
Clarify resource licensing
(This issue was raised during an OGD-2.0 workshop at the Innenministerium of Baden-Württemberg on 2016-06-29. I'm posting the results of its discussion here in a condensed form)
One of the reasons given for not using DCAT-AP is that DCAT-AP specifies the data's license on the resource level, whereas OGD-1.1 does it on the dataset level (see point 7 of comment #2 of this related issue). During the workshop mentioned above I asked why this would be a problem, since going from a license on dataset level to a license on resource level is easy: In my understanding, the dataset license already…