canmove, Confirmed users
901
edits
WebAPI/DesignGuidelines: Difference between revisions
Jump to navigation
Jump to search
m
Add periods to make it screen reader-friendly
m (Add periods to make it screen reader-friendly) |
m (Add periods to make it screen reader-friendly) |
||
| Line 48: | Line 48: | ||
==Specification work== | ==Specification work== | ||
If you get the OK from the standards community, go forth and write a specification. | If you get the OK from the standards community, go forth and write a specification. | ||
* have your work in a public location where people can comment and provide patches | * have your work in a public location where people can comment and provide patches. | ||
** Etherpad, GitHub repo, Google Doc, etc. Anything that's collaborative | ** Etherpad, GitHub repo, Google Doc, etc. Anything that's collaborative. | ||
* actual standardization decisions will be made by relevant organization | * actual standardization decisions will be made by relevant organization. | ||
** ex. a W3C Working Group, a W3C Community Group, the WHATWG, the IETF, etc. | ** ex. a W3C Working Group, a W3C Community Group, the WHATWG, the IETF, etc. | ||
* follow Mozilla's [[WebAPI/ExposureGuidelines|API exposure guidelines]] (notably sending "Intent to implement" emails) | * follow Mozilla's [[WebAPI/ExposureGuidelines|API exposure guidelines]] (notably sending "Intent to implement" emails). | ||
* carefully follow the processes of the standards organization within which you are working | * carefully follow the processes of the standards organization within which you are working. | ||
** there are often legal reasons for these processes | ** there are often legal reasons for these processes. | ||
==Design considerations== | ==Design considerations== | ||