[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: OASIS Specs and ebXML Registry (Was Re: [regrep] Concern regarding WSRP specs)
Just a thought here:
In the future, rather than waiting for comment periods of specifications
to come up to address this issue ("ebXML Registry does Web Services
too"), would it be beneficial for us to perhaps ask Karl Best to make an
OASIS-wide announcement asking all TCs that reference UDDI for Web
Services to also reference ebXML Registry as well?
Would this work? Is it even permissible?
Joe
Chiusano Joseph wrote:
>
> Works for me.
>
> "Breininger, Kathryn R" wrote:
> >
> > Looks like a usable (and flexible) framework. Maybe put headings in as noted below:
> >
> > Change Request:
> > The OASIS Registry TC would like to request that the [ADD SPEC NAME AND
> > VERSION HERE] be amended as follows:
> >
> > Current Text:
> > (insert)
> >
> > Proposed New Text:
> > (insert)
> >
> > Rationale:
> > (insert reasons)
> >
> > Additional Information:
> > (insert links, etc.)
> >
> > Kathryn
> > -----Original Message-----
> > From: Chiusano Joseph [mailto:chiusano_joseph@bah.com]
> > Sent: Wednesday, August 13, 2003 10:29 AM
> > To: Farrukh Najmi
> > Cc: Breininger, Kathryn R; ebXML Regrep (E-mail)
> > Subject: Re: [regrep] Concern regarding WSRP specs
> >
> > How's this for a framework that we can use not only for the WSRP spec,
> > but for others for which we will undoubtedly encounter the same issue:
> >
> > <Framework>
> >
> > Change the following text on p.[PAGE NUMBER]:
> >
> > [INSERT CURRENT TEXT HERE]
> >
> > to:
> >
> > [INSERT NEW TEXT HERE]
> >
> > We request this update because, as per the OASIS/ebXML Registry
> > specification version 2.0, an ebXML Registry has the ability to register
> > and maintain Web Services descriptions in the same general way that UDDI
> > does. Users may also discover Web Services in an ebXML Registry in the
> > same general way that they may do so in a UDDI Registry.
> >
> > More information on ebXML Registry's Web Services capabilities is
> > provided in the following Technical Note:
> >
> > [REFERENCE OUR TECHNICAL NOTE "REGISTERING WEB SERVICES IN AN ebXML
> > REGISTRY]
> >
> > </Framework>
> >
> > Joe
> >
> > Farrukh Najmi wrote:
> > >
> > > Chiusano Joseph wrote:
> > >
> > > ><Quote>
> > > >Farrukh has brought to my attention a concern
> > > ></Quote>
> > > >
> > > >I volunteer Farrukh. :)
> > > >
> > > For a variety of personal reasons I am reluctant to take on any mission
> > > critical tasks at the moment. Please excuse my temporary lack of ability
> > > to contribute. Thanks.
> > >
> > > >
> > > >"Breininger, Kathryn R" wrote:
> > > >
> > > >
> > > >>We should definitely submit a formal comment. Any volunteers for drafting the comment?
> > > >>
> > > >>-----Original Message-----
> > > >>From: Chiusano Joseph [mailto:chiusano_joseph@bah.com]
> > > >>Sent: Wednesday, August 13, 2003 10:01 AM
> > > >>To: Breininger, Kathryn R
> > > >>Cc: ebXML Regrep (E-mail)
> > > >>Subject: Re: [regrep] Concern regarding WSRP specs
> > > >>
> > > >><Quote>
> > > >>How would the TC like to address this issue?
> > > >></Quote>
> > > >>
> > > >>Vigorously.:)
> > > >>
> > > >>I believe there are at least 2 options:
> > > >>
> > > >>(1) Our TC can submit a formal comment to the WSRP TC (I assume?)
> > > >>(2) All Registry TC members can request that their OASIS representatives
> > > >>(if they are not individuals) disapprove the WSRP specs with the
> > > >>appropriate comment
> > > >>
> > > >>Other approaches?
> > > >>
> > > >>Joe
> > > >>
> > > >>"Breininger, Kathryn R" wrote:
> > > >>
> > > >>
> > > >>>Farrukh has brought to my attention a concern regarding the WSRP specs currently out for review, and would like to bring it up to the TC for discussion on if and how it should be addressed.
> > > >>>
> > > >>>The WSRP specs are in OASIS review prior to vote for becoming a standard. There is a statement in chapter 5 which states:
> > > >>>
> > > >>>"A Producer may be discovered through mechanisms such as [UDDI] or [WSIL], which also provide information concerning the capabilities of the service."
> > > >>>
> > > >>>and two additional reference to UDDI, but no references to ebXML or ebXML registries. Farrukh has suggested that the TC ask WSRP to also mention ebXML. How would the TC like to address this issue?
> > > >>>
> > > >>>Kathryn
> > > >>>
> > > >>>Kathryn Breininger
> > > >>>CENTRAL Project Manager
> > > >>>Emerging Technologies
> > > >>>Boeing Library Services
> > > >>>
> > > >>>425-965-0182 phone
> > > >>>425-237-3491 fax
> > > >>>kathryn.r.breininger@boeing.com
> > > >>>
> > > >>>You may leave a Technical Committee at any time by visiting http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.php
> > > >>>
> > > >>>You may leave a Technical Committee at any time by visiting http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.php
> > > >>>
> > >
> > > --
> > > Farrukh << File: Card for Joseph Chiusano >>
>
> ------------------------------------------------------------------------
> You may leave a Technical Committee at any time by visiting http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.php
begin:vcard n:Chiusano;Joseph tel;work:(703) 902-6923 x-mozilla-html:FALSE url:www.bah.com org:Booz | Allen | Hamilton;IT Digital Strategies Team adr:;;8283 Greensboro Drive;McLean;VA;22012; version:2.1 email;internet:chiusano_joseph@bah.com title:Senior Consultant fn:Joseph M. Chiusano end:vcard
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]