RE: [ebxml-iic] on involving other TCs

[Jacques Durand <JDurand@fsw.fujitsu.com>]

Title: Reminder for 9:00AM Pacific Time --> Today ebXML IIC Conference Call Info

David:

 

Yes we need to involve more broadly the standard-authoringTC,

though we still need to define how and what exactly they vote on.

What is clear to me so far, after discussion this morning is that

(1) each CTTFs will just need to involve a liaison of/to the standard-authoring TC (whether of not an IIC member),

(2) this liaison will make sure to leverage the expertise from the other TC when crafting test cases, and their feedback on final output. 

 

So  the standard-authoring TC will have authority in reviewing our Test Cases, but that would be mostly on their "interface"

side of the overall test plan, i.e. the list of test requirement items in their readable form.

Other aspects of the tests ( test formats, test architecture, testing procedures) will have final decision of the IIC alone.

Certainly a proper conformance validation involves all of the above, not just test definitions,

but I believe there is a line beyond which the IIC TC has to be trusted to do the right job.

 

In particular, for our first step we expect the standard-authoring TC to :

- verify that each test item definition is "correct" according to the specs (i.e. actually checks some aspect of conformance).

- verify that the subset of our test items that qualifies conformance to core features (minimal level) is sufficient, if properly applied.

That would be, I believe, the extent of the decision (vote) that belong to this TC.

 

regards,

 

jacques

-----Original Message-----
From: David Fischer [mailto:david@drummondgroup.com]
Sent: Monday, April 01, 2002 3:02 PM
To: Jacques Durand; ebxml-iic@lists.oasis-open.org
Subject: RE: [ebxml-iic] OASIS ebXML IIC Conference Call Info - Monday Apr il 1 at 9:00AM P T (Noon ET)

On the call this morning, Jacques brought up the notion of joint subcommittees.  Jacques' concern with this idea was that the members of this subcommittee from the other TC would not be able to vote. 

 

Joint subcommittees are a great idea and there is not any problem with voting.  The subcommittee's job is to develop conformance test plans for the other TC's specification.  Since the other TC owns their spec, they will have to vote to approve the test plans anyway.  The IIC members of the subcommittee will vote on the test plans with IIC and the members of the subcommittee from the other TC will get to vote with their TC on approval.  Everyone gets to vote -- problem solved.

 

Regards,

 

David.

-----Original Message-----
From: Jacques Durand [mailto:JDurand@fsw.fujitsu.com]
Sent: Thursday, March 28, 2002 9:24 PM
To: ebxml-iic@lists.oasis-open.org
Subject: RE: [ebxml-iic] OASIS ebXML IIC Conference Call Info - Monday Apr il 1 at 9:00AM P T (Noon ET)

All:

 

Just a reminder for conf call Monday - need to vote.

 

On the agenda:

 

- April f-2-f meeting logistics and phone-in option.

 

- XML / Barcelona status, attendence, UN-CEFACT joint meeting

 

- proposal from XML Global to host a CVS repository for the group, that contains

detailed testing material (Matt McK. / Michael K.)

 

- status of activities : (1) MS conformance testing, (2) implementation guidelines.

 

- possible press-release planned from OASIS announcing next IIC outputs (we need to

commit on some deliverable date.)

 

- two items in "orders of the day", for the TC to agree on  (not motions, as the chair cannot make "motions" I was reminded):

 

1. The creation of other IIC Conformance sub-group in addition to Messaging (CTTFs for CPPA, RegRep...)

and the opening of these CTTFs to 1 or 2 subject matter experts from the relevant TC, to help define conformance tests

for its specification. This means that, in case these experts do not become -or are not- full IIC members

(though they could) and don't vote on output documents, we still recognize their authority in *helping* us define

and author test cases for their respective specs. (Note: I checked with Karl Best on the feasibility of such cross-teams.

That is OK, knowing that members who remain "external" to IIC cannot vote on the IIC output and process.)

So, if this resolution is adopted, the CTTFs accept the involvment of these experts (to be named by their TC) and

will operate in such a way that the input from these experts is reasonably taken into account, as they may not

want to become IIC member for such a transient contribution.

 

2. The undertaking of an MS Interoperability effort, in parallel with MS Conformance and MS Implementation Guidelines.

Please see the details of the mission of the MS Interoperability Testing Task Force, attached.

Part of the resolution is also a timing requirement (that would test the team's committment...) :

Given the expertise IIC already has on this topic, a first version of the team's ouput (spec for test cases

and operating guidelines) must be ready by end of May 2002.

Also, setting-up this team should not be detrimental to other current activities, staffwise...

If this resolution is adopted, an MS Interoperability team would be set-up, *only* if it finds members who fulfill these conditions...

 

regards,

 

Jacques Durand

IIC chair

-----Original Message-----
From: Eck, Jeffery (GXS) [mailto:Jeffery.Eck@gxs.ge.com]
Sent: Monday, March 18, 2002 9:58 AM
To: ebxml-iic@lists.oasis-open.org
Subject: [ebxml-iic] OASIS ebXML IIC Conference Call Info - Monday April 1 at 9:00AM P T (Noon ET)

Hello OASIS ebXML IIC TC  Members,

The call-in information for the ebXML IIC conference call is as follows  
Date:           Monday,   April 1, 2001
Time:           9:00AM Pacific Time (Noon Eastern Time)
Toll Free:     1-877-434-7266
Long Dist:    1-301-340-5190
Meeting ID#  32965 (ebXML)  

Thanks Jeff Eck - GE Global eXchange Services 
[Jacques Durand]