- From: Jacek Kopecky <jacek.kopecky@deri.org>
- Date: Wed, 13 Sep 2006 12:16:30 +0200
- To: SAWSDL public list <public-ws-semann@w3.org>
Hi all, below I suggest replacement text for the first paragraph in section 2.2, schema mappings. The reason for this suggestion is that the current text is still biased on a scenario of mediation between two different XML structures, where a simpler scenario is plausible with the client operating on the semantic level. SAWSDL section 2.2 really only needs to provide the building blocks, lifing and lowering schema mappings, and the more complex scenario will be possible. Suggested rewrite: SAWSDL introduces schema mapping annotations to address post-discovery issues in using a Web service. Model references can be used to help determine if a service meets the requirements of a client, but there may still be mismatches in the structure of the inputs and outputs. For example, a client may have a given name and last name among its data, and these values need to be concatenated in the message to the Web service. The schema mapping would take the client's semantic data and turn it into XML, and in the process it would perform the necessary concatenation to produce the full name. In a more complex scenario, a client may use WSDL with semantic annotations to describe the service it expects. Again, if the XML structures expected by the client and by the service differ, schema mappings can translate the XML structures into the semantic model where any mismatches can be understood and resolved. Discussion will be welcome, Jacek
Received on Wednesday, 13 September 2006 10:16:34 UTC