[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Minutes of the UDDI Spec TC Telecon 20040810
Minutes of UDDI Spec TC Telecon
Date: 20040810
Chairs: Luc Clément, Systinet, luc.clement@systinet.com Tony Rogers, Computer Associates, Tony.Rogers@ca.com Logistics TC Telecon. Call hosted by Pete Wenzel, SeeBeyond. Call details:
· Toll free: Not available · Toll: +1 630-424-4862 · Participant Passcode: 9308381# · NOTE: *6 to mute, #6 to unmute
UTC: Tue-19:30, Seattle: Tue-12:30, New York: Tue-15:30, London: Tue-20:30, Frankfurt: Tue-21:30, Moscow: Tue-23:30, Tokyo: Wed-04:30, Sydney: Wed-05:30, Auckland: Wed-07:30 Agenda
3 Approval of Previous Minutes 5.1.1 AR002: Update to the Key Partitions TN 5.1.2 AR054 Resubmission of IETF publication of UDDI URL scheme 5.2.3 CR-050: Tony has a number of related ARs 5.2.4 CR-080: discard_transferToken API 5.2.6 Inserted item – dealing with multi-version registry with a V2 client 5.2.7 CR-076: get_subscriptions cannot return 0 subscriptions 5.2.8 CR-081: Required keyValue in a publisherAssertion; removal of erroneous text 5.2.9 CR-082: Duplicative keyedReference handling in bags 5.3.1 First draft of schemas and WSDL for 3.0.2 5.4 Technical Notes in Progress 5.4.1 “Using WSDL in UDDI, v2” Technical Note errata 5.4.2 Using BPEL in a UDDI Registry Technical Note 5.4.4 “Handling of anyURI datatypes” Technical Note 5.4.6 Securing the channel Technical Note 5.5 UDDI Executive and Technical White Paper 6.1 Taxonomy Management (Req 28) 6.1.1 Using OWL for the interchange format 6.2 Range-based Query (Req 23) 6.3 Boolean Query Operations (Req 20)
1 AttendanceAttendance taken.
2 Additions to Agenda1. Rob Kochman – backward compatibility issues in Chapter 10. Validating that certain choices were made deliberately. See Section 5.2.6 - Inserted item – dealing with multi-version registry with a V2 client of the minutes. 3 Approval of Previous MinutesMotion: Motion to approve the minutes of the 20040720, which are posted at: http://www.oasis-open.org/committees/download.php/8249/TCMinutes-V1.0-20040720.htm
Thanks again for Maud for hosting the last telecon. Minutes: Approved without dissent. 4 Administration4.1 Next CallLuc will host the 31 Aug UDDI Spec TC telecon.
· Call hosted by Luc Clément, Systinet. Call details: · Toll: 706-643-6177 · Toll Free: 888-502-0190 · Confirmation #: 6176211168 · NOTE: *6 to mute, #6 to unmute
UTC: Tue-19:30, Seattle: Tue-12:30, New York: Tue-15:30, London: Tue-20:30, Frankfurt: Tue-21:30, Moscow: Tue-23:30, Tokyo: Wed-04:30, Sydney: Wed-05:30, Auckland: Wed-07:30 4.2 September FTF1. Matthew will host the 20-22 Sep UDDI Spec TC FTF at Oxford. We discussed and agreed for a Monday start on 20 Sep – lasting until 22 Sep.
Matthew asked also asked for some time for the TC to meet with UK Grid representatives the morning of Thursday 23. We agreed to a half a day meeting; Matthew will organize the meeting.
· Discuss details of the Thu 23 Sept meeting with the Grid representatives.
2. Attendance for the FTF is as follows:
· Obtain confirmation from Steve
3. Matthew to provide us with details on recommended hotels Minutes: A meeting with Grid representatives is confirmed for the morning of 23 Sep. Claus must leave on the Wednesday, but asked about the possibility of dialing in on a conference phone for the Grid meeting – Matthew will investigate – Claus has volunteered to host the conference call.
The easiest method to get to Oxford from Heathrow is via a bus; train or taxi are possible, although a taxi would be expensive – Matthew will e-mail the list with details of hotel options. 4.3 OASIS New IPR Rules
From: Karl F. Best [mailto:karl.best@oasis-open.org] Sent: Friday, July 30, 2004 11:55 To: chairs@lists.oasis-open.org Subject: [chairs] reminder to chairs: OASIS IPR Policy member review
TC chairs:
On 9 July OASIS announced to its membership a draft IPR Policy that has been developed by our Board, and requested that members review and provide comment on this draft. (See http://lists.oasis-open.org/archives/members/200407/msg00002.html)
One of the documents in this review is the proposed Transition Policy, which describes how TCs will transition to the new IPR Policy by selecting an IPR mode to operate under, after which the OASIS members (organizations and individuals) represented in the TC will vote to ratify that selection.
In addition to the other issues in the IPR Policy that you individually and your companies may be interested in, I would also appreciate your TCs looking at, discussing, and commenting on the transition to the new IPR Policy, as well as any other parts of the Policy that will affect the day-to-day operations of the TC.
…
Other info · The draft IPR Policy is at: http://www.oasis-open.org/apps/org/workgroup/members-only/download.php/7515 · and the FAQ is at: http://www.oasis-open.org/apps/org/workgroup/members-only/download.php/7554 · From the FAQ: 3.6. Are there changes to the eligibility rules for Individual members? Yes. If an individual’s IP is owned by his or her employer, (as is required by most employment agreements), he or she will be unable to continue to participate under the OASIS Individual Membership level.
Minutes: Luc urged any Individual members to review the rules for IPR – corporate members are probably not affected. 5 Old Business5.1 Review of AR List5.1.1 AR002: Update to the Key Partitions TN
Nothing to note during the last telecon; AR remained open.
Minutes: We probably should look into finding a new owner for this TN – Steve hasn’t been able to join us for 3 meetings in a row. 5.1.2 AR054 Resubmission of IETF publication of UDDI URL scheme
Re: submission of "UDDI URI Scheme Registration with
IANA"
Discuss: Andrew to provide us with update.
Minutes: Andrew thinks the submission has slipped in. He will follow up with email as the registration progresses through the IETF. 5.1.3 AR055 – UBR tModels#0055: UBR tModel Submission: add ICD identifier
entries Owner: Andrew Hately Status: Open Assigned: 05 Jul
2004 Due: 10 Aug 2004 Comments: ICD code for D&B D-U-N-S system checked by Claus and sent to the list. Andrew to update files accordingly.
Luc will them perform final review, formatting, voting and upon approval posting to uddi.org
Discuss: status Minutes: Andrew to notify Luc when complete. 5.2 Change RequestsThe current list of CRs under process is listed at http://www.oasis-open.org/apps/org/workgroup/uddi-spec/download.php/8623/status.htm.
The CRs that are outstanding are: · CR-066: modified timestamp elements needed on changeRecordDelete and changeRecordDeleteAssertion. Andrew Hately · CR-050: Tony has a number of related ARs o AR0040: Additions to CR-050 o AR0042: Additions from last FTF to CR-050 o AR0046: Add the content of CR-070 to CR-050 · CR-080: discard_transferToken API, Rob Kochman · CR-074: Runtime behavior of a v2/v3 multi-version registry as it relates to empty containers and lengths supplied by a v2 client, Mirek Novotny · CR-076: get_subscriptions cannot return 0 subscriptions, Mirek Novotny · CR-081: Required keyValue in a publisherAssertion; removal of erroneous text., Mirek Novotny · CR-082: Duplicative keyedReference handling in bags, Mirek Novotny · CR-083: Clarification of multi-version node handling behavior to requests from v2 clients of entityKeyValue-based keyedReferences, Mirek Novotny
5.2.1 CR-064Re note from Claus and Andrew:
2) CR-064 Minutes: Moving CR64 back to the draft bucket while Andrew makes changes to it. He believes he can complete this in a couple of days. 5.2.2 CR-066: modified timestamp Elements Needed on changeRecordDelete and changeRecordDeleteAssertionOwner: Andrew Hately URL: http://www.oasis-open.org/apps/org/workgroup/uddi-spec/download.php/7483/uddi-spec-tc-cr066-modifiedDateForDeleteInReplication-20040624.doc Abstract: The V3 specification does not include enough information in the replication log for deletes to calculate modifiedIncludingChildren at other nodes. This change request adds the necessary timestamp on deletions.
Minutes: Andrew explained this CR to the TC. This relates to ensuring that all nodes work from the same timestamps. This is added to the 3.0.2 bucket. 5.2.3 CR-050: Tony has a number of related ARsObtain status on the following ARs from Tony: · AR0040: Additions to CR-050 · AR0042: Additions from last FTF to CR-050 · AR0046: Add the content of CR-070 to CR-050
Minutes: Tony has completed this item. 5.2.4 CR-080: discard_transferToken APIOwner: Rob Kochman URL: http://www.oasis-open.org/apps/org/workgroup/uddi-spec/download.php/7845/uddi-spec-tc-cr068-keyGenerationHiddentModel-20040718.doc Abstract: discard_transferToken API
Discuss input from Katherine Jagger (IBM) posted at http://lists.oasis-open.org/archives/uddi-spec/200408/msg00003.html
Minutes: Rob suggests deleting the transfer token when the item is deleted. After some discussion, Andrew and Luc came to the conclusion that the transfer token should be invalidated, rather than deleted. Rob will modify the CR appropriately. 5.2.5 CR-074: Runtime behavior of a v2/v3 multi-version registry as it relates to empty containers and lengths supplied by a v2 clientOwner: Mirek Novotny URL: http://www.oasis-open.org/apps/org/workgroup/uddi-spec/download.php/8638/uddi-spec-tc-cr074-v2v3MultiversionRuntimeSchemaConsiderations-20040809.doc Abstract: The v3.0.1 specification is silent with respect to the runtime behavior of a v2/v3 multi-version registry as it relates to empty containers and lengths supplied by a v2 client. This CR details the necessary behavior.
Minutes: Mirek explained the intent of the CR. He recommends defining run-time behavior (in a multi-version registry) and migration behavior separately. The behavior is pretty much the same, but specifying them separately does clarify the required behavior.
Andrew pointed out that this is similar to CR57. We will remove CR57 and replace it with this change, because this one is stated more clearly.
Tabled for review by Rob – he will ensure that all of CR57 is covered by this. 5.2.6 Inserted item – dealing with multi-version registry with a V2 clientV2 requests may stop working when data migrated into a multi-version V3 registry. Data that was accepted in a V2 registry (such as DiscoveryUrl, where the field is a string) may be rejected in V3 registry (because it is now URI).
Rob is not too happy to be rejecting something that was valid using the V2 schema. At the same time, we don’t want to store invalid URLs in the V3 registry.
Rob will ponder the situation. Tony suggested that the V2 request will validate against the V2 schema, and then the server (in the process of transforming to V3) can issue a “gentle” error message explaining the migration. That is preferable to a straight schema rejection.
Other issues include: · Another question is white-space collapse. Andrew suggests documenting that a query depending on a pair of white spaces will never return anything in V3, because of white space collapse. · Empty keyValues are permitted in V2, but not in V3 – this one is tough, because it makes sense – it is suggested that we change V3 to permit an empty keyValue. · Empty instanceParms are permitted in V2, not in V3.
Rob will write all of this up as a change request, targeting two weeks time. 5.2.7 CR-076: get_subscriptions cannot return 0 subscriptionsOwner: Mirek Novotny URL: http://www.oasis-open.org/apps/org/workgroup/uddi-spec/download.php/8639/uddi-spec-tc-cr076-subscriptionsResult-20040805.doc Abstract: The subscriptions element does not anticipate the possibility that zero subscription elements may result as part of a "get_subscriptions". The CR changes the minOccurs=”1” to allow a return structure with no subscription elements for a given user.
Minutes: If a user has no subscriptions, it is not possible to return that fact.
Added to the 3.0.2 bucket. 5.2.8 CR-081: Required keyValue in a publisherAssertion; removal of erroneous textOwner: Mirek Novotny URL: http://www.oasis-open.org/apps/org/workgroup/uddi-spec/download.php/8640/uddi-spec-tc-cr081-add_publisherAssertions-20040805.doc Abstract: The v3.0.1 specification erroneously states that empty (zero length) keyNames and keyValues permitted in add_publisherAssertions; this is incorrect as the keyValue is required.
Minutes: This is already included in CR50 – we can drop this one.
5.2.9 CR-082: Duplicative keyedReference handling in bagsOwner: Mirek Novotny URL: http://www.oasis-open.org/apps/org/workgroup/uddi-spec/download.php/8641/uddi-spec-tc-cr082-duplicativeKeyedReferencesInBags-20040805.doc Abstract: Clarification of behavior when multiple duplicative keyedReferences appear within a single categoryBag or identifierBag. The solutions calls for leaving unaltered the set of duplicative keyedRerences.
Minutes: There was some discussion of this. The same point applies to all lists of children – each time we see two children which are essentially identical (eg: two names which are the same).
This CR to be changed to cover all duplicates to be retained, possibly where we talk about preserving document order – next call.
5.2.10 CR-083: Clarification of multi-version node handling behavior to requests from v2 clients of entityKeyValue-based keyedReferencesOwner: Mirek Novotny URL: http://www.oasis-open.org/apps/org/workgroup/uddi-spec/download.php/8642/uddi-spec-tc-cr083-multiversioning%20inconsistency-20040809.doc Abstract: This CR clarifies the behavior of a multi-node with respect to handling of keys held in the keyValue of a keyedReference categorized using the entityKeyValues category system.
Minutes: Luc will merge CR 71 into the spec and then rewrite this CR to reflect the update. By the next telecon.
5.3 V3.0.25.3.1 First draft of schemas and WSDL for 3.0.2
John has uploaded only those files that have been changed, namely: · uddi_v3.xsd · uddi_v3custody.xsd · uddi_v3replication.xsd · uddi_api_v3_portType.wsdl · uddi_custody_v3_binding.wsdl · uddi_custody_v3_portType.wsdl · uddi_repl_v3_binding.wsdl · uddi_repl_v3_portType.wsdl · uddi_sub_v3_portType.wsdl
These changes were due to the following Change Requests: · 46 · 51 · 54 · 56 · 59 · 63 · 64
From Claus: I checked the files w.r.t. the listed change requests and found the following issues:
5.3.1.1 CR-054Not addressed (changeRecordConditionFailed not added to replication schema).
Minutes: Andrew will revise the files to include this.
5.3.1.2 CR-064Not addressed (empty string defaults for keyName, sortCode and useType). Also, the change request itself does not capture the usage of the useType simple type in contact, discoveryURL, email, overviewURL, and phone elements and needs to be updated accordingly.
Minutes: Andrew will revise the files to include this. 5.3.1.3 CR-046Provided that you open up CR-046 again due to the change that needs to be made to section 7.4.2.3, it would also be good to document yet another change that is so far not captured: The tenth paragraph of section 5.4.3 needs to be changed from "Following the issue of the dispositionReport by N1 to the transfer_custody call, ..." to "Following the issue of the empty message by N1 to the transfer_custody call, ..."
Minutes: Andrew will revise the files to include this, and will revise CR46 appropriately. 5.3.2 SCC14N – Errata 1Obtain status from Andrew on progress
Minutes: Andrew will deal with this soon. 5.3.3 Pending CRAndrew has a pending CR relating to the default value of signed.
Andrew may have another CR relating to Appendix I, about setting parent keys before signing. 5.4 Technical Notes in Progress5.4.1 “Using WSDL in UDDI, v2” Technical Note errataWe approved errata #2 (version 2.0.2) of the Technical Note.
To Do: Luc to send note announcing the update – still waiting on this. 5.4.2 Using BPEL in a UDDI Registry Technical NoteClaus has provided has reposted the TN based on feedback received during UDDI TC FTF Meeting June 28-30, 2004. It is ready to be revised by the assigned Editors. It is posted at http://www.oasis-open.org/apps/org/workgroup/uddi-spec/download.php/7835/uddi-spec-tc-tn-bpel-20040719.doc
The TN was submitted to the BPEL TC. Discussion so far is a mixed review and a consensus seems to be building that the TN may be too early.
Discuss next steps
Minutes: Claus reported that there have been some comments on this TN in the BPEL TC. It has now been forwarded to the subcommittee on Abstract Processes.
We’re waiting on them. Claus will urge them along; Ivona the co-author is also tracking the BPEL TC closely. We will look at this next meeting when we expect to have received input. 5.4.3 WSRP Technical NoteNote from the Chair of the WSRP TC: We would like to invite the UDDI TC to review and comment the document. You should be able to retrieve the PDF version here:
Claus provided input: http://lists.oasis-open.org/archives/uddi-spec/200407/msg00095.html
Discuss next steps
Minutes Claus reported that he received feedback on his comments from the editors, and from the subcommittee, saying that they will address them. He will copy the list on some of the feedback. 5.4.4 “Handling of anyURI datatypes” Technical NoteDiscussion of the http://www.oasis-open.org/apps/org/workgroup/uddi-spec/download.php/7502/uddi-spec-tc-tn-anyURIHandling-20040629.doc
AR0039: Andrew assigned AR to provide comment
Obtain status from Andrew Minutes Deferred 5.4.5 QoS Technical NoteLuc has been working on this (http://www.oasis-open.org/apps/org/workgroup/uddi-spec/download.php/6231/uddi-spec-tc-tn-QoS-metrics-20040402.doc ), and will report on his progress, and on interfacing with the WSDM TC.
Obtain status from Luc
Minutes: Deferred 5.4.6 Securing the channel Technical Note#0034: v.Next: REQ 18: technote on the subject of
securing the channel Owner: Tony Rogers Status: Open Assigned:
24 Feb 2004 Due: 10 Aug 2004 Comments:
Obtain status from Tony
Minutes Deferred 5.5 UDDI Executive and Technical White PaperBrent Sleeper was commissioned to update the Executive and Technical white paper and had submitted the papers for review. See http://lists.oasis-open.org/archives/uddi-spec/200408/msg00013.html
Request for reviewers (and involvement of your respective marketing teams).
Minutes Target date for feedback is 10 days from now.
Please provide feedback to Mike DeNicola, copy to Brent, and the list.
Reviewers: Tom, Tony, Claus, Luc, Daniel, George.
Luc asked that your respective marketing teams be asked to provide input. 6 UDDI v.Next Discussions6.1 Taxonomy Management (Req 28)6.1.1 Using OWL for the interchange format1. Previous AR: Katia / Massimo to investigate whether this proposal requires OWL-Full, or whether OWL-Lite will suffice. They believe that OWL-Lite will be capable of doing all we need. UPDATE: they confirmed that OWL-Full is required to support the “selectable” attribute.
2. Previous AR: John to modify the proposal to include the rationale for excluding other features of OWL (such as properties), to obviate extended discussion and rehashing of these topics. UPDATE: John has an extensively revised version of the document, but is reluctant to post it because he is not yet finished with it. We encourage him to post it as soon as he can bring himself to do so, so that the rest of the TC can provide feedback.
3. Previous AR: Katia and Massimo to assess the proposal from an OWL viewpoint.
4. Review input from Massimo on John’s “OWL as the UDDI Taxonomy Language” proposal: http://lists.oasis-open.org/archives/uddi-spec/200408/msg00009.html
5. Discussion of thread by Massimo and John: http://lists.oasis-open.org/archives/uddi-spec/200408/msg00011.html
Minutes Massimo has reviewed John’s work, and sent out a proposal that allows the use of OWL-Lite instead of OWL-Full – this is desirable because OWL-Full is still somewhat dubious, while OWL-Lite is much better-understood. He has solved the selectable problem in a different way. He has made changes to the uploaded document (there is one small error). He is on holiday at the moment, but hopes to continue with this about the end of this week. 6.1.2 Management API6.1.2.1AR: Massimo and Katia will frame a question to the best practices group of OWL about handling parts of taxonomies, and any navigation APIs. Minutes Massimo will be working on this next week.
6.1.2.2 AR0056#0056: v.Next: Taxonomy Management API Owner:
John Colgrave Status: Open Assigned: 05 Jul 2004 Due: 10
Aug 2004 Comments: Minutes Deferred 6.2 Range-based Query (Req 23)6.2.1 AR0058#0058: v.Next: Range-based Query (Req 23) Owner:
Andrew Hately Status: Open Assigned: 05 Jul 2004 Due: 11
Jul 2004 Comments: Minutes Deferred 6.3 Boolean Query Operations (Req 20)6.3.1 AR0059#0059: v.Next: Boolean Query Operations (Req 20) Owner:
Daniel Feygin Status: Open Assigned: 05 Jul 2004 Due: 18
Jul 2004 Comments: Minutes Deferred 6.3.2 AR0060#0060: v.Next: Boolean Query Operations (Req 20) -
Produce Example Queries Owner: Status: Open Assigned: 05
Jul 2004 Due: 10 Aug 2004 Comments: Minutes Deferred 6.4 Semantic Search (Req 29)6.5 AR0057#0057: v.Next: Semantic Search Owner: Katia
Sycara Status: Open Assigned: 05 Jul 2004 Due: 11 Jul 2004
Comments: Minutes Deferred 6.6 ACLs (Req 16)6.6.1 AR0038#0038: v.Next: Produce RQ-016 Proposal - Not
breaking the containment model Owner: Andrew Hately Status: Open Assigned:
12 Mar 2004 Due: 30 Mar 2004 Comments: Minutes Deferred
6.6.2 AR0031#0031: v.Next: Complete Work on the RQ-016 Proposal
(Breaking the containment model) Document Owner: Andrew Hately Status:
Open Assigned: 24 Feb 2004 Due: 02 Mar 2004 Comments: Minutes Deferred 6.7 Contacts (Req 27)6.7.1 AR0061#0061: v.Next: Contacts (Req 27) Owner: Tony
Rogers Status: Open Assigned: 05 Jul 2004 Due: 18 Jul 2004
Comments:
Minutes Deferred 6.8 Stale Data (Req 19)
Discussing the proposal that was updated at the last face-to-face. Lots of questions about the point of these proposals. Not a lot of conviction that this is a big requirement. There is some motivation for this, pushed by the fact that there is no way to validate the content of the registry – there is no real way to clean up a registry. One suggestion is that we defer this proposal for some time. Minutes Deferred 7 Additions to AgendaCovered in Section 5.2.6 Inserted item – dealing with multi-version registry with a V2 client 8 Adjournment
Adjourned 7:31am Australian Eastern Standard Time. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]