--- a/hnreq/hnreq.html Tue Nov 22 16:17:28 2011 +0100
+++ b/hnreq/hnreq.html Tue Nov 22 16:53:35 2011 +0100
@@ -65,7 +65,7 @@
<p>In all use cases, security mechanisms are made available to protect user privacy and content owners’ rights.</p>
- <p>There is currently no formally standardized way to build a web application that is able to use content discovery and control protocols to get access to the content available on different devices in the home network. This document lists the design goals and requirements that future W3C recommendations need to address in order to cover such gap. This would enable content providers to deliver web applications to any conforming device in order to enhance and harmonize the user experience.</p>
+ <p>There is no standardized way to build a web application that can use content discovery and control protocols to access the content on other devices in the home network. This document lists the design goals and requirements that future W3C recommendations need to address in order to address this problem. This would enable content providers to deliver web applications to any conforming device in order to enhance and harmonize the user experience.</p>
</section>
<section>
@@ -94,7 +94,7 @@
<dd>A <a>device</a> that presents <a>programme</a> content from a variety of sources - such as received via broadcast (cable, satellite, terrestrial), on-demand streaming services, or streamed from other devices in the home (e.g. PVR). Within the scope of this document, it is presumed that a television is connected to the <a>home network</a>.</dd>
<dt><dfn>service</dfn></dt>
- <dd>For the purposes of this document, a service is any functionality available on a <a>device</a>, such as the ability to play back audio/video content, record content, print documents, etc.</dd>
+ <dd>For the purposes of this document, a service is any functionality available on a <a>device</a>, such as the ability to play back audio/video content, record content and print documents</dd>
<dt><dfn>document</dfn></dt>
<dd>An individual resource that adheres to a certain content type, ranging from short static documents to long essays or reports with rich multimedia. For simplicity, terms such as shown, displayed, and visible might sometimes be used when referring to the way a document is rendered to the user. These terms are not meant to imply a visual medium; they must be considered to apply to other media in equivalent ways.</dd>
@@ -132,7 +132,7 @@
<section>
<h4>Compatibility with widely deployed standards</h4>
- <p>Several home network protocols (e.g. UPnP, M-DNS/DNS-SD) are in popular use today for advertising and sharing content and services in a home network environment. <a>Conforming specifications</a> SHALL set out requirements for an API that would enable interaction with those protocols.</p>
+ <p>Several home network protocols (e.g. UPnP and M-DNS/DNS-SD) are in popular use today for advertising and sharing content and services in a home network environment. <a>Conforming specifications</a> SHALL set out requirements for an API that would enable interaction with those protocols.</p>
</section>
</section>
@@ -156,12 +156,12 @@
<section>
<h4>Content Advertisement</h4>
- <p><a>Conforming specifications</a> SHOULD provide a means for application to expose content description to a service on the home network. Other devices or applications on the home network should be able to playback the content served by the application and retrieve additional metadata about the served content.</p>
+ <p><a>Conforming specifications</a> SHOULD provide a means for applications to expose content descriptions to a service on the home network. Other devices or applications on the home network should be able to play back the content served by the application and retrieve additional metadata about the served content.</p>
</section>
<section>
<h4>Services Advertisement</h4>
- <p><a>Conforming specifications</a> SHOULD provide a means for application to expose and advertise services on the home network.</p>
+ <p><a>Conforming specifications</a> SHOULD provide a means for applications to expose and advertise services on the home network.</p>
</section>
<section>
@@ -193,12 +193,12 @@
<section>
<h4>Playback of Content</h4>
- <p><a>Conforming specifications</a> SHOULD provide a means to playback content advertised by a home network content server.</p>
+ <p><a>Conforming specifications</a> SHOULD provide a means to play back content advertised by a home network content server.</p>
</section>
<section>
<h4>Playback of Live Content</h4>
- <p><a>Conforming specifications</a> SHOULD provide a means to playback live content advertised by a home network content server.</p>
+ <p><a>Conforming specifications</a> SHOULD provide a means to play back live content advertised by a home network content server.</p>
</section>
<section>
@@ -208,7 +208,7 @@
<section>
<h4>Time-synchronization</h4>
- <p>User-agents SHOULD provide applications with a means to co-time the presentation of their own content (audio, video or other) with the timeline of a programme being played back on another device, including programmes being received via broadcast. <a>Conforming specifications</a> SHOULD provide applications with a means to be aware of the progress (time within the programme) of the playback of media content on a remote device/service, including programmes being received via broadcast.</p>
+ <p><a>Conforming specifications</a> SHOULD provide a means for applications to co-time the presentation of their own content (audio, video or other) with the timeline of a programme being played back on another device, including programmes being received via broadcast. <a>Conforming specifications</a> SHOULD provide applications with a means to be aware of the progress (time within the programme) of the playback of media content on a remote device/service, including programmes being received via broadcast.</p>
</section>
<section>
@@ -228,7 +228,7 @@
<section>
<h4>Content Protection</h4>
- <p><a>Conforming specifications</a> SHOULD support the content protection mechanism for a content item used by a content server in order to playback that content item. <a>Conforming specifications</a> MUST provide a graceful failure model when a content protection mechanism is not supported.</p>
+ <p><a>Conforming specifications</a> SHOULD support the content protection mechanism for a content item used by a content server in order to play back that content item. <a>Conforming specifications</a> MUST provide a graceful failure model when a content protection mechanism is not supported.</p>
</section>
</section>