RE: [Xenocide-programming] names.xml

[mamutas <ma...@pr...>]

Hi guys,

First, make sure when you reply the post it goes to
Xen...@li... address.

I got a feeling that James has answered Red Knight's questions, but the
answers did not make to the mailing list. So, I will try to answer them =
and
James will correct me if I am wrong, ok?

1) Type checking in XML could be enforced via using of XML schemas =
instead
of DTDs. But I guess that was not meant for 'country-namegroup' link. =
This
issue could be resolved by using references to an element.
4) Namespaces could be specified in the DTD or XML header (or again, in =
XML
schemas).

That is what I remember so far without digging through my memory since =
it
was about 2 years I worked with XML.

In my understanding, if we are going to use proper XML for our =
datafiles,
then we should pick up some open source XML parser. I do not have
preferences whether it will DOM or SAX so far, it all depends on what =
memory
management we are going to have for those DBs.

Regards,
mamutas

-----Original Message-----
From: xen...@li...
[mailto:xen...@li...] On Behalf Of
red...@pr...
Sent: Thursday, August 07, 2003 3:15 PM
To: James Harlow
Subject: Re: [Xenocide-programming] names.xml


Hi,

Quoting James Harlow <ja...@is...>:

> Hi everyone. I'm going to be doing the modelling code, and while I was
> getting to know the project, I thought I'd take the liberty of =
cleaning=20
> up names.xml into proper xml with a DTD (document type declaration) so =

> it validates.
It was me who made it, and it was supposed to be XML like, not strict =
XML=20
(cause I never had done it). The idea was having a simple database to =
store=20
the names to be used in the random name generation, in a simple fashion. =

However, the changes are not dramatical and I think it would complicates =
too

much the parsing (less if we can use a proper XML parser to do that)... =
So=20
good job.

> 2. XML Comments. XML comments go like this: <!-- this is a comment=20
> -->.
> Technically they're a little more involved than this, but everyone I=20
> know thinks that using complex comments is a bad idea. C and C++=20
> comments are not valid.
Part of XML like desitions.

> 1. Improve the type-checking in the DTD. Most of the data isn't=20
> checked
> at all, and it could be - for example the <probability =
group=3D"country">=20
> could be checked to make sure country was a country that had been=20
> defined in <namegroups>.
And how you do that? Excuse my maybe lame questions, but Ive never done =
XML,

DB and Bussiness applications are not my strong point...

> 3. Write a tool so that designers don't have to edit the XML manually.
> It's my opinion that the only people who ever see text files should be =

> programmers, everyone else should have tools.
Yes all agree on that, and the tools we are doing comes from that =
philosofy.

For instance the PAQ Explorer and the repository are just 2 of them...

> 4. Add a namespace. All our XML should be put in our own namespace,=20
> eventually.
Again, how?

> 5. (And I'm an idiot for forgetting to do this) Put a version=20
> attribute
> in the <database> element.

Greetings
Red Knight


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including =
Data
Reports, E-commerce, Portals, and Forums are available now. Download =
today
and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/=
01
_______________________________________________
Xenocide-programming mailing list =
Xen...@li...
https://lists.sourceforge.net/lists/listinfo/xenocide-programming


---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.502 / Virus Database: 300 - Release Date: 7/18/2003
=20

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.502 / Virus Database: 300 - Release Date: 7/18/2003
=20