|
From: <red...@pr...> - 2003-08-07 20:32:17
|
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 > 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 (cause I never had done it). The idea was having a simple database to store 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 good job. > 2. XML Comments. XML comments go like this: <!-- this is a comment -->. > Technically they're a little more involved than this, but everyone I > know thinks that using complex comments is a bad idea. C and C++ > comments are not valid. Part of XML like desitions. > 1. Improve the type-checking in the DTD. Most of the data isn't checked > at all, and it could be - for example the <probability group="country"> > could be checked to make sure country was a country that had been > 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, > eventually. Again, how? > 5. (And I'm an idiot for forgetting to do this) Put a version attribute > in the <database> element. Greetings Red Knight |