W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2014

Re: [push] Consider renaming "push notification" to "push message" in the Push API spec

From: SULLIVAN, BRYAN L <bs3131@att.com>
Date: Thu, 13 Mar 2014 08:57:03 +0000
To: Jeffrey Yasskin <jyasskin@google.com>
CC: "public-webapps@w3.org" <public-webapps@w3.org>
Message-ID: <B318A211-58BA-4B2A-A934-9ACD7A206E0B@att.com>
I agree, Push Message is the term that is used in other standards e.g. OMA Push. The use of the term notification was a reflection of the current simplified API design which provides only a trigger to the application, as a "notification" that some data is available at the server. As we consider the introduction of an optional payload into the API, the term Push Message becomes more appropriate.

Thanks,
Bryan Sullivan

On Mar 10, 2014, at 11:23 PM, "Jeffrey Yasskin" <jyasskin@google.com<mailto:jyasskin@google.com>> wrote:

The term "push notification" in
https://dvcs.w3.org/hg/push/raw-file/tip/index.html#dfn-push-notification
seems to confuse people into thinking that the user will be
notified/bothered when such a message arrives. This is reinforced by
the fact that iOS uses "push notification" for exactly that: a way to
notify the user based on a message from a server. See
https://developer.apple.com/library/ios/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/Chapters/WhatAreRemoteNotif.html.

Since the spec already uses the name "PushMessage" for the thing
delivered by a push notification
(https://dvcs.w3.org/hg/push/raw-file/tip/index.html#pushmessage-interface),
it seems like "push message" would be a good replacement for the
current ambiguous name.

Thanks,
Jeffrey Yasskin

P.S. I'm not subscribed to public-webapps@, so please cc me if you
want me to reply.
Received on Thursday, 13 March 2014 08:57:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:22 UTC