NEW ISSUE: Editorial cleanup of normative statetments

["Martin Chapman" <martin.chapman@oracle.com>]

Target:      sca-assembly-1.1-spec-cd02.pdf,

Raiser:          Martin Chapman

Description: 

Appendix C Conformance Items, extracts each normative statement found in the main body of the spec. Unfortunately when some of these
statements are taken out of the context they seem to lose meaning. Therefore they need to be rephrased so that they stand alone.
This should be an editorial issue only. In my view the following need improving:

[ASM50023] Some reference multiplicity errors can be detected at deployment time. In these
cases, an error SHOULD be generated by the SCA runtime at deployment time.

[ASM50024] Other reference multiplicity errors can only be checked at runtime. In these cases,
the SCA runtime MUST generate an error no later than when the reference is
invoked by the component implementation.

[ASM60020] other specified attributes of the source interface and the target interface of a wire
MUST match, including Scope and Callback interface

[ASM12004] Optionally, in the sca-contribution.xml file, additional elements MAY exist that list
the namespaces of constructs that are needed by the contribution and which are
be found elsewhere, for example in other contributions.

[ASM12005] Where present, these mechanisms MUST be used by the SCA runtime to resolve
artifact dependencies.

[ASM12008] SCA runtimes MAY choose not to provide the contribution functions functionality in
any way.

[ASM12025] The SCA runtime MUST raise an error if an artifact cannot be resolved by the
precedence order above.







--------------- 
Martin Chapman | Standards Professional
Mobile: +353 87 687 6654 

ORACLE Ireland 
 "Please consider your environmental responsibility before printing this e-mail"