Re: request to liaison with FWSI TC

[john c hardin <johnchardin@comcast.net>]

Thank you. We have meetings every other Thursday, with the next meeting on
May 12, 3:00PM Eastern Time
1-712-824-4400 (US call in number)
Participant Access Code 44999

Please plan to spend 15 - 20 minutes on the agenda describing the FWSI 
activities. We should then discuss the activities of the ebSOA group and how the 
two might interact.

Best regards,
john hardin

Lee Eng Wah, Dr wrote:
> Greetings Mr. Hardin,
> 
> Heard your name being mentioned a couple of times at the OASIS
> Symposium; and it would have been good if we have the opportunity to
> meet you.
> 
> However, I am glad that you have picked up our FWSI TC message that we
> are seeking liaison with ebsoa TC.   Initially we had discussions with
> Duane Nickel when the ebsoa TC was announced in April 2004 in New
> Orleans and as our work in the FWSI Functional elements
> (application-oriented not infrastructure) are based on component-based
> approach and SOA; it was therefore purposeful to follow-up the
> developments of ebsoa and in time to establish liaison with ebsoa TC to
> make use of its specifications.
> 
> On our side, we will sign up as members of your TC and in one of your
> Meeting explain to you our FWSI work and then to discuss on how we can
> make you of your TC recommendations.
> 
> Regards,
> Eng Wah LEE
> Co-chair FWSI TC
> 
> -----Original Message-----
> From: john c hardin [mailto:johnchardin@comcast.net] 
> Sent: Sunday, 01 May, 2005 7:21 PM
> To: ebsoa; Tan Puay Siew; Lee Eng Wah, Dr; rbpascual@yahoo.com;
> andytan@intrinix.net; James Bryce Clark
> Subject: request to liaison with FWSI TC
> 
> Dear Mr. Pascual and Mr. Lee,
> A suggestion has been made by Mr. Tan to request a liaison between the
> FWSI TC 
> and the ebSOA TC. We are engaged in work to define usage profiles and
> document 
> the Technical Architecture v2.0 for the current versions of the ebXML
> and 
> Service Oriented Architecture related specifications.
> 
> Best regards,
> John Hardin
> 
> 
> Here is some additional information:
> 
> Our statement of purpose:
> To provide a set of high-level usage profile examples accompanied by a
> technical
> architecture specification, with the purpose of illustrating the
> features and 
> benefits of e-Business Service Oriented Architectures based on OASIS 
> specifications, for managers and project teams.
> 
> The TC will:
> -- Assess the subsequent and related works noted herein and the
> implementation
> experience of the existing ebXML and Web Services specifications.
> -- Update the descriptive statements of existing ebXML and Web Services 
> specifications in an updated Technical Architecture document(s) to
> reflect the 
> subsequent approved versions, and the other developments and
> implementation 
> experiences described here.
> -- Assess the implement ability and interoperability of the multiple
> ebXML and 
> Web Services specifications, provide comments and suggestions to the TCs
> 
> managing the individual specifications, and identify gaps or future work
> (if 
> any) needed or desirable for useful complete implementations.
> -- Assess the implement ability and interoperability of other relevant
> approved 
> e-business and web services standards with one or more existing ebXML 
> specifications, provide comments and suggestions (if any) to the TCs and
> other 
> panels managing the relevant individual specifications, and (if the TC
> elects) 
> provide non-normative examples or suggestions for useful combinations
> and 
> extensions of the various specifications.
> -- Adhere to the requirements of the ebXML Requirements Specification
> [v1.06] 
> and/or later revisions.
> -- Provide an opportunity for each TC that manages an individual ebXML
> and/or 
> Web Service(s) specifications to comment on and correct any descriptions
> or
> characterizations of those specifications before they are incorporated
> into any 
> work approved by this TC.
> -- Not publish normative public guidance about an existing ebXML
> specification 
> that contradicts the approved text. Suggestions for change or extension
> should 
> be welcome and recorded, but expressed in a manner that does not
> undermine the 
> approved specifications as the primary source of ebXML technical
> guidance.
> 
> 
> Our full proposed charter (voting on this new version is in process):
> http://www.oasis-open.org/apps/org/workgroup/ebsoa/download.php/12106/eb
> SOA-TC-charter-v1.01-NTC-1.pdf
> 
> Technical Committee Home Pages:
> 
> http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ebsoa
> http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=FWSI
> 

-- 
~~~~~~~~~
john c hardin
Chair, OASIS ebSOA Technical Committee
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ebsoa
313.279.1377 new *VONAGE* number
mailto:john@crossconnections.ws

"The new electronic interdependence recreates the world in the image of a global 
village."

     Marshall McLuhan, "Gutenberg Galaxy", 1962