This section describes how the WSDL extensions introduced in this document are mapped into an RDF form compatible with the WSDL 2.0 RDF mapping [WSDL 2.0 RDF]. This specification introduces the properties {model reference}, {lifting schema mapping} and {lowering schema mapping}. Since the WSDL 2.0 RDF mapping does not provide an RDF form for the element declaration and type definition components, our schema mapping properties (i.e. {lifting schema mapping} and {lowering schema mapping}) are also not mapped. Therefore we only map {model reference} properties.
To represent the {model reference} property on any WSDL component (esp. Interface and Interface Operation components, as described earlier in this document) we reuse the name of the sawsdl:modelReference extension attribute as an RDF property identifier (the full IRI of the property is then "http://www.w3.org/2002/ws/sawsdl/spec/sawsdl#modelReference"), as shown in table 4-1. As the value of {model reference} is a list of IRIs, we introduce an RDF triple for each of the IRIs.
| Property | RDF Form |
|---|---|
| (componentId of the parent component generated per IRI-References for WSDL 2.0 Components) | |
| {model reference} | (for each IRI <iri> in the value of {model reference}) <componentId> sawsdl:modelReference <iri> |
EdNote: While the value of the {model reference} property is an ordered list, the transformation to RDF does not preserve the ordering information. Also, while {model reference} can potentially contain duplicate entries, such duplication is lost in the transformation to RDF. Therefore, the RDF form will represent equivalently the following two annotations: modelReference="#concept1 #concept2" and modelReference="#concept2 #concept1 #concept2". The Semantic Annotations for WSDL Working Group requests feedback on whether this deviation would be considered harmful. Alternate solutions that preserve order and duplicate entries are considerably more complex than this simple mapping.