Minutes of UDDI Spec TC Telecon

 

Date:      20040720

 

Chairs:   Luc Clément, Systinet, luc.clement@systinet.com

Tony Rogers, Computer Associates, Tony.Rogers@ca.com

Logistics 

TC Telecon.

Call hosted by Maud Cahuzac, France Télécom. Call details:

·          Toll free:   Non available

·          Toll:   +1 650 875 3097

·          Participant Passcode:  No passcode necessary

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

1     Attendance. 2

2     Additions to Agenda. 2

3     Approval of Previous Minutes. 2

4     Administration. 2

4.1         Next Call 2

4.2         September FTF. 3

5     Old Business. 4

5.1         Review of AR List 4

5.1.1       AR002: Update to the Key Partitions TN.. 4

5.1.2       AR054 Resubmission of IETF publication of UDDI URL scheme. 4

5.1.3       AR055 – UBR tModels. 4

5.2         Change Requests. 4

5.2.1       CR-078. 4

5.2.2       CR-073. 5

5.2.3       CR-080. 5

5.2.4       CR-072. 5

5.2.5       CR-068. 5

5.2.6       CR-069. 6

5.2.7       CR-071. 6

5.2.8       CR-067. 6

5.2.9       CR-070. 7

5.2.10      CR-079. 7

5.2.11      Status of other CRs. 8

5.3         V3.0.2. 8

5.3.1       First draft of schemas and WSDL for 3.0.2. 8

5.3.2       SCC14N – Errata 1. 9

5.4         Technical Notes in Progress. 9

5.4.1       “Using WSDL in UDDI, v2” Technical Note errata. 9

5.4.2       Using BPEL in a UDDI Registry Technical Note. 9

5.4.3       WSRP Technical Note. 10

5.4.4       “Handling of anyURI datatypes” Technical Note. 10

5.4.5       QoS Technical Note. 10

5.4.6       Securing the channel Technical Note. 10

6     UDDI v.Next Discussions. 11

6.1         Deferred discussion. 11

6.1.1       Taxonomy Management (Req 28) 11

6.1.2       Range-based Query (Req 23) 11

6.1.3       Boolean Query Operations (Req 20) 12

6.1.4       Semantic Search (Req 29) 12

6.1.5       AR0057. 12

6.1.6       ACLs (Req 16) 12

6.1.7       Contacts (Req 27) 13

6.1.8       Stale Data (Req 19) 13

7     Additions to Agenda. 13

8     ADJOURNMENT. 13

 

1         Attendance

Attendance was taken.

 

Member Name

7/20/2004

Bellwood, Tom

y

Capell, Steve

n

Clement, Luc

y

Colgrave, John

n

Dovey, Matthew

y

Feygin, Daniel

n

Hately, Andrew

y

Henry, Brad A.

n

Kochman, Rob

y

Macias, Paul A.

y

Novotny, Mirek

y

Paolucci, Massimo

n

Rogers, Tony

n

Sycara, Katia

n

von Riegen, Claus

y

Wenzel, Pete

n

Wu, Zhe

y

Zagelow, George

n

 

2         Additions to Agenda

No additions

3         Approval of Previous Minutes

Motion:

Motion to approve the minutes of the 20040628-30 (FTF), which are posted at: http://www.oasis-open.org/committees/download.php/7527/TC_FTF_Minutes-V1.1-20040628-30.doc

 

Thanks again for Tom and Andrew for hosting us.

 

Minutes:

The minutes were approved.

4         Administration

4.1      Next Call

Pete Wenzel, SeeBeyond has volunteered to host the 10 Aug UDDI Spec 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

 

Volunteers sought for the next call

Minutes:

Luc will host the call.

4.2      September FTF

Matthew has offered to host a UDDI Spec TC FTF at Oxford. I have asked him to confirm 21-23 Sep (Tue-Thu); Tom might appreciate a 20 Sep start date.

 

We are waiting for a response from Matthew on the above. Claus has also offered to host the meeting in Waldorf.

 

Discussion of dates and location.

Minutes:

Matthew confirmed that he can host the meeting. We discussed and agreed for a Monday start on 20 Sep – lasting until 22 Sep.

 

Matthew 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.

 

We took a poll of attendees planning to attend the FTF with the following results; Luc will follow up to firm up the attendee list.

 

Bellwood, Tom

Y

Capell, Steve

?

Clement, Luc

Y

Colgrave, John

?

Dovey, Matthew

Y

Feygin, Daniel

?

Hately, Andrew

Y

Henry, Brad A.

?

Kochman, Rob

Y

Macias, Paul A.

N

Novotny, Mirek

Y

Paolucci, Massimo

?

Rogers, Tony

?

Sycara, Katia

?

von Riegen, Claus

Y

Wenzel, Pete

?

Wu, Zhe

 

?

Zagelow, George

?

 

 

 

 

5         Old Business

5.1      Review of AR List

5.1.1           AR002: Update to the Key Partitions TN

 

#0002: Update Key Partitions TN

Owner: Steve Capell

Status: Open

Assigned: 23 Apr 2003

Due:

 

Minutes:

Nothing to note; AR remains open.

5.1.2           AR054 Resubmission of IETF publication of UDDI URL scheme

 

Update from Andrew: Fw: [Auto Response] Filename for submission of "UDDI URI Scheme Registration with IANA"

An update on Action #54.

Apparently there's a submission window for requesting a file name for IETF drafts before each IETF meeting and this one ended before I sent the document.  It looks like I need to resubmit again on August 2nd.

 

Minutes:

Andrew will be resubmitting Aug 2nd; he missed the submission window last when it was last open. He will be informing Karl Best and the chairs of the resubmission.

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:
Luc Clement 2004-07-05 22:46 GMT
New AR: Andrew to add ICD identifier entries to any of these tModels that have defined ICD numbers (for example, D-U-N-S has an ICD). Andrew to update the tModels.

Submit to Luc for final review, formatting, voting and upon approval posting to uddi.org

Minutes:

Andrew gave us an overview

 

Claus: has taken an action item to check – “Check ICD code for DUNS”

5.2      Change Requests

5.2.1           CR-078

The document uddi-spec-tc-cr-078-schemaChanges-20040715.doc has been submitted by John Colgrave (colgrave@hursley.ibm.com) to the OASIS UDDI Specification TC document repository.

 

Document Description:

This CR describes some minor changes that can be made to the normative schemas to simplify the generation of a JAX-RPC client.

 

Download Document: 

http://www.oasis-open.org/apps/org/workgroup/uddi-spec/download.php/7765/uddi-spec-tc-cr-078-schemaChanges-20040715.doc

 

Minutes:

We discussed item 4.1 – a change in the schema allowing for key matching.  TC agreed to accept the change proposed by 4.1.

 

We discussed item 4.2 – changing the location of maxOccurs; removing the declaration of a schema it never users. TC agreed to accept the change proposed by 4.2.

 

The TC agreed to accept this CR in v3.0.2 bucket.

5.2.2           CR-073

The document uddi-spec-tc-cr073-whitespace_collapse_phone_element-20040715.doc has been submitted by Rob Kochman (robko@microsoft.com) to the OASIS UDDI Specification TC document repository.

 

Document Description:

This document describes a proposed change to the UDDI v3 schema to specify whitespace collapse for the phone element.

 

Download Document: 

http://www.oasis-open.org/apps/org/workgroup/uddi-spec/download.php/7804/uddi-spec-tc-cr073-whitespace_collapse_phone_element-20040715.doc

 

Minutes:

The TC agreed to accept this CR in v3.0.2 bucket.

5.2.3           CR-080

The document uddi-spec-tc-cr080-discard_transfertoken-20040715.doc has been submitted by Rob Kochman (robko@microsoft.com) to the OASIS UDDI Specification TC document repository.

 

Document Description:

This document describes changes to the discard_transferToken API to ensure proper behavior related to deleting transfer tokens for previously deleted entities.

 

Download Document: 

http://www.oasis-open.org/apps/org/workgroup/uddi-spec/download.php/7805/uddi-spec-tc-cr080-discard_transfertoken-20040715.doc

 

Minutes:

Rob to revisit the WSDL to ensure that the fact that we are not throwing an error has been reflected in the WSDL

 

Rob to repost.

5.2.4           CR-072

The document uddi-spec-tc-cr072-operationalInfoInReplication-20040717.doc has been submitted by Claus von Riegen (claus.von.riegen@sap.com) to the OASIS UDDI Specification TC document repository.

 

Document Description:

It is not clear if a node should validate timestamps received in the replication stream.

 

Download Document: 

http://www.oasis-open.org/apps/org/workgroup/uddi-spec/download.php/7808/uddi-spec-tc-cr072-operationalInfoInReplication-20040717.doc

 

Minutes:

The TC agreed to accept this CR in v3.0.2 bucket.

5.2.5           CR-068

The document uddi-spec-tc-cr068-keyGenerationHiddentModel-20040718.doc has been submitted by Andrew Hately (hately@us.ibm.com) to the OASIS UDDI Specification TC document repository.

 

Document Description:

The specification does not describe any difference between a tModel that has been hidden via the delete tModel API and one that is visible.  This change request proposes that a tModel must be visible in order to create new keys based on a key generator tModel.

 

Download Document: 

http://www.oasis-open.org/apps/org/workgroup/uddi-spec/download.php/7845/uddi-spec-tc-cr068-keyGenerationHiddentModel-20040718.doc

Minutes:

The TC agreed to accept this CR in v3.0.2 bucket.

5.2.6           CR-069

The document uddi-spec-tc-cr069-removeXMLDeclRestrictions-20040718.doc has been submitted by Andrew Hately (hately@us.ibm.com) to the OASIS UDDI Specification TC document repository.

 

Document Description:

Section 4.2 of the specification is excessively restrictive.  Per RFC 3023, there is no specific requirement on the encoding value in the XML declaration.  Also, the examples are listed as the form that must be used to declare content type headers which conflicts with the description in the paragraphs following the examples in 4.2.  This change request proposes removing some of the text that is too restrictive so that standard SOAP engines do not need to double parse the UDDI messages.

 

Download Document: 

http://www.oasis-open.org/apps/org/workgroup/uddi-spec/download.php/7822/uddi-spec-tc-cr069-removeXMLDeclRestrictions-20040718.doc

 

Minutes:

The TC agreed to accept this CR in v3.0.2 bucket.

5.2.7           CR-071

The document uddi-spec-tc-cr071-entityKeyValueSetBehaviorForDeletionsAndCertainUpdates-20040718.doc has been submitted by Andrew Hately (hately@us.ibm.com) to the OASIS UDDI Specification TC document repository.

 

Document Description:

The specification does not define treatment of keyValue attributes in keyedReferences pointing to entityKey value set tModels when the entity referenced in the keyValue is deleted. The specification also does not define treatment of keyValue attributes in keyedReferences pointing to value set tModels that are changed classified as entityKey value set tModels. Similarly, the specification does not define treatment of keyValue attributes in keyedReferences pointing to entityKey value set tModels that are changed to no longer be classified as entityKeyValue set tModels.  This change request clarifies the specification by adding descriptions of how a node should handle these cases.  Due to the peculiarity of changing value set tModels after they have existed, the behavior for the last two problems outlined will be that the behavior is undefined for existing keyValue attributes.

 

Download Document: 

http://www.oasis-open.org/apps/org/workgroup/uddi-spec/download.php/7823/uddi-spec-tc-cr071-entityKeyValueSetBehaviorForDeletionsAndCertainUpdates-20040718.doc

 

Minutes:

Tentatively accepted – We should accept to hold off for Mirek – 2-3 days.

5.2.8           CR-067

 

Open Issue

After looking at this for a while, there are a significant number of variable policies that could affect signature validation on keyGenerator tModels, and I believe that other security policy languages will eventually define a template to express signature and certificate policies.

Since defining all of these abstractions as part of this work item would likely delay my v.next work and also push out  v3.0.2 if we tried to contain all of this in a change request, I can withdraw this change request.  As an alternative to just withdrawing, I could also propose a change request  for updating the policies element in uddi_v3policy.xsd  to allow for elements from other namespaces:

<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

 

Minutes:

CR widthdrawn in favour of aligning with other policy mechanisms

 

5.2.9           CR-070

 

Open Issue

Note from Andrew: http://lists.oasis-open.org/archives/uddi-spec/200407/msg00076.html

 

I believe CR70 is largely editorial based on the existing section 10.2.2:

10.2.2 keyedReference data
With Version 3, tModelKey elements MUST be specified for a keyedReference structure contained within an Inquiry API requests. Requests to the Version 3 namespace containing keyedReference structures without tModelKey elements will fail schema validation and be rejected.

The first sentence of 10.2.2 should be clarified by removing an unnecessary qualification, tModelKey elements must always be specified in keyedReference elements in V3, so remove "contained within an Inquiry API requests".

A clarification should also be added to the end:  "Requests in the version 2 namespace with empty or absent tModelKey elements MAY be processed by a multi-version node as a reference to the general_keyWords tModel.  As this node behavior was optional in version 2, It is STRONGLY RECOMMENDED that all UDDI version 2 clients provide tModelKey attribute in keyedReference elements."

If desired, I can put this in the form of the full CR template.

 

Minutes:

Accepted to CR-050.

 

AR: Tony to add to CR-050.

5.2.10       CR-079

The document uddi-spec-tc-cr079-inquiry_enhancement-20040712.doc has been submitted by Zhe (Alan) Wu (alan.wu@oracle.com) to the OASIS UDDI Specification TC document repository.

 

Document Description:

Since UDDI v3 spec does not provide any time-based search, it is very hard, if not impossible at all, to perform an inquiry like ‘give me all WSDL services that are modified before last Friday.” Also, UDDI v3 spec does not allow users to limit the search scope to entities owned by a particular publisher.

 

Download Document: 

http://www.oasis-open.org/apps/org/workgroup/uddi-spec/download.php/7759/uddi-spec-tc-cr079-inquiry_enhancement-20040712.doc

Minutes:

Not approved as a CR to v3.0.2 given that is does not satisfy the criteria set forth in the “UDDI Spec TC Process” document [1] for what constitutes an acceptable CR for an errata. What Zhe was proposing is new functionality – which does not qualify.  Zhe was asked to submit his proposal as a v.Next proposal.

 

[1] http://www.oasis-open.org/committees/uddi-spec/doc/process/uddi-spec-tc-process-20021212.htm

5.2.11       Status of other CRs

Obtain status on progress on CRs

 

#0050: Submit CR-074 Owner: Luc Clement Status: Open Assigned: 05 Jul 2004 Due: 18 Jul 2004 Comments:
Luc Clement 2004-07-05 22:18 GMT
CR-074 Length Handling V2 issues pertaining to section 10.2.8. Luc Clément / Andrew Hately V3 v3.0.2


#0051: Submit CR-075 Owner: Luc Clement Status: Open Assigned: 05 Jul 2004 Due: 18 Jul 2004 Comments:
Luc Clement 2004-07-05 22:19 GMT
CR-075 Publisher Assertions – error code change (E_fatalError vs E_unsupported). Luc Clément V3 v3.0.2


#0052: Submit CR-076 Owner: Luc Clement Status: Open Assigned: 05 Jul 2004 Due: 18 Jul 2004 Comments:
Luc Clement 2004-07-05 22:20 GMT
CR-076 Get_Subscription cannot return 0 subscriptions Luc Clément V3 v3.0.2


#0053: Submit CR-077 Owner: Luc Clement Status: Open Assigned: 05 Jul 2004 Due: 18 Jul 2004 Comments:
Luc Clement 2004-07-05 22:20 GMT
CR-077 assertionStatusReport must preserve signature when used in subscription. Luc Clément V3 v3.0.2

 

Minutes:

These CRs are still outstanding. CR-077 may also be withdrawn.

5.3      V3.0.2

5.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 John:

If you are responsible for one of these Change Requests, please check the changes I have made.

 

If you think there should be other Change Requests that should be included, please speak up.

 

In the process of doing this I came across one other spec. change that needs to be added to my CR, CR-046: a change needs to be made to section 7.4.2.3 of the spec.

 

XML Spy is having a hard time with the default attribute that was added in several places by one of the CRs, but I am not sure yet whether that is a bug in XML Spy.  It claims that an empty default value can only be used with a small number of built-in types.

Minutes:

We briefly discussed this topic. Folks are welcome to start reviewing the schemas and WSDLs.

5.3.2           SCC14N – Errata 1

Obtain status from Andrew on progress

 

Minutes:

Andrew needs two more days before he is in a position to post the errata for review.

 

5.4      Technical Notes in Progress

5.4.1           “Using WSDL in UDDI, v2” Technical Note errata

 

We have completed the changes to the "Using WSDL in a UDDI Registry, Version 2" TN - this will constitute errata #2 (v2.0.2) of the TN.  The following changes have been made since errata #1:

 

20040601

1 June 2004

Luc Clément

Tony Rogers

 

Changes to tModel content to make them consistent.

Removal of section 2.5.2 (of the 20031104 version) describing an optional v3 mapping.

Removal of Footnote 1 (of the 20031104 version).

Clarified that a keyedReference to the XML Namespace category system MUST only be made if the definitions element has a target namespace, otherwise if there is no target namespace, the reference MUST NOT be made. See sections 2.4.1, 2.4.2 and 2.4.3.

20040631

31 June 2004

Version 2.0.2

Luc Clément

John Colgrave

Claus von Riegen

Generalization of the WSDL portType Reference tModel

Case-folding of v3 entity keys for consistency.

 

As noted below, you can obtain a copy of the MSWord, PDF (final/markup) and HTML versions of the TN at: http://www.oasis-open.org/apps/org/workgroup/uddi-spec/download.php/7565/uddi-spec-tc-tn-wsdl-v2.zip.

 

Motion:

Motion to approve errata #2 (version 2.0.2) of the Technical Note.

 

Minutes:

Errata #2 has been approved.

5.4.2           Using BPEL in a UDDI Registry Technical Note

Claus 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

 

Luc and Andrew were appointed as editors for this TN.

 

Minutes:

Accepted for submission to the editors.

 

Claus proposed that we submit it to the BPEL TC. We agreed that once the editors have completed the edit pass, that it be submitted to the BPEL TC. The chairs would do so.

 

Maud suggested that there was a set of use cases being discussed by BPEL TC related to UDDI. Maud will follow up with specifics.

5.4.3           WSRP Technical Note

Note 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:

http://www.oasis-open.org/apps/org/workgroup/wsrp/wsrp-pfb/download.php/7672/wsrp-pfb-uddi-tn-draft-08.doc

 

We need to assign editors to review this TN.

Minutes

Luc asked for volunteer for reviews. Matthew and Claus have volunteered and will try to close by the next telecon.

 

Luc to report back to the WSRP TC

5.4.4           “Handling of anyURI datatypes” Technical Note

Discussion of the http://www.oasis-open.org/apps/org/workgroup/uddi-spec/download.php/7502/uddi-spec-tc-tn-anyURIHandling-20040629.doc

 

Minutes

AR0039: Andrew assigned AR to provide comment

5.4.5           QoS Technical Note

Luc 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.

 

Minutes:

Luc stated that he had not made progress on this TN in the last three weeks. Andrew indicated that there was a need that had been expressed to provide the means of identifying the manageability provider; Luc indicated that the work in progress does just that but asked that Andrew follow up to ensure that the need as expressed is conveyed so it may be addressed in the TN.

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:
Luc Clement 2004-02-25 00:43 GMT
Solitic authors for a technote on the subject of securing the channel in support of improving trustworthiness

Luc Clement 2004-02-25 00:53 GMT
Assigned to Rob Kochman

Luc Clement 2004-07-17 17:44 GMT
Reassigned to Tony for review and input

Minutes

Deferred – Tony was not on the call

6         UDDI v.Next Discussions

 

Minutes

We did not have time to engage in v.Next discussion. We did obtain the following updates on progress:

·         Andrew plans to get range based query posted by end of week

·         John has done a significant update on 28; should be posted when John comes back by 1 Aug

·         16 – Andrew plans on submitting by the next call

               

6.1      Deferred discussion

6.1.1           Taxonomy Management (Req 28)

6.1.1.1           Using OWL for the interchange format

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.

 

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.

 

Previous AR: Katia and Massimo to assess the proposal from an OWL viewpoint.

Minutes

Deferred

6.1.1.2           Management API

6.1.1.2.1           

AR: Massimo and Katia will frame a question to the best practices group of OWL about handling parts of taxonomies, and any navigation APIs.

Minutes

Deferred

 

6.1.1.2.2          AR0056

#0056: v.Next: Taxonomy Management API Owner: John Colgrave Status: Open Assigned: 05 Jul 2004 Due: 10 Aug 2004 Comments:
Luc Clement 2004-07-05 22:58 GMT
We have a requirement for a management API, but no proposal as yet. There was considerable discussion of what we need, but not a detailed conclusion. The APIs we need are:
• Put / get an entire taxonomy (in OWL-UDDI format)
• Get part of a taxonomy
• Navigate taxonomy

AR: John to create a proposal for the management API.

Minutes

Deferred

6.1.2           Range-based Query (Req 23)

6.1.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:
Luc Clement 2004-07-05 23:24 GMT
AR: Andrew will flesh out his proposal to provide full details - i.e. make the included category bag list a choice: either a list of categoryBags or a list of inquiryCategoryBags.

Minutes

Deferred

6.1.3           Boolean Query Operations (Req 20)

6.1.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:
Luc Clement 2004-07-05 23:26 GMT
Update current proposal to align with either categoryBags or inquiryCategoryBags (see Req 23) for combination.

Minutes

Deferred

6.1.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:
Luc Clement 2004-07-05 23:28 GMT
A required addition to this proposal is a series of examples showing the modeling of a variety of common queries to prove that we have not lost any important expressivity. Responsibility for this AR is not yet assigned.

Minutes

Deferred

6.1.4           Semantic Search (Req 29)

6.1.5           AR0057

#0057: v.Next: Semantic Search Owner: Katia Sycara Status: Open Assigned: 05 Jul 2004 Due: 11 Jul 2004 Comments:
Luc Clement 2004-07-05 23:03 GMT
AR: Katia and Massimo to capture more detailed requirements and use cases, plus a feature set, as the beginnings of a proposal – this would include adding a design goal to discourage people from over-specifying their categorizations. This document to be brought before the TC for further discussion before taking to full proposal.

Minutes

Deferred

6.1.6           ACLs (Req 16)

6.1.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:
Luc Clement 2004-03-12 21:53 GMT
Due to the strong concerns voiced about the idea of breaking the containment model, it would be useful to have an alternative proposal. John and Andrew to work on the proposal to which does not break the containment model.

Minutes

Deferred

 

6.1.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:
Luc Clement 2004-02-25 00:34 GMT
Andrew to complete work on RQ-016 proposing the approach he advocates.
- TC to consider this approach, and decide whether breaking the containment model is acceptable in context.

Minutes

Deferred

6.1.7           Contacts (Req 27)

6.1.7.1           AR0061

#0061: v.Next: Contacts (Req 27) Owner: Tony Rogers Status: Open Assigned: 05 Jul 2004 Due: 18 Jul 2004 Comments:
Luc Clement 2004-07-05 23:36 GMT
write a proposal that shows how to use a binding template as a contact – a way of handling this using the existing data structures

 

Minutes

Deferred

6.1.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 Agenda

No new additions

8         ADJOURNMENT

We adjourned at 14:30.