OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-jc message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [ebxml-jc] Changes for the <overviewURL>s in uddi-spec-tc-tn-uddi-ebxml-updatedoverviewURLs


Thanks Ian. If Jacques and Kathryn ratify, then we can send Luc the
final go-ahead on these tModel details.

I think Kathryn should speak to your question about the UDDI and ebXML
RegRep interactions, and what has been accomplished in terms of
co-existence and cooperation. Most of the activity I have browsed lately
has been on how to register the Core Component groups CCs, ACCs, BIEs
ABIEs and whatnot.

I think JAXR provides, at the client side, integrated access to the two
main flavors of registry. Maybe there is an approach to federation that
covers both registry flavors, so that you could access any cooperating
one and be referred or serviced--as appropriate--somewhere else? I think
UDDI could already be used to register WS accessors to ebXML services
since they did write WSDLs for WS style access to ebXML RegRep. Maybe
Kathryn can update us all when we next meet!


Dale



-----Original Message-----
From: ian.c.jones@bt.com [mailto:ian.c.jones@bt.com] 
Sent: Thursday, August 07, 2003 7:54 AM
To: Dale Moberg
Cc: ebxml-jc@lists.oasis-open.org
Subject: RE: [ebxml-jc] Changes for the <overviewURL>s in
uddi-spec-tc-tn-uddi-ebxml-updatedoverviewURLs
Importance: Low


Dale,

	I agree with your comments after discussion yesterday and
reading the document.  Messaging has the least impact on this as it is I
see it as a fixed one-off thing, the impact would be on the
implementers/users of BPSS/ CPP/A.

	Is a piece missing - a way to link from a UDDI registry to an
ebXML one?  I could see this being useful especially for those already
building ebXML registries.

Ian Jones
Chair OASIS ebXML Messaging Services TC 

Email: ian.c.jones@bt.com 



-----Original Message-----
From: Dale Moberg [mailto:dmoberg@cyclonecommerce.com]
Sent: 05 August 2003 23:16
To: ebxml-jc@lists.oasis-open.org
Subject: [ebxml-jc] Changes for the <overviewURL>s in
uddi-spec-tc-tn-uddi-ebxml-updatedoverviewURLs


Hi,

I made some proposed changes for overviewURLs in the tModel information
in the UDDI technical note on ebXML.

The attachment has the changes in context along with the replaced
information items. [Hey, this infoset lingo actually makes sense
occasionally!]

The taxonomy model tModel/overviewDoc/overviewURL is proposed to be
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ebxml-jc

This would mean that the JC home page could be edited to have the links.
We can edit these ourselves, and point off to ebxml.org for version 1.0
specs, to the TCs for OASIS specs > 1.0, and to UN/CEFACT for other
specs. While more work for us, it probably will end up making it easier
over the long haul as we don't have to negotiate with multiple
organizations for permissions , providing explanations, and so on.

Change tracking was on for the other changes. I asked Monica Martin to
check on the BPSS URL. I left the 1.0 overviewURLs pointing to ebxml.org
documents. The OASIS TCs are used for the other pointers for Messaging
and CPPA.

Should we meet to ratify this? Is tomorrow at 9 possible? Ian, I can
talk to you on the Messaging call tomorrow. Jacques and Kathryn, let me
know if you want to have a short call or else just post your reactions
on this to the list. I will edit the JC page to add the main links. It
is something that can be incrementally refined...


Thanks
Dale Moberg  <<uddi-spec-tc-tn-uddi-ebxml-updatedoverviewURLs.doc>> 

You may leave a Technical Committee at any time by visiting
http://www.oasis-open.org/apps/org/workgroup/ebxml-jc/members/leave_work
group.php


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]