- From: Robert O'Callahan <rocallahan@gmail.com>
- Date: Thu, 8 Sep 2005 12:25:20 +1200
On 08/09/05, Robert O'Callahan <rocallahan at gmail.com> wrote: > > Okay, but the problem then becomes what happens when one language sets a > property and another language gets it: i.e. what you put in your note: " define > how to take a JS Object and turn it into a Perl %hash, etc." --- without > doing some N^2 conversion matrix. Avoiding the matrix means we have to > specify some common format and how each of N languages maps to it. Now, what > if the common format was --- hmm --- DOM nodes? :-) Then all we need here > are JS convenience functions to convert simple JS object trees into some DOM > representation and back again. We may or may not want to standardize those > functions but I bet they're only a few lines of E4X to write. > > An alternative is to define storage of simple JS object trees > I just found http://www.json.org which does exactly that. and then force all other languages to provide a mapping to and from that. I > guess that'd be acceptable. > ... so maybe we should just say we support JSON objects here and that's that. Rob -- ["Therefore, my dear friends, as you have always obeyed?not only in my presence, but now much more in my absence?continue to work out your salvation with fear and trembling, for it is God who works in you to will and to act according to his good purpose." Philippians 2:12-13.] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20050908/134ae5b7/attachment.htm>
Received on Wednesday, 7 September 2005 17:25:20 UTC