W3C home > Mailing lists > Public > www-ws-desc@w3.org > January 2004

[rev] Agenda, 8 January 2004 WS Desc telcon

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Wed, 7 Jan 2004 13:52:03 -0800
Message-ID: <DF1BAFBC28DF694A823C9A8400E71EA2022F3A7F@RED-MSG-30.redmond.corp.microsoft.com>
To: "Web Services Description" <www-ws-desc@w3.org>

[Added some issue numbers and administrivia links.]

0.  Dial in information (members only) [.1]:

See the public WG page [.2] for pointers to current documents and other
information, and the private page [.3] for administrative matters.

If you have additions to the agenda, please email them to the WG list
before the start of the telcon.

[.1] http://lists.w3.org/Archives/Member/w3c-ws-desc/2004Jan/0000.html
[.2] http://www.w3.org/2002/ws/desc/
[.3] http://www.w3.org/2002/ws/desc/admin

--------------------------------------------------------------------
Agenda

1.  Assign scribe.  Lucky minute taker for this week is:
      Erik Ackerman, (fallbacks: Igor Sedukhin, Adi Sakala, 
      Jeffrey Schlimmer, Amy Lewis, Arthur Ryman, Prasad Yendluri,
      Dietmar Gaertner, Roberto Chinnici, Tom Jordahl)

--------------------------------------------------------------------
2.  Approval of minutes:
  - Dec 18th telcon [.1].

[.1] http://lists.w3.org/Archives/Public/www-ws-desc/2004Jan/0005.html

--------------------------------------------------------------------
3.  Review of Action items [.1].
?         2003-09-18: Marsh to review the QA operational
                      guidelines.
?         2003-10-09: Bijan to look into message extensibility 
                      Issues (Appendix E, Jacek's review) wrt RDF data, 
                      and discuss with Jacek.
?         2003-11-03: Umit (with help of Glen) will write up a proposal 
                      for normative dispatching feature.
?         2003-11-04: Glen to write up rationale for removing headers 
                      (and?) proposal for a generic header-adding
                      property/feature.
?         2003-11-20: GlenD to write up Schemas in imported WSDL stuff
                      in specese.

[.1] http://www.w3.org/2002/ws/desc/#actions

--------------------------------------------------------------------
4.  Administrivia
  a. Upcoming FTFs
     - January 26-30, Bedford, MA (Sonic) [.1]
       WSArch 26-29(noon)
       WSDesc 28(noon)-30
       Please register! [.2]
       Joint session topics: Usage scenarios document (NOTE)
     - March 3-4, Cannes-Mandelieu, France [.3]
       Joint session with the TAG?
  b. Web Architecture Document [.4, .5] review:
       Volunteers so far: Jacek, Bijan, Jonathan
  c. WSDesc charter AC review [.6]

[.1] http://www.w3.org/2003/12/ws-desc-charter
[.2] http://www.w3.org/2002/09/wbs/34650/WSAD0401/
[.3] http://www.w3.org/2003/08/allgroupoverview.html
[.4] http://lists.w3.org/Archives/Public/www-ws-desc/2003Dec/0029.html
[.5] http://www.w3.org/TR/2003/WD-webarch-20031209/
[.6] http://lists.w3.org/Archives/Member/w3c-ws-desc/2004Jan/0003.html

------------------------------------------------------------------
5.  Task Force Status.
 a. Properties and Features (dormant)
 b. Patterns (dormant)
 c. Attributes (dormant)
 d. QA & Testing
  - Response to comments on QA Spec Guidelines [.2]
  - Implement QA Operational guidelines? [.3]
 e. Joint TF on media type description.
  - mailing list [.4]

[.1] http://lists.w3.org/Archives/Public/www-ws-desc/2003Sep/0023.html
[.2] http://lists.w3.org/Archives/Public/www-ws-desc/2003Sep/0074.html
[.3] http://lists.w3.org/Archives/Member/w3c-ws-desc/2003Sep/0023.html
[.4] http://lists.w3.org/Archives/Public/www-ws-desc/2004Jan/0000.html

------------------------------------------------------------------
6.  New Issues.  Merged issues list [.1].
  - Assign issue numbers to these proposals:
    = Abstract Faults (Paul): fault-name-uniqueness? [.2]
    = Using RDF in WSDL (see item 16)
  - Schema extracts for vector, matrix, array (Paul) [.3] (or not [.4])
  - Properties and schema languages other than XSD (Roberto) [.5] 

[.1] http://tinyurl.com/ysgl
  (redirects to http://www.w3.org/2002/ws/desc/2/06/issues.html)
[.2] http://lists.w3.org/Archives/Public/www-ws-desc/2003Dec/0046.html
[.3] http://lists.w3.org/Archives/Public/www-ws-desc/2003Dec/0048.html
[.4] http://lists.w3.org/Archives/Public/www-ws-desc/2003Dec/0049.html
[.5] http://lists.w3.org/Archives/Public/www-ws-desc/2004Jan/0006.html

------------------------------------------------------------------
7.  Two logical WSDL documents describing the same service
  - Need to answer query from Arch [.1].
  - Still have some churn over single-interface per service.

[.1] http://lists.w3.org/Archives/Public/www-ws-desc/2003Dec/0045.html

------------------------------------------------------------------
8.  Issue #24 [.1] Real difference between literal vs. encoded? 
    Originally decided that @encodingStyle is a hint about how 
    types/schema was generated. Reopened by Macromedia\Tom at 
    telecon prior to 30 July 2003.  We haven't really discussed it
    since then.

  - Discuss the use cases not satisfied by the prior decision.

[.1] http://tinyurl.com/ysgl#x24

------------------------------------------------------------------
9.  Abstract Faults
  - Proposal (Paul) [.1] as modified by [.2]

[.1] http://lists.w3.org/Archives/Public/www-ws-desc/2003Dec/0046.html
[.2] http://lists.w3.org/Archives/Public/www-ws-desc/2003Dec/0071.html

------------------------------------------------------------------
10. Issue fault-name-uniqueness [.1]: Should faults be named with
QNames? 
    In WSDL 1.1 fault names are NCNames which are not unique within 
    portType even. This leads to a cumbersome mechanism to uniquely 
    identify a fault.
  - Solved by Abstract Faults proposal?

[.1] http://tinyurl.com/ysgl#xissue%20fault%20name%20uniqueness

------------------------------------------------------------------
11. Issue 85: HTTP binding options [.1]
    - option 1: drop HTTP binding
    - option 2: input becomes POST body and output is POST response
    - option 3: option 2 + GET goes to http:address URL and output is 
                GET response
    - option 4: option 3 + rules to move all parameters into query 
                parameters for GET binding with MEP=in-out and
                @style=rpc
    - option 5: option 4 + URL replacement (not just query params)
    Latest proposal: [.3] and issues [.4]

[.1] http://lists.w3.org/Archives/Public/www-ws-desc/2003Nov/0048.html
[.2] http://www.w3.org/2002/ws/desc/2/06/issues.html#x85
[.3] http://lists.w3.org/Archives/Public/www-ws-desc/2003Dec/0051.html
[.4] http://lists.w3.org/Archives/Public/www-ws-desc/2003Dec/0059.html

==================================================================
Following items pending additional input:
------------------------------------------------------------------
12. Issue #102: Schemas in imported WSDL [.1]
    - Seems to be agreement on the existing behavior as described by
    Gudge and Amy.  Still outstanding: do we add note along the lines
    of Glen's suggestion: put text in the spec to the effect that WSDL
    processors SHOULD make schema namespaces embedded in the <types> 
    sections of imported WSDLs available to their schema processors for
    xs:import where possible.

    Awaiting specese sample from Glen.

[.1] http://lists.w3.org/Archives/Public/www-ws-desc/2003Nov/0109.html

------------------------------------------------------------------
13. Issue #103: Proposal for combining the two attribute operation
styles 
    to one (Jacek) [.1]
    Deferred pending final disposition of attribute styles.

[.1] http://lists.w3.org/Archives/Public/www-ws-desc/2003Nov/0164.html

------------------------------------------------------------------
14. Issue 64 [.1] Operations an HTTP verbs (Mark Baker) [.2, .3, .4]
  - Jacek's synthesis [.5].
  - Awaiting description from Philippe showing how properties or
    extensions can be used to annotate the WSDL with RESTful 
    properties.  Ask Mark for a definitive list of those properties 
    so we can consider how to associate them with property URIs or 
    namespaces.
  - Marking WSDL operations as "safe" (DaveO/TAG) [.6, .7]

[.1] http://tinyurl.com/mwuy#x64
[.2] http://lists.w3.org/Archives/Public/www-ws-desc/2003May/0094.html
[.3] http://lists.w3.org/Archives/Public/www-ws-desc/2003Jan/0103.html
[.4] http://lists.w3.org/Archives/Public/www-ws-desc/2003Jan/0111.html
[.5] http://lists.w3.org/Archives/Public/www-ws-desc/2003Jul/0095.html
[.6] http://lists.w3.org/Archives/Public/www-ws-desc/2003Nov/0104.html
[.7] http://lists.w3.org/Archives/Public/www-ws-desc/2003Dec/0021.html

------------------------------------------------------------------
15. Issue #104: Appendix E cleanup [.1]

[.1] http://lists.w3.org/Archives/Public/www-ws-desc/2003Sep/0136.html

------------------------------------------------------------------
16. Using RDF in WSDL [.1].
    Dependent upon RDF mapping first draft.

[.1] http://lists.w3.org/Archives/Public/www-ws-desc/2003May/0076.html
Received on Wednesday, 7 January 2004 16:52:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:28 GMT