W3C home > Mailing lists > Public > public-wai-ert@w3.org > January 2007

[comment HTTP in RDF ] Body Property content in base64 instead of string

From: Karl Dubost <karl@w3.org>
Date: Wed, 17 Jan 2007 03:08:25 -0000
To: public-wai-ert@w3.org
Message-Id: <20070117030900.382084F312@homer.w3.org>

This is a comment about 

In 2.4. Body Property, it is said:

   The body property represents an HTTP entity body as defined
   in [RFC 2616]. It can appear in nodes of both type Request or
   Response. HTTP bodies are series of bytes. Thus they MUST be
   translated to a string of text using the Base64 encoding
   scheme to make it representable in RDF.

This is puzzling. 

In 2.7 CDATA Sections, (XML Rec, 4th ed.)

   Definition: CDATA sections may occur anywhere character data
   may occur; they are used to escape blocks of text containing
   characters which would otherwise be recognized as markup.
   CDATA sections begin with the string "<![CDATA[" and end with
   the string "]]>":]

An XML parser will ignore the markup inside a CDATA section and just parse a string of text, which is the intended purpose of the definition above. Then why there is a need to encode as base64, which add another layer of shadow.

If it's a problem with RDF, why not just using the datatype "string" on "http:body"" Property:


Title: "HTTP Vocabulary in RDF"
URL: http://www.w3.org/TR/2006/WD-HTTP-in-RDF-20061220/
Date: 2007-01-17
Status: 1st WD

Karl Dubost - http://www.w3.org/People/karl/
W3C Conformance Manager, QA Activity Lead
   QA Weblog - http://www.w3.org/QA/
      *** Be Strict To Be Cool ***
Received on Wednesday, 17 January 2007 03:09:07 UTC

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