Re: [ACTION] represenation of simple and more complicated HTTP conversation in RDF

Hi,

To elaborate a little more on this, this is how I understood the proposal:

Scenario 1: Content negotiation
- The first HEAD request to a URL yields a response that contains some 
header information; this is wc1. A subsequent GET request with specific 
parameters yields the actual content; this is wc2. Since wc2 is what has 
actually been tested, wc1 could be dropped. The earl:subject points to 
the wc2 instance.

Scenario 2: Compound content
- The first GET request to a URL yields a response with actual content 
such as an HTML document; this is wc1. Subsequent GET requests are sent 
to fetch other parts of the "Web unit, for example the CSS and other 
files. These are wc2...wcN. The earl:subject points to the collection 
with wc1...wcN since these have been tested collectively.

Scenario 3: Redirect
- The first GET request to a URL yields a response that contains a 
redirect; this is wc1. A subsequent GET request (to a different URL) 
yields the actual content; this is wc2. As in content negotiation, wc1 
could be dropped (though it may make sense to record it in this case so 
that the URL change is reasoned).


Is this also how others understand the proposal? Are there other 
scenarios to think of? Are there issues with the model?

Regards,
   Shadi


Johannes Koch wrote:
> 
> Johannes Koch schrieb:
>>> Probably you performed the evaluation on wc2 because it contain 
>>> actual content. So the subject would be wc2. If OTOH you did an 
>>> evaluation on wc1, the subject would be wc1.
>>
> 
> Carlos Iglesias schrieb:
>> So the idea is to have a RDF container with both, wc1 and wc2, and 
>> point from subjet to wc2 which is inside a ¿standalone? container. 
>> Isn't it?
> 
> If you need the combination of wc1 and wc2 for something else, you can 
> create an rdf:Seq with references to both wc1 and wc2.

-- 
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 Wednesday, 13 December 2006 12:49:49 UTC