downloadURL and accessURL(Issue-70)

Domain is missing for some DCAT properties

clarify description of accessURL and downloadURL properties

provide examples of the usage of all properties particularly those that might be underspecified such as dct:accrualPeriodicity, dct:spatial, dct:temporal

versioning

describe dataset schema

dataset dependency

• List all properties in ToC
• 2 editorial comments

Use dct:rights instead of dct:license

Tracked as ISSUE-60. Resolved

reply

Consider adding dct:provenance or prov:has_provenance

• Consider adding dct:provenance or prov:has_provenance
• Consider referencing PROV

Can DCAT describe APIs?

Resolved

Add a dcat:interface property that points to a statement or manifest about technical means of accessing the dataset

Resolved

Add a property that links a distribution to an external concept that describes its access rules and methods

Resolved

• Move textual definitions into the tables for each property
• 1 editorial comment

Don't say that 2005-01-01 should be used for "unknown date in 2005"

Resolved

Don't say that 2005-01-01 should be used for "unknown date in 2005"

Resolved

• Rename dcat:dataset and dcat:distribution to dcat:hasDataset and dcat:hasDistribution
• (Note resulting long discussion thread)

Resolved

no consensus - closed

• Add something for Granularity
• Clarify how to use accrualPeriodicity

Add properties for dataset versioning, along the lines of ADMS

Add Contact and Corrections properties

What exactly is the scope of DCAT? Datasets or any kind of resource? Consider extending the scope.

Issues

• How to express dataset relationships such as "derived from"
• Time-related properties don't allow stating what agent caused the event
• Publisher is not the only dataset-agent relationship; creator and maintainer are important
• Catalog language is superfluous and ambiguous
• No license attached to each individual dataset metadata record
• Link from CatalogRecord to Catalog not necessary; link to Dataset sufficient
• Distribution types shouldn't be implicit

Suggestions

• Add classes that represent connections between DS-DS, DS-Agent, Cat-Agent
• Add Person and Organisation class
• Add classes for each type of distribution

The mental model of catalogs + datasets, and whether they can be used independently, is not really clear

Is it implied that a dcat:Dataset must have at least one distribution on the Web

What is the "single source" that the dcat:Dataset definition talks about?

Spec presents Concept and ConceptScheme in a single box despite being separate classes

Not clear what distinguishes a dataset from rdfs:Resource

Range of dct:language should be dct:LinguisticSystem

DCAT should not place restrictions on use of SKOS