I've put up a new draft for GTP version 2 on the GTP web page,
http://www.lysator.liu.se/~gunnar/gtp/
This is available in HTML, postscript, pdf, and LaTeX formats. The postscript and pdf versions are strongly recommended if you want to print it and probably also for online reading. The HTML version is passable but looks worse and has a couple of defects. If you want to quote or comment parts of the draft the LaTeX source is preferrable.
This draft does not include every command that has been discussed on the list and definitely not all commands included in GNU Go. I have intentionally tried to limit the command set to something which is sufficient for the following purposes:
1. Playing games in a tournament setting. 2. Playing games on a server. 3. Basic regression testing.
Notice in particular section 8 with comments about various design decisions and specification details.
There are some missing sections in the draft, but the headings are there so you can see what is planned.
I'm interested in feedback about: 1. Is there something which is really stupid in the design? 2. Is there some command or functionality which is urgently missing? 3. Are there any obvious errors in the specification? 4. Are there any spelling or other writing mistakes? (I'm not a native speaker.)
The old draft is now considered obsolete.
/Gunnar
PS I'll be travelling a lot during the coming weeks, and may be without mail access for extended periods of time. DS
I wrote:
I have intentionally tried to limit the command set to something which is sufficient for the following purposes:
- Playing games in a tournament setting.
- Playing games on a server.
- Basic regression testing.
I forgot to add that more commands and functionality will be considered for later protocol versions. I do want to keep this one rather small though.
/Gunnar
I forgot to add that more commands and functionality will be considered for later protocol versions. I do want to keep this one rather small though.
I would like to propose to keep the base document small, and define protocol extensions in their own documents. This would preserve your intention "to keep the document less imposing" as you wrote in the specification.
-Inge
Hi Gunnar,
The draft is awesome. It seems to be very well thought out and having it will probably open the door to widespread usage.
I'll try to update the graphical autotester when I get a chance to use the new protocol and fix some deficiencies it has.
Don
From: Gunnar Farnebäck gunnar@lysator.liu.se Sender: gtp-admin@lists.lysator.liu.se X-BeenThere: gtp@lists.lysator.liu.se X-Mailman-Version: 2.0.11 Precedence: bulk List-Unsubscribe: http://lists.lysator.liu.se/mailman/listinfo/gtp, mailto:gtp-request@lists.lysator.liu.se?subject=unsubscribe List-Id: Discussion about the computer-go protocol GTP. <gtp.lists.lysator.liu.se> List-Post: mailto:gtp@lists.lysator.liu.se List-Help: mailto:gtp-request@lists.lysator.liu.se?subject=help List-Subscribe: http://lists.lysator.liu.se/mailman/listinfo/gtp, mailto:gtp-request@lists.lysator.liu.se?subject=subscribe List-Archive: http://lists.lysator.liu.se/pipermail/gtp/ Date: Fri, 12 Jul 2002 17:39:40 +0200
I've put up a new draft for GTP version 2 on the GTP web page,
http://www.lysator.liu.se/~gunnar/gtp/
This is available in HTML, postscript, pdf, and LaTeX formats. The postscript and pdf versions are strongly recommended if you want to print it and probably also for online reading. The HTML version is passable but looks worse and has a couple of defects. If you want to quote or comment parts of the draft the LaTeX source is preferrable.
This draft does not include every command that has been discussed on the list and definitely not all commands included in GNU Go. I have intentionally tried to limit the command set to something which is sufficient for the following purposes:
1. Playing games in a tournament setting. 2. Playing games on a server. 3. Basic regression testing.
Notice in particular section 8 with comments about various design decisions and specification details.
There are some missing sections in the draft, but the headings are there so you can see what is planned.
I'm interested in feedback about: 1. Is there something which is really stupid in the design? 2. Is there some command or functionality which is urgently missing? 3. Are there any obvious errors in the specification? 4. Are there any spelling or other writing mistakes? (I'm not a native speaker.)
The old draft is now considered obsolete.
/Gunnar
PS I'll be travelling a lot during the coming weeks, and may be without mail access for extended periods of time. DS _______________________________________________ gtp mailing list gtp@lists.lysator.liu.se http://lists.lysator.liu.se/mailman/listinfo/gtp