On Wed, Mar 13, 2019 at 6:54 PM Lassi Kortela <xxxxxx@lassi.io> wrote: > wouldn't worry about a formal release or publication of these. We could > make one experimental repo with the new S-expression files. I could > update the <http://schemedoc.herokuapp.com/> API to use them and Arthur > could make versions of his personal scripts related to running the SRFI > process and website. Once the S-expression format is reasonably stable > so we can use it ourselves, we could push those files into the official > repo of each SRFI. You could do that. I was just saying that I don't feel we have explored enough the solution space... But then again, having some tools would be wonderful. (But I would say to be prepared to scrape or rewrite them.) > > Therefore the "devil is in the details"... Just saying that "a place > > would be held in the format" is not enough, as these SRFI's > > cross-reference each-other. > > It would be great to have consistent types across all the SRFIs but it > sounds like that would take a lot more time to get correct than the rest > of the things we intend to do. Therefore I would suggest a formal > announcement just for the HTML structure. The types could remain in > continuous development as long as needed, and live in their own > S-expression files which continue to be updated as progress is made. I'm OK to focus on "announcing" just the HTML-related stuff. However although we don't "announce" also the other meta-data, I do think we should have a pretty good idea (i.e. working tools and experimental sites) how the two inter-link together... Ciprian.
