#[KevinMarks]1The children are a list so have an implied order, which is document order, The place where there is ambiguity is for properties, as different languages have different default orders for their dictionary types - PHP and JS are creation order, Python is hash order, Go is random order (to stop you assuming order) so iterating the properties needs care. I don't know what Rust does.
jeremycherfas, hendursa1, neceve, theshawe, ur5us__, [Rose], [grantcodes], Ramon[d], hendursaga, charukiewicz and [jacky] joined the channel
#[jacky]Rust allows for any of the above with specification so I'm leaning on document order
#[KevinMarks]1another option is sorting keys alphabetically when writing json to make diffing clearer - I have seen this specified in some contexts (as well as normalising keys and values to utf8 rather then escaped unicode )
#[tantek]1yes the "document order" aspects of the parsing spec are essential. nothing "optional" there
jacky, kimberlyhirsh[d], jeremycherfas and gRegor joined the channel
#[jacky]Is there a particular reason for it? Tbh the inclusion of this (re: keeping it document order) would make it actually easier to implement signed forms of Microformats JSON (though that's not necessary - just something I've noticed now as a possibility)
#sknebel[jacky]: particular reason for what? child order: see e.g. any feed for why you might want document order