GeoJSON
Incubator for geojson spec rewrite and subsequent IETF RFC submission.
Status
Test and development. The idnits tool from IETF already reports 0 errors.
TODO
Some issues are to be resolved, others are not yet known:
-
Is the migration from the crs object to a crs reference ok?
-
Are the formal changes applied to the existing community spec at http://geojson.org/geojson-spec.html ok?
-
Is there consensus, that the mostly editorial changes apllied are also an enhancement or where these have to be reversed or completed?
-
Check with all authors of current version 1.0 spec, if they are willing to act as authors, or only appear in the contributors section
-
What about an ANTLR4 grammar as non-normative appendix B after the examples and before the contributors (which then would become Appendix C)?
-
Surely no (A)BNF as GeoJSON is simply not describable through ABNF (case sensitivity is missing from literals in ABNF :-) ! ... right?
-
Another possible model would be: One person as Editor on frontpage with affiliation Editor (or geojson.org like the KSON RFC) and all others in the contributor section?
-
There is also an Acknowledgments section possible in addition to (or replacing) a contributor section, where the former is mor for lengthy thanks, which might not fit so well with the approx 15 pages total of the to be submitted paginated text RFC draft ...
Generating Docs
Dependencies
Transform Markdown to XML etc.
Inside the working copy of the repo perform (current practice):
bash pandoc2rfc -R -t template.xml -x transform.xsl back.mkd middle.mkd && mv draft.txt draft-unpaginated.txt && for i in H N T X; do bash pandoc2rfc -$i -t template.xml -x transform.xsl back.mkd middle.mkd; done