Re: [push-api] Clarify subscription relationships, lifecycle, and uniqueness. (#112)

>        </p>
>        <p>
> -        The term <dfn>push subscription</dfn> refers to each logical channel aimed at delivering
> -        <a title="push message">push messages</a> from an <a>webapp server</a> to a <a>webapp</a>,
> -        which is created by a distinct subscription of such <a>webapp</a> via this Push API.
> +        A <a>push subscription</a> has an associated <dfn>subscription id</dfn>. It is used by the
> +        <a>webapp server</a> to indicate the target of the <a title="push message">push
> +        messages</a> that it submits to the <a>push server</a>. Each pair of <a>subscription id</a>
> +        and <a>endpoint</a> is expected to be globally unique.

I think this can be a MUST. If there are reasonable exceptions that indicate the need for a SHOULD, let's have a separate issue with a discussion for that.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/pull/112/files#r24087014