Conversation
gesa
left a comment
gesa
left a comment
There was a problem hiding this comment.
Cloudflare's workerd is not ideal, it's too late to ask them to change that right?
| <li><strong>Organization</strong> (required): The organization or individual responsible for the runtime</li> | ||
| <li><strong>Name</strong> (required): The human-readable name of the runtime</li> | ||
| <li><strong>Key</strong> (required): The unique string identifier</li> | ||
| <li><strong>Description</strong> (required): A brief description of the runtime</li> |
There was a problem hiding this comment.
🤔 Should this use more precision than "brief" ? A maximum character length maybe? (similarly should all fields have a character length limit?)
There was a problem hiding this comment.
Also I think "required" is fine here, but if the secretariat raises any concerns, maybe we switch to "mandatory"?
There was a problem hiding this comment.
Happy to make the switch if the secretariat raises a concern.
I'm indifferent on changing "brief". If someone has a compelling maximum character limit then I won't necessarily disagree, but I personally do not have a good idea for what that would be. Open to other wording suggestions as well.
|
What is wrong with Contrary to |
gesa
left a comment
gesa
left a comment
There was a problem hiding this comment.
For consistency, use TC55 when referring to the TC, and use WinterTC55 when referring to the GitHub org.
I am v excited about this TR. Now I need to write the ecmarkup to generate it as not-a-standard
|
@Ethan-Arrowood Bringing your notes from my PR into this primary PR
I'm deeply conflicted about the spelling of organisation within the JSON. Ecma does formally use Oxford GB English, but when it comes to code, designers have historically opted for en-US spellings. |
Co-authored-by: Aki <hi@akiro.se>
4 participants
Authors an ECMA Technical Report for the future of runtime-keys work.
Closes: #23
Note: this is still heavily WIP; you're welcome to leave feedback but please know I'm still actively working on certain parts. This will be discussed at upcoming WinterTC meetings (first one will be January 23rd), so please attend those if you want to participate in the discussion.