DCAT Data Catalog

Features

  • DCAT does not make any assumptions about [the various] serialization formats of the datasets but it does distinguish between the abstract dataset and its different manifestations or distributions
  • defines a relatively comprehensive set of reusable terms from established vocabularies (Dublin Core, SKOS, FOAF, PROV) and extends these with some integrating classes and missing properties.

Issues

Dataset Ordering (claude)

DCAT itself doesn't have a direct property for specifying the order of datasets within a catalog. This comes up when you want to present datasets in a specific sequence in a user interface or documentation, but there isn't a standard DCAT property for it. Some possible workarounds people use:

  • Use Dublin Core's terms:sequence
  • Create a custom property for ordering
  • Use RDF List structures (though this is more complex)

Terms

  • dcat:Catalog: a dataset in which each individual item is a metadata record describing datasets and data services
  • dcat:Resource: not intended to be used directly, but is the parent class of dcat:Dataset, dcat:DataService and dcat:Catalog
  • dcat:DatasetSeries:

Spatiotemporal terms

distribution frequency spatial/geographic coverage spatial resolution

dct:temporal (temporal coverage)

dcat:temporalResolution

intended to provide a summary indication of the temporal resolution of the data distribution as a single value. More complex descriptions of various aspects of temporal precision, accuracy, resolution and other statistics can be provided using the Data Quality Vocabulary VOCAB-DQV "Data on the Web Best Practices: Data Quality Vocabulary".

prov:wasGeneratedBy

References


Children
  1. Application Profile
  2. DCATv2
  3. DCATv3

Backlinks