Markdown Discuss - Sep 2014 - It's a Markdown processor, right?

Hello Markdown World,

Last month draft-seantek-text-markdown-media-type was adopted by the 
IETF Apps Area Working Group (APPSAWG). I am working on revising it.

I am trying to use uniform terms. An implementation that converts 
Markdown content to another format--most typically HTML--is called...a 
Markdown processor, right?

I have been using the term "Markdown processor". Just want to see if 
there is substantial disagreement about using that term to refer to the 
collective set of Markdown implementations out there.

Thanks,

Sean

PS I suppose it could also be called a "Markdown implementation". But 
I'm going to stick to my original nomenclature in the absence of a push 
for something else. For instance, graphical tools such as [MarkdownPad] 
may be implementations of Markdown, but they are not processors. 
MarkdownPad is a Markdown editor, that has built-in support for various 
Markdown processors (such as a GitHub Flavored Markdown processor, and a 
Markdown Extra processor).

[MarkdownPad]: http://markdownpad.com/

On Sat, Sep 6, 2014 at 3:55 PM, Sean Leonard <dev+ietf at seantek.com>
wrote:
> I have been using the term "Markdown processor"
In the context of RFCs, etc., that sounds correct. The other things
being discussed in this thread include things I think of as Markdown
editors and in other cases Markdown libraries.

c
--
Chris Lott <chris at chrislott.org>