Closed gkellogg closed 5 years ago
Now also includes updates to use INFRA for primitive types and fixes #199.
I scanned this looking to see if it was just a clean transform to the new terms -- and AFAICT it was. The only possible exception might be around JavaScript strings ... but that really has to do with our existing description including a somewhat confusing parenthetical
(UTF-8)
...which describes an encoding of unicode, not unicode.
JSON uses UTF-8, and there are other variations of unicode, so I think it's still necessary to describe it this way, otherwise UTF-16 or UTF-32 might be considered as reasonable.
This mirrors changes to the API document, but also attempts to clean up our shared terms to reference outside specs as much as possible.
Note that there is still some overlap between WebIDL definitions and ECMASCRIPT, particularly for dictionary and dictionary member.
Preview | Diff