> I don't know off the top of my head what license json.org uses. It's a "Do no evil" licence - unless you're IBM or one of their minions.
Greg On 10 April 2013 19:13, Daniel Pitts <[email protected]> wrote: > Do you mean "a common way" or "the Commons way". json.org is pretty much > canonical when it comes to JSON encoding. How much more common do you need? > I realize that this is the apache commons user list, and it wouldn't hurt > to have Commons support JSON better. However as an pragmatic engineer, I > would use json.org before asking the apache community to duplicate that > functionality, unless there are issues with licensing for you. I don't know > off the top of my head what license json.org uses. > > On 4/10/13 2:37 AM, Maurizio Cucchiara wrote: > >> Actually, when I was talking about the best way, I was asking for a >> "common" way. >> >> On 10 April 2013 02:39, Daniel Pitts <[email protected]> wrote: >> >>> I might suggest looking into the json.org library. >>> >>> > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > user-unsubscribe@commons.**apache.org<[email protected]> > For additional commands, e-mail: [email protected] > >
