OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-bindings message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [sca-bindings] Groups - sca-binding-jca-1.1-spec-cd02-rev2-issue75.docuploaded


Minor feedback items:

In the JCA specification, there are no references to "binding xml
document" outside of the conformance section.  So this sentence in
section 7.1:

"An SCA JCA Binding XML document MUST be a conformant SCA Composite
Document, SCA Definitions Document or a SCA ComponentType Document, as
defined by the SCA Assembly specification [SCA-Assembly], and MUST
comply with all the applicable requirements specified in this
specification."

seems like it is confusing matters by adding that second "MUST"
statement. Why not:
"An SCA JCA Binding XML document MUST be a conformant SCA Composite
Document, SCA Definitions Document or a SCA ComponentType Document, as
defined by the SCA Assembly specification [SCA-Assembly]."?

I suspect the reason is that we're expecting conformance to the XML
Schema, as well as the semantics of the elements when those can be
identified from more semantically rich XML analysis tools, like
Schematron.  For example, BJC20015 has a syntactic representation that
can be identified from context of the XML document itself, whereas
BJC0014 cannot be determined from the XML document itself, except by the
runtime.

Seems like, if we want to be pendantic, the problem is that BJC20015 has
a conformance target of the document, and BJC20014 has a conformance
target of the runtime, and we've not written it that way.  If we do
that, the wording of 7.2 already notes that section 7.1 must be
satisfied, and we've clarified what we mean by the otherwise hopelessly
vague "all applicable requirements specified in this specification."

In any case, "requirements specified in this specification" is awkward. 
Why not "requirements specified herein"?

Further, it turns out that we don't actually state as a MUST requirement
anywhere that the binding.jca element MUST conform to the schema.  So
perhaps we need to state that explicitly?

Looking at the JMS spec next.

-Eric.

simon_holdsworth@uk.ibm.com wrote:
> Proposed resolution to issue bindings-75
>
>  -- Mr. Simon Holdsworth
>
> The document named sca-binding-jca-1.1-spec-cd02-rev2-issue75.doc has been
> submitted by Mr. Simon Holdsworth to the OASIS Service Component
> Architecture / Bindings (SCA-Bindings) TC document repository.
>
> Document Description:
>
>
> View Document Details:
> http://www.oasis-open.org/committees/document.php?document_id=32853
>
> Download Document:  
> http://www.oasis-open.org/committees/download.php/32853/sca-binding-jca-1.1-spec-cd02-rev2-issue75.doc
>
>
> PLEASE NOTE:  If the above links do not work for you, your email application
> may be breaking the link into two pieces.  You may be able to copy and paste
> the entire link address into the address field of your web browser.
>
> -OASIS Open Administration
>   


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]