W3C home > Mailing lists > Public > public-ws-resource-access@w3.org > April 2010

RE: Editorial alignments

From: Ram Jeyaraman <Ram.Jeyaraman@microsoft.com>
Date: Fri, 23 Apr 2010 22:51:40 +0000
To: Doug Davis <dug@us.ibm.com>, "public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org>
Message-ID: <503546C5699C1144BDEA0D0DFFE7F8812D0CC8A9@TK5EX14MBXC110.redmond.corp.microsoft.com>
One comment:


  2) 3 of the 7 specs have the 'Composable Architecture' section.  And there are two variants of it.
Mex:
The Web services specifications (WS-*) are designed to be composed with each other to provide a rich set of tools for the Web services environment. This specification specifically relies on other Web services specifications to provide secure, reliable, and/or transacted message delivery and to express Web service metadata.

Eventing/EVD:
By using the XML, SOAP [SOAP11], [SOAP12], and WSDL [WSDL11]  extensibility models, the Web service specifications (WS-*) are designed to be composed with each other to provide a rich set of tools to provide security in the Web services environment. This specification specifically relies on other Web service specifications to provide secure, reliable, and/or transacted message delivery and to express Web service and client policy.
(But evd doesn't include the last sentence since it doesn't define any operations).

I think we either need to remove this section from Mex, Eventing and EVD, or pick one variant and add it to the other 4 specs.  I have a preference for adding the Eventing/EVD variant to the other 4 specs.

Using Eventing/EVD variant seems fine. I like to suggest an editorial change to the description as follows.

By using the XML, SOAP [SOAP11], [SOAP12], and WSDL [WSDL11]  extensibility models, the Web service specifications (WS-*) are designed to be composed with each other to provide a rich set of tools to provide security in for the Web services environment. This specification specifically relies on other Web service specifications to provide secure, reliable, and/or transacted message delivery and to express Web service and client policy.

Thanks.

From: public-ws-resource-access-request@w3.org [mailto:public-ws-resource-access-request@w3.org] On Behalf Of Doug Davis
Sent: Tuesday, April 20, 2010 8:21 PM
To: public-ws-resource-access@w3.org
Subject: Editorial alignments


All,
  I noticed some inconsistencies between the specs.

1) the ordering of the sections in "Terminology and Notation" differed, so made them all align with this order:
Terminology and Notation
   2.1 Notational Conventions
   2.2 Considerations on the Use of Extensibility Points
   2.4 Terminology
   2.3 Compliance
   2.5 XML Namespaces
Note: not all specs have all sections.

2) 3 of the 7 specs have the 'Composable Architecture' section.  And there are two variants of it.
Mex:
The Web services specifications (WS-*) are designed to be composed with each other to provide a rich set of tools for the Web services environment. This specification specifically relies on other Web services specifications to provide secure, reliable, and/or transacted message delivery and to express Web service metadata.

Eventing/EVD:
By using the XML, SOAP [SOAP11], [SOAP12], and WSDL [WSDL11]  extensibility models, the Web service specifications (WS-*) are designed to be composed with each other to provide a rich set of tools to provide security in the Web services environment. This specification specifically relies on other Web service specifications to provide secure, reliable, and/or transacted message delivery and to express Web service and client policy.
(But evd doesn't include the last sentence since it doesn't define any operations).

I think we either need to remove this section from Mex, Eventing and EVD, or pick one variant and add it to the other 4 specs.  I have a preference for adding the Eventing/EVD variant to the other 4 specs.

3) in some specs we say:
        A non-normative copy of the XML schema is listed below for convenience.
in others we say:
        A non-normative copy of the XML Schema description is listed below for convenience.
I'd like to change it to match the first one, "XML schema" instead of "XML Schema description", in all specs.

Any objection to me doing edits #2 and #3 as editorial changes?

thanks
-Doug
______________________________________________________
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug@us.ibm.com<mailto:dug@us.ibm.com>
The more I'm around some people, the more I like my dog.
Received on Friday, 23 April 2010 22:52:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:18:26 GMT