- From: Andy Robinson <andy@reportlab.com>
- Date: Wed, 17 Oct 2018 08:22:29 +0100
- To: Antonio Olmo Titos <antonio@w3.org>
- Cc: public-opentrack <public-opentrack@w3.org>, MartÃn <martin.alvarez@fundacionctic.org>
Hi all, Just following up on this. I'm very happy with the clarifications. Our group's GitHub repo is at "https://github.com/openath" already, so will fit very well with renaming to Open Athletics. What we currently call "OpenTrack-lite JSON" will be extremely concrete formats - basically whatever the structure of our own database is! This is already being exchanged by us and various national federations, and we have many competitions available. Because it's quite close to "only one way to do it", we can import and export right now. Our plans are to start writing out our reference data nightly into static storage (maybe S3) and we should have thousands of clubs, venues and competitions, with foreign key references. We can then run nightly jobs autogenerating the JSON LD from this, but so can others. The "OpenAthletics standard" is then free to be JSON LD, which is much more permissive (multi valued fields, multilingual, self-describing). - Andy
Received on Wednesday, 17 October 2018 07:22:53 UTC