RE: Minutes July 16

["Dale Moberg" <dmoberg@cyclonecommerce.com>]

Title: Message

We can use current URLs for each specification and for the schema files located at the OASIS web sites for our TCs.

But their overall URL for the "taxonomy tmodel" is one we cannot readily supply without doing some work. That is the holdup IMO.

 

So I would have the following comment summary by section

 

 

2.2.3 Taxonomy tModel -- we need to create a good overviewURL value

2.2.4 Common ebXML models -- use the uddi:ebxml.org: prefix for the version 1 specifications (in practice, don't care about those now anyway...)

        But use an Oasis based uddi:oasis-open.org for version 2 and higher specifications.

        I wanted to see how Karl Best was doing

        on his project to come up with names and try to align with that.

        CPPA needs to come up with 3 version 2_0 URIs for UDDI for template, cpp, and cpa (would anyone really register their CPAs in a public registry? )

 

I thought their summary of functionality was succinct and accurate even if the differences between composition and negotiation processes were munged together. (They are in

the same ballpark of leading to an accepted CPA...)

 

The only additional thing that we would need for CPPA futures is some way to identify the negotiation service and endpoint. But if/when we create WSDLs for those, we would just use UDDI wsdl conventions I guess.

 

 

Dale

 

 

-----Original Message-----
From: Breininger, Kathryn R [mailto:kathryn.r.breininger@boeing.com]
Sent: Wednesday, July 16, 2003 2:47 PM
To: Dale Moberg; ebxml-jc@lists.oasis-open.org
Cc: Karl F. Best; James Bryce Clark
Subject: RE: Minutes July 16

In our discussion this morning we also talked about having them reference the primary source for the schemas (the oasis-open.org/committees/documents URL for each TCs documents).  I think we were under the impression they wanted one overview page to reference, which as Dale noted in the minutes does not currently exist.  It sounds like they would be fine with referencing the URLs each TC uses for documents at oasis-open.org/committees/documents.  Is this how you understand Luc's note below?  My preference is that they reference the primary source, since this is stable and maintained by OASIS.

 

Kathryn

-----Original Message-----
From: Luc Clement [mailto:lclement@windows.microsoft.com]
Sent: Wednesday, July 16, 2003 11:34 AM
To: Dale Moberg; ebxml-jc@lists.oasis-open.org
Cc: Tom Bellwood; jdurand@fsw.fujitsu.com; ian.c.jones@bt.com; Breininger, Kathryn R; Karl F. Best; James Bryce Clark
Subject: RE: Minutes July 16

 Thanks for getting back to Tom and I on this. Are there not other URLs we could reference perhaps those managed by the TC and/or OASIS? Of course, these URLs would need to remain static so as to not invalidate registered tModels.

When can expect a coordinated response to (per the attached):

a. obtain review of the TN

b. assign or confirm the appropriateness of the current assignments of the following:

 

·         tModel Names (e.g. ebxml-org:specifications)

·         overview document URLs used to point to ebXML specifications (e.g. http://www.ebxml.org/specs/index.htm)

·         keyspace used for UDDI v3 tModel keys (e.g. uddi:ebxml.org:specifications)

 

....

 

If, as a conclusion of your review, you would prefer for these names and keyspaces to be assigned by the UDDI TC within its own namespace, please let Tom and I know and we will do so.

Thanks in advance for your time and consideration of this matter.

Luc Clément
Microsoft
Co-chair, OASIS UDDI Spec TC

-----Original Message-----
From: Dale Moberg [mailto:dmoberg@cyclonecommerce.com]
Sent: Wednesday, July 16, 2003 11:15
To: ebxml-jc@lists.oasis-open.org
Cc: Luc Clement
Subject: Minutes July 16


Attendance

Jamie C
Kathryn B
Jacques D
Dale M


The JC meeting reviewed the UDDI questions about use of identifiers in tModels for ebXML.

Specific issues arose concerning identifiers involving ebxml.org, for example in

<overviewDoc>
    <overviewURL>http://www.ebxml.org/specs/index.htm</overviewURL>
</overviewDoc>


While OASIS maintains the page on the above overview url, it is not kept updated with the latest OASIS (or even UN/CEFACT) products.

Also the site is, at this point, secondary to the OASIS sites and other sites.

So we think we need to consult with the JCC to see whether an adequate update policy could be adopted _or_ produce a new summary page for at least the OASIS side of the groups. Also, there was some discussion that we should work with OASIS on their new definitive naming rules for specs and conform with these. These rules are still in process.

Dale took an action item to notify Luc of UDDI that our decision could not be made today. We will initiate inquiries to find out about new pages for the overview URL and policy clarifications surrounding naming conventions within OASIS. It may be necessary to also involve the UN/CEFACT side of specifications for what they wish to do.

We did not take up the other agenda item for JCC to set policy on "highly aligned but loosely coupled"