- From: Jonathan Marsh <jmarsh@microsoft.com>
- Date: Fri, 7 Nov 2003 15:18:31 -0800
- To: <www-ws-desc@w3.org>
- Message-ID: <DF1BAFBC28DF694A823C9A8400E71EA201B62770@RED-MSG-30.redmond.corp.microsoft.com>
Web Service Description Group Minutes, FTF meeting 3-5 November 2003 Sunnyvale, hosted by Fujitsu. ------------------------------------------------------- Summary ------------------------------------------------------- Monday: Charter Extension: RESOLVED: New schedule: LC May 04 (Parts 1&2 ready by Mar 04) CR Oct 04 PR Jan-Apr 05 REC Mar-Jun 05 Errata 6 months RESOLVED: Prepare 24 month charter extension Faults: RESOLVED: Accept proposal at: http://lists.w3.org/Archives/Public/www-ws-desc/2003Nov/0025.html - Add interface/operation/infault|outfault/@name - Add binding/wsoap:FaultDefault - Add binding/operation/infault|outfault/@name - Add binding/operation/infault|outfault/@messageReference - Add binding/operation/infault|outfault/wsoap:Code|wsoap:Value|wsoap:Subcode ACTION: Pauld to work out proposal for a top-level fault in more detail RPC: RESOLVED: Accept (with minor editorial fixes) Umit's RPC proposal: http://lists.w3.org/Archives/Public/www-ws-desc/2003Nov/0007.html ACTION: JeffM to propose text to the effect that messages must conform to their schemas. RESOLVED: Accept Roberto's proposal for @rpc:signature: http://lists.w3.org/Archives/Public/www-ws-desc/2003Oct/0347.html ACTION: Sanjiva to put note in spec for this round of publication to reflect the decision of adopting Roberto's proposal. WSDL Component Designators: ACITON: Marsh put in future agenda for discussion on TAG feedback on frag id. Uniqueness on the Wire: RESOLUTION: Add discussion of dispatch to the Primer. ACTION: Umit (with help of Glen) will write up a proposal for normative dispatching feature. Tuesday: Pattern Inference: RESOLVED: Accept (with minor changes) proposal at: http://lists.w3.org/Archives/Public/www-ws-desc/2003Nov/0017.html - If the MEP (including its fault rule) permits only one fault in a given direction, then the messageReference attribute for the fault in that direction is optional, because it can be deduced from the pattern. RESOLVED: @pattern remains required - no consensus to change. Features and Properties: Still some complaints about Features and Properties - we may have LC or CR feedback on this part of the spec. Didn't reopen the issue. Arthur's proposal for <wsdl:propertySchema> was rejected. RESOLVED: Close issue #2: Add <wsoap:action uri="uri"/>. Headers: RESOLVED: Remove @headers attribute. RESOLVED: Rename @body to @message. RESOLVED: Rename @detail to @message ACTION: Glen to write up rationale for removing headers (and?) proposal for a generic header-adding property/feature. Attributes: RESOLVED: Adopt TF recommendation on get/set styles. Support for attribute styles is weakening with IBM and some in GGF now not in favor. Feature may be revisited if GGF formally changes their position, or feature might be marked as "at risk" in LC draft. ACTION: Jacekk to make proposal on combining the get/set style URIs into one. Updated definition of equivalence: Informative discussion only http binding Informative discussion only Multiple inline schemas RESOLVED: No new restrictions on embedded schemas (specifically, we don't constrain the xs:import/@location attribute on embedded schemas.) ISSUE: Does wsdl:import pull in schema components from wsdl:definitions/wsdl:types? Need to check. Wednesday: Publication: RESOLVED: Publish parts 1 and 2. Endpoint references: RESOLVED: Add a paragraph in the spec describing that <wsdl:service> can show up on the wire as a service reference. Primer will have some examples (see Roberto's counterproposal as a basis). RESOLVED: Make top WSDL elements global in the schema to facilitate reuse. ISSUE #95: Should wsdl:service/@name be optional? We don't want to force users to have to invent a name when <wsdl:service> appears on the wire, but currently we require @name within the context of a wsdl:description.
Received on Friday, 7 November 2003 18:18:26 UTC