- From: Jonathan Marsh <jmarsh@microsoft.com>
- Date: Tue, 8 Mar 2005 13:08:06 -0800
- To: <www-ws-desc@w3.org>
- Message-ID: <7DA77BF2392448449D094BCEF67569A506C63B9B@RED-MSG-30.redmond.corp.microsoft.com>
Encl: Minutes of WS Description FTF March 3-4 2005 Boston MA Summary: Thursday Issue LC70: Pluggability of Schema Languages in WSDL RESOLUTION: Clarify in sec 2.1.3 and elsewhere that there is only a single element declaration in the set for each QName. Add text along the lines suggested by David - "include a note in the spec saying that if someone combines multiple schema languages may be a problem, and we have not solved this problem." ACTION: Jonathan to formalize the CR criteria bag and drop "testing type system extensibility" into it ACTION: Jonathan will ask the WG what is the publication plan for the type system note around 3/17. Issue LC5f: QA Review on WSDL 2.0 Part 1, intro and conformance issues (f) RESOLUTION: Accepted proposal, including option A at http://lists.w3.org/Archives/Public/www-ws-desc/2005Jan/0099.html, replacing point 7 with "Thus, the meaning of the element cannot be determined without understanding the attached extension" plus other editorial license as necessary. Issue LC5f Closed. RESOLUTION: Issues LC75r, LC75v, LC70 will be closed as a consequence of LC5f. RESOLUTION: Issue LC63 closed with the resolution of LC5F and LC70. Issue LC52b: RESOLUTION: {message content model} is optional, missing when a different type system is in use. Issue LC52b closed. Async Task Force: Task Force will continue to meet. Issue 76d: Replace ADD with header construct RESOLUTION: Accept proposal C (http://lists.w3.org/Archives/Public/www-ws-desc/2005Jan/att-0094/soap-h eader-blocks.html) with the following amendments: - syntax will be <wsoap:header element="..." mustUnderstand="xs:Boolean" wsdl:required="xs:boolean"/>* - goes into part 3 and AD feature will be removed from Part 2 - similar HTTP functionality will be added: <whttp:header element="..." wsdl:required="xs:boolean"/>* - clarify that the whttp:header elements are avaiable to use within the SOAP HTTP binding ACTION: Asir to double check the subissues of 76d to see if they should be raised as issues and to do so. RESOLUTION: Issues 24, 53, 61f (dup of 76d) closed by the resolution of 76d. Friday Media Type Description Note Issue 272: Architectural issues RESOLUTION: Closed - no interest in pursuing a NOTATION based solution. ACTION: Umit to add a warning along the lines of: "The intent of the expectedMediaType attribute is to allow WSDL authors to indicate the range of media types that are acceptable for the binary data for which it is defined for, hence it serves as an design time indicator for possible contentType values that are expected. Therefore, authors are recommended to use wild cards with care, and recommended to indicate the list of media types if the set is limited." RESOLUTION: accept 2a, 2b, 3 from Addison's email ACTION: media type editors to rename xmlmime: to xmime Next steps: - Expect draft in a week - WSD, XMLP review for 2 weeks - Publish Issue LC106: Revisit LC21 resolution RESOLUTION: Have style only at the operation level, specify that the uri/multipart styles may be used for any mep with an initial message. Issue LC75e: Move RPC style to Part 2 RESOLUTION: Close LC75e as duplicate. RESOLUTION: fold parts 2 and 3 into a single document named "Adjuncts" ACTION: Editors to merge parts 2 and 3, move the rpc style from part 1 into it and name the result "Adjuncts". Issue LC75g: RPC should allow element wildcards ACTION: roberto to come up with a proposal for LC75g (wildcards in rpc style) Issue LC75h: Disallow multiple returns in RPC RESOLUTION: close 75h by adding rationale for multiple returns to the spec. Issue LC89l: Drop component model RESOLUTION: Issue closed with no action. Issue LC89g: Bleed between XML representation, infoset, pseudo-schema, component model RESOLUTION: Reclassify as editorial. Issue LC81: The Component Model is Underconstrained wrt the WSDL 2.0 Schema RESOLUTION: Editors to add constraints whereever needed to ensure component model allows no more than can be serialized as an XML document. Issue LC105: Proposal for Simplifications to the Component Model RESOLUTION: Add constraint that top-level components must be unique. RESOLUTION: Add parent property to nested components.
Attachments
- text/html attachment: 20050304-ws-desc-minutes.html
- text/html attachment: 20050303-ws-desc-minutes.html
Received on Tuesday, 8 March 2005 21:09:54 UTC