[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xdi] Proposal about null vs. undefined values
I propose that XDI Messaging use a non-JSON way of signaling no value at the queried address. JSON null would then not be overloaded for this purpose and could be round-trippable as part of user data. This signal could be formatted as text that is not JSON, i.e. not double-quoted or a number or true or false or null; or it could be out of band and not a text value in the returned value slot at all, but a separate part of the response. Libraries that talk to XDI Messaging and present a convenient interface for developers in a particular programming language could interpret this signal and pass the information in a way natural to that programming environment; in _javascript_ this might be _javascript_'s undefined, in Java, this might be Java's null. I am not sure about the two representations of "no value for this attribute" in XDI currently - I suspect it means that having both a value context node and literal node may be redundant. However this issue should be separate from the issues of storing and accurately round-tripping JSON. Joseph On Aug 20, 2013, at 6:23 AM, Markus Sabadello <markus.sabadello@xdi.org> wrote:
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]