...
- Each semantic correspondence statements contains one of the four options allowed by the specification.
Examples
...
This example shows how to embed a mapping into an XML schema document using the annotation element. It shows how the trace should use the AIRM's unique identifier as required by SWIM-INFO-019.
Code Block |
---|
language | xml |
---|
title | Example of SWIM-INFO-014 |
---|
linenumbers | true |
---|
|
<xs:annotation>
<xs:documentation>
<semanticCorrespondence>
<mapping>
<trace>-AIRM unique identifier-</trace>
</mapping>
</semanticCorrespondence>
</xs:documentation>
</xs:annotation>
|
This example shows how to embed an out-of-scope declaration into an XML schema document using the annotation element. It shows how the rationale, required by SWIM-INFO-015, is added as an attribute.
Code Block |
---|
language | xml |
---|
title | Example of SWIM-INFO-014 |
---|
linenumbers | true |
---|
|
<xs:annotation>
<xs:documentation>
<semanticCorrespondence>
<outOfScope rationale="container"/>
</semanticCorrespondence>
</xs:documentation>
</xs:annotation>
|
This example shows how to embed a reference to a change request into an XML schema document using the annotation element. It shows how the change request number is captured as an attribute.
Code Block |
---|
language | xml |
---|
title | Example of SWIM-INFO-014 |
---|
linenumbers | true |
---|
|
<xs:annotation>
<xs:documentation>
<semanticCorrespondence>
<changeRequest number="100"/>
</semanticCorrespondence>
</xs:documentation>
</xs:annotation>
|
This example shows how to embed a no semantic correspondence established declaration into an XML schema document using the annotation element. It shows how the rationale, required by SWIM-INFO-015, is added as an attribute.
Code Block |
---|
language | xml |
---|
title | Example of SWIM-INFO-014 |
---|
linenumbers | true |
---|
|
<xs:annotation>
<xs:documentation>
<semanticCorrespondence>
<noSemanticCorrespondence rationale="work in progress"/>
</semanticCorrespondence>
</xs:documentation>
</xs:annotation> |
...