On Thursday, May 5, 2016 at 4:09:06 AM UTC-5, Edward K. Ream wrote: > > On Wed, May 4, 2016 at 10:07 PM, Jose Gonzalez <[email protected]> wrote: > >> A possibility could be to specify a schema for a given json file >> indicating how to structure the document. > > > An interesting idea. > > Perhaps there are already tools that import json based on json schema. > I'll look into this. >
After a quick check, I don't think json schema are what we want. Instead, we want a description of json formats *as they applies to Leo*. That is, we want to tell Leo which fields should create children, and similar information. Naturally, existing json schema tools have no knowledge of Leo, and so can't be used. Yes, we could represent the Leonine information using json, but that's wonky and unnecessary. Instead, my original idea of providing data to a class that would help import json files seems like the simplest thing that could possibly work. EKR -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
