[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Toad-devel] File format for tournament information
From: |
Ben Finney |
Subject: |
Re: [Toad-devel] File format for tournament information |
Date: |
Wed, 2 Apr 2003 14:29:55 +1000 |
User-agent: |
Mutt/1.5.3i |
On 02-Apr-2003, Garner, Robin wrote:
> I have defined a file format for exchanging tournament data - it is
> being implemented for my system that does the Australian Tournament
> Rankings, to replace the ad-hoc formats I read at the moment.
Great! That's functionality I hadn't thought of, but would fit nicely
in my vision for TOAD.
> The attached file TournRec.lhs is a Haskell parser for the tournament
> file (proof of existence for a parser :), and the file format is
> specified in comments at the start of the program. It's early enough
> days that the format can be modified without much trouble.
Now I'll have to brush up on (i.e. learn for the first time) my Haskell
skills.
> Some examples of the format this file reads are as follows:
Any objections to defining an XML format, so that the DTD holds the
format description?
Other than that, a few comments:
- Pick, and stick to, a delimiter for the fields; you're using space
sometimes, comma sometimes. If you want a human-readable file, it
should be well-defined what is syntax and what is data. (This would
be fixed by using an XML format with every piece of data a
well-defined "element".)
- Use ISO date format; it's smaller, unambiguous, logical, and
standard. (It also matches the date field order that the majority
of the Go-playing population of the world uses :-)
I think a simple format like this is exactly what we should be aiming
for with the first round of TOAD data storage.
--
\ "I hope some animal never bores a hole in my head and lays its |
`\ eggs in my brain, because later you might think you're having a |
_o__) good idea but it's just eggs hatching." -- Jack Handey |
address@hidden F'print 9CFE12B0 791A4267 887F520C B7AC2E51 BD41714B