[revised] Agenda: 4-5 March 2004 WS Description WG FTF

[Second draft.  Note that ***** indicates items that have dependencies 0
please check for action items assigned to you!]

Logistics [1].

 [1] http://www.w3.org/2003/08/allgroupoverview.html

--------------------------------------------------------
Thursday 4 March
--------------------------------------------------------
08:30 Introductions and logistics
    - Assignment of scribes
        Igor Sedukhin, Umit Yalcinalp, Youenn Fablet, Kevin Liu
        Paul Downey, Jeff Mischkinsky, Asir Vedamuthu, David Orchard 
        Hugo Haas
    - New scribe policy: Since the chair is maintaining the issues list,
      but not the edtodo, the two can easily get out of sync.  Our
minutes 
      should henceforth include explicit actions to the editors as well
as 
      resolutions of issues.
    - Agenda review 

08:40 WSDL Component Designators:
      Trolling through old minutes does not reveal clearly whether 
      WSDL Component Designators should be added back into the draft 
      as an Appendix.  My memory says "yes, we decided that" but the 
      minutes are unclear and the edtodo does not mention this.  If 
      you clearly remember something different, this is your chance 
      to scream.

08:43 Correction to minutes on wsdl:ServiceType [2].  Confirm correction

      to the minutes as enumerated by Umit.

  [2] http://lists.w3.org/Archives/Public/www-ws-desc/2004Feb/0224.html

08:45 Issue 79: How much validation? [3]
      Jacek posted a relevant proposal [4].
      David's analysis [5]

  [3] http://www.w3.org/2002/ws/desc/2/06/issues.html#x79
  [4] http://lists.w3.org/Archives/Public/www-ws-desc/2004Feb/0121.html
  [5] http://lists.w3.org/Archives/Public/www-ws-desc/2004Feb/0234.html

09:30 Issue 121: Broken resolution of NCNAME or QNAME [6]

  [6] http://www.w3.org/2002/ws/desc/2/06/issues.html#x121

09:45 Issue 92: Layering message patterns [7]

  [7] http://www.w3.org/2002/ws/desc/2/06/issues.html#x92
 
10:15 Issue 133: Why aren't two input/output elements allowed to share 
      the same @element value? [8]

  [8] http://www.w3.org/2002/ws/desc/2/06/issues.html#x133

10:30 Break     ----------------------------------------

10:50 Issue 112: Headers at the abstract level [9]
    - Headers as first-class citizens [10]
    - Glen's OOB feature proposal [11]

  [9] http://www.w3.org/2002/ws/desc/2/06/issues.html#x112
 [10] http://lists.w3.org/Archives/Public/www-ws-desc/2004Feb/0004.html
 [11] http://lists.w3.org/Archives/Public/www-ws-desc/2004Feb/0053.html

12:00 Lunch     ----------------------------------------

[Note: Schema folks might be want to join for this early afternoon
session.]
13:30 Issue 109: WSDL versioning [12]
    - Use cases (DavidO) [13]
    - Requirements (PaulD) [14]
    - Scenarios
      [***** ACTION: DaveO to write up a proposal for augmenting 
                     schema information to enable versioned data. *****]

 [12] http://www.w3.org/2002/ws/desc/2/06/issues.html#x109
 [13] http://lists.w3.org/Archives/Public/www-ws-desc/2004Jan/0016.html
 [14] http://lists.w3.org/Archives/Public/www-ws-desc/2004Feb/0082.html

14:30 Issue 140: Version attribute [15]
    - Tom's initial proposal [16] and follow-on proposal [17]
      [***** Paul to develop clear enumeration of options *****]

 [15] http://www.w3.org/2002/ws/desc/2/06/issues.html#x136
 [16] http://lists.w3.org/Archives/Public/www-ws-desc/2004Feb/0049.html
 [17] http://lists.w3.org/Archives/Public/www-ws-desc/2004Feb/0069.html

15:15 @wsdlLocation
      [***** Awaiting proposal from Umit, basically copying 
             xsi:schemaLocation *****]

15:30 Break     ----------------------------------------

15:50 Issue 123: Requiring all operations to be bound [18]

 [18] http://www.w3.org/2002/ws/desc/2/06/issues.html#x123

16:00 Issue 117: Marking operations as 'safe' [19]
    - Hugo's proposal [20]  

 [19] http://www.w3.org/2002/ws/desc/2/06/issues.html#x117
 [20] http://lists.w3.org/Archives/Public/www-ws-desc/2004Feb/0246.html

16:30 Joint Session with TAG (Web arch [21])
    - Saying more about QName mapping (?) [22]
    - Error recovery vs. not having to "validate" parts of the doc not
      used or examined by a processor. [23]
    - Comparison of XML namespaces with Schema and WSDL namespaces. [23]
    - Cracking a component designator URI. [23]
    - Operation safety? (Issue 117) [24]

 [21] http://www.w3.org/TR/2003/WD-webarch-20031209/
 [22] http://lists.w3.org/Archives/Public/www-ws-desc/2004Feb/0164.html
 [23] http://lists.w3.org/Archives/Public/www-ws-desc/2004Feb/0180.html
 [24] http://www.w3.org/2002/ws/desc/2/06/issues.html#x117

18:00 Adjourn


-------------------------------------------------------
Friday 5 March
-------------------------------------------------------
08:30 Issue 124: Semantics of mandatory properties and features [30]

 [30] http://www.w3.org/2002/ws/desc/2/06/issues.html#x124

08:45 Issue 149: Duplicate features with conflicting @required [31]

 [31] http://lists.w3.org/Archives/Public/www-ws-desc/2004Feb/0208.html 

09:00 Issue 134: Proposal for adding Compositors [32]

 [32] http://www.w3.org/2002/ws/desc/2/06/issues.html#x112

10:30 Break     ----------------------------------------

10:50 Issue 120: Operation Name feature proposal [33, 34, 35]
    - Mark Baker had some comments [36, 37].
    - Request for being able to detect where the OperationName is
      located (Mark Baker) [38]
    - First message only, or in responses? (Jacek) [39]

 [33] http://www.w3.org/2002/ws/desc/2/06/issues.html#x120
 [34] http://lists.w3.org/Archives/Public/www-ws-desc/2004Jan/0082.html
 [35] http://lists.w3.org/Archives/Public/www-ws-desc/2004Feb/0152.html 
 [36] http://lists.w3.org/Archives/Public/www-ws-desc/2004Jan/0173.html
 [37] http://lists.w3.org/Archives/Public/www-ws-desc/2004Jan/0175.html
 [38] http://lists.w3.org/Archives/Public/www-ws-desc/2004Feb/0105.html
 [39] http://lists.w3.org/Archives/Public/www-ws-desc/2004Feb/0165.html

12:00 Lunch     ----------------------------------------

13:30 Import/include issues
    - 127: Behavior if import/include fails [40]
    - 128: Two imports for the same namespace illegal? [41] 
    - 129: Allow multiple values for import/include locations [42]

 [40] http://www.w3.org/2002/ws/desc/2/06/issues.html#x127 
 [41] http://www.w3.org/2002/ws/desc/2/06/issues.html#x128
 [42] http://www.w3.org/2002/ws/desc/2/06/issues.html#x129

14:00 Naming issues
    - 114: Name of wsoap:fault/@name [43]
    - 126: Confusion between binding and element names [44]
    - Name attribute consistency
      [***** ACTION: Sanjiva to consistify the @name attributes. *****]
      Any issues here?

 [43] http://www.w3.org/2002/ws/desc/2/06/issues.html#x114 
 [44] http://www.w3.org/2002/ws/desc/2/06/issues.html#x126

14:30 Issue 131: Treatment of optional extensions [45]

 [45] http://www.w3.org/2002/ws/desc/2/06/issues.html#x139

14:35 Issue 139: Non-deterministic schema [46]

 [46] http://www.w3.org/2002/ws/desc/2/06/issues.html#x139

14:50 Issue 148: Double check URI comparison algorithm and relative 
               URI use [47]
      [***** Needs proposal, possibly based on TAG joint session ****]

 [47] http://lists.w3.org/Archives/Public/www-ws-desc/2004Feb/0180.html

15:00 Break     ----------------------------------------

15:20 Issue 115: Improving on-the-wire conformance [48]
      STATUS: Resolution proposed at 19 Feb telcon.
      [***** Review actual text that gets added to the spec before 
             closing. *****]

 [48] http://www.w3.org/2002/ws/desc/2/06/issues.html#x115

15:30 Issue 135: WSDL Specification readability [49]
      [***** STATUS: David Orchard to produces a specific example of 
             the kind of change he envisions. *****]

 [49] http://www.w3.org/2002/ws/desc/2/06/issues.html#x135

15:40  Issue 104 Appendix E cleanup (using alternate type systems) [50,
51]
     - Bijan's review [52].
     - Might want to add OWL support to appendix E
      [***** STATUS: Awaiting concrete proposal from Jacek and 
             Bijan (does 143, 144, 145 cover it?) *****]

[50] http://www.w3.org/2002/ws/desc/2/06/issues.html#x104
[51] http://lists.w3.org/Archives/Public/www-ws-desc/2003Sep/0136.html
[52] http://lists.w3.org/Archives/Public/www-ws-desc/2004Jan/0182.html

15:50 Issue 97: Schema language for SOAP encoding [53]
    - Proposal from Jacek [54]
    - Address comments from reviewers (Paul, Asir)
    - Decide on disposition: Chair recommends a Note.
      [*****ACTION:   Paul and Asir to review the SOAP Data Model 
                      Schema. *****] 

 [53] http://www.w3.org/2002/ws/desc/2/06/issues.html#x97
 [54]
http://lists.w3.org/Archives/Public/www-ws-desc/2004Feb/att-0098/SOAPDat
aModelSchema.html__charset_ISO-8859-2

16:15 Issue 106: Using RDF in WSDL [55, 56].
      [***** STATUS: Dependent upon RDF mapping first draft, need to 
             figure out how to get unblocked from going to Last 
             Call. *****]

 [55] http://www.w3.org/2002/ws/desc/2/06/issues.html#x106
 [56] http://lists.w3.org/Archives/Public/www-ws-desc/2003May/0076.html

16:30 Issue 111: Simplified syntax?  [57]

 [57] http://www.w3.org/2002/ws/desc/2/06/issues.html#x111

17:45 Next steps towards Last Call
    - How to close any unresolved issues.
    - When will we see the first internal Last Call spec?
    - Process for reviewing and approving Parts 1 and 2.
    - Ramping up on Part 3.

18:00 Adjourn


------------------------------------------------------------------
We may need to squeeze the following item into the agenda somehow.
------------------------------------------------------------------
xx:xx Media type description TF results [55]
      [***** inputs from joint meeting with XMLP? *****]

[60]
http://lists.w3.org/Archives/Public/public-ws-media-types/2004Jan/0001.h
tml

Received on Friday, 27 February 2004 15:19:47 UTC