AbstractMapping«abstract» inherited from CDIFManifest
DiscoveryDataDescriptionStructure::Classes::AbstractMapping
Definition
Documentation
Original
Reference
cdi:AbstractMapping
CDIF
Definition
Abstract supertype for the cdif:hasPhysicalMapping family. Concrete subtypes: PhysicalMapping (generic), TextMapping (delimited / fixed-width text), LocatorMapping (locator string for structured data). Every concrete mapping carries a cdif:formats_InstanceVariable reference.
Diagram
Inheritance
Specialized by: PhysicalMapping, TextMapping, LocatorMapping
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 - optional URI for the mapping. |
Associations
| Role | Target | Multiplicity | Kind |
|---|---|---|---|
| hasPhysicalMapping | ← DataDownload | [0..*] | composition |
| hasPhysicalMapping | ← ActionResult | [0..*] | composition |
| formats | → InstanceVariable | [1] | association |