AbstractDataSet«abstract» inherited from CDIFManifest
DiscoveryDataDescription::Classes::AbstractDataSet
Definition
Documentation
Original
Reference
cdi:AbstractDataSet
CDIF
Definition
Abstract supertype for the cdi:PhysicalDataSet co-types a DataDownload may declare: TabularTextDataSet or StructuredDataSet.
Diagram
Inheritance
Specialized by: TabularTextDataSet, StructuredDataSet
Attributes
| Name | Type | Multiplicity | Description |
|---|---|---|---|
| identifier | XsdAnyUri | [0..1] | DocumentationOriginalReferenceschema:identifier DefinitionThe identifier property represents any kind of identifier for any kind of [[Thing]], such as ISBNs, GTIN codes, UUIDs etc. Schema.org provides dedicated properties for representing many of these, either as textual strings or as URL (URI) links. See [background notes](/docs/datamodel.html#identifierBg) for more details. ScopeDomain: Thing (https://schema.org/Thing). Range: PropertyValue (https://schema.org/PropertyValue), Text (https://schema.org/Text), URL (https://schema.org/URL). CDIFDefinitionThe primary identifier for the dataset; other identifiers should be listed in the sameAs field. Schema.org has three ways of encoding identifiers-- a text description, a URL, or by using the schema:PropertyValue field. The Science on Schema.org guidance strongly recommends using the PropertyValue approach. see https://github.com/ESIPFed/science-on-schema.org .... Dataset.md#identifier. Ideally, for any given data provided they would provide identifiers either all as strings or all as identifier_type. Scope@id - same as the underlying DataDownload (co-typing). |
Associations
| Role | Target | Multiplicity | Kind |
|---|---|---|---|
| alsoTypedAs | ← DataDownload | [0..1] | aggregation |