XML is overkill with little to no additional benefits. I can't read XML better
than SGF. Plus it could be difficult to implemented on platforms which do not
have pre-made libraries for reading/writing XML documents, and writing an XML
parser from scratch is not a trivial task.
However, I am in favor of changing the SGF format to allow coordinate encoding
using the "standard" coordinates system rather than the one created just for
SGF; i.e., "a1" vs "aa". This would make SGF files more readable by a human
(and computer since it wouldn't need to know the board size to properly
interpret the coordinates). To start, we just need the leading Go programs to
read either encoding format (so they are backwards compatible). This should be
somewhat trivial since you can tell which format just by looking at the
coordinate encoding. And then sometime in the near future, Go programs switch
to writing SGF files with "standard" coordinates.
Phil
----- Original Message ----
From: Jason House <[EMAIL PROTECTED]>
To: computer-go <computer-go@computer-go.org>
Sent: Monday, October 22, 2007 8:09:17 AM
Subject: [computer-go] XML alternatives to SGF
An XML alternative [1] to SGF has recently come to my attention. What do
others think of this alternative? Personally, the effect of a tag affecting
the previous tag seems kind of strange to me.
PS: I found out about this from [2], a recently closed GoGui feature request to
write more sane sgf files that contain the standard algebraic notation used in
all GUIs.
[1] http://www.rene-grothmann.de/jago/Documentation/xml.html
[2]
https://sourceforge.net/tracker/?func=detail&atid=489967&aid=1752711&group_id=59117
_______________________________________________
computer-go mailing list
computer-go@computer-go.org
http://www.computer-go.org/mailman/listinfo/computer-go/
