HTTP RFCs as RDF Classes

[apologies for cross-posting to relevant lists]


For EARL reports, ERT WG needs to provide mechanisms for recording specific Web content that may be negotiated between the server and the client. A URI is therefore not sufficient to identify such content (for example, several versions of a "Web page" under the same URL are being served by language negotiation).

In order to be able to identify such content (aka "resources", "delivery units", "Web unites" etc), ERT WG has translated some of the relevant RFCs into RDF classes and properties. The group has decided to publish this vocabulary as Working Group Notes that are separate from EARL because their scope and usage is really beyond EARL only. We plan to reuse this vocabulary in EARL 1.0 which is currently on Recommendation track.

Since this work may be useful to other groups, we would like to have your feedback and input before publishing these notes. Please provide us ( with any comments by Friday 2nd June, or let me know if you intend to provide comments after this period.

Here are the relevant documents (they are pretty short):

* HTTP in RDF, 8 May 2006, Editors' Note

* RDF822 in RDF, 2 May 2006, Editors' Note

More information about ERT WG work and deliverables:


Shadi Abou-Zahra     Web Accessibility Specialist for Europe | 
Chair & Staff Contact for the Evaluation and Repair Tools WG | 
World Wide Web Consortium (W3C)  | 
Web Accessibility Initiative (WAI), | 
WAI-TIES Project,       | 
Evaluation and Repair Tools WG, | 
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 Thursday, 11 May 2006 14:18:19 UTC