OASIS UDDI Specification TC

Face-to-Face Meeting Minutes

Minutes - UDDI Spec TC FTF Meeting, 20030211-12

Date:February 11-12 2003

Location: Microsoft Corporation

1065 La Avenida

Silicon Valley Campus, Bldg 1

Mountain View, CA94043

Chairs: Tom Bellwood, IBM,

Luc Clément, Microsoft,

Itinerary

Thuesday, 11 February2003

09:00 – 12:00TC meets

  • Attendance
  • Review meeting objectives
  • New Agenda Items
  • Process Items
  • ReviewTN on “UDDI Registry for ebXML Components
  • Review CR List (V3 Errata)

12:00 – 1:00Lunch

1:00-5:00TC meets

  • Complete Review of CR List (V3 Errata)

Wednesday, 12 February 2003

9:00 – 12:00TC Meets

  • Complete Review of CR List (V3 Errata)
  • Reports from Subcommittees

12:00 - 1:00Lunch

1:00-4:00TC meets

  • TaxonomyTN Proposal
  • V4 Discussion
  • Discussion of Additions to Agenda
  • Review of meeting ARs
  • Next Telecon and FTF

4 pmAdjourn

Agenda

  1. Attendance
  2. Additions to Agenda
  3. Approval of Previous Minutes
  4. Old Business
  5. New Business
  6. Discussion of Additions to Agenda
  7. Upcoming Meetings

1Attendance

Attendance was taken. The following members where presents at the FTF:

Member Name / Company or Organization / E-mail id
Bellwood, Tom / IBM /
Cahuzac, Maud / France Telecom /
Candadai, Arun / Asera /
Cho, Pyounguk / Iona /
Clement, Luc / Microsoft /
Felsted, Patrick R. / Novell Inc. /
Feygin, Daniel / Unitspace /
Hately, Andrew / IBM /
Ioannides, Demetrios / Individual /
Kawai, Aikichi / NTT /
Kibakura, Keisuke / Fujitsu /
Lee, Eric / Microsoft /
Lee, Sam / Oracle /
Rogers, Tony / Computer Associates /
Srivastava, Alok A. / Oracle /
von Riegen, Claus / SAP AG /
Zagelow, George / IBM /

Regrets were received from:

Member Name / Company or Organization / E-mail id
Anderson, Steve / OpenNetwork /
Alban, Hedy / Max Shevet Consulting /
Atkinson, Bob / Microsoft /
Boubez, Toufic / Layer Seven Technologies /
Carrer, Marco / Oracle /
Chalimeda, Naresh / Tata Consultancy Services /
Colgrave, John / IBM /
Corda, Dr. Ugo / SeeBeyond Technology /
De Nicola, Mike / Fujitsu /
Dadbhawala, Dharmesh / Iona /
Dovey, Matthew / OxfordUniv. /
Drake, Trey / Sun /
Gadbois, David / Sun /
Garg, Shishir / France Telecom /
Hashida, Yukio / NTT /
Henry, Brad A. / NCR /
Hunter, Ian D. / TIBCO /
Macias, Paul A. / LMI /
Parham, Jeff / Microsoft /
Patil, Sanjaykumar / Iona /
Reed, Archie / Critical Path /
Stephens, Bruce / BEA /
Thomas Manes, Anne / Individual /
Turner, Kirby / Individual /
Voskob, Max / MSI Business Solutions /
Wahl, Mark / Sun /

2Identify Additions to Agenda

  • IANA submission of UDDI URI scheme registration – need to review IP statement issue recommendations from IETF.
  • KAVI system

3Approval of Previous Minutes

MOTION: Move to approve the last minutes posted at

Motion to accept the minutes was approved: minutes approved

4Old Business

4.1Review of AR List

We reviewed, obtained status from AR ownersand updated the AR List posted at: The following summarizes the discussion and status of the ARs discussed as part of day-1’s review of the AR list.

Item No. / TC Position / Description / Assigned To / Status / Due Date
AR 005 / Approved / Obtain feedback from the WS-I BP subcommittee with respect to modifying the UDDI V3 WSDL to comply with WS-I's suggested restraint on use of <wsdl:import>. Proposed changes can be found in the Minutes of the Face-to-Face 20021111 - 20021112 / Claus von Riegen / The WS-I accepted UDDI's proposed <wsdl:import> approach.
WS-I will be running UDDI WSDL through their test tools.
We are waiting for feedback from John Colgrave to determine whether to close this item; John had suggested that there were issues. / 4-Mar-03
AR 007 / Approved / Prepare the submission document that will be used to register the uddi: scheme / Andrew Hately / Andrew working on this. IP rules need to be identified with the registration at IANA.
CR009 should be dealt with before registering the syntax.
The topic of IP rules regarding the registration of the uddi: scheme with IANA was added as an agenda item for the FTF to be covered day-2. / 4-Mar-03
AR 008 / Approved / Register the scheme for V3 Entity Case Folding / Tom Bellwood or Luc Clement / Waiting for 007 completion / dependent on AR 007
AR 009 / Approved / Review errata process on OASIS Stds and report back / Tom Bellwood / Item delayed until 15 Feb when Tom will contact Chris Kurt on latest process proposed. / 15-Feb-03
AR 010 / Approved / Draft the errata process for OASIS standard based on Bill's feedback / Tom Bellwood / Still open / 15-Feb-03
AR 016 / Approved / Update Key partitions TN. / Pat Felsted / In progress / 4-Mar-03

Discussion – please note that the AR list has been updated. See for latest version.

4.2Status of V2 Standardization Process

As you can see from recent OASIS news, the 30-day public review period for the UDDI V2 specification started on 2/3/2003. Comments will be taken in the uddi-comment email list. At the conclusion of the 30-day formal review period, the TC will need to consider any issues raised and decide on their disposition prior to submitting the V2 specification to OASIS vote as an OASIS Standard. During this month, we will need to track the uddi-comment group closely and respond as necessary to threads started there as part of this review.

Discussion:

We will be collecting all comments made on the V2 spec from the uddi-comment mail group during the official review period. All of these must be addressed. If the TC feels that any require changes to the specification, we start over. Otherwise the TC documents how they wish to address each item and includes this in a package with our formal request for the OASIS board to vote on UDDI V2 as an OASIS Standard.

Luc encouraged each of the TC members to insure their company representatives vote on this once the board considers UDDI V2.

4.3Directing Your Annual Dues to the UDDI Member Section

George gave an overview of Member Sections and their role as umbrellaorganizations for one or more TCs. For UDDI, the Member Section ishandling ancillary tasks for the Spec TC, such as budget, marketing, etc.While there is currently only one TC, there is growing support for creating a Marketing "TC". The advantages of participation at the MS level are participation in election of the Board of Directors, serving on the board, election of theChair of the board, and serving as Chair. We will likely have an electionof part of Board this summer, and it would be good to have a larger pool of potential board members.

There is also a financial incentive for joining the Member Section. Apercentage of OASIS dues are routed to the Member Section, which we can useto promote UDDI. The Board believes we need to do a much better job ofpromoting UDDI to cement UDDI as a key technology for Web Services.

Promotion could be in the form of white papers, trade show participation,publishing of best practices, documenting customer references, etc. Wehave considerable revenue coming in from the current MS members, but more members would give us that much more resource to use to promote UDDI.

George asked that the TC members seriously consider having their companiesjoin the Member Section. Under current OASIS rules, that would bepossible at the time OASIS membership is renewed (although we could lobbyto change the OASIS rules). George is available at any time forquestions.

4.4UDDI Registry for ebXML components

Keisuke Kibakura walked us through the TN. During the course of the discussion we identified a number of issues that needed to be addressed. These are described below.

  1. tModel Naming Conventions. We noted that the naming convention used to name the tModels (e.g. tModel Name:ebxml-org:specifications) should align to naming conventions adopted by the ebXML community.
  2. Doman Name Keyspace. We noted that the keyspace proposed for use did not satisfy the need to the ebXML community to own and manage its keyspace (e.g. tModel UDDI Key (V3): uddi:ubr.uddi.org:categorization:ebxml.org:specifications) and that it should be altered to the following: uddi:ebxml.org:specifications. We expressed the need for input from the ebXML community.
  3. overviewURL. We identified the need for the ebXML TCs to validate the URLs proposed for the overviewURLs of the tModels identified.
  4. The above led us to conclude that consultation with the ebXML TC was warranted and we would express to them a desire to comment and validate the modeling, recommendations, naming and propsed keyspaces
  5. There was agreement for the need to provide rationale of modeling a CPP as a businessService. We felt that this was important given that ebXML audience whom the TN is directed at.
  6. In light of the above, we felt it important to provide a list of definitions that would help readers understand UDDI terminology. As such, references to the V3 glossary and use of footnotes would be made to provide explanatory text.

AR 017: (target – 14 Feb 03) Alok to draft the rationale (per 5. above); we need to have this validated.

AR 018: (target – 19 Feb 03) Keisuke-san to take Alok’s input as well as the input received during the course of the meeting and issue a draft to the Editors.

AR 019: (target – 26 Feb 03) As Editors, Daniel, Tony, Lucwill edit and return to Keisuke-santhe document. Keisuke-san will resubmit the TC for comment.Target date is 26 Feb - in time for the 4 March telecom; this is dependent on input from Alok and Keisuke-san.

AR 020: There was a suggestion that the TN would be submitted for comment via various (UDDI-member company) members to the various ebXML TCs. The specific approach remains TBD. Chairs to address.

4.5Review of CR List

We reviewed the CR List posted at:

Note that this file has been updated on the OASIS site – please refer to it for current status. Also note that most of the CR documents have been renamed to add the CR number. This should make sorting simpler. The example in the template also reflects this format change.

The goal of the FTF review was to cover CRs that have not yet been accepted for inclusion as errata; discuss them; and proceed to informal vote for their inclusion into the next errata bucket as applicable.

CR Authors entertained the TC by their presentations of each CR. Followingis the result of the review:

4.5.1CR-001

CR # / Document Identifier / Title / Action / Authors / Editor
CR-001 / uddi-spec-tc-cr-utf16-20021025 / Adoption of UTF-16 / Claus von Riegen

Claus walked us through the CR. There was discussion as to whether we should mandate utf-8/utf-16 on the client; the rationale for doing so is that the server may return utf-16.Motion to add to the bucket was made.

We agreed to accept this CR for inclusion in the V3 bucket.

4.5.2CR-002

CR # / Document Identifier / Title / Action / Authors / Editor
CR-002 / uddi-spec-tc-cr-typos-20030110 / Consolidated Typos & Errors from 11/11 FTF / Tom Bellwood

Tom is still collecting input on this CR. We reviewed further input at the FTF – see below.

4.5.3CR-007

CR # / Document Identifier / Title / Action / Authors / Editor
CR-007 / uddi-spec-tc-cr-httptmodel-20021119 / http transport tModel Definition / Anne Thomas Manes

We want to split this CR into two. We tentatively agree to revert to the tModel description back to what it was in V2.

The optional suggestion to add a new tModel needs to be submitted as a new CR; arguably, it should be resubmitted as a TN (see below).We also need to determine which activity is dependent (if at all) on it.

Given the number of tModels being created by the “Using WSDL in a UDDI Registry, Version 2.0”, “UDDI Registry for ebXML Components” and others to come, Luc suggested that we need to identify a general framework for posting and promoting new tModels rather than issuing an erratum to the spec. No decision made. This topic will be taken up on a future call.

AR 020: Anne to resubmit CR-007 as two CRs. CR-007 should request that the tModel description be returned back to that of V2. The other should be resubmitted as a TN defining a new tModel.

4.5.4CR-008

CR # / Document Identifier / Title / Action / Authors / Editor
CR-008 / uddi-spec-tc-cr-subscriptionresults-20021206 / Subscription Results Design / Daniel Feygin

There is agreement with the CR.Daniel suggested removing “list” from the “subscriptionResultsList” result structure given that it is redundant. We discussed this and concluded that other structure had the same problem. That said, this was done for consistency with other API result structure and given this we opted to keep the names as is.

We agreed to accept this CR for inclusion in the V3 bucket.

4.5.5CR-009

CR # / Document Identifier / Title / Action / Authors / Editor
CR-009 / uddi-spec-tc-cr-009-20030121 / Correction for legal key characters / John Colgrave

We discussed the CR at length. At issue was whether to open up the v3 spec allowing IP addressed in the keying scheme. Tony pointed out that we had accepted the “recommended” keying scheme as the normative keying scheme and as such, there is further justification for not accepting the IP discussion

AR 021: Andrew is making a change and reposting to allow John to comment.

This should be tracked as a v4 item

4.5.6CR-010

CR # / Document Identifier / Title / Action / Authors / Editor
CR-010 / uddi-spec-tc-cr-isreplacedby-20030121 / IsReplacedBy tModel / Anne Thomas Manes

We want and agree to generalize the behavior ensuring that isReplacedBy can be used in situations where the relationship is more than a 1:1. Specifically, at issue is cardinality of relationships: 1:1, 1:many, many:1, many:many; these suggest different usages and thus represent either use of categorization or identification.

We concluded that if we were to create a new tModel, we would categorize it as a categorization rather than an identifier system.

We agreed to fix the spec and fix the definition of identifier in the glossary.

Finally, we concluded that any related tModel should be considered as part of a TN/BP and considered for v4 for inclusion.

We agreed to update the definition of the identifier in the glossary ( refers).

AR 022: Action items:

  • Andrew to post to the list on this topic
  • Wait for Anne's reply to Andrew’s note
  • Allow Daniel and Claus to clarify their position based on Anne's reply.

4.5.7CR-011

CR # / Document Identifier / Title / Action / Authors / Editor
CR-011 / uddi-spec-tc-cr-11-20030113
schema: / uddi:overviewDocument complex type contains redundant sequence element / Max Voskob

We agreed to accept this CR for inclusion in the V3 bucket.

We discussed the need to surface schema changed being introduced in the specification to theSDK developer community; this is a general matter that we’ll need to address as part of the errata process

4.5.8CR-012

CR # / Document Identifier / Title / Action / Authors / Editor
CR-012 / uddi-spec-tc-cr-virtualdeletesinsubscription-20030123
PPT: / Handling virtual deletes in subscription / Claus von Riegen

We concluded that:

  1. The behavior ofissuing repetitive virtual deletes (or not) should be non-prescriptive; clients should be informed of this potential server behavior though.
  2. In the case where an“add” and a “delete” occur within the subscription window, we need to be prescriptive and state that a node MUST not return the entity at all (given that the return structure does not allow for it).

AR 023: Claus to update the CR.

4.5.9CR-013

CR # / Document Identifier / Title / Action / Authors / Editor
CR-013 / uddi-spec-tc-cr-custodytransferkeybagsubset-20030120 / Handling subsets of approved keyBag in transfer_custody message / Claus von Riegen

We agreed to accept this CR for inclusion in the V3 bucket.

4.5.10CR-014

CR # / Document Identifier / Title / Action / Authors / Editor
CR-014 / uddi-spec-tc-cr-hwmvectorandexcludednodes-20030120 / High water mark vector and excluded nodes / Claus von Riegen

We agreed to accept this CR for inclusion in the V3 bucket.

4.5.11CR-015

CR # / Document Identifier / Title / Action / Authors / Editor
CR-015 / uddi-spec-tc-cr-listdescriptionoptionality-20030120 / Is listDescription required or optional? / Claus von Riegen

We agreed to accept this CR for inclusion in the V3 bucket.

Note: this CR does not apply to v2 as suggested in the document header.

4.5.12CR-016

CR # / Document Identifier / Title / Action / Authors / Editor
CR-016 / uddi-spec-tc-cr-keyGeneratorTmodelVisibility-20030120 / Key generator tModel visibility / Claus von Riegen

We agreed to augment the paragraph to augment the behaviour in the presence of the save and specifyan error code to be returned. There is a general agreement that the E_keyUnavailable would be used.

We edited the CR at the meeting. The document was reposted by Tom as

We agreed to accept this CR for inclusion in the V3 bucket

4.5.13CR-017

CR # / Document Identifier / Title / Action / Authors / Editor
CR-017 / uddi-spec-tc-cr-operationalinfoformovedentities-20030120 / Effect of moving contained entities on operational info / Claus von Riegen

We edited the CR at the meeting (corrected a typo in the problem outline). The document was reposted by Tom as

We agreed to accept this CR for inclusion in the V3 bucket.

4.5.14CR-018

CR # / Document Identifier / Title / Action / Authors / Editor
CR-018 / uddi-spec-tc-cr-ownershipcheckbeforemove-20030120 / Ownership check before move / Claus von Riegen

We agreed to accept this CR for inclusion in the V3 bucket.

4.5.15CR-019

CR # / Document Identifier / Title / Action / Authors / Editor
CR-019 / uddi-spec-tc-cr-keytypecheckduringpublication-20030120 / Key type check during save operations / Claus von Riegen

We edited the CR during the meeting for typos. The document was reposted by Tom

We agreed to accept this CR for inclusion in the V3 bucket.

4.5.16CR-020

CR # / Document Identifier / Title / Action / Authors / Editor
CR-020 / uddi-spec-tc-cr-tmodelcorrections / Miscellaneous corrections to tModels in Chapter 11 / Andrew Hately

We agreed to accept this CR for inclusion in the V3 bucket.

4.5.17CR-021

CR # / Document Identifier / Title / Action / Authors / Editor
CR-021 / uddi-spec-tc-cr-elementformdefaultincustody
Schema 1:
Schema 2: / Custody schema should have elementformdefault=”qualified” / Andrew Hately

We agreed to accept this CR for inclusion in the V3 bucket.

4.5.18CR-022

CR # / Document Identifier / Title / Action / Authors / Editor
CR-022 / / service projection move / Andrew Hately

AR 024: Andrew to update the CR. Luc to forward the master to the diagram used in the CR to Andrew.Andrewis going to update the problem statement with state diagrams of where things go wrong when the "dangling" behavior is used for moved service projections during replication.

4.5.19CR-023

CR # / Document Identifier / Title / Action / Authors / Editor
CR-023 / / v2 v3 key mapping / Andrew Hately

Resend to author: review the policy section and move the new para proposed for 10.1.1 to a more appropriate location

AR 025: Andrew to update the CR

4.5.20CR-024

CR # / Document Identifier / Title / Action / Authors / Editor
CR-024 / / discard transfer token / Andrew Hately

We agreed to accept this CR for inclusion in the V3 bucket.

4.5.21CR-025

CR # / Document Identifier / Title / Action / Authors / Editor
CR-025 / / error on multiple get_transferToken / Andrew Hately

We agreed to accept this CR for inclusion in the V3 bucket.