Container and context for data and processes. This is the same Dataset type described by the Administrative Core profile, which also defines dataFiles and administrative metadata.
#Properties
| Property | Type | Cardinality | Required | Description |
|---|---|---|---|---|
id | Text | 0..1 | MAY | Optional identifier within an application-defined scope. Implementations that require an internal identifier SHOULD use this field. The domain model does not automatically assign identifiers. |
type | Text | 1 | MUST | Dataset |
additionalTypes | Text | 0..* | MAY | Discriminator for decoration types. |
conformsTo | Text | 1..* | MUST | MUST include provenance-core as its profile discriminator. Additional classifications or specializations MAY also be included. |
identifiers | Text | 1..* | MUST | Identifiers by which the dataset is known or referenced, such as a DOI, accession number, repository name, or other identifying string. Identifiers may be globally scoped or scoped to a particular system or context. |
processes | Process | 0..* | SHOULD | Processes contained in this dataset |
hasParts | Dataset | 0..* | SHOULD | Contained datasets from any profile. Each child declares its own profile, independently of its parent and siblings; the same nesting options apply at every depth. |
additionalProperties | Annotation | 0..* | MAY | Extensible metadata |
#Relationships
The diagram could not be displayed. Its source is available below.
Diagram source
flowchart TD
additionalTypes@{ shape: stadium, label: "string" }
id@{ shape: stadium, label: "string" }
ct@{ shape: stadium, label: "string" }
d[Dataset]
d --additionalTypes--> additionalTypes
d --processes--> Process
d --hasParts--> part["Dataset (part)"]
d --additionalProperties--> Annotation
d --identifiers--> id
d --conformsTo--> ct