proposal for "Content" class

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 |