- From: Mercurial notifier <cvsmail@w3.org>
- Date: Fri, 27 Jul 2012 11:44:11 +0000
- To: public-dap-commits@w3.org
changeset: 175:f23f7e1c5b53
tag: tip
user: norifumi kikkawa <norifumi.kikkawa@jp.sony.com>
date: Fri Jul 27 20:30:32 2012 +0900
files: wi-addendum-local-services/Overview.html
description:
added definitions for mDNS and DNS-SD
diff -r a2ae4ee687a1 -r f23f7e1c5b53 wi-addendum-local-services/Overview.html
--- a/wi-addendum-local-services/Overview.html Wed Jul 25 13:27:10 2012 +0900
+++ b/wi-addendum-local-services/Overview.html Fri Jul 27 20:30:32 2012 +0900
@@ -15,7 +15,7 @@
specStatus: "ED",
// the specification's short name, as in http://www.w3.org/TR/short-name/
- shortName: "Web Intents-UPnP addendum",
+ shortName: "Web Intents-LD addendum",
// if your specification has a subtitle that goes below the main
// formal title, define it here
@@ -149,6 +149,10 @@
stated in this specification. </li>
<li><dfn>Web Intents enabled UPnP device</dfn>: A <a>Web Intents enabled UPnP device</a> MUST support [[!UPNP-DEVICEARCH]] and the conformance criteria
stated in this specification. </li>
+ <li><dfn>mDNS enabled User Agent</dfn>: A <a>mDNS enabled User Agent</a> MUST support Web Intents [[!WEBINTENTS]] and the conformance criteria
+ stated in this specification. </li>
+ <li><dfn>Web Intents enabled mDNS device</dfn>: A <a>Web Intents enabled mDNS device</a> MUST support [[!DNS-SD]] and the conformance criteria
+ stated in this specification. </li>
</ul>
<p>
@@ -170,8 +174,14 @@
<dt>Web Intents</dt>
<dd>This addendum specification is dependent on and defines optional extensions to the basic Web Intents specification, [[!WEBINTENTS]]. </dd>
<dt>UPnP Device Architecture 1.0</dt>
- <dd>This addendum specification is dependent on and defines vendor specific extensions to the UPnP Device Architecture 1.0 specification, [[!UPNP-DEVICEARCH]] </dd>
- </dl>
+ <dd>This addendum specification is dependent on and defines vendor specific extensions to the UPnP Device Architecture 1.0 specification, [[!UPNP-DEVICEARCH]]. </dd>
+ <dt>IANA Service Name and Transport Protocol Port Number Registry</dt>
+ <dd>This addendum specification adds new entry on it, [[!IANA-SRVPORT-REG]]. </dd>
+ <dt>DNS-SD</dt>
+ <dd>This addendum specification is dependent on it, [[!DNS-SD]]. </dd>
+ <dt>mDNS</dt>
+ <dd>This addendum specification assumes the use of it in typical cases but does not dependent on it strictly, [[!MDNS]]. </dd>
+ </dl>
</p>
</section>
@@ -199,8 +209,11 @@
<section>
<h3>mDNS related terms</h3>
<p>
- TBD...
+ The <a>mDNS enabled User Agent</a> has the role of a <dfn id="dfn-registration">DNS client</dfn> with capability of DNS-SD.
</p>
+ <p>
+ The <a>Web Intents enabled mDNS device</a> discovered by the <a>mDNS enabled User Agent</a> has the roles of <dfn id="dfn-registration">service</dfn> according to mDNS and DNS-SD.
+ </p>
</section>
@@ -459,16 +472,80 @@
<section>
- <h2>mDNS adaptation</h2>
+ <h2>mDNS (DNS-SD) adaptation</h2>
<p>
+ This section describes how the User Agent handles Web Intents Services provided by local devices supporting mDNS and DNS-SD.
+ </p>
+
+ <section>
- This section describes how the User Agent handles Web Intents Services provided by local devices supporting mDNS.
- </p>
+ <h3>Web Intents enabled mDNS device</h3>
+
+ <p>
+ The <a>Web Intents enabled mDNS device</a> <em class="rfc2119" title="must">must</em> support this section.
+ </p>
+
+ <section>
+
+ <h4>Web Intents service type for DNS-SD</h4>
+
+ <p>
+ The <a>Web Intents enabled mDNS device</a> <em class="rfc2119" title="must">must</em> support DNS-SD with a SRV record of the <code>webintents</code> service type.
+ </p>
+
+ <p class="note">
+ A service type <code>webintents</code> should be registered in IANA (http://www.iana.org/form/ports-services).
+ </p>
+
+ <p>
+ The TXT record for the <code>webintents</code> service must have following parameters:
+ </p>
+ <ul>
+ <li>
+ <code>location</code>: <em class="rfc2119" title="required">required</em>. States the location to the Web Intents document in the <a class="internalDFN" href="#dfn-web-intents-enabled-mdns-device">Web Intents enabled mDNS device</a>.
+ The value of this header is path to be concatinated with a host of the <a class="internalDFN" href="#dfn-web-intents-enabled-mdns-device">Web Intents enabled mDNS device</a> to determine the location. The definition of the Web Intents document is same as that for UPnP.
+ </li>
+ <li>
+ <code>action</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> <br>
+ This allows the <a>mDNS enabled User Agent</a> to filter received mDNS messages so that the <a>mDNS enabled User Agent</a>s only have to
+ retrieve Web Intents documents for matching Web Intents Actions.
+ </li>
+ </ul>
+
+ </section>
+
+ <section class="informative">
+ <h3>Sample Records</h3>
+
+ <p>
+ See below for the example records for Web Intents. A <a>mDNS enabled User Agent</a> looking for devices supporting http://webintents.org/view Web Intents can understand that
+ it is possible to get a Web Intents document for "LivingRoomTV" at http://192.168.1.47:3619/webntents.html.
+ </p>
+
+ <ul>
+ <li>
+ <code>_webintents._tcp.local. 120 IN PTR LivingRoomTV._webintents._tcp.local.</code>: A LivingRoomTV instance serves webintents service.
+ </li>
+ <li>
+ <code>LivingRoomTV._webintents._tcp.local. 120 IN SRV 0 0 3619 TV40EX-W2000.local.</code>: A host "TV40EX-W2000" in the link local network offers the LivingRoomTV webintents service instance in its port 3619.
+ </li>
+ <li>
+ <code>LivingRoomTV._webintents._tcp.local. 120 IN TXT location=/webintents.html action=http://webintents.org/view</code>: It offers http://webintents.org/view type of Web Intents. The absolete path for its Web Intents document is "/webintents.html". Note that the actual binary format of the TXT record value is concatinating key-value pairs each of which is a single byte length followed by 0-255 length key=value character string as defined in [DNS-SD].
+ </li>
+ <li>
+ <code>TV40EX-W2000 120 IN A 192.168.1.47</code>: A host "TV40EX-W2000" is on 192.168.1.47.
+ </li>
+ </ul>
+
+ </section>
- <p>
- TBD....
- </p>
</section>
Received on Friday, 27 July 2012 11:44:17 UTC