Tuesday, 31 October 2006
Friday, 20 October 2006
- RE: XML Schema requires a type in addition to name to identify an element
- RE: Header blocks in wrpc:signature
- RE: WSDL 2.0 primer CR comments
- RE: WSDL 2.0 primer CR comments
- RE: XML Schema requires a type in addition to name to identify an element
- RE: Header blocks in wrpc:signature
- RE: service and binding name shown as QNames in example - should be NCNames
- RE: Component Values Must Be Context Independent
Tuesday, 17 October 2006
Monday, 16 October 2006
- CR080: Canonical component designators?
- RE: {rpc signature} REQUIRED when rpc style is not specified?
- RE: Fragment identifier syntax not XPointer Framework-compatible
- RE: Suggested editorial changes for IRI and Multipart styles
- RE: Assetions covered by schema validation
- RE: Suggested editorial changes to adjuncts section 4.1.1 wrpc:signature
- RE: Questions on {http method} and {safety} extension properties
- RE: Request 2 clarifications for RPC style
- RE: WSDL 2.0 part 2 comment - 2.3.x, 2.2.x wording problems
- RE: Request 2 clarifications for RPC style
- RE: Deconstructing MEPs
- RE: {http cookies} REQUIRED?
- RE: {http cookies} REQUIRED?
- RE: Endpoint component {name} property vs xml representation as a QName
- RE: Prefix declarations in inlined schema
- RE: service and binding name shown as QNames in example - should be NCNames
- RE: Suggestion to change {safety} to {safe}
- RE: Why don't whttp:authenticationType and {http authentication scheme} match?
- RE: Editorial: Where does {http location ignore uncited} appear?
- RE: HTTPHeader name should be xs:string, not xs:QName
- RE: Questions on {http method} and {safety} extension properties
- RE: Clarification needed on HTTP Transfer Coding
- RE: when does wsoap:code appear?
- RE: When does {safety} appear?
- RE: "interface" attribute info item on service component
- RE: Inline schemas with no target namespace
- RE: Missing properties in the property summary (Core table d-1, second half)