[OSM-talk] Xml design

[Andy Robinson]

You don't need it specifically for dropdowns but you could have the client
editing software use the XSD to present to the user an "pre-approved" set of
defined keys (and values). By approved, I mean a set of keys and values
fitting a specific definition rather than defined on the fly by the user.

Cheers

Andy

Andy Robinson
Andy_J_Robinson at blueyonder.co.uk 

>-----Original Message-----
>From: talk-bounces at openstreetmap.org [mailto:talk-
>bounces at openstreetmap.org] On Behalf Of bvh
>Sent: 07 January 2007 1:12 PM
>To: talk at openstreetmap.org
>Subject: Re: [OSM-talk] Xml design
>
>On Sun, Jan 07, 2007 at 12:21:01PM +0000, scott wrote:
>> With the current XML design of k="" v="" it would seem very difficult to
>> create a useful XSD for the data.  A tight XSD would help to avoid
>> duplication,spelling mistakes, reduce the xml size, and would allow for
>> the gui to present useful drop downs.  For example we currently have
>
>Maybe I should read up on XSD (any pointers) but why do we need it for
>dropdowns?
>
>cu bart
>
>_______________________________________________
>talk mailing list
>talk at openstreetmap.org
>http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk