[prev in list] [next in list] [prev in thread] [next in thread] 

List:       9fans
Subject:    Re: [9fans] (no subject)
From:       "ozan s. yigit" <oz () silentrunning ! ca>
Date:       2007-05-26 0:09:50
Message-ID: E1Hrjqw-00072V-I7 () hex ! silentrunning ! ca
[Download RAW message or body]

sure i understand the skew between implementation vs spec; there are many
[often embarrassing] examples of it in the protocol circles. so long as people
are at the same table agreeing to interoperate, we can fix that. there are
seventy different APIs in 28 different languages (not counting the unlisted 
limbo implementation) for this lightweight data interhange format. you
are nitpicking. [and also forgetting the irregularities lispers had
introduced into their notations, eg. power brackets, array brackets
and the like]

oz

> >some sort of agreement over the structure [for json] and wide support for it
> 
> there isn't though: i had to adjust the code to account for what
> they apparently meant as opposed to what was documented, given examples
> that people produce.
> it was similar but a bit worse for ogdl.


[prev in list] [next in list] [prev in thread] [next in thread]