Metadata supports human-readable ‘liability’ statement/ disclaimer for the data.

[johnd-im]

Creator Name: John Davidson Creator Affiliation: Contractor, Department of the Interior/OCIO/CDO

Requirement(s)

Metadata supports human-readable ‘liability’ statement/ disclaimer for the data (i.e., a statement of liability assumed by the distributor of the data).

Problem Statement

Target Audience / Stakeholders

Intended Uses / Use Cases

Existing Approaches - Optional

• The DOI's "Application Profile of DCAT-US 1.1" metadata specifies mandatory property $.dataset.liability (multiplicity:1, range: string)
• See FGDC CSDGM "distribution liability" (distliab)

Additional context, comments, or links - Optional

A requirement of the DOI's "Application Profile of DCAT-US 1.1" metadata specification.

[fellahst]

In response to the requirement for including a human-readable 'liability' statement in the metadata, we have introduced a new property and class in the DCAT-US profile:

• New Property: dcat-us:liabilityStatement
• Associated Class:dcat-us:LiabilityStatement

This enhancement ensures that liability information associated with datasets is clearly articulated and accessible within the metadata, providing legal clarity and transparency for data distributors and users alike.

[TDabolt]

Flag for discussion. The proposed solution meets the requirement however is there a legal basis for needing a liability statement?

[fellahst]

A section for legal metadata in usage guideline has been added in the specification. This section can be used as starting point for discussion and review by legal experts.