tentative decisions on changes to HTTP-in-RDF

Dear Group,

Following the recent discussion on the ERT WG list, please find below a 
tentative suggestions of changes to be made to the HTTP-in-RDF document. 
Please send any comments and thoughts to the list, we will discuss these 
changes on a teleconference call tomorrow.

#1. clarify the scope of the vocabulary (somewhere in section 1)

#2. (deffered) timestamp requests and responses
  - this needs more discussion and will not be implemented in this draft

#3. add a short blurb on the convention for normalisation of values

#4. (deffered) add "http:transcript" property
  - this needs more discussion and will not be implemented in this draft

#5. change named properties for headers to resource values

#6. adopt the Jakarta method for header element values

#7. refine description of the algorithm

#8. provide mechanism for extensible response code

#9. describe the sequence of requests in the connection class


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 Tuesday, 20 March 2007 15:53:51 UTC