[uf-dev] JSON serialization of microformats

[Kevin Marks]

> not just JSON....
>
> The little perl liberal parser I made here  (work in progress ... still some
> bugs to fix) puts its output into a perl hash - with any element where there
> can be multiple values represented by an array. (that should be reflected in
> any conversion to JSON too).
>
> I don't really see the need to substitute ..
> the first one found could be in [0] regardless...
>
> I'd like to see a bit of discussion about such output  from parsers
> generally with the aim of
> working out something that where it is as easy as possible to get at data
> for simple applications
> while still maintaining some clues to its hierarchy for more complex apps.
> (even if it means some data might need to be duplicated)

JSON is a good way to represent the kinds of nested hashes and arrays
that perl, PHP, Python and Javascript all make natural - there is a
consistent two-way mapping to native forms in each of these languages.