NEW ISSUE: editorial RM Protocol Elements dives right into extensibilitydiscussion, no intro

[Christopher B Ferris <chrisfer@us.ibm.com>]

Title: editorial RM Protocol Elements
dives right into extensibility discussion, no intro

Description:

Section 3 seems to jump right in with
a note to implementers, without at all introducing what the RM protocol
elements are, are for, etc.

It starts out, on line 265 (CD4 draft):
        The
following protocol elements define extensibility points at various places.
Implementations MAY add
        child
elements and/or attributes at the indicated extension points but MUST NOT
contradict the semantics
        of
the parent and/or owner, respectively. If a receiver does not recognize
an extension, the receiver
        SHOULD
ignore the extension.

        ...

Target: spec

Type: editorial

Proposal:

It would seem to me that the content
of section 3 is really separate sub-sections that deals specifically with
extensibility considerations, composition,
etc. I would think that the spec would be better off if these were called
out in their own 
subsections, and some introductory text
were provided, that explains what is in the sub-sections that follow.

Thus, I think that the following would
do the trick:

3 RM Protocol Elements

The following sub-sections define the
various RM protocol elements, and prescribe their usage by a conformant
implementation.

3.1 Considerations on the Use of Extensibility
Points

        (first
para of current section 3)

3.2 Considerations on the Use of "Piggy-backing"

        (2ndpara
of current section 3)

3.3 Composition with WS-Addressing

        (remainder
of section 3 prose)

and renumber sub-sections 3.1 through
3.8 accordingly.

Cheers,

Christopher Ferris
STSM, Software Group Standards Strategy
email: chrisfer@us.ibm.com
blog: http://www.ibm.com/developerworks/blogs/dw_blog.jspa?blog=440
phone: +1 508 377 9295