Index

Classes

Name Description

Name	Description
`Agent`	An entity (person, organization, or software) that can be a publisher, creator, or contributor of a resource.
`Any`	n/a
`Concept`	A unit of thought (an idea or notion) that can be expressed as a term.
`Container`	n/a
`DataCatalog`	A curated collection of metadata about datasets, data services, and related resources.
`DataService`	A service that provides access to a dataset or a collection of datasets.
`Dataset`	A collection of data, published or curated by a single agent, and available for access or download.
`DatasetSeries`	A series of datasets that are related in some way (e.g., by time, version, or theme).
`Distribution`	A specific representation of a dataset, typically available for download or access via a service.
`Duty`	An obligation attached to a permission or prohibition.
`Kind`	A vCard kind representing a contact point for a resource.
`LicenseDocument`	A vCard kind representing a contact point for a resource.
`Metric`	A measurable aspect of data quality (e.g., accuracy, completeness).
`PeriodOfTime`	A temporal extent or interval.
`Permission`	Grants the assignee the right to perform an action.
`Policy`	' The Policy class has the following properties: A Policy MUST have one uid property value (of type IRI [rfc3987]) to identify the Policy. A Policy MUST have at least one permission, prohibition, or obligation property values of type Rule. (See the Permission, Prohibition, and Obligation sections for more details.) A Policy MAY have none, one, or many profile property values (of type IRI [rfc3987]) to identify the ODRL Profile that this Policy conforms to. (See the ODRL Profiles section for more details.) A Policy MAY have none, one, or many inheritFrom property values (of type IRI [rfc3987]) to identify the parent Policy from which this child Policy inherits from. (See the ODRL Inheritance section for more details.) A Policy MAY have none or one conflict property values (of type ConflictTerm) for Conflict Strategy Preferences indicating how to handle Policy conflicts.(See the Policy Conflict Strategy section for more details.) An ODRL Policy MAY also declare properties which are shared and common to all its Rules. Specifically; action properties, sub-properties of relation (such as target), and sub-properties of function (such as assigner and assignee). See section Compact Policy for validation requirements on these shared properties. An ODRL Policy must either: Only use terms defined in the ODRL Core Vocabulary [odrl-vocab], or Use an ODRL Profile that declares the supported vocabulary used by expressions in the Policy. In the latter case, the profile property MUST be used to indicate the IRIs of the ODRL Profile(s). See the ODRL Profiles section for more details on mechanisms to define ODRL Profiles and conformance requirements. (The Examples in this document will use ODRL Profile identifiers for illustrative purposes only.) An ODRL Policy MAY be subclassed to more precisely describe the context of use of the Policy that MAY include additional constraints that ODRL processors MUST understand. Additional Policy subclasses MAY be documented in the ODRL Common Vocabulary [odrl-vocab] or in ODRL Profiles. A Policy class MUST be disjoint will all Policy subclasses (except for Set). '
`Prohibition`	Denies the assignee the right to perform an action.
`QualityMeasurement`	An observation of a metric applied to a specific resource.
`Resource`	A resource that is described in the catalog (e.g., a dataset, a data service, or a catalog).
`Rule`	'The Rule class is the parent of the Permission, Prohibition, and Duty classes. The Rule class represents the common characteristics of these three classes. A Rule class MUST be disjoint with all other Rule subclasses. The Rule class has the following properties: A Rule MUST have one action property value of type Action. A Rule MAY have none or one relation sub-property values of type Asset. A Rule MAY have none, one or many function sub-property values of type Party. A Rule MAY have none, one or many failure sub-property values of type Rule. A Rule MAY have none, one or many constraint property values of type Constraint/LogicalConstraint. A Rule MAY have none or one uid property values (of type IRI [rfc3987]) to identify the Rule so it MAY be referenced by other Rules. Note: The above property cardinalities reflect the normative ODRL Information Model. In some cases, repeat occurrences of some properties are also supported (as described in Policy Rule Composition and Compact Policy) but the normative atomic Policy is consistent with the above property cardinalities. Explicit sub-properties of the abstract relation, relation and failure properties must be used, the choice depending on the subclass of Rule in question.'
`Set`	ODRL Set policy, the default subclass of Policy, representing any combination of Rules

Agent

An entity (person, organization, or software) that can be a publisher, creator, or contributor of a resource.

Any

n/a

Concept

A unit of thought (an idea or notion) that can be expressed as a term.

Container

n/a

DataCatalog

A curated collection of metadata about datasets, data services, and related resources.

DataService

A service that provides access to a dataset or a collection of datasets.

Dataset

A collection of data, published or curated by a single agent, and available for access or download.

DatasetSeries

A series of datasets that are related in some way (e.g., by time, version, or theme).

Distribution

A specific representation of a dataset, typically available for download or access via a service.

Duty

An obligation attached to a permission or prohibition.

Kind

A vCard kind representing a contact point for a resource.

LicenseDocument

A vCard kind representing a contact point for a resource.

Metric

A measurable aspect of data quality (e.g., accuracy, completeness).

PeriodOfTime

A temporal extent or interval.

Permission

Grants the assignee the right to perform an action.

Policy

' The Policy class has the following properties: A Policy MUST have one uid property value (of type IRI [rfc3987]) to identify the Policy. A Policy MUST have at least one permission, prohibition, or obligation property values of type Rule. (See the Permission, Prohibition, and Obligation sections for more details.) A Policy MAY have none, one, or many profile property values (of type IRI [rfc3987]) to identify the ODRL Profile that this Policy conforms to. (See the ODRL Profiles section for more details.) A Policy MAY have none, one, or many inheritFrom property values (of type IRI [rfc3987]) to identify the parent Policy from which this child Policy inherits from. (See the ODRL Inheritance section for more details.) A Policy MAY have none or one conflict property values (of type ConflictTerm) for Conflict Strategy Preferences indicating how to handle Policy conflicts.(See the Policy Conflict Strategy section for more details.) An ODRL Policy MAY also declare properties which are shared and common to all its Rules. Specifically; action properties, sub-properties of relation (such as target), and sub-properties of function (such as assigner and assignee). See section Compact Policy for validation requirements on these shared properties. An ODRL Policy must either: Only use terms defined in the ODRL Core Vocabulary [odrl-vocab], or Use an ODRL Profile that declares the supported vocabulary used by expressions in the Policy. In the latter case, the profile property MUST be used to indicate the IRIs of the ODRL Profile(s). See the ODRL Profiles section for more details on mechanisms to define ODRL Profiles and conformance requirements. (The Examples in this document will use ODRL Profile identifiers for illustrative purposes only.) An ODRL Policy MAY be subclassed to more precisely describe the context of use of the Policy that MAY include additional constraints that ODRL processors MUST understand. Additional Policy subclasses MAY be documented in the ODRL Common Vocabulary [odrl-vocab] or in ODRL Profiles. A Policy class MUST be disjoint will all Policy subclasses (except for Set). '

Prohibition

Denies the assignee the right to perform an action.

QualityMeasurement

An observation of a metric applied to a specific resource.

Resource

A resource that is described in the catalog (e.g., a dataset, a data service, or a catalog).

Rule

'The Rule class is the parent of the Permission, Prohibition, and Duty classes. The Rule class represents the common characteristics of these three classes. A Rule class MUST be disjoint with all other Rule subclasses. The Rule class has the following properties: A Rule MUST have one action property value of type Action. A Rule MAY have none or one relation sub-property values of type Asset. A Rule MAY have none, one or many function sub-property values of type Party. A Rule MAY have none, one or many failure sub-property values of type Rule. A Rule MAY have none, one or many constraint property values of type Constraint/LogicalConstraint. A Rule MAY have none or one uid property values (of type IRI [rfc3987]) to identify the Rule so it MAY be referenced by other Rules. Note: The above property cardinalities reflect the normative ODRL Information Model. In some cases, repeat occurrences of some properties are also supported (as described in Policy Rule Composition and Compact Policy) but the normative atomic Policy is consistent with the above property cardinalities. Explicit sub-properties of the abstract relation, relation and failure properties must be used, the choice depending on the subclass of Rule in question.'

Set

ODRL Set policy, the default subclass of Policy, representing any combination of Rules

Types

No types are defined in the schema.

Enumerations

Name Description

Name	Description
`PartyCollection`	a Party that is a single entity representing a set of member entities. This indicates that all the members of the set will undertake the same functional role in the Rule. For the purpse of the simple_data_catalog, an enumerated list representing the IDS-RAM roles is used.

PartyCollection

a Party that is a single entity representing a set of member entities. This indicates that all the members of the set will undertake the same functional role in the Rule. For the purpse of the simple_data_catalog, an enumerated list representing the IDS-RAM roles is used.