Wednesday, 31 May 2006
- RE: Suggestion to change {safety} to {safe}
- RE: New Woden Results
- RE: New Woden Results
- Re: Suggestion to change {safety} to {safe}
- Re: Parts 1 and 2 Treat Defaults Inconsistently with Eachother
- RE: Component Model Results
- Re: 27 April 2006 WSDL Implementer's call minutes
- RE: interchange issue: empty properties vs. absent properties
- New Woden Results
- Fw: Missing properties in the property summary (Core table d-1, second half)
- Re: Suggestion to change {safety} to {safe}
- Re: Parts 1 and 2 Treat Defaults Inconsistently with Eachother
- Violated Assertions added to TestMetadata.xml
- RE: FW: Component Values Must Be Context Independent
- RE: FW: Component Values Must Be Context Independent
- RE: FW: Component Values Must Be Context Independent
- Re: WSDL 2.0 Component Model Interchange Format - HTTP Error Code Format
- Re: "interface" attribute info item on service component
- Re: Clarification needed on HTTP Transfer Coding
- RE: FW: Component Values Must Be Context Independent
Tuesday, 30 May 2006
- RE: FW: Component Values Must Be Context Independent
- sparql-protocol-query.wsdl
- Interop topics and references
- Re: "interface" attribute info item on service component
- RE: "interface" attribute info item on service component
- Re: "interface" attribute info item on service component
- RE: SparqlQuery-1G missing schemaLocation
- Agenda: 23 May 2006 WS Description telcon
- RE: SparqlQuery-1G missing schemaLocation
Thursday, 25 May 2006
Wednesday, 24 May 2006
- Re: Parts 1 and 2 Treat Defaults Inconsistently with Eachother
- Suggestion to change {safety} to {safe}
- Re: Comment on Part 2, Section 6.5.2
- Re: Comment on Part 2, Section 5.9.3
- Re: Parts 1 and 2 Treat Defaults Inconsistently with Eachother
Friday, 26 May 2006
Tuesday, 23 May 2006
Tuesday, 30 May 2006
- Re: SparqlQuery-1G missing schemaLocation
- Re: SparqlQuery-1G missing schemaLocation
- SparqlQuery-1G missing schemaLocation
- RE: "interface" attribute info item on service component
- Re: Clarification needed on HTTP Transfer Coding
- Re: WSDL 2.0 Component Model Interchange Format - HTTP Error Code Format
- Re: "interface" attribute info item on service component
- RE: "interface" attribute info item on service component
- Re: "interface" attribute info item on service component
- RE: Uniqueness of QNames in 'extends' attribute
- Re: FW: Component Values Must Be Context Independent
- Re: "interface" attribute info item on service component
- RE: Uniqueness of QNames in 'extends' attribute
- Re: Missing properties in the property summary (Core table d-1, second half)
- Re: Inline schemas with no target namespace
- Re: Questions on {http method} and {safety} extension properties
- Re: When does {safety} appear?
- Re: when does wsoap:code appear?
Monday, 29 May 2006
- Re: Comment on Part 2, Section 6.5.2
- Re: Comment on Part 2, Section 5.9.3
- RE: interchange issue: empty properties vs. absent properties
- RE: Parts 1 and 2 Treat Defaults Inconsistently with Eachother
- Re: WSDL 2.0 Component Model Interchange Format - HTTP Error Code Format
- RE: Interchange result update.
- Re: Clarification needed on HTTP Transfer Coding
- RE: WSDL 2.0 Component Model Interchange Format - HTTP Error Code Format
- Re: WSDL 2.0 Component Model Interchange Format - HTTP Error Code Format
- RE: WSDL 2.0 Component Model Interchange Format - HTTP Error Code Format
- Re: Control over Interface Extensions
- Re: WSDL 2.0 Component Model Interchange Format - HTTP Error Code Format
Sunday, 28 May 2006
Friday, 26 May 2006
Thursday, 25 May 2006
- No implementor call today?
- RE: Parts 1 and 2 Treat Defaults Inconsistently with Eachother
- RE: interchange issue: empty properties vs. absent properties
Wednesday, 24 May 2006
- RE: interchange issue: empty properties vs. absent properties
- Interchange result update.
- RE: interchange issue: empty properties vs. absent properties
- interchange issue: empty properties vs. absent properties
- when does wsoap:code appear?
- When does {safety} appear?
Tuesday, 23 May 2006
- RE: WSDL 2.0 Component Model Interchange Format - HTTP Error Code Format
- FW: Component Values Must Be Context Independent
- "interface" attribute info item on service component
- RE: Component Values Must Be Context Independent
- Missing properties in the property summary (Core table d-1, second half)
- RE: Component Values Must Be Context Independent
- RE: WSDL 2.0 Component Model Interchange Format - HTTP Error Code Format
- Probable Regrets for May 25 telecons
Thursday, 18 May 2006
Tuesday, 23 May 2006
- RE: WSDL 2.0 Component Model Interchange Format - HTTP Error Code Format
- Re: WSDL 2.0 Component Model Interchange Format - HTTP Error Code Format
- RE: Component Values Must Be Context Independent
Monday, 22 May 2006
- Re: WSDL 2.0 Component Model Interchange Format - HTTP Error Code Format
- Re: WSDL 2.0 Component Model Interchange Format - HTTP Error Code Format
Friday, 19 May 2006
- Inline schemas with no target namespace
- Parts 1 and 2 Treat Defaults Inconsistently with Eachother
- RE: Uniqueness of QNames in 'extends' attribute
- WSDL 2.0 Component Model Interchange Format - HTTP Error Code Format
- WSDL 2.0 Component Model Interchange Format Update
- Part 2, 5.6.3 XML Representation of subcodes is inconsistent
- Re: Uniqueness of QNames in 'extends' attribute
Thursday, 18 May 2006
Wednesday, 17 May 2006
- Agenda: 18 May 2006 WS Description telcon
- RE: Some new interchange results
- Re: Some new interchange results
Tuesday, 16 May 2006
Thursday, 11 May 2006
Wednesday, 10 May 2006
Tuesday, 9 May 2006
- Agenda: 11 May 2006 WS Description telcon
- RE: WSDL 2.0 Component Model Interchange Format Updated with Part 2 Extensions
- RE: WSDL 2.0 Component Model Interchange Format Updated with Part 2 Extensions
- Comment on Part 2, Section 6.5.2
- Comment on Part 2, Section 5.9.3
- WSDL 2.0 Component Model Interchange Format Updated with Part 2 Extensions
Monday, 8 May 2006
- Re: RDF Mapping status report
- RE: Another WSDL 2.0 implementation?
- RE: Another WSDL 2.0 implementation?
- RE: Another WSDL 2.0 implementation?
- Re: Another WSDL 2.0 implementation?
- Another WSDL 2.0 implementation?
- Re: wsdl2.0 and basic profile 2.0
- RDF Mapping status report
Sunday, 7 May 2006
Saturday, 6 May 2006
Friday, 5 May 2006
Thursday, 4 May 2006
- RE: Test results rollup
- Re: Test results rollup
- RE: Test results rollup
- RE: Test results rollup
- Re: Test results rollup
- RE: Test results rollup
- RE: Test results rollup
- RE: Test results rollup
- Re: Test results rollup
- Part 2 Adjuncts Comments (1 -5)
- Test results rollup
- Re: typeDefinitions property optional?
Wednesday, 3 May 2006
- Re: typeDefinitions property optional?
- RE: typeDefinitions property optional?
- typeDefinitions property optional?
Tuesday, 2 May 2006
- Re: 27 April 2006 WSDL Implementer's call minutes
- Re: 27 April 2006 WSDL Implementer's call minutes
- Re: 27 April 2006 WSDL Implementer's call minutes