Re: [w3c/manifest] Rewrote Proprietary manifest members section to discourage vendor prefixing. (PR #1073)

@marcoscaceres commented on this pull request.



> +            it can do so, but with care.
+          </p>
+          <p>
+            We encourage implementors adding proprietary extensions to consider
+            whether they could become a standard (i.e. if it would make sense
+            for a second user agent on a different platform to make use of that
+            member, even if no other user agent has expressed interest right
+            now). If so, we ask authors to design the API in a vendor-neutral
+            way, and propose it as a standard (see [[[#incubations]]]). If the
+            new member is truly proprietary (i.e. will only ever make sense in
+            the context of a proprietary ecosystem), use this process, and
+            prefix it with the short name of that proprietary ecosystem to avoid
+            name collisions.
+          </p>
+          <p>
+            Do not use vendor prefixes which you intend to later remove once it

```suggestion
            Do not use vendor prefixes that you intend to later remove once it
```

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/pull/1073#pullrequestreview-1364120176
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/pull/1073/review/1364120176@github.com>