This is an example specification used to test, develop, and document the ReSpec.js specification publishing system. This really isn't so much a specification as a playground in more ways than one.

RFC 2119 is not OPTIONAL

There are several RFC 2119 keywords: MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL. They are only recognised in uppercase, so that one may still write normally if one must. Importantly, the MUST NOT fail when happening over line breaks, but:

Small Talk about Abbreviations

W3C is no different from other geek outfits, and is therefore full of abbreviations. We don't care about the silly debate going on about abbr and acronym, we just support whatever people use, so that the following all ought to work:

A Defining Moment

A definition is an element that marks out a term that is defined in the current block.

They can sometimes be definitions with a title so that they can be written in the flow of the sentence without disruption.

Sometimes you will see an AbbrDef, which is an abbreviation-based definition.

One thing that should definitely work is creating definitions over multiple lines in the source.

It is then possible to reuse them. The title trick works both ways so that definitions can be reused fluidly. It would be possible to automatically detect them but for the time being they require an a element.

This should have no problem mixing up with abbr as AbbrDef shows, and a definition with a title works over several lines, just like definitions over multiple lines.

The Dahut interface

This is a simple example of the way in which Web IDL [[WEBIDL]] interfaces are created. This one is for the Dahut interface.

readonly attribute DOMString chirality
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
attribute unsigned long age
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
Dahut turnAround (in float angle, in boolean fall)
Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
unsigned long trip ()
Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
void yell ([AllowAny] in unsigned long volume, [TreatNullAs=EmptyString] in DOMString sentence)
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

A Good Reference

One can trivially make references to any specification, say for instance [[WIDGETS]], [[WICD]], and even in a normative way [[!REX]] or [[!SVGMOBILE12]]. It's all about I18N, [[ZHMARK]].

Russian Turtles

This section has an h2 title in the original source.

Russian Turtles

This section has an h2 title in the original source.

Russian Turtles

This section has an h2 title in the original source.

Russian Turtles

This section has an h2 title in the original source.

Russian Turtles

This section has an h2 title in the original source.

Russian Turtles

This section has an h2 title in the original source.

Including other data

Including other data is easy!

The example below is from an external file:


    
      

Transforming content

Transforming content is also easy! this text is hilighted by being wrapped in an 'em'.

Acknowledgements

Many thanks to Marcos Cáceres for moral support, and to Bert Bos and Geoffrey Sneddon for their tools from which I pilfered joyfully.