One of these suggestions come around every year or so. It used to be that "we should use XML" and we would hear that a couple of time per year or so.
Personally I don't care for SGF but I'm a firm believe that if it's not broken, don't fix it. I suggest you simply build a tool to translate from and to XML and publish that tool. There could be javascript and php versions of those routines and perhaps also java and other languages. I do appreciate json and believe it to be elegant and if this wheel were not already invented I probably would be in favor of json. Don On Sat, Aug 18, 2012 at 7:48 AM, Petr Baudis <[email protected]> wrote: > Hi! > > On Fri, Aug 17, 2012 at 09:07:19PM +0100, Jonathan Chetwynd wrote: > > SGF has rather limited metadata, JGF could standardise at least part > > of this... > > examples might include: > > Location: ie GPS or similar > > PC[] > > > Timing of moves see javascript date object > > BL[], OB[] etc. > > I think the most obvious representation as JSON is a straightforward > syntactic translation from SGF, and a common chunk of javascript code > can serve as that... The next step can be to have an option to generate > SGF.json directly but I don't see a great case for that except for > optimization of particular webapp setups. > > Petr "Pasky" Baudis > _______________________________________________ > Computer-go mailing list > [email protected] > http://dvandva.org/cgi-bin/mailman/listinfo/computer-go >
_______________________________________________ Computer-go mailing list [email protected] http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
