Opinions on in-band variation signaling

[mofo syne]

Was thinking that generic block directives concept in
http://talk.commonmark.org/t/block-directives could assist with this.

>>>
!pandoc:
This is a Title
Sean Leonard
November 2014
<<< (compact)

or if there is spaces in the metadata block. No need for %, since we
know that it is metadata already.

>>>
!pandoc:
::::::::::::::::::::::::::::::::
This is a Title
Sean Leonard
November 2014
::::::::::::::::::::::::::::::::
<<< (fenced)

Good for document declaration. E.g. should we load resume.css or
blog.css default styles.

On Wed, Nov 12, 2014 at 10:47 AM, Sean Leonard <dev+ietf at seantek.com> wrote:
> Regarding the text/markdown registration:
>
> At least one commentator (Larry Masinter) specifically requested that the variant identifier be included in-band in the Markdown content, rather than as part of the metadata. I disagree with in-band signaling (as has been registered earlier on this list). Nevertheless, I wanted to take a straw poll and see if anyone has tried to implement in-band Markdown variation identifiers, with any success. Do any implementers have experience with picking the type of Markdown based on some info at the top of the Markdown content? Does it work—or will it never work? Or is it “bad” for particular reasons?
>
> By in-band, I mean a Markdown file with content like this:
>
>>>>
> !pandoc
> % This is a Title
> % Sean Leonard
> % November 2014
>
> Blah blah *blah*.
> <<< (fortin’s suggestion)
>
>>>>
> [!pandoc]: # "This is a pandoc document."
> % This is a Title
> % Sean Leonard
> % November 2014
>
> Blah blah *blah*.
> <<< (seantek’s suggestion)
>
> -Sean
> _______________________________________________
> Markdown-Discuss mailing list
> Markdown-Discuss at six.pairlist.net
> https://pairlist6.pair.net/mailman/listinfo/markdown-discuss