In section 9, the draft Standards Documentation Specification says "all files in a standard must be in an open format for which parsers are commonly available" and lists some acceptable formats. Section 11 says "Normative human readable documents should be in XHTML format". I think the intent there was to make the standard easily accessible and easily viewable. This recommendation hasn't always been followed, with some documents saved as Word documents (not an open format) or in open formats other than XHTML.
HTML seems like a nice format because it can be marked up in a standard way and anybody can view it in a browser. But now MarkDown, GitHub Flavored MarkDown (GFM), and various wiki syntaxes are commonly used. Should they be allowed? If we continue to manage the standards repo at GitHub, then GFM would be very convenient. But even with converters like PanDoc, it's hard to get a clean conversion between formats.
At the moment, I'm thinking that specific allowed formats should not be proscribed in a Standards Documentation Standard. One could simply say that the human-readable documents should be easily accessible via the Web, be in an open format, and easily viewable. This would allow for MarkDown (in the context of GitHub), HTML (in the context of a "normal" website), or PDF (which on most computers when accessed via a web link will either be displayed directly in a browser or will launch an application that can display it).
In section 9, the draft Standards Documentation Specification says "all files in a standard must be in an open format for which parsers are commonly available" and lists some acceptable formats. Section 11 says "Normative human readable documents should be in XHTML format". I think the intent there was to make the standard easily accessible and easily viewable. This recommendation hasn't always been followed, with some documents saved as Word documents (not an open format) or in open formats other than XHTML.
HTML seems like a nice format because it can be marked up in a standard way and anybody can view it in a browser. But now MarkDown, GitHub Flavored MarkDown (GFM), and various wiki syntaxes are commonly used. Should they be allowed? If we continue to manage the standards repo at GitHub, then GFM would be very convenient. But even with converters like PanDoc, it's hard to get a clean conversion between formats.
At the moment, I'm thinking that specific allowed formats should not be proscribed in a Standards Documentation Standard. One could simply say that the human-readable documents should be easily accessible via the Web, be in an open format, and easily viewable. This would allow for MarkDown (in the context of GitHub), HTML (in the context of a "normal" website), or PDF (which on most computers when accessed via a web link will either be displayed directly in a browser or will launch an application that can display it).