In response to request on the public mailing list, I converted the 1.0a specification to Ascii Doc format. Please note that I broke the document into multiple adoc files. jsr32_1_0_a.asc is the master, and includes all the others. GitHub currently renders includes as document links, rather than placing them inline -- but when rendered offline using AsciiDoctor, it'll produce one document.
At present, the pseudo-code examples in the Section 9: Job Runtime Lifecycle (job_runtime_lifecycle.doc) REQUIRES validation against the spec ... the nested-list structure is a mess. Preferably we can re-write this as a line numbered pseudocode template rather than a nested list as it was in the original spec; but I didn't want to take any liberties with it.
Several XML snippets, examples, and samples need reformatting for syntax highlighting, and we could do a better job at picking out inline code for highlighting.
In response to request on the public mailing list, I converted the 1.0a specification to Ascii Doc format. Please note that I broke the document into multiple adoc files. jsr32_1_0_a.asc is the master, and includes all the others. GitHub currently renders includes as document links, rather than placing them inline -- but when rendered offline using AsciiDoctor, it'll produce one document.
At present, the pseudo-code examples in the Section 9: Job Runtime Lifecycle (job_runtime_lifecycle.doc) REQUIRES validation against the spec ... the nested-list structure is a mess. Preferably we can re-write this as a line numbered pseudocode template rather than a nested list as it was in the original spec; but I didn't want to take any liberties with it.
Several XML snippets, examples, and samples need reformatting for syntax highlighting, and we could do a better job at picking out inline code for highlighting.
But I think this is a pretty solid start.