Barb,
(Speaking as one of the OSOA SCA Spec Authors)
The OSOA SCA spec terms do talk about "compliant implementations" - but
this is a piece of legalese that has no force, since the specifications
themselves nowhere define what compliance is.
The OSOA SCA specs in fact deliberately left things loose in terms of
compliance. Now that the SCA specs are being taken forward for
standardization in OASIS, then compliance and test suites are part of
the work plan. However, this is an item that will complete in the future.
Regarding Tuscany, it is intended to faithfully implement the functions
described in the OSOA SCA 1.0 specifications. It isn't complete yet,
but the Tuscany team are working hard to implement all the functions
described in the specifications. There are also pieces of Tuscany that
(legitimately) go beyond the specifications, such as supporting useful
and interesting implementation types and binding types that are not
currently specified.
Yours, Mike.
Chair, OSOA SCA Assembly working group.
Barb Cochrane wrote:
I have a quick question I hope one of the Apache team can help me with: is
Tuscany's SCA 1.0 API a compliant implementation of OSOA's Service Component
Architecture Specification? I'm asking because of the OSOA SCA Spec license
terms.
Thanks in advance!
Cheers,
Barb
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
