does file content deserve its own class?

Hi,

During this week's teleconference we continued the discussion on "test subjects that are local files". Here the minutes of this discussion:
  <http://www.w3.org/2006/10/04-er-minutes#item01>


There was no resolution but several important points were made:
 * It would be useful to have a possibility to store a (base64) copy of the file contents (for example when the file is not publicly available).
 * File URI can not be assumed to be unique and so a property to store the file name is needed as a label for the file contents (see also related comment by Charles [1]).
 * A uri:uri property is not needed in the WebContent class since the rdf:about attribute can be used (see separate discussion in the minutes [2]).

[1] <http://lists.w3.org/Archives/Public/public-wai-ert/2006Oct/0010>
[2] <http://www.w3.org/2006/10/04-er-minutes#item02>


A conclusion that can be drawn from this is that there is a separate use case for FileContent from WebContent. The two are indeed related and WebContent could be extended to fit the requirements for local files (a generic "Content" class?). So the question is: does file content deserve its own class?


If we decide for creating a FileContent class, here is an example of how instances of these classes could look like:

<earl:WebContent rdf:about="http://www.example.org/page.html">
  <dc:date rdf:datatype="&xmls;Date">2005-06-25</dc:date>
  <dc:format>text/html</dc:format>
  <earl:httpRequest>
    <!--// REQUEST HEADERS //-->
  </earl:httpRequest>
  <earl:httpResponse>
    <!--// RESPONSE HEADERS //-->
  </earl:httpResponse>
</earl:WebContent>

<earl:FileContent rdf:ID="unique123">
  <dc:date rdf:datatype="&xmls;Date">2005-06-25</dc:date>
  <earl:filename>file.html</earl:filename>
  <earl:filesource><![CDATA[aksgbq3833o3gbo4zgblakc8t9ut2]]></earl:filesource>
</earl:FileContent>


Here is the RDFS for the proposed FileContent class:

 <rdfs:Class rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#FileContent">
   <rdfs:label xml:lang="en">File Content</rdfs:label>
   <rdfs:comment xml:lang="en">Subjects that are available on a local file system</rdfs:comment>
   <rdfs:subClassOf rdf:parseType="Collection">
     <owl:Restriction>
       <owl:onProperty rdf:resource="http://purl.org/dc/elements/1.1/date"/>
       <owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:minCardinality>
     </owl:Restriction>
   </rdfs:subClassOf>
 </rdfs:Class>

 <rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#filename">
   <rdfs:label xml:lang="en">File Name</rdfs:label>
   <rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#FileContent"/>
   <rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#string"/>
 </rdf:Property>

 <rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#filesource">
   <rdfs:label xml:lang="en">File Source</rdfs:label>
   <rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#FileContent"/>
   <rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#string"/>
 </rdf:Property>


Looking forward to discussion and input!

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 Thursday, 5 October 2006 07:44:37 UTC