[HN Gopher] Seeking comments on the Data Catalog (DCAT) standard... ___________________________________________________________________ Seeking comments on the Data Catalog (DCAT) standard v3.0 Author : metasemantic Score : 64 points Date : 2023-09-18 14:20 UTC (8 hours ago) (HTM) web link (github.com) (TXT) w3m dump (github.com) | westurner wrote: | - [ ] DOC: The JSON-LD context file links 404: https://doi- | do.github.io/dcat-us/#json-ld-context | | 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? | jhoechtl wrote: | How is open data these days? I have the feeling it lost a lot of | steam? | jedsundwall wrote: | Open data is dead, long live open data! | https://radiant.earth/blog/2023/05/we-dont-talk-about-open-d... | | 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. | isodev wrote: | Does anyone know why is there a "-US" suffix in the name? Is it | an extension to the standard DCAT v3? | meepmorp wrote: | > DCAT-US v3 is not a "new" standard; it is a "profile" of or | implementation of the World Wide Web Consortium's (W3C) DCAT | standard. | | It was hidden at the top of the list of bullet points in the | readme. | markus92 wrote: | Yeah it is. It basically narrows the spec down a bit. For | example, it has some specific classes like the dcat-us | AccessRestriction class, but it also mandates the publisher of | a catalog (collection of datasets), while vanilla DCAT has it | as a recommended field. | | 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. | abrahms wrote: | recommended title update: Replace DCAT with "Data Catalog (DCAT)" | dang wrote: | Ok, done. Thanks! | 1MachineElf wrote: | I haven't kept up with National Information Exchange Model | (NIEM)[0] since the first Obama term. Is this related somehow? | | [0] https://en.wikipedia.org/wiki/NIEMOpen | jiggawatts wrote: | If I searched the Internet high and low for a whole day, I doubt | I could find a better example of this phenomenon for which I | don't have a name: standards that exist to keep standard | authorities busy. Standards that are actually seventeen layers of | standards, all developed in isolation from the real ecosystem. | Standards that will have between zero and at most three | implementations, all mutually incompatible. | peter_l_downs wrote: | For more information about DCAT-US, click through to | | https://github.com/DOI-DO/dcat-us/wiki/What-is-DCAT%E2%80%90... | | > 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. ___________________________________________________________________ (page generated 2023-09-18 23:00 UTC)