- From: Martin Duerst <duerst@w3.org>
- Date: Mon, 28 Jul 2003 10:52:55 -0400
- 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 <FONT> Tag is > > Bad</title> > > > > I take the value of this 'title' property to be: > > > > "Why the <FONT> Tag is Bad"^^rdf:XMLLiteral > >Eh? Really? Yes, I agree with Graham. Take another example: <title rdf:parseType='Literal'>Why the <FONT> Tag is <strong >Really</strong> Bad</title> The <strong> tag is markup. The < and > 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 <FONT> 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 >literal. > >If you wanted/needed > > "Why the <FONT> Tag is Bad"^^rdf:XMLLiteral > >then you'd have to say > > <title rdf:parseType='Literal'>Why the &lt;FONT&gt; Tag is > Bad</title> > >No? > >If this is not the case, then I've really missing something >major here and am very alarmed! > >Patrick
Received on Monday, 28 July 2003 13:26:47 UTC