David James und Luigi Montanez haben auf dem im Blog der Sunlight Labs einen sehr interessanten Artikel über Datenkataloge geschrieben. Es geht dabei darum eine Empfehlung zu formulieren worauf bei Datenkatalogen für Regierungsdaten zu achten ist. Dabei haben sie die Beispiele data.gov, data.dc.gov, data.gov.uk und utah.gov/data nach den Kategorien “Resource-Oriented Architecture”, “Defining a Vocabulary” und “Formats” untersucht:
Drafting Guidelines for Government Data Catalogs
A major focus of the Sunlight Labs is to push government to publish its data online. In recent months, we’ve gained in-depth familiarity with government data catalogs through our work on the National Data Catalog. The most prominent example of a data catalog is data.gov. Since its launch last year, a handful of states and cities have followed suit with their own efforts. As more data catalogs come online, we want to make sure their contents are open and exchangeable. We want to determine how to best structure the data catalog itself, and we want to ensure that the metadata it contains — the data about the data — exists in the most accessible way possible.
Weiter unten formulieren sie einen ersten zusammenfassenden Vorschlag:
- Ensure that you have enough metadata to closely follow the vocabulary.
- If publishing the catalog as a website, use the Microformat on the data detail pages.
- If publishing an API, use XML or JSON in conjunction with Resource-Oriented principles.
- If publishing the data catalog as a bulk download, use XML, JSON, or CSV.
- To publish updates of entries in the catalog, use Atom.
Related posts:
No related posts.
