[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Groups - Conference call modified
Conference call has been modified by Bill Pope (zpope@pobox.com). Date: Tuesday, 31 August 2004 Time: 12:00pm - 01:00pm Eastern Time Event Description: Dial in information: -------------------------------------------- US participants : 866-214-3176 International participants : 404-827-9098 Access code : 2433958 --------------------------------------------- Thanks to BEA for hosting this call. Agenda: Plan for closure 1. Completion of the specification 2. Advancement (or not) of the specification to OASIS standard 3. Role of the TC going forward Minutes: Agenda: Plan for Closure - Completion of the specification Status of the WSDL, normative or non-normative - Advancement (or not) of the spec to OASIS standard - Role of the TC going forward Attending: Bill Pope Mark LIttle Sazi Temel Doug Bunting Martin Chapman Tony Fletcher Alastair Green Bob Haugen Alex Ceponkus Meeting is quorate * Closing the Specification Peter would like to go through final editorial review - Suggests two week period for TC review - Another step is required, handling of the WSDL, inclusion of these into the specifications - Happy with the technical accuracy, edits needed should be copy edit type material. Alex and Peter need two more weeks editorial time. Alastair: Proposal is to maintain the WSDL as a seperate non-normative section, the natural language text is definitive and takes precedence when there are conflicts. Doug: schema and WSDL provide information above that provided by the natural language text. These (schema and wsdl) should normative as they are used by generation engines. Bill: there does need to be a precedence if we have two ways of saying the same thing. Alastair: the WSDL and the schema are expressions of the specification for a specific purpose and are normative within the context of that purpose. Tony: the WSDL is a possible binding but may not be the only binding. This can be addressed in the conformance clause. If you implement a binding for which WSDL is provide then you must do it in the manner defined in the WSDL file. Alastair: Unless the WSDL adds something substantive content to the schema and the specification it adds generative ability but does not impact the technical content of the specification. The WSDL is not a new binding, it is a different expression of a binding that already exists in the specification. ... open discussion ... Alastair: this needs further investigation Two issues: 1. The XML and its status 2. The Schema and its status Tony: there are often 2 and sometimes 3 ways to express the same thing in the specification. These are intended to be the same in each case, we can just consider these things bugs and address them as they come up. Alastair: timetables, schedule a next meeting for two weeks time with editorialy complete specification and ready to discuss the issues of schema and WSDL inclusion and conflict resolution between the different expressions (natural language and XML). Tony: the actual document is bloated with saved changes and other information. This should also be removed. Alastair: motion The TC aims to bring the current work to the point of a vote on a final draft for comtee draft for BTP 1.1 on the following schedule: Tuesday Sept 14th: resolution of final issues on XML, WSDL, and natural language text Friday Sept 17th: Final draft is available for review Monday Oct 4th: Voting on Cmttee Draft opens, subject to OASIS procedural constraints Seconded by Tony Passed unopposed Alex: There is a "URI to be determined" how should we deal with this. Alastair: Choreo can host the next conference call on Tuesday September 14th. View event details: http://www.oasis-open.org/apps/org/workgroup/business-transaction/event.php?event_id=5870 PLEASE NOTE: If the above link does not work for you, your email application may be breaking the link into two pieces. You may be able to copy and paste the entire link address into the address field of your web browser.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]