Subject: RE: [fwsi] Re: [soa-rm] JtC = cross post solution (was) ... Re: The real SOA challenge?
Perhaps a mapping of the FWSI Functional Elements to the future SOA Blueprints and SOA-RM reference architecture(s) might be valuable for adoption and connect-the-dots purposes? Joe Joseph Chiusano Associate Booz Allen Hamilton 700 13th St. NW Suite 1100 Washington, DC 20005 O: 202-508-6514 C: 202-251-0731 Visit us online@ http://www.boozallen.com > -----Original Message----- > From: Tan Puay Siew [mailto:pstan@SIMTech.a-star.edu.sg] > Sent: Tuesday, November 29, 2005 12:50 AM > To: John Hardin; James Bryce Clark > Cc: email@example.com; firstname.lastname@example.org; > email@example.com; > firstname.lastname@example.org; email@example.com > Subject: RE: [fwsi] Re: [soa-rm] JtC = cross post solution > (was) ... Re: The real SOA challenge? > > Hi All > I personally like the cross-TC idea that Jamie proposed. > > Just a thought from FWSI point-of-view. In the FWSI work, we > are more concern with defining the needed functionalities for > web services applications. These applications are expected to > be developed based on the SOA paradigm. However, we have not > and do not intend to articulate any architecture in the > specifications. As such, we would greatly welcome any > thought/mind-share on SOA or just service architectures. > > Look forward to hear/see what Jamie has in mind in greater details > > Rgds > -ps- > > > -----Original Message----- > From: John Hardin [mailto:firstname.lastname@example.org] > Sent: Friday, November 18, 2005 6:45 AM > To: James Bryce Clark > Cc: email@example.com; firstname.lastname@example.org; > email@example.com; > firstname.lastname@example.org; email@example.com > Subject: [fwsi] Re: [soa-rm] JtC = cross post solution (was) > ... Re: The real SOA challenge? > > > I think this is a great idea. I'm looking forward to the conversation > Jamie. > > James Bryce Clark wrote: > > 1. Reply to Joe and John: I hope so. > > 2. Request to all: This interesting but long thread > is going on > > in > > five e-mail lists. These TCs have much in common, that > properly is a > > basis for further chat, but while maintaining the separate and > > independent activities of each TC. I would like to suggest a > solution. > > It would take some duplicate traffic off these lists, and provide a > > place for these cross-TC, SOA-oriented coordination conversations. > > I suggest that these 5 TCs consider starting a "service > architecture > > joint committee." The rules of that OASIS structure can be > found at > > http://www.oasis-open.org/committees/process.php#2.16. It does not > > require any surrender of each committee's own work plan or > views, but > > would provide a forum for discussion of possible voluntary > > coordination. I will take this up further with your > committee chairs, > > > and discuss what kind of charter/outline might work. If > the TCs (or > > some subset of them) wish to do so, a JtC would create a > place where > > matters of joint interest can be more effectively discussed. > > Regards Jamie > > > > ~ James Bryce Clark > > ~ Director, Standards Development, OASIS > > ~ firstname.lastname@example.org > > > > At 08:39 AM 11/17/2005, Chiusano Joseph wrote: > > > >>> From: John Hardin [mailto:email@example.com] > >>> Sent: Thursday, November 17, 2005 10:29 AM > >>> * * * > >>> We are working these three items into the next generation of the > >>> OASIS Technical Architecture. > >> > >> > >> I believe you meant to say "ebXML Technical Architecture"? Joe > > > > > > > > > > -- > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > | john c hardin > | Chief Technology Officer > | http://www.maphin.net > | 606.598.7353 office > | 606.813.4316 cell > | mailto:firstname.lastname@example.org > | > | Chair - OASIS ebSOA Technical Committee > | http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ebsoa > | > | > | "The new electronic interdependence recreates the world in the > | image of a global village." > | > | Marshall McLuhan, "Gutenberg Galaxy", 1962 > |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > >