Convert to ecmarkup

[gesa]

I wish git did a better job of letting a file be renamed and then changed. or changed and then renamed. basically, I wish git could handle renaming files.

[gesa]

Some notable comparisons:

• The PDF version of the standard that has been approved by the GA
• The PDF version of this branch
• The HTML version

[gesa]

Differences to watch for:

• Clause 5.3 Web workers is now identified as normative-optional, due to the fact that supporting web workers is not a requirement, but if an implementation does support web workers, the requirements apply.
• references to Clause 6 are weird. the clause title is "The global scope" which makes for odd mid-sentence reference. Maybe just use "see clause 6" or manually title xrefs as 'the global scope'.

Suggestions

• Add "ECMAScript" as a term in clause 4
• Rename all Clause 5 subclauses to drop "Methods and properties defined in" and "Interfaces defined in". Maybe add another single sentence to clarify in clause 5 or at the beginning of clauses 5.1 & 5.2
• I think I've tested most of the links? someone should do so systematically. or add a script into ecmarkup/emu-format to do that for me.

I've updated the files in the comment above (and torched the cache) with the last few commits

[gesa]

Suggested change

	<p>As such, this Ecma Standard defines the Minimum common web API specification, which defines a subset of Web Platform APIs for server runtimes to implement for interoperability with the web. This is the first edition of the standard, corresponding to the 2025 snapshot. As the web platform and web server runtimes grow and evolve, the committee will aim to publish with an annual cadence.</p>
	<p>As such, this Ecma Standard defines a minimum common web API, which identifies a subset of Web Platform APIs for server runtimes to implement for interoperability with the web. This is the first edition of the standard, corresponding to the 2025 snapshot. As the web platform and web server runtimes grow and evolve, the committee will aim to publish with a regular cadence.</p>

[gesa]

Suggested change

	<p>This Standard defines the 2025 snapshot of the Minimum common web API, a curated subset of APIs defined by web platform standards from W3C and WHATWG, which is intended to define a minimum set of capabilities common to browser and web server runtime environments based on ECMAScript.</p>
	<p>This Standard defines the 2025 snapshot of the minimum common web API, a curated subset of APIs within web platform standards from standards organizations such as W3C and WHATWG, which is intended to define a minimum set of capabilities common to browser and web server runtime environments based on ECMAScript.</p>

[gesa]

Suggested change

	<p>A conforming implementation of this Standard shall provide the interfaces and properties listed in this specification, according to their definition in the corresponding W3C or WHATWG standard. A conforming implementation shall also conform to ECMA-262.</p>
	<p>A conforming implementation of this Standard shall provide the interfaces and properties listed in this specification, according to their definition in the corresponding standard. A conforming implementation shall also conform to ECMA-262.</p>

[jasnell]

if we wanted, we could have the pdf also built automatically and available on the website.

[jasnell]

LGTM with the additional suggested edits.