Agenda: 21 December 2006 WS Description telcon

"Jonathan Marsh" <[email protected]>
Newsgroups gmane.comp.web.services.description
Message-ID <013d01c723ce$e6fca2a0$3401a8c0@DELLICIOUS>
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/2006Dec/0006.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 one of:
      Anish Karmarkar, Glen Daniels, Charlton Baretto,
      Roberto Chinnici, Gilbert Pilz, Jean-Jacques Moreau
      Philippe le Hegaret, Tony Rogers, Tom Jordahl, Amy Lewis

--------------------------------------------------------------------
2.  Approval of minutes:
  - Dec 14 [.1]

[.1]
http://lists.w3.org/Archives/Public/www-ws-desc/2006Dec/att-0059/20061214-ws
-desc-minutes.html

--------------------------------------------------------------------
3.  Review of Action items [.1].

[Interop]
?         2006-11-30: [interop] John Kaputin to create a test case 
                      with "required=false". 
?         2006-12-14: [interop] Jonathan to fix transferCodings - 
                      add control group

[WG]
DONE [.3] 2006-10-12: pdowney to review the Schema WG note on versioning 
                      in 1.1.
?         2006-12-14: Arthur to examine the equivalence of 0006 and 0014
?         2006-12-14: plh to check with XMLP whether they should be 
                      interested in 204 as well
?         2006-12-14: plh to come up with a more detailed proposal for 
                      CR112 if possible

Current Editorial Action Items

Note: Editorial AIs associated with LC issues recorded at [.2].

[.1] http://www.w3.org/2002/ws/desc/#actions
[.2] http://www.w3.org/2002/ws/desc/5/cr-issues/actions_owner.html
[.3] http://lists.w3.org/Archives/Public/www-ws-desc/2006Dec/0062.html

---------------------------------------------------------------------
4.  Administrivia
  - Year end telcons
    + Dec 28: cancel
    + Jan 4: resume telcon
  - LC reviews
    + Databinding [.1]
    + Policy [.2], Charlton's draft comments [.3]
  - WSDL 1.1 component designators
    + Do we have a preference? [.4]
  - Interchange format draft Note [.5]

[.1] http://lists.w3.org/Archives/Member/w3c-ws-desc/2006Nov/0010.html
[.2] http://lists.w3.org/Archives/Public/www-ws-desc/2006Nov/0127.html
[.3] http://lists.w3.org/Archives/Public/www-ws-desc/2006Dec/0055.html
[.4]  http://lists.w3.org/Archives/Public/www-ws-desc/2006Dec/0049.html
[.5] http://lists.w3.org/Archives/Public/www-ws-desc/2006Dec/0044.html

---------------------------------------------------------------------
5.  MTOM Description
  - Paul's proposal [.1]
  - Jonathan/Asir's counter-proposal [.2]

[.1] http://lists.w3.org/Archives/Public/www-ws-desc/2006Nov/0029.html
[.2] http://lists.w3.org/Archives/Public/www-ws-desc/2006Dec/0016.html

-----------------------------------------------------------------
6.  Issue CR108: Do MessageLabel-0006 and MessageLabel-0014 state the 
                 same requirement? [.1]
  - Arthur agrees [.2]
  - Amy recommends removing the third assertion [.3], and points out
    The lack of restrictions enforcing a one-to-one correspondence 
    between binding operations and interface operations.
  - ACTION: Arthur to examine the equivalence of 0006 and 0014
  - Amy's analysis [.4]

[.1] http://www.w3.org/2002/ws/desc/5/cr-issues/#CR108
[.2] http://lists.w3.org/Archives/Public/www-ws-desc/2006Nov/0085.html
[.3] http://lists.w3.org/Archives/Public/www-ws-desc/2006Dec/0033.html
[.4] http://lists.w3.org/Archives/Public/www-ws-desc/2006Dec/0058.html

-----------------------------------------------------------------
7.  Issue CR111: Mapping WSDL meps to the HTTP binding [.1]
  - ACTION: plh to check with XMLP whether they should be interested 
            in 204 as well

[.1] http://www.w3.org/2002/ws/desc/5/cr-issues/#CR111

-----------------------------------------------------------------
8.  Issue CR112: HTTP Location property definition [.1]
  - ACTION: plh to come up with a more detailed proposal for CR112 
            if possible
[.1] http://www.w3.org/2002/ws/desc/5/cr-issues/#CR112

-----------------------------------------------------------------
9.  Issue CR114: Mapping WSDL MEPs to SOAP MEPs [.1]

[.1] http://www.w3.org/2002/ws/desc/5/cr-issues/#CR114

-----------------------------------------------------------------
10. Issue CR115: Suggested editorial change for assertion Import-0072 [.1]

[.1] http://www.w3.org/2002/ws/desc/5/cr-issues/#CR115

-----------------------------------------------------------------
11. Issue CR116: 6.7.1.1 Construction of the request IRI using the 
                 http location [.1]

[.1] http://www.w3.org/2002/ws/desc/5/cr-issues/#CR116

-----------------------------------------------------------------
12. Issue CR117: Re: 6.7.1.1 Construction of the request IRI using the 
                 http location [.1]

[.1] http://www.w3.org/2002/ws/desc/5/cr-issues/#CR117

-----------------------------------------------------------------
13. Issue CR118: Suggested removal of 2 assertions [.1]

[.1] http://www.w3.org/2002/ws/desc/5/cr-issues/#CR118

-----------------------------------------------------------------
14. Issue CR119: Missing attribute in section 6.2 [.1]

[.1] http://www.w3.org/2002/ws/desc/5/cr-issues/#CR119

-----------------------------------------------------------------
15. Issue CR120: SOAP Response and IRI style [.1]

[.1] http://www.w3.org/2002/ws/desc/5/cr-issues/#CR120

-----------------------------------------------------------------
16. Issue CR121: WSDL enhancement request [.1]

[.1] http://www.w3.org/2002/ws/desc/5/cr-issues/#CR121

-----------------------------------------------------------------
17. Issue CR122: Clarification about ignoreUncited behaviour [.1]

[.1] http://www.w3.org/2002/ws/desc/5/cr-issues/#CR122

-----------------------------------------------------------------
18. Issue CR123: HTTP Method selection [.1]

[.1] http://www.w3.org/2002/ws/desc/5/cr-issues/#CR123

-----------------------------------------------------------------
19. Issue CR124: editorial: features and properties in "xml 
                 representation" sections [.1]

[.1] http://www.w3.org/2002/ws/desc/5/cr-issues/#CR124

-----------------------------------------------------------------
20. Issue CR125: problem with pattern attribute definition? [.1]

[.1] http://www.w3.org/2002/ws/desc/5/cr-issues/#CR125

-----------------------------------------------------------------
21. Issue CR126: Re: New interchange results [.1]

[.1] http://www.w3.org/2002/ws/desc/5/cr-issues/#CR126

-----------------------------------------------------------------
22. Issue CR127: Message Dispatching Primer Section [.1]

[.1] http://www.w3.org/2002/ws/desc/5/cr-issues/#CR127

-----------------------------------------------------------------
23. Issue CR128: Interface Inheritance Section [.1]

[.1] http://www.w3.org/2002/ws/desc/5/cr-issues/#CR128

-----------------------------------------------------------------
24. Issue CR129: RE: Comment on Fragment [.1]

[.1] http://www.w3.org/2002/ws/desc/5/cr-issues/#CR129

-----------------------------------------------------------------
25. Issue CR130: Question on double curly braces with HTTP [.1]

[.1] http://www.w3.org/2002/ws/desc/5/cr-issues/#CR130

-----------------------------------------------------------------
26. Issue CR131: Clarifying assertion for HTTP Location [.1]

[.1] http://www.w3.org/2002/ws/desc/5/cr-issues/#CR131

-----------------------------------------------------------------
27. Issue CR021: Re: WSDL describing Interface operation safety [.1]

[.1] http://www.w3.org/2002/ws/desc/5/cr-issues/#CR021
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.