- From: Dave Pawson <dave.pawson@gmail.com>
- Date: Fri, 23 Nov 2012 14:59:01 +0000
- To: Markdown List <public-markdown@w3.org>
On 23 November 2012 14:50, Ryan Freebern <rfreebern@unionstmedia.com> wrote: > I mean that a casual markdown user shouldn't find that a majority of their > documents are invalidated by a parser that implements our spec. Bit like asking for full forwards compatibility? > > I agree that additional profiles would alleviate this problem, but I think > their development needs to be active alongside the core spec. Each time we > decide to restrict the syntax in the core spec, we should explicitly add the > dropped syntax options to a potential additional profile document. In this > case, if we choose to use > > #+ ...\n > > as our header syntax, we should add the variant with arbitrary trailing hash > marks and the setext variant to potential profile documents immediately. > Then, if usage surveys show them to be uncommon, those profiles can be > dropped. Yes.... with one caveat. That the core profile not mention them in order that it be fully standalone? > > Perhaps these documents can be part of the wiki for now and codified later. If you wish to start such a document on the wiki please do, I find the above description quite clear. (Guessing) would you say you are aiming at an intermediate profile (good across the pareto implementations) or app-specific, good for only a few implementations? regards -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. http://www.dpawson.co.uk
Received on Friday, 23 November 2012 15:00:16 UTC