Binary file wi-addendum-local-services/Example_scenario_1/Slide1.png has changed
Binary file wi-addendum-local-services/Example_scenario_1/Slide2.png has changed
Binary file wi-addendum-local-services/Example_scenario_1/Slide3.png has changed
Binary file wi-addendum-local-services/Example_scenario_2/Slide1.png has changed
Binary file wi-addendum-local-services/Example_scenario_2/Slide2.png has changed
Binary file wi-addendum-local-services/Example_scenario_2/Slide3.png has changed
Binary file wi-addendum-local-services/Example_scenario_2/Slide4.png has changed
--- a/wi-addendum-local-services/Overview.html Fri Oct 05 15:19:00 2012 -0700
+++ b/wi-addendum-local-services/Overview.html Thu Oct 18 13:55:39 2012 +0200
@@ -287,13 +287,28 @@
<li>
<code>action.webintents.org</code>: <em class="rfc2119" title="optional">optional</em>. If supported, states the Web Intents
<code>action</code> of the supported Web Intents Services and <em class="rfc2119" title="must">must</em>
- match the <code>action</code> attributes of the Service registration markup in the Web Intents document. To support more than
- one Web Intents <code>action</code> the action strings <em class="rfc2119" title="must">must</em> be separated with
- comma. Commas included in action strings <em class="rfc2119" title="must">must</em> be percent-encoded as
- defined in [[!RFC3986]], section-2.1.
- <br />
+ match the <code>action</code> attributes of the Service registration markup in the Web Intents document. Each action string
+ <em class="rfc2119" title="must">must</em> be surrounded by double-quotes and if more than one Web Intents action is defined
+ the action strings <em class="rfc2119" title="must">must</em> be separated with comma.
+ <br /> <br />
This header allows the <a>UPnP enabled User Agent</a> to filter received SSDP messages so that the <a>UPnP enabled User Agent</a> only has to
- retrieve Web Intents documents for matching Web Intents Actions.
+ retrieve Web Intents documents for matching Web Intents Actions.
+ <br /> <br />
+ Examples of action.webintents.org headers:
+ <ul>
+ <li>
+ action.webintents.org:"view"
+ </li>
+ <li>
+ action.webintents.org:"http://intents.w3.org/experimental-discover"
+ </li>
+ <li>
+ action.webintents.org:"http://intents.sony.net/local-discover","view"
+ </li>
+ <li>
+ action.webintents.org:"http://intents.w3.org/experimental-discover","http://intents.w3.org/experimental-view"
+ </li>
+ </ul>
</li>
</ul>
@@ -306,7 +321,7 @@
<p>
The <a>Web Intents enabled UPnP device</a> <em class="rfc2119" title="must">must</em> host Web Intents documents for the Web Intents Services the <a>Web Intents enabled UPnP device</a> supports.
Web Intents documents are html pages that contain Web Intents Service registration markup according to the rules for Web Intents Service registration defined
- by [[!WEBINTENTS]]. They may also contain Service handler code for Services registered within the same document.
+ by [[!WEBINTENTS]]. They </a> <em class="rfc2119" title="may">may</em> also contain Service handler code for Services registered within the same document.
</p>
</section>
@@ -375,7 +390,9 @@
<li>
It is expected that the Web Intents document contains registration markup and the <a>UPnP enabled User Agent</a> interprets this
- registration markup according to the rules for registration defined by [[!WEBINTENTS]] and register the Services accordingly.
+ registration markup according to the rules for registration defined by [[!WEBINTENTS]] and register the Services accordingly.
+ The Web Intents document is not displayed to the user and for security reasons it is recommended that the <a>UPnP enabled User Agent</a>
+ during the Service registration process just interprets the registration markup and other related "safe" elements such as favicon.
</li>
<li>
@@ -432,7 +449,9 @@
<li>
It is expected that the Web Intents document contains registration markup and the <a>UPnP enabled User Agent</a> interprets the
- Web Intents document according to the rules for registration defined by [[!WEBINTENTS]] and register the Services accordingly.
+ Web Intents document according to the rules for registration defined by [[!WEBINTENTS]] and register the Services accordingly.
+ The Web Intents document is not displayed to the user and for security reasons it is recommended that the <a>UPnP enabled User Agent</a>
+ during the Service registration process just interprets the registration markup and other related "safe" elements such as favicon.
</li>
<li>
@@ -458,9 +477,7 @@
<h4>Support for Web Intents and UPnP</h4>
<p>
In addition to the normative statements defined in this specification a <a>UPnP enabled User Agent</a> that complies to this specification
- supports Web Intents according to [[!WEBINTENTS]] and UPnP Discovery, Description and Control according to [[!UPNP-DEVICEARCH]].
- However, it is implementation dependent whether this is supported natively in the User Agent or supported through some external component,
- e.g. an in-device web server.
+ supports Web Intents according to [[!WEBINTENTS]] and UPnP Discovery and Description according to [[!UPNP-DEVICEARCH]].
</p>
</section>
@@ -587,7 +604,9 @@
<li>
It is expected that the Web Intents document contains registration markup and the <a>mDNS enabled User Agent</a> interprets this
- registration markup according to the rules for registration defined by [[!WEBINTENTS]] and register the Services accordingly.
+ registration markup according to the rules for registration defined by [[!WEBINTENTS]] and register the Services accordingly.
+ The Web Intents document is not displayed to the user and for security reasons it is recommended that the <a>mDNS enabled User Agent</a>
+ during the Service registration process just interprets the registration markup and other related "safe" elements such as favicon.
</li>
<li>