Versions Compared

Key

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

...

This example shows how to embed a mapping into an XML schema document using the annotation element. It shows how the trace (or multiple traces) should use the AIRM's unique identifier as required by SWIM-INFO-019. Further mapping examples are available on the Understanding and recording mappings page.

Code Block
languagexml
titleExample of SWIM-INFO-014
linenumberstrue
<xs:annotation> 
 <xs:documentation>  
  <semanticCorrespondence>   
   <mapping>    
    <trace type="informationConceptTrace">-AIRM unique identifier-</trace>
    <trace>...
    <trace type="narrowingTrace">-AIRM unique identifier-</trace>   
   </mapping>  
  </semanticCorrespondence> 
 </xs:documentation>
</xs:annotation> 

...

Code Block
languagexml
titleExample of SWIM-INFO-014
linenumberstrue
<xs:annotation> 
 <xs:documentation>  
  <semanticCorrespondence>  
   <noSemanticCorrespondence rationale="incomplete mapping"/>  
  </semanticCorrespondence> 
 </xs:documentation>
</xs:annotation>

This example shows how to embed a mapping into an XML schema document using the annotation element. It builds on the other examples and includes the <xs:appinfo> element that specifies information to be used by the application. This is an optional element and can be used when the intention is to use an application to further process the semantic correspondences.

Code Block
languagexml
titleExample of SWIM-INFO-014
linenumberstrue
<xs:annotation> 
 <xs:appinfo>Semantic Correspondence</xs:appinfo>
 <xs:documentation>  
  <semanticCorrespondence>   
   <mapping>    
    <trace type="informationConceptTrace">-AIRM unique identifier-</trace>
    ...
    <trace type="narrowingTrace">-AIRM unique identifier-</trace>   
   </mapping>  
  </semanticCorrespondence> 
 </xs:documentation>
</xs:annotation>