ConceptScheme

Package: 
Is Abstract: 
no
Is Pattern: 
no
Definition: 

A comprehensive list of the concepts measured by the data that are being documented that is maintained by an agency. In addition to the standard name, label, and description, allows for the inclusion of an existing ConceptScheme by reference, assignment of a controlled vocabulary for the scheme, inclusion of descriptions for Concepts and ConceptGroups in-line or by reference.

Property: 
NameCardinalityDatatypeDescription
conceptSchemeName
0..n
A name for the ConceptScheme. May be expressed in multiple languages. Repeat the element to express names with different content, for example different names for different systems.
label
0..n
A display label for the ConceptScheme. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.
description
0..1
A description of the ConceptScheme. May be expressed in multiple languages and supports the use of structured content.
Relationship: 
NameTarget ObjectDescriptionSource cardinalityTarget cardinalityRelationship type
conceptSchemeReference
Reference to an existing ConceptScheme for inclusion.
0..n
0..n
Neither
vocabulary
Identifies and describes the vocabulary used to create the concept scheme.
0..n
0..1
Neither
concept
Describes an individual concept.
0..n
0..n
Aggregation

Stage:

DDI 3.2: 
c:ConceptSchemeType
Is extendable: 
Is property: 
0
RDF Mapping: 
LabelTypeURI
ConceptScheme
skos:closeMatch
http://www.w3.org/2004/02/skos/core#ConceptScheme

Comments

larry's picture

Can a vocabulary be used for many ConceptSchemes?
Is the direction of Concept to ConceptScheme relationship correct?
Is the direction of Concept to ConceptGroup relationship correct?