Client-to-user notification is the API that is made available to a service worker to indicate that data and interactions are pending for the user on this particular device, and that the service is ready to provide them. Subject to the browser's configuration, these notifications may be used to trigger a variety of attention-getting interface elements, including "toast" or "Growl"-style ephemeral windows, ambient notifications (e.g. glowing, hopping, pulsing), or collections (e.g. pull-down notification panels, lists of pending events). These Notifications are constructed to allow the service worker to receive notification when the user indicates interest in one of them, allowing the data presentation or interaction to proceed immediately.

Panel

A user-interface region (typically rectangular) that is temporarily displayed above content and browser chrome; these are used for short-lived interactions that are user-initiated or very important.

Recommend

The user-initiated act of indicating that a piece of web content (typically a URL) should be marked as being of interest to a user. No input other than than the URL is expected. A recommend can be completed with no widget; it has no user interface other than the button, menu bar, or command that indicates "recommend this".

Server-to-client notification

Server-to-client notification is a system by which a service arranges for notifications to be delivered promptly and efficiently to a client. It is not a feature of this proposal, though existing web techniques including WebSockets, Server-sent events, XMLHttpRequest with long polling (or infrequently quick polling) can all be used from service workers. It is expected that a service worker that has received a server-to-client notification will often relay this data into a client-to-user notification.

Service message

A message is a JSON-encoded string that is either sent by the browser to the service worker, or sent by the service worker to the browser. These messages are used to coordinate the display of browser-managed user interface elements and to respond to user and content interactions. See Message Serialization for encoding details.

Service worker

A long-running JavaScript computation environment, managed by the browser and served by a user-specified web address, which acts as a coordination and communication hub for integration between the browser and a web service.

Share

The user-initiated act of sending a piece of web content (typically a URL) with an optional comment, explanation, or other data, to a user address, list of user addresses, social network, or other destination. The details of a share interaction are service-specific and a ShareWidget is required to render the user interface to complete a share.

Sidebar

A vertical rectangle of screen space, positioned to the side of normal browser content in a tabbed browser window, which is stable across brower navigation and tab-focus changes. A sidebar may be minimized, which causes it to be rendered entirely in "above-the-content/not-overlaid-over-content" layout space.

Social service provider

A web service that provides one or more APIs to a browser to enable social features. It is defined to the browser by a structured text file, which tells the browser how to load JavaScript and HTML resources that brings its functions into the browser.

Widget

A user-interface element, created by the browser, which provides a visual region for the display of content produced by the service provider.

Fuente de la revisión

<div class="note">
<p><strong>Note:</strong> A continuación hay algunos puntos destacados donde los enlaces necesitan ser añadirdos en el documento mientras son escritos.</p>
</div>
<p>Para hacer uso de la Social API (si estás escribiendo un nuevo proveedor de servicios sociales o trabajando con un proveedor ya existente), hay un número de términos que necesitas saber. ¡Este glosario te ayudará!</p>
<dl>
<dt>
Client-to-user notification</dt>
<dd>
Client-to-user notification is the API that is made available to a service worker to indicate that data and interactions are pending for the user on this particular device, and that the service is ready to provide them. Subject to the browser's configuration, these notifications may be used to trigger a variety of attention-getting interface elements, including "toast" or "Growl"-style ephemeral windows, ambient notifications (e.g. glowing, hopping, pulsing), or collections (e.g. pull-down notification panels, lists of pending events). These Notifications are constructed to allow the service worker to receive notification when the user indicates interest in one of them, allowing the data presentation or interaction to proceed immediately.</dd>
<dt>
Panel</dt>
<dd>
A user-interface region (typically rectangular) that is temporarily displayed above content and browser chrome; these are used for short-lived interactions that are user-initiated or very important.</dd>
<dt>
Recommend</dt>
<dd>
The user-initiated act of indicating that a piece of web content (typically a URL) should be marked as being of interest to a user. No input other than than the URL is expected. A recommend can be completed with no widget; it has no user interface other than the button, menu bar, or command that indicates "recommend this".</dd>
<dt>
Server-to-client notification</dt>
<dd>
Server-to-client notification is a system by which a service arranges for notifications to be delivered promptly and efficiently to a client. It is not a feature of this proposal, though existing web techniques including <a href="/en-US/docs/WebSockets" title="/en-US/docs/WebSockets">WebSockets</a>, <a href="/en-US/docs/Server-sent_events" title="/en-US/docs/Server-sent_events">Server-sent events</a>, <code><a href="/en-US/docs/DOM/XMLHttpRequest" title="/en-US/docs/DOM/XMLHttpRequest">XMLHttpRequest</a></code> with long polling (or infrequently quick polling) can all be used from service workers. It is expected that a service worker that has received a server-to-client notification will often relay this data into a client-to-user notification.</dd>
<dt>
Service message</dt>
<dd>
A message is a <a href="/en-US/docs/JSON" title="/en-US/docs/JSON">JSON</a>-encoded string that is either sent by the browser to the service worker, or sent by the service worker to the browser. These messages are used to coordinate the display of browser-managed user interface elements and to respond to user and content interactions. See <span style="color:#ffff00;"><span style="background-color: rgb(255, 0, 0);">Message Serialization</span></span> for encoding details.</dd>
<dt>
Service worker</dt>
<dd>
A long-running JavaScript computation environment, managed by the browser and served by a user-specified web address, which acts as a coordination and communication hub for integration between the browser and a web service.</dd>
<dt>
Share</dt>
<dd>
The user-initiated act of sending a piece of web content (typically a URL) with an optional comment, explanation, or other data, to a user address, list of user addresses, social network, or other destination. The details of a share interaction are service-specific and a <span style="color:#ffff00;"><code><span style="background-color: rgb(255, 0, 0);">ShareWidget</span></code></span> is required to render the user interface to complete a share.</dd>
<dt>
Sidebar</dt>
<dd>
A vertical rectangle of screen space, positioned to the side of normal browser content in a tabbed browser window, which is stable across brower navigation and tab-focus changes. A sidebar may be minimized, which causes it to be rendered entirely in "above-the-content/not-overlaid-over-content" layout space.</dd>
<dt>
Social service provider</dt>
<dd>
A web service that provides one or more APIs to a browser to enable social features. It is defined to the browser by a structured text file, which tells the browser how to load JavaScript and HTML resources that brings its functions into the browser.</dd>
<dt>
Widget</dt>
<dd>
A user-interface element, created by the browser, which provides a visual region for the display of content produced by the service provider.</dd>
</dl>