Markdown validity Re: Agreeing on Historical Markdown

2014-07-12 Thread Sean Leonard
As I'm thinking about this, I have other questions: Can a Markdown parser/processor fail? Is there a concept of Markdown validity--i.e., can Markdown content be invalid (from the perspective of Markdown, not (X)HTML)? As I understand it: A Markdown processor identifies Markdown control

Re: Markdown validity Re: Agreeing on Historical Markdown

2014-07-12 Thread Aristotle Pagaltzis
* Sean Leonard dev+i...@seantek.com [2014-07-12 16:35]: However, if you have Markdown in the HTML content with markdown=1 as with PHP Markdown Extra, it is necessary to parse the HTML with something other than a straight HTML parser since the straight HTML parser will misinterpret the Markdown

Re: Markdown validity Re: Agreeing on Historical Markdown

2014-07-12 Thread Michel Fortin
Le 12-juil.-2014 à 10:32, Sean Leonard dev+i...@seantek.com a écrit : Markdown may have a concept of HTML validity. A Markdown processor that identifies HTML in Markdown content may determine that the HTML is valid or invalid. For example, it may identify div ... [end of document] as HTML

Re: Markdown validity Re: Agreeing on Historical Markdown

2014-07-12 Thread Waylan Limberg
On Jul 12, 2014, at 2:52 PM, Michel Fortin michel.for...@michelf.ca wrote: [snip] When you have a question like this, just try it Babelmark 2: http://johnmacfarlane.net/babelmark2/?normalize=1text=%3Cdiv%3E Yes, that's what we all do. And to answer your other question, notice that only two

Re: Markdown validity Re: Agreeing on Historical Markdown

2014-07-12 Thread Sean Leonard
On 7/12/2014 12:31 PM, Waylan Limberg wrote: On Jul 12, 2014, at 2:52 PM, Michel Fortin michel.for...@michelf.ca wrote: [snip] When you have a question like this, just try it Babelmark 2: http://johnmacfarlane.net/babelmark2/?normalize=1text=%3Cdiv%3E Yes, that's what we all do. And to answer

Re: Markdown validity Re: Agreeing on Historical Markdown

2014-07-12 Thread Waylan Limberg
On Jul 12, 2014, at 6:23 PM, Sean Leonard dev+i...@seantek.com wrote: On 7/12/2014 12:31 PM, Waylan Limberg wrote: On Jul 12, 2014, at 2:52 PM, Michel Fortin michel.for...@michelf.ca wrote: [snip] When you have a question like this, just try it Babelmark 2:

Markdown internal metadata Re: Markdown validity

2014-07-12 Thread Sean Leonard
I think I can move on to my next question: It seems that all Markdown content is expected to appear inside of a block-level element in HTML parlance; i.e., inside body or one of its block-level descendants (div, p, td, form, h1...h6, etc.). I tried to do some head stuff, as in:

Re: Markdown internal metadata Re: Markdown validity

2014-07-12 Thread Karl Dubost
Le 13 juil. 2014 à 09:26, Sean Leonard dev+i...@seantek.com a écrit : Therefore, *when it matters*, what are strategies that Markdown users currently use to manage HTML metadata such as those metadata items defined in search for multi-markdown.

Re: Markdown internal metadata Re: Markdown validity

2014-07-12 Thread Shane McCarron
We did some work on accessible markdown a year ago. Adding RDFa and aria markup to help add metadata to the content. I don't think I have any good pointers right now but it was all about making sure the generated HTML was wcaag company and semantically meaningful. On Jul 12, 2014 7:52 PM, Karl

Re: Markdown internal metadata Re: Markdown validity

2014-07-12 Thread Fletcher T. Penney
These are some of the things that lead to me releasing MultiMarkdown 9 years ago: * The realization that Markdown documents could be complete documents, and not just a snippet of text to be inserted in a blog CMS * That these complete documents would need some sort of metadata (Gruber was not

Re: Markdown internal metadata Re: Markdown validity

2014-07-12 Thread Aristotle Pagaltzis
* Alan Hogan cont...@alanhogan.com [2014-07-10 23:00]: You are entirely correct that there is a strong chance that this API call would actually send an updated copy of a JSON object including fields such as “title”, “date”, “url”, and “body”, the last of which may implicitly or explicitly be