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

[HTTP-in-RDF] data URL

From: Johannes Koch <johannes.koch@fit.fraunhofer.de>
Date: Wed, 18 Apr 2007 13:00:35 +0200
Message-ID: <4625FA53.7090608@fit.fraunhofer.de>
To: public-wai-ert@w3.org

Hi group,

I reread the 'The "data" URL scheme' RFC (2397). Section 2 reads

>    The URLs are of the form:
> 
>                     data:[<mediatype>][;base64],<data>
> 
>    The <mediatype> is an Internet media type specification (with
>    optional parameters.) 
[...]
>    If <mediatype> is omitted, it defaults to text/plain;charset=US-ASCII.

1. We looked for a mechanism to store the content bytes (for the body 
property). But as you see the data URL spec requires to add the media 
type for non-default media types. So the data URL cannot be used for 
storing _only_ the content bytes. Adding the media type from the 
Content-Type header would be sort of redundant. What happens when both 
ocurrences of a media type are different in the RDF model?

I think we should discuss the use of data URLs again.

2. Anyway, there's a missing ";" before "base64" in Example 2.12 in 
<http://www.w3.org/TR/2007/WD-HTTP-in-RDF-20070323/#body>:

> <http:body rdf:resource="data:base64,aksgbq3833o3gbo4zgblakc8t9ut2">

must be

<http:body rdf:resource="data:;base64,aksgbq3833o3gbo4zgblakc8t9ut2">

-- 
Johannes Koch
BIKA Web Compliance Center - Fraunhofer FIT
Schloss Birlinghoven, D-53757 Sankt Augustin, Germany
Phone: +49-2241-142628    Fax: +49-2241-142065
Received on Wednesday, 18 April 2007 11:01:47 GMT

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