 WSDL 2.0 Candidate Recommendation Issues List
WSDL 2.0 Candidate Recommendation Issues List
Individual view
This list received comments from 0 groups and 60 individuals.
Comments from individuals
- Amelia A Lewis (alewis@tibco.com)
    [2 issues ]- CR124 :
      editorial: features and properties in "xml representation" sections [open]
- CR125 :
      problem with pattern attribute definition? [open]
 
- Arthur Ryman (arthur.ryman@gmail.com)
    [1 issue ]- CR110 :
      Semantics of {http cookies} Property. [open]
 
- Arthur Ryman (ryman@ca.ibm.com)
    [22 issues ]- CR018 :
      RE: Review of WS-A WSDL Binding [open]
- CR022 :
      Component Values Must Be Context Independent [open]
- CR024 :
      Part 2 Adjuncts Comments (1 -5) [open]
- CR025 :
      Part 2 Adjuncts Comments (1 -5) [open]
- CR026 :
      Part 2 Adjuncts Comments (1 -5) [open]
- CR027 :
      Part 2 Adjuncts Comments (1 -5) [open]
- CR028 :
      Part 2 Adjuncts Comments (1 -5) [open]
- CR029 :
      Part 2 Adjuncts Comments (1 -5) [open]
- CR030 :
      Part 2 Adjuncts Comments (1 -5) [open]
- CR031 :
      Part 2 Adjuncts Comments (1 -5) [open]
- CR032 :
      Part 2 Adjuncts Comments (1 -5) [open]
- CR033 :
      Part 2 Adjuncts Comments (1 -5) [open]
- CR034 :
      Comments on Part 2, Chapter 6 [open]
- CR035 :
      Comments on Part 2, Chapter 6 [open]
- CR036 :
      Comments on Part 2, Chapter 6 [open]
- CR037 :
      Comments on Part 2, Chapter 6 [open]
- CR040 :
      Comment on Part 2, Section 5.9.3 [open]
- CR041 :
      Comment on Part 2, Section 6.5.2 [open]
- CR042 :
      Re: Uniqueness of QNames in 'extends' attribute [open]
- CR043 :
      Part 2, 5.6.3 XML Representation of subcodes is inconsistent [open]
- CR044 :
      Parts 1 and 2 Treat Defaults Inconsistently with each other [open]
- CR126 :
      Re: New interchange results [open]
 
- Ashok Malhotra (ashok.malhotra@oracle.com)
    [1 issue ]- CR129 :
      RE: Comment on Fragment Identifiers [open]
 
- Bjoern Hoehrmann (derhoermi@gmx.net)
    [1 issue ]- CR003 :
      wsdl20-adjuncts vs RFC 4288 [open]
 
- Chathura Herath (chathurah@gmail.com)
    [1 issue ]- CR074 :
      Assetions covered by schema validation [open]
 
- Cindy McNally (cindymcnally_6@hotmail.com)
    [1 issue ]- CR128 :
      Interface Inheritance Clarification [open]
 
- Daniel Barclay (daniel@fgm.com)
    [2 issues ]- CR064 :
      WSDL 2.0 primer CR comments [open]
- CR065 :
      Re: WSDL 2.0 primer CR comments [open]
 
- Daniel Barclay (daniel@fgm.com)
    [1 issue ]- CR068 :
      WSDL 2.0 part 2 comment - 2.3.x, 2.2.x wording problems [open]
 
- david.vanderfeesten@alcatel.be (david.vanderfeesten@alcatel.be)
    [1 issue ]- CR008 :
      Web Services Description Language (WSDL) Version 2.0 SOAP 1.1 Binding:  example @ section 2.4 [open]
 
- Eran Chinthaka (chinthaka@wso2.com)
    [1 issue ]- CR091 :
      WSDL 2.0 Fault Binding [closed]
 
- Eric Foutz (eric_foutz@symantec.com)
    [1 issue ]- CR121 :
      WSDL enhancement request [open]
 
- Eric van der Vlist (vdv@dyomedea.com)
    [3 issues ]- CR052 :
      Serializing only part of the body with HTTP binding [open]
- CR053 :
      Allow absolute URI in {location} [open]
- CR054 :
      URIPath feedback [open]
 
- georgi.georgiev.pv@hitachi.com (georgi.georgiev.pv@hitachi.com)
    [1 issue ]- CR142 :
      Leftovers of trailing slashes in replacement parameters [open]
 
- Glen Daniels (gdaniels@sonicsoftware.com)
    [1 issue ]- CR014 :
      CR ISSUE: Bug in SOAP binding (Section 5.5.2 of Adjuncts) [open]
 
- Graham Turrell (gturrell@googlemail.com)
    [1 issue ]- CR062 :
      Re:service and binding name shown as QNames in example - should be NCNames [open]
 
- Hugo Haas (hugo@w3.org)
    [2 issues ]- CR009 :
      SOAP binding: empty SOAP Action [open]
- CR010 :
      Typo in HTTP binding [open]
 
- Hugo Haas (hugo@w3.org)
    [1 issue ]- CR039 :
      Mentions of "error" and "fatal error" in Part 2 [open]
 
- Jacek Kopecky (jacek.kopecky@deri.org)
    [2 issues ]- CR020 :
      Bogus assertions in 3.1.3? [open]
- CR038 :
      editorial: part 2, table b-1 incomplete? [open]
 
- Jacek Kopecky (jacek.kopecky@deri.org)
    [1 issue ]- CR147 :
      RFC: operation safety as semantic annotation? [open]
 
- Jason T. Greene (jason.greene@jboss.com)
    [1 issue ]- CR082 :
      Header blocks  in wrpc:signature [open]
 
- Jeremy Hughes (hughesj@apache.org)
    [4 issues ]- CR061 :
      service and binding name shown as QNames in example - should be NCNames [closed]
- CR063 :
      Prefix declarations in inlined schema [open]
- CR066 :
      Endpoint component {name} property vs xml representation as a QName [open]
- CR153 :
      The WSDL 2.0 namespace - will it change? [open]
 
- John Kaputin (gmail) (jakaputin@gmail.com)
    [12 issues ]- CR002 :
      Do <import> and <include> support extensibility elements? [open]
- CR007 :
      Assertion required for property <constraint> [closed]
- CR056 :
      Questions on {http method} and {safety} extension properties [open]
- CR057 :
      HTTPHeader name should be xs:string, not xs:QName [open]
- CR058 :
      Suggestion to change {safety} to {safe} [open]
- CR088 :
      Ambiguity in Part regarding built-in XML Schema types [open]
- CR090 :
      Ambiguity in Part regarding built-in XML Schema types [closed]
- CR130 :
      Question on double curly braces with HTTP Location [open]
- CR131 :
      Clarifying assertion for HTTP Location [open]
- CR137 :
      Spelling mistake in Part 2 [open]
- CR140 :
      Re: Spec Issue - associating local names in HTTP location with element declarations [open]
- CR141 :
      Re: Spec Issue - unmatched single curly braces in HTTP Location [closed]
 
- John Kaputin (gmail) (jakaputin@gmail.com)
    [3 issues ]- CR055 :
      Clarification needed on HTTP Transfer Coding [open]
- CR072 :
      Questions on {http method} and {safety} extension properties [open]
- CR145 :
      Clarify 'scope' of {element declarations} and {type definitions} re SparqlQuerySimplified-1G [open]
 
- John Kaputin (gmail) (jakaputin@gmail.com)
    [12 issues ]- CR002 :
      Do <import> and <include> support extensibility elements? [open]
- CR007 :
      Assertion required for property <constraint> [closed]
- CR056 :
      Questions on {http method} and {safety} extension properties [open]
- CR057 :
      HTTPHeader name should be xs:string, not xs:QName [open]
- CR058 :
      Suggestion to change {safety} to {safe} [open]
- CR088 :
      Ambiguity in Part regarding built-in XML Schema types [open]
- CR090 :
      Ambiguity in Part regarding built-in XML Schema types [closed]
- CR130 :
      Question on double curly braces with HTTP Location [open]
- CR131 :
      Clarifying assertion for HTTP Location [open]
- CR137 :
      Spelling mistake in Part 2 [open]
- CR140 :
      Re: Spec Issue - associating local names in HTTP location with element declarations [open]
- CR141 :
      Re: Spec Issue - unmatched single curly braces in HTTP Location [closed]
 
- John Kaputin (gmail) (jakaputin@gmail.com)
    [3 issues ]- CR055 :
      Clarification needed on HTTP Transfer Coding [open]
- CR072 :
      Questions on {http method} and {safety} extension properties [open]
- CR145 :
      Clarify 'scope' of {element declarations} and {type definitions} re SparqlQuerySimplified-1G [open]
 
- John Kaputin (gmail) (jakaputin@gmail.com)
    [12 issues ]- CR002 :
      Do <import> and <include> support extensibility elements? [open]
- CR007 :
      Assertion required for property <constraint> [closed]
- CR056 :
      Questions on {http method} and {safety} extension properties [open]
- CR057 :
      HTTPHeader name should be xs:string, not xs:QName [open]
- CR058 :
      Suggestion to change {safety} to {safe} [open]
- CR088 :
      Ambiguity in Part regarding built-in XML Schema types [open]
- CR090 :
      Ambiguity in Part regarding built-in XML Schema types [closed]
- CR130 :
      Question on double curly braces with HTTP Location [open]
- CR131 :
      Clarifying assertion for HTTP Location [open]
- CR137 :
      Spelling mistake in Part 2 [open]
- CR140 :
      Re: Spec Issue - associating local names in HTTP location with element declarations [open]
- CR141 :
      Re: Spec Issue - unmatched single curly braces in HTTP Location [closed]
 
- John Kaputin (gmail) (jakaputin@gmail.com)
    [3 issues ]- CR055 :
      Clarification needed on HTTP Transfer Coding [open]
- CR072 :
      Questions on {http method} and {safety} extension properties [open]
- CR145 :
      Clarify 'scope' of {element declarations} and {type definitions} re SparqlQuerySimplified-1G [open]
 
- Jonathan Marsh (jmarsh@microsoft.com)
    [5 issues ]- CR013 :
      Relax IRI style cardinality [open]
- CR067 :
      {http cookies} REQUIRED? [closed]
- CR076 :
      {rpc signature} REQUIRED when rpc style is not specified? [open]
- CR079 :
      Fragment identifier syntax not XPointer Framework-compatible [open]
- CR080 :
      Canonical component designators? [open]
 
- Jonathan Marsh (jmarsh@microsoft.com)
    [7 issues ]- CR023 :
      typeDefinitions property optional? [open]
- CR046 :
      Missing properties in the property summary (Core table d-1, second half) [open]
- CR050 :
      When does {safety} appear? [open]
- CR051 :
      when does wsoap:code appear? [open]
- CR059 :
      Editorial: Where does {http location ignore uncited} appear? [open]
- CR060 :
      Why don't whttp:authenticationType and {http authentication scheme} match? [open]
- CR069 :
      Deconstructing MEPs [open]
 
- Jonathan Marsh (jmarsh@microsoft.com)
    [5 issues ]- CR013 :
      Relax IRI style cardinality [open]
- CR067 :
      {http cookies} REQUIRED? [closed]
- CR076 :
      {rpc signature} REQUIRED when rpc style is not specified? [open]
- CR079 :
      Fragment identifier syntax not XPointer Framework-compatible [open]
- CR080 :
      Canonical component designators? [open]
 
- Jonathan Marsh (jmarsh@microsoft.com)
    [7 issues ]- CR023 :
      typeDefinitions property optional? [open]
- CR046 :
      Missing properties in the property summary (Core table d-1, second half) [open]
- CR050 :
      When does {safety} appear? [open]
- CR051 :
      when does wsoap:code appear? [open]
- CR059 :
      Editorial: Where does {http location ignore uncited} appear? [open]
- CR060 :
      Why don't whttp:authenticationType and {http authentication scheme} match? [open]
- CR069 :
      Deconstructing MEPs [open]
 
- Jonathan Marsh (jmarsh@microsoft.com)
    [5 issues ]- CR013 :
      Relax IRI style cardinality [open]
- CR067 :
      {http cookies} REQUIRED? [closed]
- CR076 :
      {rpc signature} REQUIRED when rpc style is not specified? [open]
- CR079 :
      Fragment identifier syntax not XPointer Framework-compatible [open]
- CR080 :
      Canonical component designators? [open]
 
- Jonathan Marsh (jonathan@wso2.com)
    [7 issues ]- CR085 :
      RE: F&P Primer work done. [closed]
- CR086 :
      {http cookies} prohibited inconsistently [closed]
- CR087 :
      Turning off http transfer coding [closed]
- CR132 :
      RE: Proposal for CR108 [closed]
- CR133 :
      {http location} ignored on SOAP request-response MEP? [open]
- CR136 :
      What does this table row mean? [open]
- CR157 :
      RE: LocationTemplate-1G test [closed]
 
- Jonathan Marsh (jonathan@wso2.com)
    [4 issues ]- CR134 :
      Operation dispatch when there isn't a SOAP body. [closed]
- CR135 :
      Operation dispatch when there isn't a SOAP body. [closed]
- CR144 :
      RE: LocationTemplate-1G totally hosed ;-) [open]
- CR146 :
      Ignoring uncited and nillable [open]
 
- Jonathan Marsh (jonathan@wso2.com)
    [7 issues ]- CR085 :
      RE: F&P Primer work done. [closed]
- CR086 :
      {http cookies} prohibited inconsistently [closed]
- CR087 :
      Turning off http transfer coding [closed]
- CR132 :
      RE: Proposal for CR108 [closed]
- CR133 :
      {http location} ignored on SOAP request-response MEP? [open]
- CR136 :
      What does this table row mean? [open]
- CR157 :
      RE: LocationTemplate-1G test [closed]
 
- Jonathan Marsh (jonathan@wso2.com)
    [4 issues ]- CR134 :
      Operation dispatch when there isn't a SOAP body. [closed]
- CR135 :
      Operation dispatch when there isn't a SOAP body. [closed]
- CR144 :
      RE: LocationTemplate-1G totally hosed ;-) [open]
- CR146 :
      Ignoring uncited and nillable [open]
 
- Jonathan Marsh (jonathan@wso2.com)
    [7 issues ]- CR085 :
      RE: F&P Primer work done. [closed]
- CR086 :
      {http cookies} prohibited inconsistently [closed]
- CR087 :
      Turning off http transfer coding [closed]
- CR132 :
      RE: Proposal for CR108 [closed]
- CR133 :
      {http location} ignored on SOAP request-response MEP? [open]
- CR136 :
      What does this table row mean? [open]
- CR157 :
      RE: LocationTemplate-1G test [closed]
 
- Lawrence Mandel (lmandel@ca.ibm.com)
    [21 issues ]- CR001 :
      Suggestion Summary appendix? [closed]
- CR005 :
      Built in XML Schema types [open]
- CR019 :
      Must XML schema elements by imported in WSDL 2.0? [open]
- CR070 :
      Request 2 clarifications for RPC style [open]
- CR071 :
      Request 2 clarifications for RPC style [open]
- CR073 :
      Suggested editorial changes to adjuncts section 4.1.1 wrpc:signature [open]
- CR096 :
      Assertions that are not assertions [open]
- CR097 :
      Assertions that are not assertions [open]
- CR098 :
      Assertions that are not assertions [open]
- CR099 :
      Assertions that are not assertions [open]
- CR100 :
      Duplicate assertions [open]
- CR101 :
      Duplicate assertions [open]
- CR102 :
      Duplicate assertions [open]
- CR103 :
      Duplicate assertions [open]
- CR104 :
      One more duplicate assertion [open]
- CR105 :
      More Duplicate and Non-Assertions [open]
- CR106 :
      More Duplicate and Non-Assertions [open]
- CR107 :
      More Duplicate and Non-Assertions [open]
- CR108 :
      Do MessageLabel-0006 and MessageLabel-0014 state the same requirement? [open]
- CR115 :
      Suggested editorial change for assertion Import-0072 [open]
- CR118 :
      Suggested removal of 2 assertions [open]
 
- Lawrence Mandel (lmandel@ca.ibm.com)
    [2 issues ]- CR006 :
      Correction for assertion BindingFault-0058 [open]
- CR075 :
      Suggested editorial changes for IRI and Multipart styles [open]
 
- Lawrence Mandel (lmandel@ca.ibm.com)
    [21 issues ]- CR001 :
      Suggestion Summary appendix? [closed]
- CR005 :
      Built in XML Schema types [open]
- CR019 :
      Must XML schema elements by imported in WSDL 2.0? [open]
- CR070 :
      Request 2 clarifications for RPC style [open]
- CR071 :
      Request 2 clarifications for RPC style [open]
- CR073 :
      Suggested editorial changes to adjuncts section 4.1.1 wrpc:signature [open]
- CR096 :
      Assertions that are not assertions [open]
- CR097 :
      Assertions that are not assertions [open]
- CR098 :
      Assertions that are not assertions [open]
- CR099 :
      Assertions that are not assertions [open]
- CR100 :
      Duplicate assertions [open]
- CR101 :
      Duplicate assertions [open]
- CR102 :
      Duplicate assertions [open]
- CR103 :
      Duplicate assertions [open]
- CR104 :
      One more duplicate assertion [open]
- CR105 :
      More Duplicate and Non-Assertions [open]
- CR106 :
      More Duplicate and Non-Assertions [open]
- CR107 :
      More Duplicate and Non-Assertions [open]
- CR108 :
      Do MessageLabel-0006 and MessageLabel-0014 state the same requirement? [open]
- CR115 :
      Suggested editorial change for assertion Import-0072 [open]
- CR118 :
      Suggested removal of 2 assertions [open]
 
- Lawrence Mandel (lmandel@ca.ibm.com)
    [2 issues ]- CR006 :
      Correction for assertion BindingFault-0058 [open]
- CR075 :
      Suggested editorial changes for IRI and Multipart styles [open]
 
- Lawrence Mandel (lmandel@ca.ibm.com)
    [21 issues ]- CR001 :
      Suggestion Summary appendix? [closed]
- CR005 :
      Built in XML Schema types [open]
- CR019 :
      Must XML schema elements by imported in WSDL 2.0? [open]
- CR070 :
      Request 2 clarifications for RPC style [open]
- CR071 :
      Request 2 clarifications for RPC style [open]
- CR073 :
      Suggested editorial changes to adjuncts section 4.1.1 wrpc:signature [open]
- CR096 :
      Assertions that are not assertions [open]
- CR097 :
      Assertions that are not assertions [open]
- CR098 :
      Assertions that are not assertions [open]
- CR099 :
      Assertions that are not assertions [open]
- CR100 :
      Duplicate assertions [open]
- CR101 :
      Duplicate assertions [open]
- CR102 :
      Duplicate assertions [open]
- CR103 :
      Duplicate assertions [open]
- CR104 :
      One more duplicate assertion [open]
- CR105 :
      More Duplicate and Non-Assertions [open]
- CR106 :
      More Duplicate and Non-Assertions [open]
- CR107 :
      More Duplicate and Non-Assertions [open]
- CR108 :
      Do MessageLabel-0006 and MessageLabel-0014 state the same requirement? [open]
- CR115 :
      Suggested editorial change for assertion Import-0072 [open]
- CR118 :
      Suggested removal of 2 assertions [open]
 
- Mark Nottingham (mnot@mnot.net)
    [1 issue ]- CR011 :
      CR Comment on WSDL Version 2, part 2: Adjuncts [open]
 
- matthew.d.rawlings@jpmchase.com (matthew.d.rawlings@jpmchase.com)
    [1 issue ]- CR078 :
      XML Schema requires a type in addition to name to identify an element [closed]
 
- Philippe Le Hegaret (plh@w3.org)
    [1 issue ]- CR084 :
      Re: New issue (editorial): Missing attribute/elements in syntax  summary in part 2 5.1 [open]
 
- Philippe Le Hegaret (plh@w3.org)
    [2 issues ]- CR116 :
      6.7.1.1 Construction of the request IRI using the http location [open]
- CR143 :
      Tranfer-Encoding vs Content-Encoding [open]
 
- Ramkumar Menon (ramkumar.menon@gmail.com)
    [18 issues ]- CR004 :
      <appInfo> for the WSDL [closed]
- CR015 :
      value space of "extends" attribute Info Item [2.2.2.2 WSL 2.0 Core Language] [open]
- CR016 :
      wrpc:signature for RPC style [closed]
- CR045 :
      Inline schemas with no target namespace [open]
- CR047 :
      "interface" attribute info item on service component [closed]
- CR048 :
      "interface" attribute info item on service component [closed]
- CR049 :
      "interface" attribute info item on service component [closed]
- CR089 :
      Definition of Interface Message Reference [closed]
- CR092 :
      Re: WSDL 2.0 Fault Binding [Plus two Questions] [open]
- CR093 :
      Re: WSDL 2.0 Fault Binding [Plus two Questions] [open]
- CR094 :
      Assertion SOAPBinding-2503001 [closed]
- CR095 :
      Part 2 - {element declaration} property for SOAP Header Block component [closed]
- CR138 :
      {element declaration} for Interface Fault component [closed]
- CR139 :
      Suggestion on Part - 2 : Adjuncts [open]
- CR150 :
      Assertion Summary Texts in Part 1 [open]
- CR151 :
      XML Syntax Summary in Part 1 [open]
- CR152 :
      Assertion on Bindings for Interface that only define faults [open]
- CR155 :
      Proposal for Assertion InterfaceMessageReference-0042 [open]
 
- Ramkumar Menon (ramkumar.menon@gmail.com)
    [4 issues ]- CR012 :
      Semantics of wsdl:import [open]
- CR081 :
      Synchronous v/s Asynchronous, a WSA question, and few suggestions [closed]
- CR083 :
      Editorial >> WSDL 2.0 definitions v/s WSDL 2.0 descriptions [closed]
- CR154 :
      InterfaceMessageReference-1205002 [closed]
 
- Ramkumar Menon (ramkumar.menon@gmail.com)
    [18 issues ]- CR004 :
      <appInfo> for the WSDL [closed]
- CR015 :
      value space of "extends" attribute Info Item [2.2.2.2 WSL 2.0 Core Language] [open]
- CR016 :
      wrpc:signature for RPC style [closed]
- CR045 :
      Inline schemas with no target namespace [open]
- CR047 :
      "interface" attribute info item on service component [closed]
- CR048 :
      "interface" attribute info item on service component [closed]
- CR049 :
      "interface" attribute info item on service component [closed]
- CR089 :
      Definition of Interface Message Reference [closed]
- CR092 :
      Re: WSDL 2.0 Fault Binding [Plus two Questions] [open]
- CR093 :
      Re: WSDL 2.0 Fault Binding [Plus two Questions] [open]
- CR094 :
      Assertion SOAPBinding-2503001 [closed]
- CR095 :
      Part 2 - {element declaration} property for SOAP Header Block component [closed]
- CR138 :
      {element declaration} for Interface Fault component [closed]
- CR139 :
      Suggestion on Part - 2 : Adjuncts [open]
- CR150 :
      Assertion Summary Texts in Part 1 [open]
- CR151 :
      XML Syntax Summary in Part 1 [open]
- CR152 :
      Assertion on Bindings for Interface that only define faults [open]
- CR155 :
      Proposal for Assertion InterfaceMessageReference-0042 [open]
 
- Ramkumar Menon (ramkumar.menon@gmail.com)
    [4 issues ]- CR012 :
      Semantics of wsdl:import [open]
- CR081 :
      Synchronous v/s Asynchronous, a WSA question, and few suggestions [closed]
- CR083 :
      Editorial >> WSDL 2.0 definitions v/s WSDL 2.0 descriptions [closed]
- CR154 :
      InterfaceMessageReference-1205002 [closed]
 
- Ramkumar Menon (ramkumar.menon@gmail.com)
    [18 issues ]- CR004 :
      <appInfo> for the WSDL [closed]
- CR015 :
      value space of "extends" attribute Info Item [2.2.2.2 WSL 2.0 Core Language] [open]
- CR016 :
      wrpc:signature for RPC style [closed]
- CR045 :
      Inline schemas with no target namespace [open]
- CR047 :
      "interface" attribute info item on service component [closed]
- CR048 :
      "interface" attribute info item on service component [closed]
- CR049 :
      "interface" attribute info item on service component [closed]
- CR089 :
      Definition of Interface Message Reference [closed]
- CR092 :
      Re: WSDL 2.0 Fault Binding [Plus two Questions] [open]
- CR093 :
      Re: WSDL 2.0 Fault Binding [Plus two Questions] [open]
- CR094 :
      Assertion SOAPBinding-2503001 [closed]
- CR095 :
      Part 2 - {element declaration} property for SOAP Header Block component [closed]
- CR138 :
      {element declaration} for Interface Fault component [closed]
- CR139 :
      Suggestion on Part - 2 : Adjuncts [open]
- CR150 :
      Assertion Summary Texts in Part 1 [open]
- CR151 :
      XML Syntax Summary in Part 1 [open]
- CR152 :
      Assertion on Bindings for Interface that only define faults [open]
- CR155 :
      Proposal for Assertion InterfaceMessageReference-0042 [open]
 
- Ramkumar Menon (ramkumar.menon@gmail.com)
    [4 issues ]- CR012 :
      Semantics of wsdl:import [open]
- CR081 :
      Synchronous v/s Asynchronous, a WSA question, and few suggestions [closed]
- CR083 :
      Editorial >> WSDL 2.0 definitions v/s WSDL 2.0 descriptions [closed]
- CR154 :
      InterfaceMessageReference-1205002 [closed]
 
- Ramkumar Menon (ramkumar.menon@gmail.com)
    [18 issues ]- CR004 :
      <appInfo> for the WSDL [closed]
- CR015 :
      value space of "extends" attribute Info Item [2.2.2.2 WSL 2.0 Core Language] [open]
- CR016 :
      wrpc:signature for RPC style [closed]
- CR045 :
      Inline schemas with no target namespace [open]
- CR047 :
      "interface" attribute info item on service component [closed]
- CR048 :
      "interface" attribute info item on service component [closed]
- CR049 :
      "interface" attribute info item on service component [closed]
- CR089 :
      Definition of Interface Message Reference [closed]
- CR092 :
      Re: WSDL 2.0 Fault Binding [Plus two Questions] [open]
- CR093 :
      Re: WSDL 2.0 Fault Binding [Plus two Questions] [open]
- CR094 :
      Assertion SOAPBinding-2503001 [closed]
- CR095 :
      Part 2 - {element declaration} property for SOAP Header Block component [closed]
- CR138 :
      {element declaration} for Interface Fault component [closed]
- CR139 :
      Suggestion on Part - 2 : Adjuncts [open]
- CR150 :
      Assertion Summary Texts in Part 1 [open]
- CR151 :
      XML Syntax Summary in Part 1 [open]
- CR152 :
      Assertion on Bindings for Interface that only define faults [open]
- CR155 :
      Proposal for Assertion InterfaceMessageReference-0042 [open]
 
- Roberto Chinnici (Roberto.Chinnici@Sun.COM)
    [1 issue ]- CR149 :
      Re: rpc:signature question. [open]
 
- Williams, Stuart (skw@hp.com)
    [1 issue ]- CR021 :
      RE: WSDL describing Interface operation safety [open]
 
- Yalcinalp, Umit (umit.yalcinalp@sap.com)
    [1 issue ]- CR017 :
      Action Item 2006-02-16 [open]
 
- Youenn Fablet (youenn.fablet@crf.canon.fr)
    [13 issues ]- CR077 :
      URI comparison [open]
- CR109 :
      SOAP Fault code issue [open]
- CR111 :
      Mapping WSDL meps to the HTTP binding [open]
- CR112 :
      HTTP Location property definition [open]
- CR113 :
      SOAP Response query string issue [open]
- CR114 :
      Mapping WSDL MEPs to SOAP MEPs [open]
- CR117 :
      Re: 6.7.1.1 Construction of the request IRI using the http location [open]
- CR119 :
      Missing attribute in section 6.2 [open]
- CR120 :
      SOAP Response and IRI style [open]
- CR122 :
      Clarification about ignoreUncited behaviour [open]
- CR123 :
      HTTP Method selection [open]
- CR127 :
      Message Dispatching Primer Section [open]
- CR156 :
      Query parameter separator value [open]
 
- Youenn Fablet (youenn.fablet@crf.canon.fr)
    [1 issue ]- CR148 :
      Re: LocationTemplate-1G totally hosed ;-) [open]
 
- Youenn Fablet (youenn.fablet@crf.canon.fr)
    [13 issues ]- CR077 :
      URI comparison [open]
- CR109 :
      SOAP Fault code issue [open]
- CR111 :
      Mapping WSDL meps to the HTTP binding [open]
- CR112 :
      HTTP Location property definition [open]
- CR113 :
      SOAP Response query string issue [open]
- CR114 :
      Mapping WSDL MEPs to SOAP MEPs [open]
- CR117 :
      Re: 6.7.1.1 Construction of the request IRI using the http location [open]
- CR119 :
      Missing attribute in section 6.2 [open]
- CR120 :
      SOAP Response and IRI style [open]
- CR122 :
      Clarification about ignoreUncited behaviour [open]
- CR123 :
      HTTP Method selection [open]
- CR127 :
      Message Dispatching Primer Section [open]
- CR156 :
      Query parameter separator value [open]
 
Maintained by Web Services Description Working Group.Last update: $Date: 2007/03/14 00:12:34 $
This page was generated as part of the
Extensible Issue
Tracking System (ExIT)
Copyright ©
2003, 2004
W3C® (MIT, ERCIM,
Keio), All Rights Reserved. W3C liability, trademark, document
use and software licensing
rules apply. Your interactions with this site are in accordance with
our public and
Member
privacy statements.