SGF 5 & shells.
- As one who also also uses SGF for games other than Go, I think the current
discussion is somewhat misguided. Attempting to optimize and make concrete
the ideal set of properties and conventions for Go is laudable, but isn't
really what SGF is all about.
The core "shell" of SGF is a specification that will allow tools
to be written to read, write and manipulate collections of games
in SGF format, with no knowlege at all about what game type is
The second "shell" of SGF is a more rigorous specification of the
content of certain specific properties, such that *if* those properties
are used, they should be used in a manner consistant with the specification,
and smart tools that deal with more than one specific game can rely
on common format for those properties among all games.
The third "shell" of SGF is a subspecies of SGF devoted
to a particular game. It is pointless to try to define a generic
standard that will be meaningful for all games and allow meaningful
display of all games. There is simply too much variability. Defining
SFG-Go as an official standard is a fine idea, but shouldn't affect
the first two shells of SGF at all. And it shouldn't be called SGF5.