Hello,
I have added an XML schema file describing the osm format 0.5.
I have testet it with "xmllint -schema osm-0.5-schema.xml osmfile"
Someone said, a schema file would be better for code generation and testing.
(xmllint can also use dtd).
The file format is defined by the programs who reads/wr
On Sun, Nov 9, 2008 at 5:48 AM, Brett Henderson <[EMAIL PROTECTED]> wrote:
> I've been meaning to create a schema for a long time but never got
> around to it, it didn't seem like a very high priority. If people hate
> Schema that much then I guess a DTD should be created for change files
> instea
Frederik Ramm wrote:
> Does
>
> http://wiki.openstreetmap.org/index.php/OSM_Protocol_Version_0.5/DTD
>
> not work?
>
> You're right about the change files though, I don't know if there's
> anything for that. Then again, while it is very easy to validate your
> application's output against a DTD,
[replying to both of Frederik's messages]
On Sunday 09 November 2008, 01:02:13, Frederik Ramm did write:
> Hi,
>
> Florian Lohoff wrote:
> > I dont think anyone expects every reponse of the server to be validated.
>
> I was under the impression that Hugh did.
>
Well, it would be ideal on the s
On Sat, Nov 08, 2008 at 04:02:13PM +0100, Frederik Ramm wrote:
> Hi,
>
> Florian Lohoff wrote:
> >I dont think anyone expects every reponse of the server to be validated.
>
> I was under the impression that Hugh did.
>
> >I have no problems if the DTD is a moving target and
> >people get told so
Hi,
Florian Lohoff wrote:
> I dont think anyone expects every reponse of the server to be validated.
I was under the impression that Hugh did.
> I have no problems if the DTD is a moving target and
> people get told something changed. But currently there is nothing to
> check against
Does
http
On Sat, Nov 08, 2008 at 02:38:23PM +0100, Frederik Ramm wrote:
> None that I am aware of. Frankly, I'm not even sad about this, I believe
> any kind of server-side validation would be
>
> * a lot of work to implement
> * slowing down API requests
> * hard to maintain
>
> while any kind of clie
Hi,
Hugh Barnes wrote:
> Oh, that's insane. Such a powerful tool. You're stating the opposite of
> obvious … obvious would be that you use the DTD to validate against. What
> kind
> of validation exists?
None that I am aware of. Frankly, I'm not even sad about this, I believe
any kind of se
On Saturday 08 November 2008, 00:29:11, Matt Amos did write:
> i've also worked with XML Schema (with a big 'S') and found it to be
> unwieldy and ultimately unhelpful. something more human-readable would
> be better :-)
>
It's a good example of what Frederik is afraid of OSM "becoming" (for want
[sorry, Frederik, this was meant for the list…]
On Saturday 08 November 2008, 21:17:44, Frederik Ramm did write:
> Hi,
>
> Hugh Barnes wrote:
> > I thought I saw a page some time ago which had a DTD in it, and someone
> > suggested we use RELAX NG instead to define the content model.
>
> All t
Hi,
Hugh Barnes wrote:
> I thought I saw a page some time ago which had a DTD in it, and someone
> suggested we use RELAX NG instead to define the content model. Can't find it
> now. That person was right. We'll have a lot more joy with it. It's also a
> good idea to add attribute constraints e
On 7 Nov 2008, at 12:36, Hugh Barnes wrote:
And I take it the API itself (the interface) is almost finalised and
it's too
late for comments? If not, where do you prefer them? Given recent
discussions,
I guess the list.
We will be doing discussions on the API this weekend.
http://wiki.op
On Fri, Nov 7, 2008 at 12:36 PM, Hugh Barnes <[EMAIL PROTECTED]> wrote:
> I noticed on the todo list for the Protocol v.0.6
> (http://wiki.openstreetmap.org/index.php/OSM_Protocol_Version_0.6#Pending),
> the wiki lists "XML Schema".
>
> I thought I saw a page some time ago which had a DTD in it, an
On Fri, Nov 7, 2008 at 12:36 PM, Hugh Barnes <[EMAIL PROTECTED]> wrote:
> Does this still need doing? (I'll help) Do we literally intend to use XML
> Schema (count me out if so) or do we mean just a schema for the XML (small
> "s") ?
yes, it still needs doing. i think it means schema with a small
I noticed on the todo list for the Protocol v.0.6
(http://wiki.openstreetmap.org/index.php/OSM_Protocol_Version_0.6#Pending),
the wiki lists "XML Schema".
I thought I saw a page some time ago which had a DTD in it, and someone
suggested we use RELAX NG instead to define the content model. Can't
On Tue, Jun 24, 2008 at 4:15 PM, Dominik Spies <[EMAIL PROTECTED]> wrote:
> Hi,
>
> is there a offical XML-Schema for the OSM-Protocol V0.5?
> It's not very difficult to translate this but if somebody has done it
> already..
You clearly missed:
http://wiki.openstreetmap.org/index.php/OSM_Protocol
Dominik Spies schreef:
> @Stefan
>
> is there any output of your effort you may share?
http://kinkrsoftware.nl/contrib/osm/osm-0.5.xsd
I hope it can give you a starting point, it seems not to be passing by
the validator yet...
Stefan
___
dev mailin
>> wouldn't be enough?
>
> No, because this would
>
> 1. allow ways with one node which we don't want
> 2. require tags to be specified BEFORE the nodes which isn't a requirement
now I got it. I'm not an expoert in DTD, simply didn't catch the fact
that this list is ordered.
In cleartext, this m
Hi,
> wouldn't be enough?
No, because this would
1. allow ways with one node which we don't want
2. require tags to be specified BEFORE the nodes which isn't a
requirement
Bye
Frederik
--
Frederik Ramm ## eMail [EMAIL PROTECTED] ## N49°00'09" E008°23'33"
___
Dominik Spies schreef:
> is there a offical XML-Schema for the OSM-Protocol V0.5?
> It's not very difficult to translate this but if somebody has done it
> already..
>
> Abd I have a question regarding this line in the DTD:
>
>
>
> why tag*,nd,tag*,nd,(tag|nd)* ?
>
> I think this means: zero
Hi,
is there a offical XML-Schema for the OSM-Protocol V0.5?
It's not very difficult to translate this but if somebody has done it already..
Abd I have a question regarding this line in the DTD:
why tag*,nd,tag*,nd,(tag|nd)* ?
I think this means: zero to unlimited tag-elements, exaclty one
nd
21 matches
Mail list logo