[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [regrep] Meeting reminder and agenda
People are interested in and are pursuing the registration of ebXML components and services within UDDI registries. To accomplish this, a key tenet of UDDI ism in this case, the ebXML organizations, agree to and possibly act as the caretakers and owners of their own taxonomies. For instance, as some want to register ebXML components and services in a UDDI registry they should utilize a taxonomy that is well understood (and possibly maintained) by ebXML-interested and cognizant parties. A very simple taxonomy has been proposed within the UDDI TN for this purpose and the author and editors of the TN are doing the right thing by requesting the relevant ebXML TCs to review this simple taxonomy. It sounds like Paul has volunteered (or at least asked) to talk with those ebXML relevant TCs. Helping him to accomplish this task is a small step toward interoperability and corporation between ebXML and UDDI registries. Joel Munter, Intel desk: 480.552.3076 cell: 602.790.0924 -----Original Message----- From: MACIAS, Paul [mailto:PMACIAS@lmi.org] Sent: Thursday, March 06, 2003 9:49 AM To: Chiusano Joseph Cc: Breininger Kathryn R; ebXML Regrep (E-mail) Subject: RE: [regrep] Meeting reminder and agenda Yeah, sorry for confusion. I should have been better at reviewing my responses. Just hope I eventually got there. :) I agree that this is an issue beyond any one ebXML community. I really think that UDDI intended for me to go to MS and CPPA and see if they agree on things like the definitions (2.1) and the concepts that represent their specs in parts like 2.2.3 and 2.2.4 . Which I do intend to do. But, I think the coordination of ebXML concepts that have representations among various ebXML TC specs (and in other OASIS TCs as UDDI is doing) helps to reinforce the concepts in all the specifications. I do not participate in any of the other ebXML TCs so I'm trying to get the issue in front of them. Any recommendations on how I should go about it would be greatly appreciated. Thanks, Paul -----Original Message----- From: Chiusano Joseph [mailto:chiusano_joseph@bah.com] Sent: Thursday, March 06, 2003 11:17 AM To: MACIAS, Paul Cc: Breininger Kathryn R; ebXML Regrep (E-mail) Subject: Re: [regrep] Meeting reminder and agenda That's completely different than what I conveyed from your original request. ;) As you know, "language" is such a broad term - specific, concrete examples from the UDDI document and their relevance to this issue would be very helpful. It's also possible that this issue is for a "higher" committee to consider - such as one of the joint committees - as it involves cross-TC issues. Joe "MACIAS, Paul" wrote: > > I'm using namespace in the sense of an area for managing registered objects, not the technical namespace. So don't look for a technical representation of "namespace". If that's still confusing just ignore it, because it's not the core issue. > > The point is that UDDI would like to to know whether their language properly represents language from the ebXML specifications. Now, the owning ebXML TCs can and should make that analysis to ensure the intenet of their specifications is acurately reflected. But I thought (hoped) that there has been some coordination on common language between ebXML Reg/Rep and the other ebXML specification that we could still provide a set of eyes to consider that part of the UDDI request. Such an exercise would help insure that our own specification properly aligns in language used by the other TCs. I'm not talking about using the same glossary (though I think that should be the case IMHO.) Rather, think about how we have rolled in ebMS and ebXML CPPA and see if we are all being consistant. Does that make sense? Seem worth while? > > Thanks, > > Paul > > -----Original Message----- > From: Chiusano Joseph [mailto:chiusano_joseph@bah.com] > Sent: Thursday, March 06, 2003 10:44 AM > To: MACIAS, Paul > Cc: Breininger Kathryn R; ebXML Regrep (E-mail) > Subject: Re: [regrep] Meeting reminder and agenda > > Thanks - please see below. > > <Quote> > The UDDI TC would like ebXML community validate, > 1) the naming conventions used to identify the ebXML namespace aligns > with ebXML conventions, and > 2) the URLs in the overviewURL elements are correct. > </Quote> > > Regarding (1) - Still unclear what you mean. There is no mention of > namespace in this entire document. Also what are "ebXML conventions" for > namespaces? None exist as far as I know. > > Regarding (2) - Can't this simply be done by verifying the URL in a > browser (i.e. anyone can do this)? Perhaps the UDDI folks mean something > else? > > If it would help, perhaps you can have an additional UDDI TC member > clarify this request for us so we don't keep going around in circles. > Don't mean to be harsh, just that business is business. > > Joe > > "MACIAS, Paul" wrote: > > > > Joe, > > > > Certainly. The paper focuses on explaining how a to implement registration of web services based on ebXML CPPA activities. The paper proposes a taxonomy for ebXML specifications. However, UDDI believes that the ebXML community is the proper owner of such a taxonomy and changed the tModel Keys to create an ebXML namespace if you will. > > > > Sections 2.2.3 & 2.2.4 define the ebXML related tModels. You'll see in schema an "overviewURL" element that is intended to link to a ebXML location for the framework/specification related to the tModel. > > > > The UDDI TC would like ebXML community validate, > > 1) the naming conventions used to identify the ebXML namespace aligns with ebXML conventions, and > > 2) the URLs in the overviewURL elements are correct. > > > > There is not an ebXML Reg/Rep spec involved in the UDDI paper, so the second issue really is something for other ebXML TCs to validate. But we may want to consider the first issue on ebXML naming conventions. I am in the process of trying to get these questions in front of the ebXML MS and CPPA TCs as well. > > > > If there is any questions or comments, please let me know. > > > > Thanks, > > > > Paul > > > > -----Original Message----- > > From: Chiusano Joseph [mailto:chiusano_joseph@bah.com] > > Sent: Thursday, March 06, 2003 10:04 AM > > To: MACIAS, Paul > > Cc: Breininger Kathryn R; ebXML Regrep (E-mail) > > Subject: Re: [regrep] Meeting reminder and agenda > > > > Paul, > > > > <Quote> > > the TC would like our input on a Namespace and URLs associated with > > the Note. > > </Quote> > > > > Regardless of whether or not we have the opportunity to discuss this on > > the call today, I would recommend that you provide more details on such > > requests when you present them to the listserv. That will help spark > > discussions that can be very valuable in the time leading up to our > > discussions on a call. It would also help us better prepare to offer > > points of view. > > > > I am very familiar with this paper, having read a preliminary version of > > it. However, I'm not sure what you mean by Namespaces and URLs. Please > > provide more details. > > > > Respectfully, > > Joe > > > > "MACIAS, Paul" wrote: > > > > > > Kathryn, > > > > > > If time permits I'd like to add a discussion item I'm bringing forward from UDDI. The UDDI TC is preparing a Technical Note on UDDI as a registry for ebXML components, and the TC would like our input on a Namespace and URLs associated with the Note. The document is undergoing some editing, but I've attached a recent version. > > > > > > Thanks, > > > > > > Paul > > > > > > -----Original Message----- > > > From: Breininger, Kathryn R [mailto:kathryn.r.breininger@boeing.com] > > > Sent: Wednesday, March 05, 2003 4:57 PM > > > To: ebXML Regrep (E-mail) > > > Subject: [regrep] Meeting reminder and agenda > > > Importance: High > > > > > > This is a reminder of our ebXML Reg/Rep telecon tomorrow, March 6th, at 1:30 pm Pacific Time. This is our regular bi-weekly telecon, and is scheduled from 1:30-3:30. Call in information is below: (pass code is correct!) Joe may not be available for this telecon due to a conflict, so we will postpone his items until next time if he is not on the line. > > > > > > USA domestic toll free number: 1-866-235-8350 > > > Pass code: 669014# > > > Here is the phone number for the operator if you have any problems: > > > 206-655-2254. > > > > > > Agenda: > > > 1. Minute taker > > > 2. Approval of minutes from last meeting (correction) > > > 3. Status on specs, review of changes (chapter 12, Generic Header, Users and Organizations, etc.) > > > 4. Namespace discussion - any resolution? > > > 5. Review of action items for spec > > > 6. Position paper update > > > 7. OASIS Forum on the Direction of Web Services - Report out > > > 8. Discussion on CCTS implementation in Registry (if Joe is available) > > > 9. Best Practice Paper (if Joe is available) > > > 10. Other issues/items > > > 11. Next meeting > > > > > > Please let me know if there are additional items you would like added to the agenda. > > > > > > Thanks. > > > > > > Kathryn Breininger > > > CENTRAL Project Manager > > > Emerging Technologies > > > Boeing Library Services > > > > > > 425-965-0182 phone > > > 425-237-3491 fax > > > kathryn.r.breininger@boeing.com > > > > > > ---------------------------------------------------------------- > > > To subscribe or unsubscribe from this elist use the subscription > > > manager: <http://lists.oasis-open.org/ob/adm.pl> > > > > > > ------------------------------------------------------------------------ > > > Name: uddi-spec-tc-tn-uddi-ebxml-20030227.doc > > > Type: Microsoft Word Document (application/msword) > > > uddi-spec-tc-tn-uddi-ebxml-20030227.doc Encoding: BASE64 > > > Description: uddi-spec-tc-tn-uddi-ebxml-20030227.doc > > > Download Status: Not downloaded with message ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl> ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]