Re: [sca-assembly] NEW ISSUE: (v1.1) Upgrade ASM12017, ASM12030,ASM14004 be mandatory statements

[Eric Johnson <eric@tibco.com>]

I hesitate to comment on the the substance of the proposal, since this 
hasn't been logged yet, but:

What's the normative target of ASM12030?

For ASM14004, what's the definition of static analysis?

-Eric.

On 3/14/11 8:23 AM, Martin Chapman wrote:
> Target: SCA Assembly v1.1 Specification (and Test assertion/cases)
>
> Description: During review of the specification three normative statements would increase portability/interoperability of SCA Runtimes by being made mandatory. The statements affected are ASM12017, ASM12030, ASM14004.
>
> Proposal:
>
> ASM12017:
>
> Change: "[ASM12017] Where a component that is the target of a wire is removed, without the wire being changed, then future invocations of the reference that use that wire SHOULD fail with a ServiceUnavailable fault...."
>
> To: "[ASM12017] Where a component that is the target of a wire is removed, without the wire being changed, then future invocations of the reference that use that wire MUST fail with a ServiceUnavailable fault...."
>
> ASM12030:
>
> Change: "[ASM12030] For XML definitions, which are identified by QNames, the @namespace attribute of the export element SHOULD be the namespace URI for the exported definitions."
>
> To: "[ASM12030] For XML definitions, which are identified by QNames, the @namespace attribute of the export element MUST be the namespace URI for the exported definitions."
>
> ASM14004:
>
> Change: "[ASM14004] When an error that could have been detected through static analysis is detected and raised at runtime for a component, the component SHOULD NOT be run until the error is fixed."
>
> To: "[ASM14004] When an error that could have been detected through static analysis is detected and raised at runtime for a component, the component MUST NOT be run until the error is fixed."
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>