| Issue | Spec Part | Description | Resolution | Priority | Status |
|---|---|---|---|---|---|
| Registering media type | PartZ | We need to file a media type registration for WSDL. | Gotta do it | Medium | |
| Primer | Primer Editors to include best practices and the Schema group to review the best practices language. | During 20030311 telecon. | |||
| None | Part 1 | Add text regarding generation of errors when name conflicts occur. Probably needs to be a general statement somewhere in a 'Processing Model' section' | Low | Pending | |
| None | Part 1 | Rework component model so that semantics of properties are listed in the original property table, rather than spread through property table, xml rep and mapping sections | Low | Pending | |
| None | Part 1 | Make more terms into links in the component model part of the spec. | Low | Pending | |
| None | Part 1 | Be consistent in wrapping component model property names in curly braces {} | Low | Pending | |
| Unknown | Part 2 | Add a conformance section | Low | Pending | |
| Unknown | Part 3 | Add a conformance section | Low | Pending | |
| None. | Part 1, 2, 3 | Add markup to identify testable assertions. | [email] plus add @id (or similar) with unique and stable value. | Low | Pending |
| None. | Part 1, Part 3 | Add a few, non-normative examples, perhaps in an Appendix. | Low | Pending | |
| 4 | Part 2 | Interaction between the namespace attribute on soap:body and the targetNamespace of global element declarations. | Use Prasad's ammendment to Martin's proposal (minutes). | Medium | Done JJM. 2003/01/09 |
| 5 | Part 2 | Value and position of encodingStyle attribute. | Incoporate Arthur's proposal (email), i.e. encodingStyle can appear on soap header blocks (first level only), soap faults and soap body blocks (first level only) and contains one and only one URI. Incoporate Gudge's amendment (minutes), i.e. encodingStyle attribute with a value of "" is not allowed. | Medium | Done. JCS 20030117. |
| 17 | Part 2 | How to specify the SOAP role. | As described in proposal, with minor amendments from Gudge and Jonathan. | Medium | Done JJM. 2003/1/10 |
| 23 | Part 2 | Support SOAP 1.2 Module and Property |
- Add soap:Module - Add wsdl:Property (or similar) |
Medium | Done. JJM. 2003/01/16 |
| 25 | Part 2 | Relationship between XML Schemas and SOAP Data Model | Drop use AII | Medium | Done. JCS 20030115. |
| 34 | Part 1 | Port type extensibility. | Incorporate current state into main branch. Add new issue concerning uniqueness of operation names | Medium | Done. MJG 20021010. |
| 37 | Part 2 | Remove parameterOrder. | Removed section on parameterOrder. | Medium | Done. MJG 20020910 |
| 38 | Part 1 | Clarify extensibility. | JJM. Incorporated into spec already? | Medium | Done. MJG 20030117 |
| 42 | Part 1 | Shall "element" attribute of "part" only refer to elements defined in schema? | Current text allows reference to any XML based type system using element and/or type. Issue noted in spec regarding other type systems. | Medium | Done. MJG 20020910 |
| 43 | Part 1 | Does order matter for the child elements of "definitions"? | Order detailed in spec already. import*, types?, (message | portType | binding |service )* | Medium | Done. MJG 20020901 |
| 51 | Part 2 | Asymmetry between SOAP body and SOAP header |
- Drop parts AII from soap:body - Drop message and part AIIs from soap:header - Add element, type and localname AIIs to soap:header |
Medium | Done. JCS 20030115. |
| 57 | Part 1 | Should Operations permit alternate and multiple responses? | No action. | Medium | Done. MJG 20020910 |
| Unknown | Part 2 | Incorporate attribute roll-up into SOAP binding | Simplify common syntax for SOAP binding | Medium | Done. JCS 20030115. |
| Unknown | Part 1 | Remove name attribute from definitions. | Incorporate resolution. | Medium | Done. MJG 20021127. |
| Unknown | Part 1 | Update text on extensibility to reflect substitution group approach. | Medium | Done. MJG 20030117 | |
| Unknown | Part 1 | Remove 'pretend schema' | Delete it. | Medium | Done. MJG 20021127 |
| issue importing documents in same namespace | Part 1 | Two proposals, use wsdl:import and wsdl:include or use wsdl:using. Decided at Newton, MA FTF on 12th November that we will use wsdl:import and wsdl:include. | Incorporate resolution. wsdl:import works like xsd:import. wsdl:include works like xsd:include EXCEPT that chameleon includes are not allowed. | Medium | Done. MJG 20030116 |
| None | Part 1 | Add text regarding how QName resolutions works. | Medium | Done. MJG 20030117 | |
| None | Part 1 | Add text stating that without wsdl:import one CANNOT refer to WSDL components in a namespace other than the target | Medium | Done. MJG 20030116 | |
| None | Part 1 | Add text regarding multiple symbol spaces | Medium | Done. MJG 20030116 | |
| MA Minutes | Part 1 | Add text stating that if a portType inherits two operations that have the same local name then the component models of both operations must be identical | Medium | Done. MJG 20030116 | |
| MA Minutes | Part 1 | Add text stating that equivalence is based on component model equivalence. | Medium | Done. MJG 20030116 | |
| issue allow nonxml typesystems | Part 1 | Ensure other type systems are allowed in addition to XML Schema. This includes non-xml type systems ( e.g. Java ). | Write up that extensibility attributes/elements annotate the component model and that such attributes/elements can be used to refer to other type systems. | High | Done. MJG 2003-04-28 |
| None | Part 1 | Add text regarding how xs:import works when a child of wsdl:types | High | Done. MJG 2003-04-28 | |
| None | Part 1 | Incorporate changes related to multiple type systems in WSDL in addition to XML Schema. | Spec changes detailed in e-mail from Amelia Lewis. | High | Done. MJG 2003-01-20 |
| VA Minutes | Part 1 | Amend 'set of part definitions' to be 'list of part definitions'. This is from the Virginia minutes but I can't remember the reasoning behind it. | Low | Done. JCS 20030522 | |
| VA Minutes | Part 1 |
rather than type and element properties on part, have a variety of property to be more extensible Text from ednote previously in the spec: May need some other property akin to {variety} in operation components to easily distinguish between element and type based parts. This would also make integration with other type systems easier as such type systems would still need to define things in terms of elements or types |
Modify the {content reference} property of the part component to: a) Not be a reference, but rather be like other 'references' in WSDL b) Admit to other content descriptions than XML element decls and XML schema type defs |
Medium | Not relevant as message/part is now history. SW 2003/09/29. |
| VA Minutes | Part 1 | Rework section 2.5.2 to account for cases where faults are not allowed ( input-only, output-only ). | Low | Done. MJG 20030118 | |
| None | Part 1 | Be consistent in wrapping Infoset property names in square brackets []. | Low | Done SW 20040226 (until proven otherwise) | |
| AZ FTF | Part 1 | Change type of {variety} property to URI rather than enumeration. | Medium | Done as part of ComponentModelForMEPs merge. MJG 2003-03-05 | |
| AZ FTF | Part 1 | Change name of {variety} property to {message exchange pattern} | Re-opened by Gudge 20030213 to keep all MEP related changes in a single branch. | Medium | Done as part of ComponentModelForMEPs merge. MJG 2003-03-05 |
| Unknown | Part 1 | Amend binding components to allow the roll-up style in Part 2 | Amend the mapping of the {operations} property to be based on both the operation element children and the operations in the referenced portType. A binding always has as many operations as there are in the {operations} property of the port type it binds. | Medium | Done SW 20040226 |
| Unknown | Part 1 | Semantics associated with WSDL target namespace | Add text similar to 2a from dbooth proposal as per decision on 31st October 2000 | Medium | Done. 2003-02-13 MJG. |
| Unknown | Part 1 | Operation name uniqueness | Incorporate resolution from Scottsdale, AZ FTF | Medium | Done. 2003-02-13. MJG |
| 6a, 41 | Part 2 | Leave HTTP request URLs segmented, flat, and (somewhat) human readable. | Update documents as needed with improved wording. | Low | Superceded |
| Unknown | Part 1 | Add a conformance section | Low | Done SW at March 2004 F2F | |
| Unknown | All | Add markup for testable assertions | Low | JJM: now covered further below | |
| Unknown | All | Renaming | Incorporate renaming decisions from Cambridge face-to-face meeting: 'portType' to 'interface', 'binding/@type' to 'binding/@interface', 'service/port' to 'service/endpoint', 'interface/operation/@mep' to 'interface/operation/@pattern'. | Medium | Done. MJG 20030313 |
| Unknown | Part 1 | Merge in ComponentModelForMEPs branch | Medium | Done 20030305 MG. | |
| Unknown | Part 1 | Update component model and xml rep for bindings to accomodate new model and syntax for port type operations per ComponentModelForMEPs work | Medium | SW - done a while back (?) | |
| Unknown | Part 1 | Add statement about xs:import along the same lines as wsdl:import WRT visibility of components. Remove notion of Types Component. | Medium | Done. MJG 2003-04-28 | |
| Unknown | Part 1 | Normative status of schema | Add text stating that documents that do NOT conform to the schema are not valid WSDL documents. Note that documents that DO conform to the schema MIGHT be valid WSDL documents. Such documents MUST conform to other constraints defined in the spec. | Medium | Done. MJG 2003-04-28 |
| Unknown | Part 2 | Naming of @transport | Implement proposal in email. | High | Done. JCS 2003/05/22 |
| Editorial | Part 1 | 'recursive' interface inheritance | Add a note stating that recursive inheritance is not allowed | High | Done. 2003-05-27 MJG |
| Editorial | Part 1 | Add inheritance text | The inheritance model is currently not described in the spec. | Medium | Gudge thinks this is covered adequately by 2.4.1 and 2.7.1. |
| Editorial | Part 1 | Add more context information | Add more context to the specification- provide more descriptive wording to make it easier for someone to read the specification and to relate to Web services etc. before jumping into component-by-component descriptions. In particular, expand as appropriate the text and diagrams of the new section 2 "Web Service Definition", Part 1. | Medium | Done. JJM 2003/05/23 |
| Editorial | Part 1 | Add pseudo-syntax to Part 1 | Low | Partial. JJM 2003/05/23 Done. JCS 2003/06/03 | |
| Editorial | Part 3 | Add pseudo-syntax to Part 3 | Add (non-normative) pseudo-syntax description for each component. (JM will automatically generate the markup from the schemas.) | Low | Done. JJM 2003/05/23 |
| Editorial | Part 1 | Add new attribute "interface" to <service> | Add new attribute "interface" to <service>. A "service" is a collection of endpoints bound to the same interface and therefore the same resource. | High | Done. JJM 2003/05/23 |
| Editorial | Part 1 | Add "targetResource" attribute to <service> | Add optional "targetResource" attribute to <service>, taking a URI naming the resource upon which the service operates. This allows relating services with different interfaces that operate on the same underlying resource. | High | Done. JJM 2005/05/23 |
| Editorial | Part 3 | Infosetize the HTTP binding | Rewrite the HTTP binding from a component model point of view. | High | Done. JJM 2003/05/14 |
| Editorial | Part 1 | Add HTTP binding text | Incorporate and edit the HTTP binding text from Philippe (leave out the SOAP part for now). (Philippe has not yet posted his latest draft.) | High |
Done. JCS 2003/05/21 JJM 2003/05/22 JCS 2003/05/22 JJM 2003/05/23 |
| None | Part 1 | I've noticed that when portTypes were changed to interfaces, it seems the substitution broke some uppercasings, for example in table 18: "Element substitution groups defined for element based extensibility" where we see element declarations such as msgAndinterfaceExt - the 'i' should be upper case. | Low | Done. JCS 2003/07/24 | |
| 6e | Part 3 | email. | Resolved as proposed per 29 May 2003 telecon. | Medium | Done. JCS 2003/05/29 |
| None | Part 2 | Patterns confound messages with faults and would be clearer if faults were allowed via explicit rules. | Add two rules for defining when faults may occur. Allow others to define other rules. [email] | Medium | Done. AL 2003/06/12 |
| None. | XML Schema | Replace substitution groups with xs:any etc. | Per 3 July 2003 telecon [email] will replace substitution groups with open content model. Per 17 July 2003 telecon, decided to use @processContents='lax'. Per 24 July 2003 telecon, decided to use @namespace='##other'. | Medium | Done. JCS 2003/08/03 |
| None. | Part 1 | Remove wsdl:service/@targetResource. | Per 17 July 2003 telecon. | Medium | Done. JCS 2003/07/24 |
| None. | Part 1 | Remove diagrams in Section 1.1. | Per 17 July 2003 telecon. | Medium | Done. JCS 2003/07/24 |
| None. | Part 1, Part 2 | Explain how WSDL 1.1 @use='encoded', @encodingStyle=SOAP Section 5 works in WSDL 1.2 with @encodingStyle. | Medium | Not relevant any more as @use='encoded' etc. is gone. SW 2003/09/29. | |
| None. | Part 2 | Recommendations of the patterns task force include: 1. A pattern does not exhaustively define all messages between the named parties. 2. A pattern defines only details relevant to > 1 party. 3. Identify the participants involved in the pattern. 4. Refine existing patterns in light of (3). | Per 30 July 2003 meeting in Raleigh, NC, decided to adopt recommendations. | Medium | Done. JCS 20030802 |
| None. | Part 2 | Recommendations of the patterns task force include: 5. Refine fault rules in light of Identify the participants involved in the pattern. | Per 30 July 2003 meeting in Raleigh, NC, decided to adopt recommendations. | Medium | Done. AL 2003/08/08 |
| issue message parts, issue eliminate message | Part 1, Part 3 | Proposal to remove message and message/part constructs. Replace with interface/operation/input/@body that points to a GED. (Restricts SOAP to a single GED in s:Body.) Replace with interface/operation/input/@headers that point to a list of GEDs. Same for interface/operation/output. interface/operation/fault TBD. Add attribute to operation to indicate whether a set of rules was used when writing the schema as a hint/guide to reconstructing method signatures in proxy code. | Per 30 July 2003 meeting in Raleigh, NC, decided to incorporate the proposal. | Medium | Done. JCS 2003/08/04 |
| None. | Part 1, Part 3 | If one interface X extends another interface Y in another namespace N, the operations in X are the union of {[local name], [target namespace]} for the operations in X and Y. Currently, operations are referenced within a binding by NCName. Allowed to use the same NCName for two operations within an interface (including inheritance) only if they are in separate target namespaces. To refer to an operation within a binding, how would the namespace N be brought in to refer to operations within Y? Within the context of an interface, a QName uniquely identifies an operation (given inheritance); proposed referring to an operation by QName. | Per 31 July 2003 meeting in Raleigh, NC, decided to refer to operations by QName (instead of NCName) within a binding. | Medium | Done. SW 2003/10/02 |
| None. | Part 1, Part 3 | Proposal to make @interface AII optional on binding (and not defined on binding/operation). If there is no @interface AII specified, then there MUST NOT be any operation-specific binding details; if an @interface AII is specified, then there MAY be. QName of binding/@interface, when present, MUST match QName of service/@interface. | Per 31 July 2003 meeting in Raleigh, NC, decided to refer to operations by QName (instead of NCName) within a binding. | Medium | Done. JCS 2003/08/01 |
| None. | Part 1 | [e-mail] Allow attribute and child element extensibility on wsdl:import and wsdl:include. Extensions do not affect the component model, either of import or include (which do not have a component) or of the imported / included components. | Per 11 Sep 2003 telecon, accepted the above. | Medium | Done |
| 77 | Part 1, 2 | [e-mail] The semantics of other AIIs with [local name] = 'name' does not match the semantics of interface/input/@name and interface/output/@name. The latter is used to correlate messages with the interface/@pattern and does not allow the author of the wsdl:interface to coin a name (as other AIIs with the same [local name] do). | Per 11 Sep 2003 telecon, decided to use 'messageReference'. | Medium | Done. RRC 2003/09/11 |
| None. | Part 1, Primer | [e-mail] Chameleon schema pose problems when imported, and the draft currently has special rules to deal with this problem. | Per 17 Sep 2003 telecon, decided to remove special handling for chameleon schema. To use a pre-existing schema that does not have a target namespace, use include instead of import. | Medium | Done. RRC 2003/09/19 |
| None. | Part 1, Part 2 | Rename Message Pattern | Per 17 Sep 2003 telecon, decided to rename Message Pattern to Message Exchange Pattern. | Medium | Done Part 1 JJM 2003/09/18 |
| None. | Part 1 | Indicate if an operations is getting / setting an "attribute". | Per 23 Sep 2003 meeting in Palo Alto, CA, decided to: define two URIs and associated rules: one to indicate an operation gets the value of an attribute and one to indicate an operation sets the value. | Medium | Added placeholders SW 2003/09/29 |
| None. | Part 1 | Current Appendix C: URI References for WSDL constructs uses fragment identifies and they may be problematic. TAG discussin the issue. | Per 24 Sep 2003 meeting in Palo Alto, CA, decided to move Appendix C to a separate document on our mapping to RDF. | Medium | Done, JJM 2003/10/13 |
| None. | Part 1, Part 2, Part 3 | Specification version | Per 22-24 Sep 2003 F2F and 2 Oct 2003 telecon, decided to rename specification to WSDL 2.0 (was 1.2). | Medium | Done a while ago (closed by SW 20040226) |
| None. | Part 2 | The introduction states that patterns do not exhaustively describe the messages exchanged by a service with other services and notes that a message described in the pattern may be sent (e.g., 'broadcast') to other endpoints too. | Per 2 Oct telecon, decided to replace 'broadcast' with 'multicast' in the introduction. | Medium | Done. JCS 2003/10/07 |
| None. | Part 1 | Roberto noted in [ e-mail], that we have a mismatch between the interface-level message reference components and the binding-level ones. Proposed add a binding fault reference component (pretty much identical to the existing binding message reference component), and rename the {name} property of the binding message reference component to {messageReference}, so as to match the interface. | Per 8 Oct telecon, decided to adopt proposal; note that AII on binding/operation/outfault would be messageReference (not name). | Medium | Done. SW 2003/10/28 |
| None. | Part 2 | Does a fault terminate a pattern? | Per 16 Oct telecon, decided that a fault terminates a pattern. | Medium | Done. AL 20031104 |
| None. | Part 1 | Add @name to interface/operation/{infault,outfault} [email]. | Per 3 Nov face-to-face meeting, decided to accept this proposal. | Medium | Done. SW 20031104 |
| None. | Part 1 | Clarify RPC style rules [email]. | Per 3 Nov face-to-face meeting, decided to accept this proposal with clarifications (see meeting notes). | Medium | Done. SW 20031104 |
| None. | Part 1 | Add signature hint [email]. | Per 3 Nov face-to-face meeting, decided to accept this proposal. | Medium | Done. RRC 20040312 |
| None. | Part 1 | Make @messageReference optional when unambiguous [email]. | Per 4 Nov face-to-face meeting, decided to accept this proposal with clarifications as noted in meeting minutes. | Medium | Done. JCS 20031104 |
| None. | Part 1 | Remove interface/operation/{input,output}/@headers [email]. | Per 4 Nov face-to-face meeting, decided to accept this proposal. | Medium | Done. JCS 20031104 |
| None. | Part 1 | Rename interface/operation/{input,output}/@body. Rename interface/operation/{infault,outfault}/@details. | Per 4 Nov face-to-face meeting, decided to rename interface/operation/{input,output}/@body to ./@message and interface/operation/{infault,outfault}/@details to ./@message. | Medium | Done. JCS 20031104 |
| None. | Part 1 | Update 'attribute' get/set style to reflect recommendations from Attributes Task Force [email]. | Per 4 Nov face-to-face meeting, decided to accept the updates to the two style URIs. (Separate proposal to introduce new syntactic convention for attributes was not accepted.) | Medium | Status changed SW 20040226 as attribute style is now gone. |
| None. | Part 1 | wsdl:definitions/wsdl:types may contain > 0 xs:import, xs:include, and xs:schema, and xs:schema may include/import siblings of wsdl:definitions/wsdl:types. | Per 4 Nov face-to-face meeting, decided to allow > 0 xs:import, xs:include, and/or xs:schema and allow xs:schema to import/include any siblings. | Medium | Done. RRC 2004-03-15 |
| None. | Part 1 | How does one indicate that a component of a message is a reference to a service (perhaps constrained to the interface it implements)? | Per 5 Nov face-to-face meeting, decided to explicitly indicate the appropriateness of the usage described in proposal; decided not to define a new type and/or new attribute. | Medium | Status changed SW 20040226 as we've covered introduced a note to explain a mechanism to send service references. |
| None. | Part 1 | Need to explain what is visible when one WSDL imports another. | Suggested wording [email, email]. | Medium | Done SW 20040226 |
| None. | Part 1, RDF Note, and/or Primer | What does target namespace resolve to? | Per 20 Nov 2003 and 4 Dec 2003 teleconference, decided to recommend that the target namespace resolve to the WSDL document. (May need to revisit given expected TAG finding that target namespaces should resolve to a human-readable document with RDDL links.) | Medium | Done SW 20040226 |
| None. | Part 1 | binding/operations/{infault,outfault}/@messageReference is redundant [email] | Per 4 Dec 2003 telecon, decided to cut binding/operations/{infault,outfault}/@messageReference. | Medium | Done. JCS 20031204 |
| None. | Part 2 | Use of 'async' in pattern name may be misleading [email] | Per 4 Dec 2003 telecon, rename pattern 'Asynchronous Out-In' to 'Output-Optional-Input'. | Medium | Done. JCS 20031204 |
| None. | Part 1 | Endpoint references [email] | 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). | Medium | Done SW 20040226 |
| None. | Part 1 | Endpoint references [email] | Make top WSDL elements global in the schema to facilitate reuse.. | Medium | Done. By Gudge, I guess! |
| 105 | Part 1 | Accept Paul's proposal to hoist faults in the interface. |
1. Rename faultDefault to fault 2. Allow <value>,<subcode> as children of <wsoap:fault[Default]> 3. Remove per-operation (in|out)fault 4. Consistify the @name attributes. |
Medium | Done SW 20040311 |
| 89 | Part 1 | Fault namespace | Close issue 89 by changing the namespace of wsoap:fault to wsdl:fault, and add a corresponding component in the abstract model. | Medium | Done SW 20040311 |
| Part 1 | Attribute styles | Remove attribute styles. | Medium | Done SW 20040226 | |
| 102 | Part 1 | Schema import | Issue 102 closed with Amy's clarification [email]. | Medium | Done. RRC 2004-03-15 |
| 95 | Part 1 | service/@name: | @name optional for the standalone service type use. it will be required inside the context of a wsdl document. we may be able to describe in the schema as well as in the spec but we should check for side effect. Close issue 95. | Medium | Status changed SW 20040226 as covered by note about service reference use of 'service'. |
| 91 | Part 1, 2 | MEP terminology | Issue 91 is closed, editors will use the term "Message Exchange Pattern" rather than "Message Pattern". | Medium | DONE aal 2004-02-05 |
| Part 2 | renaming the label of MEPs | Change MEP labels from A and B to IN and OUT | Medium | DONE aal 2004-02-05 | |
| Part 1 | editors to add statement on "extensibility changes semantics" | Editors to do it per telecon 20040219 | Medium | Done SW 20040315 | |
| 122 and email | Part 1 | Semantics of value of @messageReference in binding message ref components confused Yaron. | Editors to try to clarify wording a bit | Low | Done SW 20040415 |
| 143 | Part 1 | referencing other type systems. | Merge in changes in proposal from Gudge ( CVS Branch Issue143 ) | Low | Done. 2004-02-27. MJG. |
| None | Part 1 | Add text regarding errors related to include | It is an error for an include to result in two top-level components of the same type, having the same name. Refer to uniqueness constraints on top-level names. | Medium | Pending |
| Editorial | Part 1 | Features and properties guidelines | Incorporate features and properties guidelines into the specification. (Waiting for text from Glen on properties.) | High | DONE. JJM 20040318 |
| None | Part 1 | Include agreed comment 1 from Kevin. | See [email] | Medium | DONE. JJM 20040317 |
| None | Part 1 | Include agreed comment 2 from Kevin. | See [email] | Medium | No longer present in spec. JJM 20040317 |
| None | Part 1 | Include agreed comment 3 from Kevin. | See [email] | Medium | Typo no longer present in spec. JJM 20040317 |
| None | Part 1 | Include agreed comment 4 from Kevin. | See [email] | Medium | DONE. JJM 20040317 |
| None | Part 1 | Include agreed comment 5 from Kevin. | See [email] | Medium | Done as a result of David Booth's WSDL processor editorial work. JJM 20040317 |
| None. | Part 1, 2 | Specification feedback | Editors to consider and address feedback [email]; initial response from editors [email]. | Medium | DONE. JJM 20040318 |
| None. | Part 2 | Add patterns that use fault-replaces-message rule. [email] | Per 16 Oct telecon, decided to add these patterns. | Medium | TODO |
| None. | Part 2 | Part2_Editors to clarify wording in fault-replaces-message rule that a fault is GENERATED but not necessarily SENT. | Per XX Oct telecon | Low | TODO |
| Unknown | Part 2 | Compliance for Patterns | Add compliance statement for MEPs, e.g., two implementations using a shared binding. | Medium | Pending |
| Unknown | Part 2 | Internationalized URIs | Incorporate boilerplate from i18n for international characters in URIs | Low | Pending |
| None. | Part 3 | Rework the HTTP binding now that messages have been removed. | Medium | DONE. JJM 20040305 | |
| None. | Part 3 | Mirror the component of Part 1, i.e. (model, XML representation, mapping). | Low | TODO | |
| None. | Part 3 |
- Define default SOAP binding rules: @body goes into
soap:Body, and each of @headers goes into soap:Header. - Drop wsoap:Body and wsoap:Fault. - Drop @type, @namespace, @localname, @encodingStyle from wsoap:Header. - Add @mustUnderstand from wsoap:Header; value MUST agree with any value specified in the corresponding element. - Rework as necessary now that messages have been removed. |
Per 31 July 2003 meeting in Raleigh, NC, accepted the above. | High | Pending |
| None. | Part 3 | Replace wsoap:operation/@soapAction with wsoap:action/@uri [email]. | Per 4 Nov face-to-face meeting, decided to accept this proposal. | Medium | TODO |
| 105 | Part 3 | Accept Paul's proposal to hoist faults in the interface. |
1. Rename faultDefault to fault 2. Allow <value>,<subcode> as children of <wsoap:fault[Default]> 3. Remove per-operation (in|out)fault 4. Consistify the @name attributes. |
Medium | |
| Part 3 | Add statement to Part 3 on "Actual binding format is not just defined by the binding, but also by the extension elements in use. | Telecon 20040219 | Medium | ||
| Part 1 | Implement David Booth's proposal on making all notes non-normative and moving the normative text into the regular paragraphs. | Telecon 20040318 | Medium | DONE. JJM 20040318 | |
| Part 1 | Make binding/operation/(input|output)/@messageLabel optional and have the same rules as the corresponding thing in interface/operation for computing the value. | Telecon 20040318 | Medium | Done SW 20040319 | |
| Part 1 | Clarify the meaning of 'change' WRT to optional extensions. | Telecon 20040318 | Medium | Done SW 20040318 | |
| Part 1 | Incorporate Jonathan's proposal for issues 146 & 150 (with #empty changed to #none) | Telecon 20040318 | Medium | Done SW 20040319 | |
| Part 3 | Include proposal from Youenn regarding HTTPS. | Telecon 20040415 | Medium | Pending | |
| 179 | Part 3 | PUT and DELETE need to be added | TBD by Hugo/PLH | ||
| None | Part 1 | Combine {name} : NCName and {targetNamespace} : URI into {name} : QName on all applicable components. See email: Editorial for Part 1 section 2.18. | Proposal accepted. See email: RE: Editorial for Part 1 section 2.18 | Medium | Done by AGR 20050209 | --> |
| open |
| closed |
| subsumed |
| pending |
| cancelled |
| editorial |