...
- "concept" trace / "definition" trace: point to the comprehensive or even normative definition (when available) or to the best matching wider AIRM concept
- "information concept" trace
- "data concept" trace
- "data type" trace:
- "additional" traces: traces that add qualifiers. helping achieving a more accurate semantic definition by giving more context to the main mapping
Note |
---|
Can we survive with just using these names that are inspired by the words in the spec? |
Source and target of traces
"concept" trace / "definition" trace:
Usage Notes: This will normally point to a resource in the AIRM Information Model, i.e. an AIRM information concept.
However, occasionally (e.g. when mapping the definition of certain containers), it may necessary to refer to the definition part of a (CLDM) data concept.
In this case, the data type of the AIRM trace target is not part of the trace semantics.
The start point depends on the requirement being fulfilled
Reading order of traces
General consensus seems to be:
- "concept" trace
- "data type" trace
- "additional" traces
All traces have an AND relationship.
Annotating traces
Add a comment of the mapping (or trace?). This comes in handy for example when tracing legacy interfaces that have data type constraints leading to loss of Information.
...
level of alignment (eg exact, broader, etc aka SKOS-like).
Note |
---|
We only need additional traces if the main trace is "specialised" |
AIRM_Rule 60
The 'Definition:Adapted' AIRM::TaggedValue shall be completed in order to indicate the level of semantic correspondence with the source definition. The list of values is:
...
· Generalised: Source definition is a generalised case of the target definition.
AIRM_Rule 116
A data or information construct is considered to be in semantic correspondence with the AIRM if one of the following conditions holds:
1. The definition of the construct is an exact copy of the definition of a specific AIRM element, or it is syntactically equal, or is rewritten or is specialised as described in AIRM_Rule 60.
2. It can be demonstrated that the definition of the construct can be decomposed into several elementary concepts, each corresponding to an AIRM element as per previous bullet. This decomposition must be comprehensive, i.e. cover all parts of the definition.
Representing traces in XSD
...