Post by alandau on Jul 18, 2015 13:59:38 GMT -8
A little while back, I wrote up the last complete GDL specification as an easier-to-modify HTML file and put it on Github: github.com/AlexLandau/gdl-spec
I hadn't heard anything back from any Stanford representatives regarding hopefully making this into a definitive standard, but Bertrand alluded to the project in chat during the last qualifier (a problem came up regarding the response format for an "info" command), so perhaps I should post about it here and work on getting it more updated.
Putting the standard on Github would allow more people to take on the work of writing and editing the specification, and in return get a better-defined set of requirements and standards for GGP players (and servers) to follow. It would also allow for versioning of the rules, so e.g. a tournament could say it is using version 1.2.0, or a GGP codebase could specify it was built against the 1.1.2 standard (for the benefit of the person who discovers it and wants to build on it three years later).
Along with versioning, issue tracking, pull requests and branching all work nicely here. The latter two can be used to propose new features for GDL (e.g. random players or a new timing mechanism for matches) and specify experimental versions to be tried in tournaments.
I hadn't heard anything back from any Stanford representatives regarding hopefully making this into a definitive standard, but Bertrand alluded to the project in chat during the last qualifier (a problem came up regarding the response format for an "info" command), so perhaps I should post about it here and work on getting it more updated.
Putting the standard on Github would allow more people to take on the work of writing and editing the specification, and in return get a better-defined set of requirements and standards for GGP players (and servers) to follow. It would also allow for versioning of the rules, so e.g. a tournament could say it is using version 1.2.0, or a GGP codebase could specify it was built against the 1.1.2 standard (for the benefit of the person who discovers it and wants to build on it three years later).
Along with versioning, issue tracking, pull requests and branching all work nicely here. The latter two can be used to propose new features for GDL (e.g. random players or a new timing mechanism for matches) and specify experimental versions to be tried in tournaments.