jmdyck/es-spec-emu

The ECMAScript 2015 language specification, formatted in ecmarkup (with ecmarkdown and grammarkdown)

es-spec-emu's Issues

Need aoid=Type on Clause 6 (sec-ecmascript-data-types-and-values)

Type is called from many abstract operations. See tc39/ecmarkup#36.

Too much XML

• DTD is bad
• XML declaration is bad
• XSLT stylesheet is bad

Otherwise it is a matter of taste. E.g. I think adding /s on void elements is bad and sets a bad precedent.

emu-prodref

Would be nice to implement emu-prodref. My thinking is that we put the emu-grammar definitions in the annex and then all other occurrences of the identical production are replaced with emu-prodref. That way all the syntax is in one place.

need inline attribute for alternative references

Somewhat related to #11, emu wants an inline attribute on alternative references, eg. in clauses that define semantics for a production.

Abrupt completion should be a dfn

See this section: http://www.ecma-international.org/ecma-262/6.0/index.html#sec-completion-record-specification-type.

UTF-8 encoding

We should use a UTF-8 encoding, as UTF-8 is pretty much assumed on the web these days. No reason to use more HTML entities than we have to IMO.

use gh-pages branch instead of master

This will allow a preview of the HTML file in the browser via Github Pages.

Need aoid for emu-clauses that define abstract operations

Title says it, I think?

Replace `emu-internal-ref refid="id"` with `emu-xref href="#id"`

Subclauses of annexes should still be annexes

Presently the output has emu-clause's nested under annexes.

dfn and emu phrases

I notice that dfn is used heavily in your output. Which is great! But I wonder two things:

1. How can we get a dfn for Completion such that Completion{ ... } links appropriately?
2. Are dfns over-used? For example there is a dfn for "language" and some other really basic terms. Do we want those auto-linking all over the place?

Output multiple documents linked my imports

One giant document will be very hard to edit.

I am not sure of the best heuristic here as I have tried many. I had the best luck with an algorithm that sets a max size of a file and, starting from leaf clauses, builds a .html until it exceeds max size. But generally I got the sense that we will just want to pick something reasonable to start with and once we use this as a source format we can move/rejigger things at will.