Author: Dann Corbit
Date: 18:42:07 06/23/04
Go up one level in this thread
On June 22, 2004 at 23:14:34, Andrew Wagner wrote: >So, the next step is to figure out what scripts should be written for parsing >the XML, and what tags should be built into the standard. Here are some ideas I >have...suggestions, anyone? > >Tags: ><MoveList/> ><Move/> ><ComputerAnalysis> > <Depth/> > <eval/> > <PV/> every field in the EPD record should be contained in the above. (depth is a good addition, eval == ce, pv is pv) ></Computer Analysis> ><Computer Statistics> > <FailHighPercent/> > <Nodes/> > <HashMoveCutoffPercent/> > <EGTBHits/> > <Extensions/> > <HashPercent/> > <BetaCutoffs/> > <TimeSearched/> ></Computer Analysis> ><Event/> ><White/> ><Black/> ><WhiteElo/> ><BlackElo/> ><Result/> ><Location/> ><TimeControl/> ><Round/> ><AnalyzingComputer> > <Hardware> > <Software> ></AnalyzingComputer> > >Scripts: >Fen list (turns a game into a list of FENs) >EPD list (produces an EPD list of interesting positions, possibly based on !/? >notations >Crosstable >Replay (javascript replay board) >Summary (just shows a list of moves in a format like: > 1.e4 (00:01) e5 (00:00) etc. Instead of naming them all, you might use something like UCI and allow the program to define them for new parameters. Of course, a standardized set would be nice for a foundation. Previous attempts at chess XML fell on their face.
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.