W3C home > Mailing lists > Public > public-ws-addressing@w3.org > March 2005

WSA Core minor editorial issues

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Mon, 7 Mar 2005 18:51:19 -0800
Message-ID: <7DA77BF2392448449D094BCEF67569A506C173D4@RED-MSG-30.redmond.corp.microsoft.com>
To: <public-ws-addressing@w3.org>

A straight through read of the Core draft brought a few editorial items
to my attention.

1) The Short Table of Contents does not provide significant value over
the complete version since the complete version fits easily on a single
screen with room to spare.  I assume this is automatically generated by
the build process.  Can we drop the Short Version?

2) Section 2.2 has this line:
  /wsa:EndpointReference/wsa:ReferenceParameters/[reference parameters]
which departs from the standard notation.  I think it should be:
  /wsa:EndpointReference/wsa:ReferenceParameters/{any}

3) The following extensibility points for attributes are not documented
in the spec:
  /wsa:EndpointReference/wsa:Address/@{any}
  /wsa:EndpointReference/wsa:ReferenceParameters/@{any}

I assume the standard boilerplate would describe these: "This is an
extensibility mechanism to allow additional attributes to be specified."

4) Section 3 states (awkwardly):
  "[source endpoint] : endpoint reference (0..1) 
   Reference of the endpoint where the message originated from."

Suggest rewording to "Reference to the endpoint at which the message
originated."

5) Section 3.1 doesn't discuss whether attribute extensions are allowed.
Rather than introducing lots of /@{any} notation, perhaps we could state
generally that extension attributes are allowed.

6) Many sections and subsections don't have explicit ids (e.g. Security
Considerations).  It's nice to have readable IDs for linking to the spec
with fragments.
Received on Tuesday, 8 March 2005 02:51:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:35:04 GMT