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

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-assembly message

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


Subject: NEW ISSUE: Make support for constrainingType an optional compliance point


TARGET: SCA Assembly spec CD03

DESCRIPTION:
Section 6 describes the support for constrainingType which is used to constrain the shape of a component definition. It is trying to solve a set of top down design use cases. I'd like to assert that there may be many different ways to capture the top down design of a component or more importantly the design of a set (or assembly) of components. The presence of required support for constrainingType constrains each vendor to a specific top-down design mechanism. There is likely to be wide variability in the methodology and/or tooling used by each vendor in their approach to support for top-down design.

PROPOSAL:
In short, switch the compliance point for the whole of the constrainingType capability to be an optional compliance point. If a vendor chose to implement constrainingType, the rules as stated in the spec would be followed.

I am happy to take the time to write proposed wording after the issue is opened.

Dave Booz
STSM, BPM and SCA Architecture
Co-Chair OASIS SCA-Policy TC and SCA-J TC
"Distributed objects first, then world hunger"
Poughkeepsie, NY (845)-435-6093 or 8-295-6093
e-mail:booz@us.ibm.com



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