- From: Waterfeld, Dr. Walter <Walter.Waterfeld@softwareag.com>
- Date: Wed, 1 Nov 2006 16:10:01 +0100
- To: "Tomas Vitvar" <tomas.vitvar@deri.org>
- Cc: <public-ws-semann-comments@w3.org>
- Message-ID: <BE6B7C2303852F45A1433D41312A174C02A95D91@DAEMSG03.eur.ad.sag>
Hello Tomas, here are some comments on the current SA-WSDL working draft: inclusion of mapping between XML schema types and ontology concepts The SAWSDL specification provides only a (probably smaller) part of the necessary specifications for semantic web services. This is probably ok in order to make progress. On the other hand it contains a mapping between XML schema and ontology. This is a quite specific part, which is not needed in every scenario where semantic web services are used. Therefore this part should be a separate specification. It may be even used for completely other purposes than in the context of web services. example ontology purchaseorder The example ontology purchaseorder is used in the modelReferences of the SAWSDL. It is not contained in the spec and version accessible via http://www.w3.org/2002/ws/sawsdl/spec/ontology/purchaseorder does not contain all used classes. many schema mapping technologies For the schema mapping all together 3 technologies are used in the examples: SPARQL, XSLT, XQuery. This is quite confusing. At least some more positioning - when to use what - is needed. more then links the SAWSDL specification currently provides in its core only the definition of links to the identification of more or less arbitrary documents. I would like to see at least the kind of support that xml schema has in WSDL. That means additionally an embedding of the semantic model definition should be defined. The major additional requirement would be that there is an XML serialization of the semantic models. This would allow in a standard way to transport semantic models within WSDLs. listofAnyURI XML has several possibilities to represent ordered values. The encoding with atomic datatype is very special and somehow outside the XML node mechanisms. Is it really a good idea to use these very special list datatypes? Best regards Walter Dr. Walter Waterfeld Software AG crossvision R&D Uhlandstraße 12 64297 Darmstadt Germany email: Walter.Waterfeld@softwareag.com
Received on Thursday, 2 November 2006 02:36:59 UTC