[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xdi] Proposal about null vs. undefined values
It's tempting to map JSON's value null to some special role in the XDI graph, but I think this opens the door to problems unless it's really an exact fit. Client programs could be using any semantics for JSON null, so any specific XDI semantics will differ from somebody's. XDI values are JSON values, and XDI promises round-trippable storage of them. The straightforward way to do this is to explicitly represent it as a special value like JSON's values true and false. I believe the status quo is non-roundtrippable because the two cases of not assigning a value to an attribute, and assigning JSON null as the value of an attribute, produce the same result in the XDI graph, which becomes JSON null on retrieval. This is the issue my example raised. Markus, can you confirm whether current behavior is as I just described? On Aug 17, 2013, at 9:58 PM, Drummond Reed <drummond.reed@xdi.org> wrote:
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]