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

Re: proposal for "Content" class

From: Shadi Abou-Zahra <shadi@w3.org>
Date: Mon, 04 Dec 2006 16:50:54 +0100
Message-ID: <457443DE.6070706@w3.org>
To: public-wai-ert@w3.org
Hi,

Following the latest discussion regarding sequences [1], and the recent 
proposal by Johannes [2], please find an updated proposal for the RDFS 
attached. The only difference to the previous version is a restriction 
that every HTTPContent class must have *exactly one* httpRequest and 
httpResponse pair.

[1] <http://www.w3.org/2006/11/22-er-minutes#item01>
[2] <http://lists.w3.org/Archives/Public/public-wai-ert/2006Nov/0025>

Regards,
   Shadi


Shadi Abou-Zahra wrote:
> Dear group,
> 
> During the previous teleconference we talked about a comprehensive model 
> for "Content" which includes Web content and local file content, as well 
> as HTTP content. Please find a rough outline of this model below, and an 
> initial RDFS for the schema attached. Please send comments and feedback 
> to the list for discussion.
> 
> OUTLINE:
> --------
> 
> #1: Content class
>  - generic for any kind of (e-)content such as content available on the 
> Web or on a local storage
>  - introduces the "date" property which refers to the date at which the 
> content was actually fetched
>  - introduces the "source" property which could be used to record the 
> actual source of the content
> 
> #2: WebContent class (subclass of Content)
>  - for any content that is available on the Web, including via FTP, 
> gopher, or any other protocol
>  - introduces the URI property which could be used to identify the Web 
> resource
> 
> #3: FileContent class (subclass of Content)
>  - for any content that is available on flat files, that is not via the 
> Web (such as shared drives etc)
>  - introduces the filename property which could be used to identify the 
> non-Web resource
> 
> #3: HTTPContent class (subclass of WebContent)
>  - for any Web content that is available via the HTTP protocol
>  - introduces the httpRequest/httpResponse properties which could be 
> used to record the HTTP headers and/or content
>  - the inherited date, URI, and source properties may be duplicated by 
> the HTTP vocabulary
> 
> 
> 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 Monday, 4 December 2006 15:51:07 GMT

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