more editorial changes

[Jacques Durand <JDurand@us.fujitsu.com>]

Relaying these proposed edits from Monica M. as she investigated in the JC how to align the ebXML specifications.

 

-Jacques

 

> ebMS v3.0 (0.7) [2]

> 

>    "The ebXML infrastructure is composed of several independent, but

>    related, components. Specifications for the individual components

>    are fashioned as stand-alone documents. 

mm1: Suggest minor change to:

     From the onset, the ebXML framework has been composed of several

    independent, but related or aligned, components. Specifications for

    each component can be used individually, composed as desired, or

    integrated with other evolving technologies.

> Each specification is self-contained, meaning a conforming 

> implementation may ignore other

>    ebXML specifications. 

mm1: Suggest minor change to:

    Each specification is self-contained, as it pertains to a conforming

    implementation.

> Some references and bindings across ebXML

>    specifications should be interpreted as integration help, not

>    requirement to integrate. 

mm1: Suggest minor change to:

    Some references and bindings across ebXML specifications may be

    interpreted as guidance rather than as requirements to integrate.

> This applies to ebMS also, which may refer

>    in particular to CPPA specification, though does not require its

>    use: ebMS relies on a concept of "Agreement" the concrete

>    representation of which (e.g. CPA or other configuration

>    information) is left for implementors to decide."

mm1: Suggest minor change too:

    This applies to ebMS also, which may refer to or allow an

    implementation choice to use the CPPA specification: ebMS relies on

    a concept of "Agreement" the concrete representation of which (e.g.

    CPA or other configuration information) is left for implementors to

    decide.