> The docs you list are a bit confusing, so I went to the XML itself, > and that has some issues, mainly name/document related. > > 1. The "osm" tag name is already used for a format, so I suggest not using > it. > > Similarly "osmChange" or "osc" files are already maybe you should call > this something else?
Thank you for pointing me at this. I think of osmAugmented or osmAugmentedChange and subsequently a file name extension .osa. > 2. The sections are a bit confusing in that the order is very > important. That makes parsing a bit more difficult than it might need > to be if you just renamed sections? Eg "keep" means two different > things in two different contexts, but by using the same name, it means > your parser must keep a lot of state. What do you mean exactly? The purpose of the elements in keep is always the same: this is data that is unchanged but related to changed data. Of course there are different reasons why an element arrives in keep. However, this will make things difficult: an element could be present for more than one reason, for example a node because it is referred by more than one element. What do you think of the hierarchy for nodes: - coords changed - tags changed - part of a changed geometry for ways: - members changed - geometry of members changed - tags changed and for relations the same, maybe with a separate set of events for nested relations, in the sense that a element is listed only once at the event of highest precedence. Cheers, Roland
_______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
