WSDL 2.0 Last Call Schedule (Regrets for July 1)

Regrets for me on July 1 as I will also be enjoying "Canada" day.

Helen


-----Original Message-----
From: Peter Madziak 
Sent: Tuesday, June 15, 2004 9:08 AM
To: Jonathan Marsh; www-ws-desc@w3.org
Subject: RE: WSDL 2.0 Last Call Schedule (Regrets for July 1)



Regrets for me on July 1 as I will be enjoying "Canada Day" as well.

Peter

-----Original Message-----
From: David Orchard [mailto:dorchard@bea.com]
Sent: Monday, June 14, 2004 5:55 PM
To: Jonathan Marsh; www-ws-desc@w3.org
Subject: RE: WSDL 2.0 Last Call Schedule



Regrets for July 1.  July 1st is a statutory holiday in Canada, known as "Canada day" and so I will not be on the call that day.

Cheers,
Dave

> -----Original Message-----
> From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org]On
> Behalf Of Jonathan Marsh
> Sent: Monday, June 14, 2004 1:03 PM
> To: www-ws-desc@w3.org
> Subject: WSDL 2.0 Last Call Schedule
> 
> 
> 
> Follows is an aggressive but I think doable schedule for getting WSDL
> 2.0 to last call.  It will take either a greater ability by the WG to
> address issues by email, or by the chair to declare issues closed if
> there are no proposals forthcoming.  If we miss this schedule and are
> still resolving issues in London, our August holiday will be 
> scrapped to
> keep publication from slipping into September.
> 
> June 17th (2 hour telcon)
>  Issues scheduled for closure:
>   174 Jonathan Part 1 Design  Tie WSDL conformance to XML 
> conformance? 
>   175 Jonathan Part 1 Design  Is it valid for a XML 1.1 document to
> import 
>                               or include a XML 1.0 document (and vice 
>                               versa)? 
>   176 Jonathan Part 1 Design  Can a WSDL 2.0 XML 1.1 document contain
> (or 
>                               reference), a XML Schema 1.0 type
> description?  
>   177 Jonathan Part 1 Design  Normative dependence on XML Schema 1.0 
>                               precludes XML 1.1 
>   207 WG       Part 3 Design  How to mark which elements to optimize
>   212 Mark     Part 1 Design  Explain using bindings across all
> operations 
>   216 Mark     Part 1 Design  RPC and XML Schema not orthogonal 
>   217 Mark     Part 1 Design  Syntax for multiple styles 
>   221 Mark     Part 1 Design  Identify components by URI 
>   222 Mark     Part 1 Design  Name[space] for the intended semantics 
>   223 Mark     Part 1 Design  Import/include processing model 
>   224 Mark     Part 1 Design  Formalize component model
> 
> June 24th (2 hour telcon)
>  Issues scheduled for closure:
>   112 Glen/DaveO Part 1 Design  New headers/body style?  
>   130 DaveO    Part 3 Design  Need async request/response 
> HTTP binding 
>   157 Glen     Part 1 Design  f&p at the service level 
>   160 Jacek    Part 1 Design  Formalize processing model 
>   167 Hugo     Part 1 Ed      Synchronize pseudo-schema 
>   169 DaveO    Part 1 Design  Syntax for webMethod - property or
> attribute?
>   209 Mark     Part 1 Design  Reference frag ids from media type 
>                               registration 
>   214 Mark     Part 1 Design  Refine "properties" terminology 
>   219 Mark     Part 1 Design  Actual value vs. normalized value
>   220 Mark     Part 1 Design  Document interface extension semantics 
>   225 Mark     Part 1 Design  Non-XML type system extensibility.
> 
> July 1st (2 hour telcon)
>  Issues scheduled for closure:
>   135 Jonathan/Arthur/DavidB Part 1 Ed      WSDL Specification
> readability 
>   158 ?        Part 3 Design  Setting HTTP headers in the 
> HTTP binding 
>   159 WG       Part 1 Design  Messages with mixed Body content or 
>                               multiple element content 
>   168 ?        Part 1 Design  Which operation 
>   189 DaveO    Part 3 Design  Binding message content to URI
>   195 DaveO    Part 1 Design  Property value merging
>   197 ?        Part 1 Design  Don't override interface feature
> requiredness 
>                               in binding 
>   210 ?        Part 1 Design  Refine equivalence algorithm
>   211 ?        Part 1 Design  Omit interface message in binding?
>   218 ?        Part 1 Design  Justify interface faults.
> 
> July 8th (90 min telcon):
>  Any leftover issues
> 
> July 15th (90 min telcon):
>  Editors complete editorial work for WG review.
> 
> July 22nd (90 min or less telcon):
>  Approval of Last Call drafts.
> 
> July 26th WSDL 2.0 Last Call publication.
> 
> July 29th (no telcon)
> 
> Aug 2-5th (London FTF):
>  Early Last Call comments
>  Media Type Desciprtion
>  Primer
>  RDF Mapping
>  CR preparation
> 
> Aug 6th-30th
>  WG holiday
> 
> Sept 2nd (90 min telcon)
>  Resume regular telcons.
> 
> 
>

Received on Tuesday, 15 June 2004 09:14:30 UTC