App id refinement based on i18n review

espinr commented 1 year ago

Closes #7

This change (choose at least one, delete ones that don't apply):

Makes editorial changes (changes informative sections, or changes normative sections without changing behavior)

If it changes the specification itself, the following tasks have been completed:

[X] Confirmed there are no ReSpec errors.

Commit message:

Based on @aphillips' suggestions on the PR #58 and issue #7
Appropriate wording (uniquely instead of univocally)
Clarify the 'is string' INFRA definition.
Avoid misunderstandings with the word RECOMMENDED.

Preview | Diff

espinr commented 1 year ago

As I mentioned in #7 , I've clarified explicitly (in the description) that:

The value of app_id is both case-sensitive and sensitive to different ways of encoding characters in Unicode. Consequently, two app_id values are equal only if they are encoded as the same sequence of code points.

And, since our naming convention is more guidance than compliance, I moved the suggestion to the usage note to clearly separate the conformance from the usage tips.

The commit is a3b9fcfc4abb8c2770f83a63c1a3e7339aa77d4b

The preview is at https://pr-preview.s3.amazonaws.com/espinr/miniapp-manifest/pull/61.html#app_id-member

xfq commented 1 year ago

I18N discussed this in their teleconference of 2023-02-09 and they were satisfied with this PR. Thank you!

w3c / miniapp-manifest

App id refinement based on i18n review #61