W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > October 2010

Re: ISSUE-58: PlainLiteral and TypedLiteral value for strings [RDFa 1.1 API]

From: Shane McCarron <shane@aptest.com>
Date: Thu, 28 Oct 2010 13:33:59 -0500
Message-ID: <4CC9C217.7050800@aptest.com>
To: nathan@webr3.org
CC: Toby Inkster <tai@g5n.co.uk>, RDFa Working Group WG <public-rdfa-wg@w3.org>, sysbot+tracker@w3.org
Nathan,

I don't think so.  What we said in the call is that the data is not 
interpreted at all.  As a result I think that Toby is exactly correct.  
Javascript translates (within quotation marks) \n to a newline and \t to 
a tab.  If that was in the source, then it will be in the 'value'.

On 10/28/2010 1:04 PM, Nathan wrote:
> Toby Inkster wrote:
>> On Thu, 28 Oct 2010 11:54:29 +0100
>> Nathan <nathan@webr3.org> wrote:
>>
>>> Primarily, if we have the following triple:
>>>
>>> <#nbsp> <http://example.com/lit> "Hello \n\tWorld." .
>>>
>>> Do we expect the related call to object.toString() and/or
>>> object.value to return
>>>
>>> "Hello \n\tWorld."
>>>
>>> or
>>>
>>> "Hello
>>>     World."
>>
>> I would expect the following to succeed (assuming an assert function is
>> defined which takes an expression and throws an exception if the
>> expression is false):
>>
>>     assert(object.toString() == object.value);
>>     assert(object.toString() == "Hello \n\tWorld.");
>>     assert(object.toString() != "Hello \\n\\tWorld.");
>>
>
> ahh.. my take away from todays telecon was the inverse of what you 
> just said.

-- 
Shane P. McCarron                          Phone: +1 763 786-8160 x120
Managing Director                            Fax: +1 763 786-8180
ApTest Minnesota                            Inet: shane@aptest.com
Received on Thursday, 28 October 2010 18:34:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:05:22 UTC