Re: [push-api] Move to using just endpoint (#129)

> -          <a>application server</a> through the webapp. For example, the
> -          <code>subscriptionId</code> may be used as a push service API request parameter or
> -          request body element.
> -          </li>
> -          <li>As a URI, the <code>endpoint</code> of a <code>PushSubscription</code> provides a
> -          flexible means for push services to deliver webapp-specific subscription and/or push
> -          service API parameters to the <a>application server</a>, through the webapp.
> -          </li>
> -        </ul>
> -        <p>
> -          Push services that are compatible with the Push API will be expected to clarify how these
> -          data are used in their APIs, e.g. through their developer programs. Examples of
> -          considerations include:
> +          The fields included in the <code>PushSubscription</code> is all the information needed for
> +          an <a>application server</a> to send a <a>push message</a>. Push services that are
> +          compatible with the Push API will be expected to provide an <a>endpoint</a> that conforms

Detailed definition of the endpoint should really go in the concepts section, or the dependencies section if it is defined in the IETF spec.

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