- From: Shadi Abou-Zahra <shadi@w3.org>
- Date: Tue, 17 Jul 2007 11:00:09 +0200
- To: Carlos A Velasco <carlos.velasco@fit.fraunhofer.de>
- CC: public-wai-ert@w3.org
Hi Carlos, Thank you for raising this issue, it has been recorded as issue #32: - <http://www.w3.org/WAI/ER/EARL10/issues#cont> Regards, Shadi Carlos A Velasco wrote: > Hi all, > > As I mentioned to Shadi last week, when working on the guide, I stumble > into what I think is a small issue with the Content class for non-HTTP > resources. > > For the usual HTTP resources, I do not think it is an issue, as the > HTTP-in-RDF vocabulary can be used to express correctly URIs via > earl:context. > > However, for non-HTTP resources, since we got rid of the uri property, > the only way to express URIs of Content resources is via rdf:about, > which *IMHO*, there are use cases where this is appropriate, whereas in > other scenarios, rdf:about may be an 'internal pointer' to where > resources are stored or retrieved after testing. > > Furthermore, for HTTP resources, for servers with content negotiation, > rdf:about cannot be used with the URI of the resource, as several > resources could be retrieved under the same URI, and context is more > than necessary. Same applies to Test Subject. > > Solution: maybe some optional property like earl:nonHttpUri, or back to > uri:uri ... > > regards, > carlos -- 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 |
Received on Tuesday, 17 July 2007 09:04:35 UTC