Hi, that is the right path, every format needs a specification About submitting it to Eclipse Foundation, that is a good idea, but I think that it is just the colophon, not the goal.
Before dealing with bureaucracy of the process of Eclipse Foundation, or ISO, or whatever institution, I would write a specification and test it. That is, you write an specification, and developers have doubts and ask questions. Then you revise the specification: Isn't that point clear enough? Should I add examples? How should this ambiguity be solved? Maybe this was not as evident and obvious as I thought. Some day, there will barely be serious doubts or questions, and all would be clearly solved pointing to a section of the specification. Then you can begin to think about the process of submitting to any institution if you want to, but it is not necessary if there is a authoritative site to read a clear specification. i.e. yaml format is defined here: https://yaml.org/spec/ and needn't Eclipse foundation, that would be just a bonus. -- You received this message because you are subscribed to the Google Groups "asciidoc" 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/asciidoc. For more options, visit https://groups.google.com/d/optout.
