Re: [wsbpel-implement] 9/29/2003: Interoperability Definition Draft

[Diane Jordan <drj@us.ibm.com>]

A definition might be useful, but  I don't think we should include 
conformance as one of the objectives or activities for this subgroup.   It 
implies a great degree of completeness both in definition and execution of 
test cases.   There are also implications regarding the results for those 
implementations that are tested that I don't think  the TC should get 
involved in.
 
Regards, Diane
IBM  Dynamic e-business Technologies
drj@us.ibm.com
(919)254-7221 or 8-444-7221, Mobile: 919-624-5123





Monica Martin <monica.martin@sun.com>
09/30/2003 01:56 PM
 
        To:     ygoland@bea.com
        cc:     wsbpel-implement@lists.oasis-open.org
        Subject:        Re: [wsbpel-implement] 9/29/2003: Interoperability 
Definition Draft


Yaron Goland wrote:

>I wonder if we don't need a third definition in addition to portability 
and
>interoperability - Conformance.
>
>Conformance - Tests designed to assure that an implementation is 
conformant
>with a standard.
> 
>
mm1: Actually in looking over the portability question, I had this same 
take. Although, I would have to admit that portability is related to or 
congruous with conformance.. If you look at the assumptions of 
portability, it is about a baseline of core capabilities. Conformance 
can formalize that and provide the capability to assign levels for core 
and 'building' functions.  A derived conformance definition (that looks 
to the ISO IEC Guide 2)  is provided below:

    Fulfillment of an implementation of all requirements specified;
    adherence of an implementation to the requirements of one or more
    specific standards or specifications.

You can find more information - actually there was an OASIS TC that 
developed a conformance specification last year 
(http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ioc - 
'Conformance' under the list of TCs).

Thanks.

>>-----Original Message-----
>>From: Monica Martin [mailto:monica.martin@sun.com]
>>Sent: Monday, September 29, 2003 12:21 PM
>>To: wsbpel-implement@lists.oasis-open.org
>>Subject: [wsbpel-implement] 9/29/2003: Interoperability
>>Definition Draft
>>
>>
>>As requested today, these are derived definitions from previous work
>>done including inputs from ISO IEC, ebXML IIC and other
>>venues including
>>those in the testing arena, such as NIST (National Institute
>>of Science
>>and Technology):
>>
>>Interoperability includes products (such as information systems),
>>services or processes that can interoperate or work together.
>>Software
>>interoperability is defined as two or more software
>>implementations of a
>>specification working together. This does not mean that the
>>implementations are conformant to the specifications implemented. The
>>software interoperability is typically tested under controlled
>>environment and via an interoperability trial. Issues arising out of
>>these trials may be addressed by:
>>o    Usage guidelines
>>o    Best practices
>>o    Input for new conformance tests
>>o    Technical recommendations
>>o    Specification upgrade
>>
>> From a test perspective, interoperability testing is:
>>Process of verifying that two implementations of the same
>>specification,
>>or that an implementation and its operational environment, can
>>interoperate according to the requirements of an assumed agreement or
>>contract. This contract does not belong necessarily to the
>>specification, but its terms and elements should be defined
>>in it with
>>enough detail, so that such a contract, combined with the
>>specification,
>>will be sufficient to determine precisely the expected behavior of an
>>implementation, and to test it
>>
>>
>> 
>>
>
> 
>