Sam Tobin-Hochstadt writes:
The draft leaves the semantics of the top level fundamentally unspecified. If this aspect of the charter cannot be portably accomplished, it should not be standardized. Simply describing a feature without saying what it should do is not standardization.
The WG decided by unanimous consent to take no action on this ticket.
They are not entirely specified, it's true. But there is no reason to force everything to be either 100% specified or 0% specified. A standard is a contract between user and implementer, and it may quite legitimately partly constrain the implementer or user while still providing some freedom of action. No standard, not even highly restrictive ones like ECMAscript 5, constrains everything.