Add Internationalization Considerations section

[marcoscaceres]

There may or may not be any internationalization concerns with the spec, but we should make sure to have an "Internationalization Considerations" section stating that we've taken i18n into consideration. Of course, if there are things that should be considered, we should add them there :)

We will also ask the i18n WG to review the spec to see if they have any feedback for us.

This is part of w3c/webappswg#25

[mrmcpowned]

For a spec standpoint, there doesn't appear to me to be any i18n issues. All of the information that's provided as part of the API isn't user-generated, and I'm not sure if there's any other i18n obligations outside of that. From looking at the appmanifest spec as an example, it seems their i18n section focuses on user-generated content at the least,

If there's consensus on this, would the best practice be to omit the section or simply state that there aren't any "Internationalization Considerations" as part of that section?

[marcoscaceres]

Best practice would be to include the section and just say there are none that we know of.