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

Ahh (!), sorry I was being dumb for a moment, okay we all agree, great. 
Issue closed as void.

Cheers!

Shane McCarron wrote:
> 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.
> 

Received on Thursday, 28 October 2010 18:52:43 UTC