- From: Eric Prud'hommeaux <eric@w3.org>
- Date: Fri, 29 Sep 2006 16:10:22 +0200
- To: Joel Farrell <joelf@us.ibm.com>, Holger Lausen <holger.lausen@deri.org>
- Cc: SAWSDL public list <public-ws-semann@w3.org>, Jacek Kopecky <jacek.kopecky@deri.org>, webreq@w3.org
http://www.w3.org/TR/2006/WD-sawsdl-20060928/ appears ready to publish.
However, I made some changes and would like them checked before I push
the button. Note the comments (preceeded by a #) on each line starting
with "@@". I would like feedback from the editors before publishing,
if possible. A quick "yeah, sure" will finish the publication proccess
(note that webreq is Cc:d).
The diffs:
@@ -361,7 +400,7 @@ # padding of -2 not legal CSS
semantic information is included in the document via WSDL extension elements
as shown below on lines 3 to 14.</p>
-<pre style="margin-left:10px;padding-left:-2px">
+<pre style="margin-left:10px;padding-left:0px">
01 <wsdl:description … >
02
03 <rdf:RDF
@@ -529,7 +568,7 @@ # apparent typo
<pre>…
<xs:simpleType name="Confirmation"
- <strong>sawsdl:modelReference="http://www.w3.org/2002/ws/sawsdl/spec/ontology/purchseorder#OrderConfirmation"</strong>>
+ <strong>sawsdl:modelReference="http://www.w3.org/2002/ws/sawsdl/spec/ontology/purchaseorder#OrderConfirmation"</strong>>
…
</xs:simpleType>
…</pre>
@@ -682,7 +721,7 @@ # I believe we switched to Response. The doc supports this.
processor applies the transformation that can be retrieved from the URI given in
the value of sawsdl:liftingSchemaMapping and applies the transformation to those
elements where the schema mapping was specified. In the example above
-<em>http://www.w3.org/2002/ws/sawsdl/spec/mapping/Request2Ont.xslt</em>
+<em>http://www.w3.org/2002/ws/sawsdl/spec/mapping/Response2Ont.xslt</em>
will be applied to
<em>OrderRequest</em>
elements. If a mapping is specified on a global type definition the mapping
@@ -696,8 +735,8 @@ # Could not find OrderItem2Ont.xslt or MyDefOrderItem2Ont.xslt
<em>liftingSchemaMapping</em> is specified on it. The complex type of <em>orderItem</em> is defined later in the schema and the
complex type itself has a schema mapping. In such a case, the <em>liftingSchemaMapping</em> specified on the element overwrites the one
specified on the complex type. This means that only the schema mapping that is given with the URI
-http://www.w3.org/2002/ws/sawsdl/spec/mapping/OrderItem2Ont.xslt applies to the element orderItem.
-The http://www.w3.org/2002/ws/sawsdl/spec/mapping/MyDefOrderItem2Ont.xslt does not apply. The reason for
+http://example.org/mapping/OrderItem2Ont.xslt applies to the element orderItem.
+The http://example.org/mapping/OrderType2Ont.xslt does not apply. The reason for
specifying such an override rule to allow an element to indicate the type mapping does not apply.</p>
<pre>…
@@ -824,7 +863,7 @@ # switched to Resopnse
elementFormDefault="qualified">
<xs:element name="OrderRequest"
sawsdl:modelReference="http://www.w3.org/2002/ws/sawsdl/spec/ontology/purchaseorder#OrderRequest"
- sawsdl:liftingSchemaMapping="http://www.w3.org/2002/ws/sawsdl/spec/mapping/Request2Ont.xslt">
+ sawsdl:liftingSchemaMapping="http://www.w3.org/2002/ws/sawsdl/spec/mapping/Response2Ont.xslt">
<xs:complexType>
<xs:sequence>
<xs:element name="customerNo" type="xs:integer" />
the most important is the "Could not find OrderItem2Ont.xslt or
MyDefOrderItem2Ont.xslt" comment. If they exist somewhere, please
let me know quickly so I can include them in the publication.
I added some ids (anchors) on the appendixes and switched the doc to
UTF-8. If the editors are content with this, I commit this document
back to the editor's draft. Otherwise, we need to duplicate some of
this work the next time we publish.
The button gets pushed in 2 hours if noone objects.
--
-eric
home-office: +1.617.395.1213 (usually 900-2300 CET)
+33.1.45.35.62.14
cell: +33.6.73.84.87.26
(eric@w3.org)
Feel free to forward this message to any list for any purpose other than
email address distribution.
Received on Friday, 29 September 2006 14:09:25 UTC