discovery-api/Overview.src.html
changeset 182 595192a920a0
parent 181 a66764a2345e
child 183 21b44409354f
     1.1 --- a/discovery-api/Overview.src.html	Fri Aug 03 15:16:38 2012 +0200
     1.2 +++ b/discovery-api/Overview.src.html	Fri Aug 03 15:44:17 2012 +0200
     1.3 @@ -380,7 +380,7 @@
     1.4      <script src="tools/syntaxhighlighter/js/shBrushXml.js" type="text/javascript" class='remove'></script>
     1.5      <script src="tools/syntaxhighlighter/js/shBrushJScript.js" type="text/javascript" class='remove'></script>
     1.6  
     1.7 -    <script src='./js/profiles/w3c-common-loader.js' type="text/javascript" class='remove'></script>
     1.8 +    <script src='http://www.w3.org/Tools/respec/respec-w3c-common' type="text/javascript" class='remove' async></script>
     1.9      <style type="text/css">
    1.10        /* Custom CSS optimizations (Richard Tibbett) */
    1.11  
    1.12 @@ -555,7 +555,7 @@
    1.13  
    1.14        <p>
    1.15           The term DOM is used to refer to the API set made available to scripts in Web applications, and does not necessarily imply the existence of an actual <code>Document</code> object or of any
    1.16 -         other <code>Node</code> objects as defined in the DOM Core specifications. [[!DOM-CORE]]
    1.17 +         other <code>Node</code> objects as defined in the DOM Core specifications. [[!DOM4]]
    1.18        </p>
    1.19  
    1.20        <p>
    1.21 @@ -1257,7 +1257,7 @@
    1.22        </table>
    1.23  
    1.24        <p>
    1.25 -         Events with an event type of <code>message</code> defined in this specification are <a href="http://dev.w3.org/html5/postmsg/#messageevent" class="externalDFN"><code>MessageEvent</code></a> objects as defined in [[!WEBMESSAGING]].
    1.26 +         Events with an event type of <code>message</code> defined in this specification are <a href="http://dev.w3.org/html5/postmsg/#messageevent" class="externalDFN"><code>MessageEvent</code></a> objects as defined in [[!POSTMSG]].
    1.27        </p>
    1.28  
    1.29        <p>
    1.30 @@ -1271,7 +1271,7 @@
    1.31              <h2>Service Discovery</h2>
    1.32  
    1.33        <p>
    1.34 -         A <a>user agent</a> conforming to this specification MAY implement <acronym title="Simple Service Discovery Protocol">SSDP</acronym> [[!UPNP]] and Zeroconf [[!ZEROCONF]] service discovery mechanisms
    1.35 +         A <a>user agent</a> conforming to this specification MAY implement <acronym title="Simple Service Discovery Protocol">SSDP</acronym> [[!UPNP-DEVICEARCH11]] and Zeroconf [[!ZEROCONF]] service discovery mechanisms
    1.36           to enable Web pages to request and connect with HTTP services running on networked devices, discovered via either mechanism, through this API. When a <a>user agent</a> implements either of these service discovery mechanisms, then it MUST conform to the corresponding algorithms provided in this section of the specification.
    1.37        </p>
    1.38        <p>
    1.39 @@ -1370,7 +1370,7 @@
    1.40           <h5>Universal Plug-and-Play (<acronym title="Universal Plug-and-Play">UPnP</acronym>)</h5>
    1.41  
    1.42           <p>
    1.43 -            For each SSDP Presence Announcement [[!UPNP]] - a HTTP NOTIFY request - received from a user-agent-initiated SSDP Discovery Request [[!UPNP]], the <a>user agent</a> MUST run the following steps:
    1.44 +            For each SSDP Presence Announcement [[!UPNP-DEVICEARCH11]] - a HTTP NOTIFY request - received from a user-agent-initiated SSDP Discovery Request [[!UPNP-DEVICEARCH11]], the <a>user agent</a> MUST run the following steps:
    1.45           </p>
    1.46  
    1.47           <ol class="rule">
    1.48 @@ -1389,7 +1389,7 @@
    1.49  
    1.50              <li>
    1.51                 Let <var>root device descriptor file</var> contain the contents of the file located at the URL provided in the first occurrence of <var>Location</var> obtained according to the rules
    1.52 -               defined in the section 'Retrieving a description using HTTP' [[!UPNP]].
    1.53 +               defined in the section 'Retrieving a description using HTTP' [[!UPNP-DEVICEARCH11]].
    1.54              </li>
    1.55  
    1.56              <li>
    1.57 @@ -1398,7 +1398,7 @@
    1.58  
    1.59              <li>
    1.60                 Let <var>advertised services</var> be a <a>list of all advertised services</a> obtained from the <var>root device descriptor file</var> containing all sub-nodes of the <code>serviceList</code> node as described in
    1.61 -               the section 'Device Description' [[!UPNP]].
    1.62 +               the section 'Device Description' [[!UPNP-DEVICEARCH11]].
    1.63              </li>
    1.64  
    1.65              <li>
    1.66 @@ -1542,7 +1542,7 @@
    1.67                             Let <var>content clone</var> be the result of obtaining the message body of the HTTP NOTIFY request. If <var>content clone</var> is empty, then the <a>user agent</a> MUST abort these steps.
    1.68                          </li>
    1.69                          <li>
    1.70 -                          Create a new <code>message</code> event that uses the <a href="http://dev.w3.org/html5/postmsg/#messageevent" class="externalDFN"><code>MessageEvent</code></a> interface [[!WEBMESSAGING]], with the name <code>message</code>,
    1.71 +                          Create a new <code>message</code> event that uses the <a href="http://dev.w3.org/html5/postmsg/#messageevent" class="externalDFN"><code>MessageEvent</code></a> interface [[!POSTMSG]], with the name <code>message</code>,
    1.72                             which does not bubble, is not cancelable, and has no default action.
    1.73                          </li>
    1.74                          <li>