[Servercert-wg] [DRAFT] SC26 - Pandoc-Friendly Markdown Formatting Changes
Jos Purvis (jopurvis)
jopurvis at cisco.com
Thu Jan 16 14:10:36 MST 2020
The following is the ballot to update the BRs with formatting changes to make them Pandoc-friendly for changing our automation methods. I’m just looking for two endorsers at this point; I’ll add the timeline once we formally open the ballot.
BALLOT SC26: Pandoc-Friendly Markdown Formatting Changes
The following ballot is proposed by Jos Purvis of Cisco Systems and has been endorsed by XXX and YYY.
Purpose: This ballot modifies the formatting of the Baseline Requirements in order to make the presentation of content consistent and aligned with “vanilla” Markdown. This will permit the use of pandoc as a format-translation tool to automatically produce a PDF, DOCX, and HTML version of the Baseline Requirements document with each update and allow the Forum to use the Markdown-formatted version as the canonical version of the Baseline Requirements. This ballot does NOT declare any version canonical: it merely paves the way to the possibility of doing so in the future by making the document formatting cleaner. In addition, the ballot is not intended to change the meaning of the Baseline Requirements at all—much effort has been spent in ensuring the meaning and wording of the Requirements has not changed in reformatting the presentation elements.
Changes: The changes involved in the ballot are small formatting changes but large in number. As a result, rather than listing the changes individually, members are requested to review the redline of the ballot to see the differences. The pull request containing the set of changes to be implemented can be seen here:
https://github.com/cabforum/documents/pull/142
More specifically, the set of changes to the Baseline Requirements document being proposed in this ballot is shown in this comparison:
https://github.com/cabforum/documents/pull/142/files/93b31c97ec095766152bc67f1723c4dc40cb197e..f452eaa012fb6bc29530f4d91893f4b39a4b8af6
In addition to the above changes, some template files are being added to Github that will assist in formatting but not change any BR content. A copy of the resulting formatting changes in each document format can be seen in the attached documents (ref. BR-26.pdf, BR-26.html, BR-26.docx). These changed versions can be compared to the current versions of the document found at https://github.com/cabforum/documents.
--
Jos Purvis (jopurvis at cisco.com<mailto:jopurvis at cisco.com>)
.:|:.:|:. cisco systems | Cryptographic Services
PGP: 0xFD802FEE07D19105 | +1 919.991.9114 (desk)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cabforum.org/pipermail/servercert-wg/attachments/20200116/b4f9796e/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: BR-SC26.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 82124 bytes
Desc: BR-SC26.docx
URL: <http://cabforum.org/pipermail/servercert-wg/attachments/20200116/b4f9796e/attachment-0001.docx>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cabforum.org/pipermail/servercert-wg/attachments/20200116/b4f9796e/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: BR-SC26.pdf
Type: application/pdf
Size: 261341 bytes
Desc: BR-SC26.pdf
URL: <http://cabforum.org/pipermail/servercert-wg/attachments/20200116/b4f9796e/attachment-0001.pdf>
More information about the Servercert-wg
mailing list