Capture

Package: 
Version: 
1
Is Abstract: 
yes
Is Pattern: 
no
Definition: 

A measurement that describes a means of capturing data. This class can be extended to account for different specific means. Use a specific instantiation of a Capture to describe a means of capturing a measurement.

Explanatory Notes: 

Provides an abstract base so that current and future forms of data capture can use this as an extension base and be freely mixed and matched within conceptual instruments as needed such as capturing a GPS point (using a RepresentedMeasurement) when administering a questionnaire (using RepresentedQuestions).

Example: 
A survey question, blood pressure reading; MRI images; thermometer; web service; experimental observation. Classes could include InstanceQuestion, InstanceMeasurement or other class extending Capture.
Property: 
NameCardinalityDatatypeDescription
name
0..n
A name for the measurement. A linguistic signifier. Human understandable name (word, phrase, or mnemonic) that reflects the ISO/IEC 11179-5 naming principles. If more than one name is provided provide a context to differentiate usage.
displayLabel
0..n
A structured display label providing a fully human readable display for the identification of the object. Supports the use of multiple languages and structured text.
usage
0..1
Explanation of the ways in which some decision or object is employed. Supports the use of multiple languages and structured text.
purpose
0..1
A description of the purpose or use of the Measurement. May be expressed in multiple languages and supports the use of structured content.
captureSource
0..1
The source of a capture structure defined briefly; typically using an external controlled vocabulary
analysisUnit
0..n
Identifies the unit being analyzed such as a Person, Housing Unit, Enterprise, etc.
Relationship: 
NameTarget ObjectDescriptionSource cardinalityTarget cardinalityRelationship type
hasResponseDomain
0..n
0..n
Aggregation
hasConcept
Capture has a Concept
0..n
0..n
Neither
hasInstruction
Capture has an Instruction
0..n
0..n
Aggregation
hasExternalAid
Capture has an External Aid
0..n
0..n
Aggregation

Stage:

Is extendable: 
Is property: 
0
RDF Mapping: 

Comments

Changed to extends AnnotatedIdentifiable, so that we can create a InstrumentConponent has Capture relationship

Need to review "instruction" vs "commandcode" when is each appropriate