- From: Sanjiva Weerawarana <sanjiva@watson.ibm.com>
- Date: Tue, 11 Jun 2002 16:06:38 +0600
- To: "WS-Desc WG \(Public\)" <www-ws-desc@w3.org>
W3C WS Desc WG F2F Meeting June 10-12, Paris, France Minutes AM Monday Next deliverables: ----------------- - publish document "as-is" after the meeting - need to decide name of document and namespace - would like to publish all parts, including requirements - will include issues in the docs to make sure its clear that this is a *working* draft and lots of things are still to be done - what's going to be in the primer? David Booth will provide an overview - RDF mapping: on backburner for now, will tackle after getting the draft in better shape Publication Schedule: -------------------- - target is to have an updated draft a week after the F2F to review (must contain edits reflecting decisions at the meeting) - spend a week of review and then take a vote - target publication date is June 30th Discussion on Extensibility: --------------------------- - Discussing the proposal that Roberto sent to the list on June 6th - Current proposal is to allow an extension to CHANGE the semantics of the base language - Not everyone is in agreement with that - (long and colorful discussion on this topic) - proposal from Keith: why not just leave WSDL 1.1's model except make it open-content - proposal presented by Glenn: taking Keith's proposal and trying to explain it - features of extensions 1) do we have a "catch-fire-and-die" flag - local - global 2) scoping of extensibility - proposals A) top-level <wsdl:requiredExtension uri="..."/> - global catch-fire-and-die flag - any qualified/attrributes can appear anywhere (without being declared as a required extension) - in prolog B) @wsdl:required anywhere - local catch-fire-and-die flag (based on element qname) - scoped (I didn't quite write this down right) - indirectly required attributes - status quo (modulo prose) + open-content C) <wsdl:extension namespace="uri"/> - (B) + top-level declaration of extension namespace - We'll decide between (A) & (B) and then consider (C) - Straw poll: (A): 3 (B): 11 (lots more than for (A)) - After lunch we'll consider (C) and also question of whether extensions are allowed to modify WSDL semantics or not. - LUNCH
Received on Tuesday, 11 June 2002 06:07:19 UTC