Hi Philippe,
Thank you for your review comments, Please find some responses below:
Philippe Le Hegaret wrote:
> - how do you correlate requests and responses? At first, I thought
> document order was the answer but since document order isn't significant
> in RDF, I don't know if you considered this.
We did consider this and decided it is outside the scope of the
vocabulary but of a higher-level model. For example, in EARL we have an
HTTPContent class which in the current proposal contains exactly one
Request and one Response class so that it represent exactly one
client-server interaction.
Other options include using the RDF sequence lists (rdf:seq) which
define a specific order of the list items. Each item in the sequence
list could be a Request or Response. In other words, you will have to
define the model for how to use this vocabulary in WSDL.
> - We store XML in the message body when we deal with SOAP messages, but
> that doesn't seem to be allowed by http:body.
Indeed it is but the XML Literal needs to be converted to base64 first.
It will also need to be translated back in order to be human readable...
> - The HTTP response definition in section 2.2 is missing http:version.
> - Example 2.2 is missing a http:responseCode.
Thanks for spotting these, not sure if we can slip in these changes
before the publication.
Regards,
Shadi
--
Shadi Abou-Zahra Web Accessibility Specialist for Europe |
Chair & Staff Contact for the Evaluation and Repair Tools WG |
World Wide Web Consortium (W3C) http://www.w3.org/ |
Web Accessibility Initiative (WAI), http://www.w3.org/WAI/ |
WAI-TIES Project, http://www.w3.org/WAI/TIES/ |
Evaluation and Repair Tools WG, http://www.w3.org/WAI/ER/ |
2004, Route des Lucioles - 06560, Sophia-Antipolis - France |
Voice: +33(0)4 92 38 50 64 Fax: +33(0)4 92 38 78 22 |