[Openstreetmap-dev] new XML schema discussion moved

Immanuel Scholz immanuel.scholz at gmx.de
Tue Oct 4 10:16:15 BST 2005


Hi again,

wow.. like chatting over a mailing list. Hope the others still listening?


>> - String is key=value;key2=value2;key3=value3 and so on.
>
> that can be the convention, sure

No, that's a server interna.

If the string does not get exported in this way, there is no need to make
it a "convention" ;-). And if you keep that within the server, you may
alter the key/value structure later without having anyone to reimplement
anything (or relearning new syntax things etc)


>> - Semicolons in keys or value are replaced by '%3B' before storing and
>> replaced back when reading. (from URL-encoding)
>
> or just put things in quotes, makes the parser slightly more difficult
> but hey

Again, the parser that has to understand this format is server-intern, so
do what you want, except that it have to be able to store ; in a key or a
value as well ;)


> but but but we're finding GPX a bit of a kludge and there is this nice
> XML Schema page on the wiki...

Ok, so no extensions to GPX. No problem with me.. :).

You can fill out the GPX-optional tags as a bonus. If there are
corresponding keys in the properties-string, e.g. you can fill a
waypoint's <ele> if there is a key named "ele".

string in db:
ele=562.2;name=JOIN THE PARTY!;until=23 March'06

becomes in GPX:

<wpt ...>
  <name>JOIN THE PARTY!</name>
  <ele>562.2</ele>
</wpt>

and in my XML suggestion:

<node id="123" ... />
<property key="ele" value="562.2" />
<property key="name" value="JOIN THE PARTY!" />
<property key="until" value="23 March'06" />


However, Nick will get angry, since he already implemented the
<extensions> stuff in osm-editor ;-).



Ciao, Imi.






More information about the dev mailing list