- From: Joel Farrell <joelf@us.ibm.com>
- Date: Thu, 2 Nov 2006 16:26:46 -0500
- To: "Ramkumar Menon" <ramkumar.menon@gmail.com>
- Cc: public-ws-semann@w3.org
- Message-ID: <OFFAF8F06A.4FFC3E9F-ON8525721A.0075A270-8525721A.0075CED2@us.ibm.com>
Hello Ramkumar, Thank you for the review. These problems have all been fixed in the lastest editors draft - http://www.w3.org/2002/ws/sawsdl/spec/SAWSDL.html. Regards, Joel public-ws-semann-request@w3.org wrote on 10/31/2006 01:55:49 PM: > Hi Jacek, > > I ran a spellcheck and found these grammatical/typo errors in the > spec. The errors are enclosed in double quotes. > Hope this helps. > > rgds, > Ram > > > 1) Section Name: Abstract > > Current: > > This document defines a set of extension attributes for the Web > Services Description Language [WSDL 2.0] that "allow to" describe > additional semantics of WSDL components. > > Proposed: > This document defines a set of extension attributes for the Web > Services Description Language [WSDL 2.0] that allows description of > additional semantics of WSDL components. > > 2) Section 1.4 > > Current: > A loweringSchemaMapping is also attached to the OrderRequest element > to point to a mapping, in this case an XML document, "that" shows > how the elements within the OrderRequest can be mapped to semantic > data in the model. > > Proposed: > A loweringSchemaMapping is also attached to the OrderRequest element > to point to a mapping, in this case an XML document, which shows how > the elements within the OrderRequest can be mapped to semantic data > in the model. > > 3) Section 2 - Annotation Mechanism > > Current: > This specification does not address the annotation of service > implementations. It provides "a" reference mechanisms that can be > applied to WSDL type, interface and operation components to point to > concepts defined in semantic models. > > Proposed: > This specification does not address the annotation of service > implementations. It provides reference mechanisms that can be > applied to WSDL type, interface and operation components to point to > concepts defined in semantic models. > > > 4) Section 2.1 - SAWSDL Model Reference > > a) > Current: > The value of the "a" modelReference attribute is a set of zero or > more URIs, separated by whitespaces, that identify concepts in a > semantic model. > > Proposed: > The value of the modelReference attribute is a set of zero or more > URIs, separated by whitespaces, that identify concepts in a semantic model. > > b) > > Current: > It is recommended that the URI used for pointing to a semantic > concept "resolves" to a document containing its definition. > > Proposed: > It is recommended that the URI used for pointing to a semantic > concept resolve to a document containing its definition. > > > > 5) Section 3.2 > > Current: > Message parts are referenced from the portType structure in WSDL 1.1 > "which" generally corresponds to the WSDL 2.0 interface structure. > > Proposed: > Message parts are referenced from the portType structure in WSDL 1.1 > that generally corresponds to the WSDL 2.0 interface structure. > > 6) Section A.1 > > Current: > This data corresponds to the element "which" has been annotated with > the loweringSchemaMapping and can be used by some agent to invoke > the purchase order Web service. > > Proposed: > This data corresponds to the element that has been annotated with > the loweringSchemaMapping and can be used by some agent to invoke > the purchase order Web service. > > > > -- > Shift to the left, shift to the right! > Pop up, push down, byte, byte, byte! > > -Ramkumar Menon > A typical Macroprocessor
Received on Thursday, 2 November 2006 21:27:32 UTC