W3C home > Mailing lists > Public > public-wai-ert@w3.org > April 2011

[HTTP-in-RDF] StatusCode, statusCodeNumber, and dc:identifier

From: Shadi Abou-Zahra <shadi@w3.org>
Date: Wed, 20 Apr 2011 00:10:01 +0200
Message-ID: <4DAE0839.1080901@w3.org>
To: ERT WG <public-wai-ert@w3.org>
Dear ERT WG,

Please find below a description of the "StatusCode issue" [1]. Feel free 
to comment in advance of the meeting.

[1] <http://www.w3.org/WAI/ER/HTTP/issues#StatusCodeClass>

Original comment by David Remahl:

Essence of the comment:
  - the StatusCode Class [2, 3] does not have an identifier for the 
status code number, and the commenter suggests using dct:identifier.

[2] <http://www.w3.org/TR/2009/WD-HTTP-in-RDF10-20091029/#StatusCodeClass>
[3] <http://www.w3.org/2008/http-statusCodes>

Following that suggestion, the RDF code [3] would look like this:

<rdf:Description rdf:about="#statusCode404">
   <dct:isPartOf rdf:resource="#statusCodeGroup4xx"/>
   <dc:title xml:lang="en">Not Found</dc:title>
   <rdf:type rdf:resource="http://www.w3.org/2006/http#StatusCode"/>

  - #1. HTTP-in-RDF already provides a statusCodeNumber property [4], 
which records the *status code sent by the server*
  - #2. CarlosV suggests using and XMLInterger datatype rather than 
Literal values for the status code


Proposed resolution:
  - use dct:identifier (with or without XMLInteger datatype) in addition 
to statusCodeNumber, to represent the "should value" rather than what 
was actually sent by the server (could be useful for consistency checks)

Other options:
  - change statusCodeNumber from "value sent by the server" to "should 
value", and move it from Response to StatusCode class (possibly make it 
a sub-property of dct:identifier too)
  - create another property, say "statusCodeValue", as an XMLInteger 
datatype that lives in the StatusCode class (possibly make it a 
sub-property of dct:identifier too)



Shadi Abou-Zahra - http://www.w3.org/People/shadi/ |
   WAI International Program Office Activity Lead   |
  W3C Evaluation & Repair Tools Working Group Chair |
Received on Tuesday, 19 April 2011 22:10:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:59 UTC