Working towards the next version of the SWIM Supporting Material

Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Different types of traces


Can we survive with just using these names that are inspired by the words in the spec?
RequirementTrace requiredTrace nameDefinition
SWIM-INFO-016 Mapping of information conceptsrequires one concept trace"information concept" tracetrace from the information concept in the information definition to the AIRM concept that has an equivalent or wider meaning
SWIM-INFO-017 Mapping of data concepts

requires one concept trace and one data type trace

  1. "data concept" trace
  2. "data type" trace
  1. trace from the data concept in the information definition to the AIRM concept that has an equivalent or wider meaning
  2. trace to the data type in the AIRM that has an equivalent or wider meaning
SWIM-INFO-018 Additional traces to clarify the mappingallows any number of additional clarifying traces"additional" tracetrace to an AIRM concept to fully describe the narrowing of the concept being mapped

Source and target of traces

The usual start point depends on the requirement being fulfilled.

Trace nameSourceTarget
"information concept" traceLikely sources: information exchange requirements

Best place to start: Conceptual Model.

If not found there, use Contextual Model or Logical Model

  1. "data concept" trace
  2. "data type" trace
Likely sources: service message

Best place to start: Logical Model.

If not found there, use Contextual Model or Conceptual Model for the "data concept" trace
"additional" tracesource depends on the trace being clarified

Should be in the same model as the trace being qualified.

Reading order of traces

General reading order is:


Advance users may like to add extra detail concerning the level of semantic correspondence achieved. The requirements talk about "equivalent or wider meaning"

Definition being traced to is...Annotations that can make this more explicit

ExactCopy: Definition of concepts in the information definition and the AIRM are exact copy of each other.

SyntacticallyEqual: Definitions are only different due to syntax corrections (grammar, spelling) but are otherwise equivalent.

Rewritten: The definition of the concept in the information definition has been rewritten to reflect information definition specificity. However, the meaning is the same, i.e. the definition still describes exactly the same concept as the AIRM.

WiderSpecialised: The definition in the information definition is a special case of the definition found in the AIRM.

We only need additional traces if the main trace is "specialised"


How should the different traces be represented in the XSD examples we use?

Trace nameElement nameAttribute
"information concept" trace<informationConceptTrace><trace keyword="informationConceptTrace>
  1. "data concept" trace
  2. "data type" trace



<trace keyword="dataConceptTrace>

<trace keyword="dataTypeTrace>

"additional" trace<additionalTrace>

<trace keyword="additionalTrace>

Full example

If we apply all of this:

Code Block
   <xs:documentation>    <semanticCorrespondence>      <mapping>        <informationConceptTrace<xs:documentation>
      <mapping note="loss of info because of legacy">
        <informationConceptTrace degree="specialised">-AIRM unique identifier-</informationConceptTrace>    <additionalTrace>informationConceptTrace>
        <additionalTrace>-AIRM unique identifier-</additionalTrace>      </mapping>    </semanticCorrespondence>  </xs:documentation><additionalTrace>

Example of tracing exercise


However it should be consistent with the information given at the AIRM homepage. Links to the according pages will also help.