W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > July 2003

RE: first pass parseType="Literal" text for primer

From: Martin Duerst <duerst@w3.org>
Date: Mon, 28 Jul 2003 10:52:55 -0400
Message-Id: <>
To: <Patrick.Stickler@nokia.com>, <gk@ninebynine.org>, <w3c-rdfcore-wg@w3.org>, <w3c-i18n-ig@w3.org>

Hello Patrick,

At 14:31 03/07/28 +0300, Patrick.Stickler@nokia.com wrote:

> > 2. <title rdf:parseType='Literal'>Why the &lt;FONT&gt; Tag is
> > Bad</title>
> >
> > I take the value of this 'title' property to be:
> >
> >    "Why the &lt;FONT&gt; Tag is Bad"^^rdf:XMLLiteral
>Eh? Really?

Yes, I agree with Graham. Take another example:

<title rdf:parseType='Literal'>Why the &lt;FONT&gt; Tag is <strong
 >Really</strong> Bad</title>

The <strong> tag is markup. The &lt; and &gt; are characters
that are escaped to avoid them being confused with markup.
The way this is represented in the current N-triples syntax is:

"Why the &lt;FONT&gt; Tag is <strong>Really</strong> Bad"^^rdf:XMLLiteral

It would be weird if markup would go unescaped, but characters
would have to be doubly escaped.

Regards,    Martin.

>Don't you mean
>    "Why the <FONT> Tag is Bad"^^rdf:XMLLiteral
>Surely the entities are resolved the same as for any
>If you wanted/needed
>     "Why the &lt;FONT&gt; Tag is Bad"^^rdf:XMLLiteral
>then you'd have to say
>   <title rdf:parseType='Literal'>Why the &amp;lt;FONT&amp;gt; Tag is 
> Bad</title>
>If this is not the case, then I've really missing something
>major here and am very alarmed!
Received on Monday, 28 July 2003 13:26:47 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:54:06 UTC