Spec doesn't define that child order is significant #545
Description
This is just an oversight; one of the things that was so obvious nobody realized it was missing.
Attributes are explicitly defined as ordered; properties are defined as officially unordered (but might be ordered in particular language representations). But child lists don't say either way. It's clearly intended that they're an ordered list.
(I'm just filing this because I'm about to get off the bus and won't have time to go fix it immediately. If someone else wants to fix it in the spec before I get to it, feel free.)