W3C home > Mailing lists > Public > public-wai-ert@w3.org > November 2006

recording the URI in WebContent class

From: Shadi Abou-Zahra <shadi@w3.org>
Date: Fri, 10 Nov 2006 09:54:52 +0100
Message-ID: <45543E5C.80805@w3.org>
To: public-wai-ert@w3.org

Dear Group,

During the previous teleconferences we discussed where to best record 
the URI of a Web resource in the WebContent class. We identified that 
using rdf:about was not adequate (intranets, private networks, dynamic 
addresses, etc) and that we need to keep a property to record the URI.

The question is now where to best have this property. We already have 
such a property in the "HTTP Vocabulary in RDF". So the WebContent class 
would currently look like this:

<earl:WebContent rdf:ID="myID">
   <earl:httpRequest>
     <http:GetRequest>
       <uri:uri>http://www.example.org:80/</uri:uri>
     </http:GetRequest>
   </earl:httpRequest>
</earl:WebContent>

We also discussed duplicating the uri:uri property directly within the 
WebContent class to simplify queries. The WebContent class would then 
look like this:

<earl:WebContent rdf:ID="myID">
   <uri:uri>http://www.example.org:80/</uri:uri>
   <!--// the part below would be optional //-->
   <earl:httpRequest>
     <http:GetRequest>
       <uri:uri>http://www.example.org:80/</uri:uri>
     </http:GetRequest>
   </earl:httpRequest>
</earl:WebContent>

While the HTTP vocabulary is currently optional, the URI will need to be 
duplicated if the HTTP vocabulary is used. It is also unclear which URI 
should be exactly recorded, for example if the original GET request 
yields a redirection to a different URI.

My proposal would be to go with the first approach and use the HTTP 
vocabulary to record the information about the Web resource. It is more 
precise and I don't think the query becomes that much more complicated 
(though a little longer).

What do others think?


SIDE NOTE: on a side note (while we are at it), rdf:about *could* still 
be used depending on the Web resource, and what the tool is actually 
trying to record. This is an application (and context) specific decision 
and is related to the definition of rdf:about. This is another variant 
of how the WebContent class could look like:

<earl:WebContent rdf:about="http://www.example.org:80/">
   <earl:httpRequest>
     <http:GetRequest>
       <uri:uri>http://www.example.org:80/</uri:uri>
     </http:GetRequest>
   </earl:httpRequest>
</earl:WebContent>


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 |
Received on Friday, 10 November 2006 08:55:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:27 GMT