Use of Markdown to replace XML

[joesain26]

Challenge: One of the primary drawbacks of XML and XHTML is tooling. While XSLT is able to process XHTML tags, there is no flexibility to choose between Markdown and XML/XHTML.

Proposals:

• Enhance formatting in text fields, which may provide greater expressibility in the prose documentation and make it easier to author than XML and XHTML.
• Using Markdown instead of or alongside HTML would better support human-readable information within SCAP content.
• Make it easier for Content Developers to build in material for a wide audience and make clearer documentation/guidance in content.
• Decide if we want to make expressive documentation easier to develop and if we want to be able to support more graphical documentation.

[joesain26]

This issue is essentially covered by scapcommunity/XCCDF issue 4, Better Support for Human-Readable Information (https://github.com/scapcommunity/XCCDF/issues/3). Closing it here.