Re: To start at the beginning

Re: the scope, I know most discussion so far has centered on the markdown →
HTML flow, but is there value in writing the spec using generic terms
("Level one header", "numbered list", etc.) rather than explicitly
referring to HTML tags? Markdown can theoretically be compiled to any other
presentational format, so the spec ought to be applicable to all of them. I
could easily see someone wanting to write a markdown → LaTeX or a markdown
→ MediaWiki converter, for example.

Ryan


On Tue, Nov 20, 2012 at 4:11 AM, Dave Pawson <dave.pawson@gmail.com> wrote:

> As we put more ideas to the group I'm getting lost.
> Rather than additions, perhaps we can start with what we know are
> essential.
> 1. Scope
> 2. Deliverables
> 3. Definition of syntax + semantics
>
> 1. Scope.
>   Proposal. We define syntax and semantics for a MD to HTML basic.
> 2. Deliverables.
>   a single document containing syntax and semantics (of transformed to
> XHTML).
> 3. From http://daringfireball.net/projects/markdown/syntax
> The basic elements are
>
> Blocks
>
> para
> headers
> lists
> codeblock
> [optional, blockquotes, rules]
>
> Inlines
>
> links
> emphasis
> code
> [optional, images]
>
> Others.
> Escapes
> [optional automatic links]
>
>
> Proposal. We take each in turn and gain agreement on these, entering
> them as each is defined.
> The 'optional' ones above, I'm proposing be dropped from the basic.
>
>
> Comments or alternatives for a way ahead please.
>
> regards
>
>
> --
> Dave Pawson
> XSLT XSL-FO FAQ.
> Docbook FAQ.
> http://www.dpawson.co.uk
>
>