<requirement name="conformance-testing" stories="cli-entrypoint,cli-documentation,conformance-assets,conformance-full"> These are intended to double as conformance tests. </requirement> <requirement name="parser-phases" stories="architecture"> Parsing has two phases: </requirement> <requirement name="leaf-blocks" stories="block-leaf"> This section describes the different kinds of leaf block that make up a Markdown document. </requirement> <requirement name="block-quotes" stories="block-quotes"> The following rules define [block quotes]: </requirement> <requirement name="list-structure" stories="block-lists"> A [list](@) is a sequence of one or more list items [of the same type]. </requirement> <requirement name="escapes-references" stories="inline-escapes"> Any ASCII punctuation character may be backslash-escaped: </requirement> <requirement name="code-spans-breaks" stories="inline-code-breaks"> A [code span](@) begins with a backtick string and ends with a backtick string of equal length. </requirement> <requirement name="emphasis-rules" stories="inline-emphasis"> The following rules define emphasis and strong emphasis: </requirement> <requirement name="links-images" stories="inline-links"> There are two basic kinds of links in Markdown. </requirement> <requirement name="html-autolinks" stories="inline-html"> Text between `<` and `>` that looks like an HTML tag is parsed as a raw HTML tag and will be rendered in HTML without escaping. </requirement> <requirement name="block-rendering" stories="render-blocks"> HTML is capable of representing the structural distinctions we need to make, and the choice of HTML for the tests makes it possible to run the tests against an implementation without writing an abstract syntax tree renderer. </requirement> <requirement name="inline-rendering" stories="render-inline"> Note that not every feature of the HTML samples is mandated by the spec. </requirement> <requirement name="output-normalization" stories="render-normalization"> For example, the spec says what counts as a link destination, but it doesn't mandate that non-ASCII characters in the URL be percent-encoded. </requirement> <unattached story="cli-errors"/> </unattached>
Run artifact