canmove, Confirmed users
901
edits
ExposureGuidelines: Difference between revisions
→Exceptions
No edit summary |
|||
| Line 22: | Line 22: | ||
Exceptions to the standardization rules above include: | Exceptions to the standardization rules above include: | ||
# during the first 12 months of development of new user-facing products, APIs that have not yet been embraced by other vendors or thoroughly discussed by standards bodies may be shipped | # during the first 12 months of development of new user-facing products, APIs that have not yet been embraced by other vendors or thoroughly discussed by standards bodies may be shipped '''only as a part of this product''', thus clearly indicating their lack of standardization and limiting any market share they may attain | ||
# ecosystem- and hardware-specific APIs that are not standard or of interest to the broader web at that time (or ever) may be shipped in a way to limit their harm of the broader web (ex. only on a device or only in specific builds with clear disclaimers about applicability of exposed APIs). An example of this is the FM Radio API for Firefox OS. | # ecosystem- and hardware-specific APIs that are not standard or of interest to the broader web at that time (or ever) may be shipped in a way to limit their harm of the broader web (ex. only on a device or only in specific builds with clear disclaimers about applicability of exposed APIs). An example of this is the FM Radio API for Firefox OS. | ||
# APIs which only Mozilla is interested in at that time. In cases such as this (which will likely be rare), Mozilla will solicit feedback from as many relevant parties as possible, begin the standardization process with a relevant standards body, and create a test suite as part of the standards process. An example of this is the Push Notifications API. | # APIs which only Mozilla is interested in at that time. In cases such as this (which will likely be rare), Mozilla will solicit feedback from as many relevant parties as possible, begin the standardization process with a relevant standards body, and create a test suite as part of the standards process. An example of this is the Push Notifications API. | ||
# APIs which will be hidden behind preferences. APIs like this can also skip the required API review (see below). | # APIs which will be hidden behind preferences. APIs like this can also skip the required API review (see below). | ||
=Declaring Intent= | =Declaring Intent= | ||