6.7.1.1 Construction of the request IRI using the http location
Assertion on Bindings for Interface that only define faults
Assertion Summary Texts in Part 1
Clarify 'scope' of {element declarations} and {type definitions} re SparqlQuerySimplified-1G
editorial: features and properties in "xml representation" sections
HTTP Location property definition
HTTP Method selection
Ignoring uncited and nillable
Interface Inheritance Clarification
InterfaceMessageReference-1205002
Leftovers of trailing slashes in replacement parameters
LocationTemplate-1G totally hosed ;-)
Mapping WSDL MEPs to SOAP MEPs
Mapping WSDL meps to the HTTP binding
Message Dispatching Primer Section
Missing attribute in section 6.2
New interchange results
New issue (editorial): Missing attribute/elements in syntax summary in part 2 5.1
Operation dispatch when there isn't a SOAP body.
Parts 1 and 2 Treat Defaults Inconsistently with Eachother
problem with pattern attribute definition?
Proposal for CR108
Question on double curly braces with HTTP Location
rpc:signature question.
Semantics of {http cookies} Property.
SOAP Fault code issue
SOAP Response and IRI style
SOAP Response query string issue
Spelling mistake in Part 2
Suggested removal of 2 assertions
Suggestion on Part - 2 : Adjuncts
Tranfer-Encoding vs Content-Encoding
Turning off http transfer coding
Two comments and a question on the WSDL HTTP Binding Extension
WSDL 2.0 Fault Binding
WSDL 2.0 Fault Binding [Plus two Questions]
XML Syntax Summary in Part 1
{element declaration} for Interface Fault component
{http cookies} REQUIRED?
{http location} ignored on SOAP request-response MEP?
Last message date: Friday, 23 February 2007 03:17:48 UTC