I'm involved with a data collection and archiving project right now. Occasionally I'll get distracted with ideas like "Maybe I should make it compliant with Dublin Core/OWL/DCAT/WhateverTripleFlavorOfTheMonth" and then I go down a rabbit hole of meta(meta(meta)) documents like this for two hours and come back feeling like I know less than when I started.
So I just make up some JSON thing that seems like it will probably make intuitive sense in 100 years, write programs to generate and read that, and get on with my day.
I'd love for there to be some kind of "get to the point" document (complete with examples!) that didn't require reading 10,000 pages of bureaucrat-ese before having any hope of understanding it.
Someone did a good job, I think, in setting this up to be functional and address the main issues that government catalogs should accomplish- what data that the people paid for are available?
It’s also understandable through the json scheme if you’d like to skip the pretty easy to understand web site, https://resources.data.gov/standards/catalog/dcat-us/
My biggest fear with us-dcat3 was that it would be incompatible with 1.1. And this page says it won’t be, so I’m staying optimistic until I review.
> DCAT-US is the metadata standard associated with the requirements for enterprise data inventories in the OMB M-13-13 open data policy and the Foundations for Evidence-Based Policymaking Act Title II, OPEN Government Data Act (Evidence Act). The Evidence Act applies to all agencies. These federal policies do not apply to state and local governments which may have their own policies. However, state and local governments are welcome voluntarily to contribute their metadata to Data.gov. To do so, they must publish their metadata using the DCAT-US standard while omitting any federal-specific metadata elements as noted in the documentation.
NIEM was really complicated to implement, and I think that contributed to limited use.
DCAT is for cataloging and describing datasets and I think is used pretty extensively (I think google was using it when they would scrape and then describe data in their data commons project, among others).
Open data is undeniably a good and important thing, but a lot of people have stumbled thinking that merely making data open would make data useful. It's time to focus on creating useful data products, some of which will be made available under an open license, some of which will not.
Also, it says the schema for physical units are specified by this spec?
FWIU, QUDT Quantities, Units, Dimensions, and Types URIs MAY be used with
https://Schema.org/QuantitativeValue; and neither CSVW nor Model for Tabular Data and Metadata on the Web specify how to indicate physical quantities and units with a controlled vocabulary with URIs?
In Europe, the EU promotes their own DCAT-AP profile a bit more. Same purpose, quite widely used actually by governments, but not completely compatible with DCAT-US even though both are extensions of DCAT. Fun fact, DCAT-AP v1 predates the standardization of regular DCAT v1, which led to some minor inconsistencies. In the subsequent versions that development process is a bit more aligned now.
It was hidden at the top of the list of bullet points in the readme.
As someone who follows open data closely, I thought this was an update to the W3C DCAT Standard, not the US profile & implementation.