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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-architecture message

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


Subject: Re: TA agenda Tokyo


Duane,

I like the direction you are headed. 

I think we all know that agreement on the ebXML Architecture is crucial.
I don't think we will consider that agreement reached unless everyone who 
considers themself a stakeholder is encouraged to participate. I recommend
a day-long, open, Architecture meeting -- attendance limited to room size. 
We should be equipped with a data projector, the document, and all comments.

The goal of the meeting is to edit and/or record editorial instructions
which the participants agree are needed prior to the next round of reviews 
and comments. A high degree of success would have the complete set of 
editorial instructions decided by the end of the day and incorporated by 
the end of the week. Lesser degrees of success we should not tolerate.

The keys to the success of such a meeting are the cooperation of all 
participants and the effectiveness of the chair in managing the process. 
Cooperation of participants includes constructive compliance, whereby
one agrees to record dissent on a decision to allow the group to move on.
Similarly, members can empower another member to represent their view,
thereby reducing the number of active participants.

The responsibility of Quality Team members in this scenario includes 
providing process advice to the chair and all participants; their goal
is to keep the meeting moving along and help overcome any obstacles.
The Quality Review team is guided by best practice, the ebXML Process
and Requirements, and input provided by particpating members of ebXML.

This open process ensures that all parties are heard, actions are
recorded and vetted, and process is observed to be working smoothly.

Anyway, that is what I think, from an ebXML Quality Review perspective. 

Regards,

Murray




At 11:32 PM 10/28/00 -0700, duane wrote:
>Anders, Murray, Nagwa, Brian et al:
>
>I would like to propose that on Tuesday we hold a special session with a
>split group from TA and QRT.   We should split the TA team into two
>groups - one to work with QRT on addressing their specific comments on
>the TA spec and the second team to start categorizing the general
>comments we receive from the other teams.
>
>Murray Maloney from QRT has already agreed to sit with us for a while
>and I would also hope that Tim, Nagwa and Jon also attend or have at
>least one other QRT member attend with a list of currently outstanding
>issues.  
>
>I think that by working together in Tokyo for one full day,  we can
>fully address the issues facing the TA spec.
>
>Comments?
>
>Duane Nickull
>
>"agrangard@nycall.com" wrote:
>> 
>> Below you will find my proposed TechArch agenda for the Tokyo meeting. As
>> you will see I have tried to keep it as clean as possible to allow core work
>> to be done. If you want to add or change anything, please do so before
>> Thursday next week.
>> 
>> Have a good trip and see you in Tokyo.
>> 
>> Anders
>> 
>> Draft Agenda
>> ebXML Technical Architecture Project Team
>> Tokyo, 6 - 10 November 2000
>> 
>> Monday, 6 November
>> 09:00 - 10:00 ebXML Technical Orientation
>> 10:00 - 11:00 Open Plenary
>> 11:00 - 12:00 Opening of the TA meeting, practical details, new sub-group:
>> Security
>> 12:00 - 13:00 Lunch
>> 13:00 - 17:30 Review received comments
>> 
>> Tuesday, 7 November
>> 08:00 - 08:15 Report from yesterdays Steering Committee
>> 08:15 - 12:00 Review received comments (subgroups)
>> 12:00 - 13:00 Lunch & Learn (Presentation on Conformance)
>> 13:00 - 16:00 Review received comments (subgroups)
>> 16:00 - 17:30 Review received comments
>> 17:30 - 18:00 Wrap-up, input to steering committee
>> 
>> Wednesday, 8 November
>> 08:00 - 08:15 Report from yesterdays Steering Committee
>> 08:15- 12:00 Review received comments (subgroups), Joint sessions with other
>> PTs, as appropriate
>> 12:00 - 13:00 Lunch & Learn
>> 16:00 - 17:30 Review received comments
>> 17:30 - 18:00 Wrap-up, input to steering committee
>> 
>> Thursday, 9 November
>> 08:00 - 08:15 Report from yesterdays Steering Committee
>> 08:15 - 12:00 Finalise Tech Arch 1.0 (subgroups), review of Hong Kong
>> presentation (Krishna Sankar)
>> 12:00 - 13:00 Lunch & Learn
>> 13:00 - 16:30 Finalise Tech Arch 1.0
>> 16:30 - 17:00 Wrap-up, input to steering committee
>> 
>> Friday, 10 November
>> 08:00 - 12:00 Prepare closing plenary presentation and future work
>> 12:00 - 13:00 Lunch
>> 13:00 - 15:00 ebXML Closing Plenary
>


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

Search: Match: Sort by:
Words: | Help


Powered by eList eXpress LLC