- From: WonSuk Lee via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 02 Nov 2010 16:41:51 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/app-launcher
In directory hutz:/tmp/cvs-serv30913/2009/dap/app-launcher
Modified Files:
Overview.html
Log Message:
first draft
Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/app-launcher/Overview.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- Overview.html 14 Sep 2009 15:36:05 -0000 1.2
+++ Overview.html 2 Nov 2010 16:41:49 -0000 1.3
@@ -1,55 +1,525 @@
<!DOCTYPE html>
<html>
- <head>
- <title>The Application Launcher API</title>
- <meta http-equiv='Content-Type' content='text/html;charset=utf-8'/>
- <script src='../ReSpec.js/js/simple-node.js' class='remove'></script>
- <script src='../ReSpec.js/js/shortcut.js' class='remove'></script>
- <script src='../ReSpec.js/js/respec.js' class='remove'></script>
- <script src='../ReSpec.js/bibref/biblio.js' class='remove'></script>
- <script class='remove'>
+<head>
+
+ <title>The Application Launcher API</title>
+ <meta http-equiv="content-type" content="text/html; charset=UTF-8" />
+
+ <script src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>
+ <script class="remove">
var respecConfig = {
- specStatus: "ED",
- shortName: "app-launcher-api",
- // publishDate: "2009-08-06",
+ specStatus: "ED",
+ shortName: "app-launcher",
+ editors: [
+ {name: "이강찬(Kangchan Lee)", company: "ETRI", companyURL: "http://www.etri.re.kr/"},
+ {name: "이원석(Wonsuk Lee)", company: "ETRI", companyURL: "http://www.etri.re.kr/"},
+ {name: "Bryan Sullivan", company: "AT&T", companyURL: "http://att.com/"}
+ ],
+ publishDate: "2010-11-02",
// previousPublishDate: "1977-03-15",
edDraftURI: "http://dev.w3.org/2009/dap/app-launcher/",
// lcEnd: "2009-08-05",
};
- </script>
- <script src='../common/config.js' class='remove'></script>
- </head>
- <body>
- <section id='abstract'>
- This is the abstract for your specification.
- </section>
-
- <section id='conformance'></section>
-
- <section>
- <h2>Requirements</h2>
- <p>
- ...
- </p>
- </section>
-
- <section class='appendix'>
- <h2>Features for Future Consideration</h2>
+
+ respecConfig.wg = "Device APIs and Policy Working Group";
+ respecConfig.wgURI = "http://www.w3.org/2009/dap/";
+ respecConfig.wgPublicList = "public-device-apis";
+ respecConfig.wgPatentURI = "http://www.w3.org/2004/01/pp-impl/43696/status";
+
+ </script>
+
+ <link rel="stylesheet" href="http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css" type="text/css" media="screen" />
+</head>
+
+
+
+<body>
+
+<section id="abstract">
+ <p>This specification defines an Application Programming Interface (<acronym
+ title="Application Programming Interface">API</acronym>) for that provides lauching application in device. </p>
+</section>
+
+<section id="sotd">
+ <p>This document represents the early consensus of the group on the scope and features of the proposed Application launcher
+ <acronym title="Application Programming Interface">API</acronym>. Issues and
+ editors note in the document highlight some of the points on which the group is still working and would particularly like to get
+ feedback.
+ </p>
+</section>
+
+<section id="conformance">
+</section>
+
+<section class="informative">
+
+ <h2>Introduction</h2>
+ <p>W3C application launcher <acronym title="Application Programming Interface">API</acronym> provides interface for invoking the native applications
+ such as messaging, telephony and installed applications. An installed native application can be launched based on scheme of the standard URI
+ Generic Syntax [[!URI]]. The following example URIs illustrate several URI schemes for application laucher <acronym
+ title="Application Programming Interface">API</acronym>.
+ <dl>
+ <dt>http(s) : launching installed browser in the device [[!URI]]</dt>
+ <dd><a href="http://www.w3.org/2009/dap/">http://www.w3.org/2009/dap/</a></dd>
+ <dt>mailto: lauching email application [[!URI]][RFC6068]</dt>
+ <dd><a href="mailto:chan@w3.org">mailto:chan@w3.org</a>, <a href="mailto:chan@w3.org?subject=test">mailto:chan@w3.org?subject=test</a> </dd>
+ <dt>tel: launching telephony application [[!URI]][RFC3966]</dt>
+ <dd><a href="tel:+82-123-456-789">tel:+82-123-456-789</a></dd>
+ <dt>sms: launching SMS application [RFC5724]</dt>
+ <dd><a href="sms:+82-123-456-789">sms:+82-123-456-789</a></dd>
+ </dl>
+ </p>
+
+ <p class="note">Need to clarification.
+ What is the minimum supported URI scheme and their native applications?
+ <a href="http://www.openmobilealliance.org/Technical/release_program/docs/URI_Schemes/V1_0-20080626-A/OMA-TS-URI_Schemes-V1_0-20080626-A.pdf">mmsto, sip</a>, file, and etc .
+ </p>
+</section>
+
+<section class="Use_cases_and_requirements">
+ <h2>Use Cases and Requirements</h2>
+ <section class="Use_cases">
+ <h2>Use Cases</h2>
+ <p>
+ <h4 id='uc1'>Use Case 1: Launching the device browser (URI base Application Launching using http URI scheme)</h4>
+ A Web application needs to launch the device browser in order to provide a "full browser experience" for
+ a website. Without the ability to explicitly launch the browser
+ (through a URI scheme e.g. http:// or https://),
+ all the Web application can do is to load the website content directly, if it can access it.
+ This may prevent the intended user experience, e.g. the launching of a browser session with
+ a content storefront link.
+ </p>
+ <p>
+ <h4 id='uc2'>Use Case 2: Launching a dialer for a phone call (URI base Application Launching using other URI scheme)</h4>
+ Web applications, such as one in a social network service, would provide personal contact information
+ such as phone numbers or email addresses. The user of the Web application gives a call to
+ his/her friends by clicking a phone number in the contact information. Using an appropriate application launcher API, a web application
+ invokes a device dialer with a standardized URI(e.g. tel:, sms:). The device dialer
+ would be invoked with the given phone number so that the user can call
+ his/her friend by just clicking a call button.
+ </p>
+ <p>
+ <h4 id='uc3'>Use Case 3: Launching an application to open document files (URI base Application Launching with MIME type)</h4>
+ A web application would open document files(e.g. doc, pdf format) with a specific
+ viewer or text editor. The web application invokes a native application to open
+ a file using an application launcher API.
+ </p>
+ <p>
+ <h4 id='uc4'>Use Case 4: Setting default application (Management functionality for Application Launching)</h4>
+ An application is designed to work best with a particular browser, e.g. some Web resources to be invoked through the browser need a feature set supported by the particular browser. The application can find out what browsers are installed on the device, and set the default browser to use for links that launch the external browser, e.g. anchor elements with trget "_blank" or window.open methods.
+ </p>
+
+ <p>
+ <h4 id='uc5'>Use Case 5: Using a web application as a home launcher (External Application Launching)</h4>
+ Using an application launcher API, a web application would launch a native application without the need to specifying URI
+ or mime type. Once a web application fetches applications installed on a device, it displays the list of applications. User can start an application just by clicking the icon
+ of the application.
+ </p>
+ <p>
+ <h4 id='uc6'>Use Case 6: Find/retrieve applications on the device (Management functionality for Application Launching)</h4>
+ Using an application launcher API, a web application would check whether a specific application is installed on the device.
+ </p>
+
+
+ </section>
+
+ <section class="requirements">
+ <h2>Requirements</h2>
+ <p class="note">Need to develop the more requirements based on Use Cases.</p>
+
<p>
- This is a list of features that have been discussed with respect to this version of the
- API but for which it has been decided that if they are included it will be in a future
- revision.
+ The following requirements for application launcher <acronym title="Application Programming Interface">API</acronym> have been expressed.
+ The requirements for this set of interfaces may moved in the Device API Requirements document [[DAP-REQS]].
+
</p>
+
<ul>
- <li>...</li>
+ <li>It SHOULD be possible to pass arguments to a launched application.</li>
+ <li>It MAY be possible to change the default application for a given mime type.</li>
+ <li>It MAY be possible to get the default application for a given mime type.</li>
+ </ul>
+
+ <!--
+ <li>A User Agent MAY provide means for non-web applications to register themselves as handlers for
+ media types and URI schemes. (Note that this may be outside the scope of this API.)</li>
+ <li>It SHOULD be possible to launch an application for which no media type or protocol handler exists.</li>
+ <li>It SHOULD be possible to launch an application asynchronously.</li>
+ <li>It SHOULD be possible to launch an application synchronously.</li>
+ <li>It SHOULD be possible to retrieve applications installed on the device.</li>
+ <li>It SHOULD be possible to execute the non-web applications with the least information(e.g., application id, name).</li>
+
+ <li>For applications that run synchronously, it SHOULD be possible to catch the output streams (STDOUT/ERR etc.).</li>
</ul>
- </section>
-
- <section class='appendix'>
- <h2>Acknowledgements</h2>
<p>
- ...
+ The following requirements, while they could be considered to be functionally part of this API,
+ are already addressed as part of the HTML5 [[HTML5]]
+ <a href='http://www.w3.org/TR/html5/browsers.html#custom-handlers'>Custom scheme and content handlers</a>:
</p>
- </section>
- </body>
+ <ul>
+ <li>This interface MUST enable (web) applications to register themselves as handlers for a specific protocol.</li>
+ <li>A User Agent MAY provide default handlers for a specific protocol.</li>
+ <li>This interface MUST enable (web) applications to register themselves as handlers for a specific media type.</li>
+ <li>A User Agent MAY provide default handlers for a specific media type.</li>
+ -->
+ </section>
+</section>
+
+<section>
+<h2>Usage Examples</h2>
+ <p>The following code extracts illustrate how to work with a application launcher <acronym title="Application Programming Interface">API</acronym>
+ in the device: </p>
+
+ <p class="note">Further examples are required to give better understanding concerning
+ the overall functions of the application launcher API. </p>
+
+ <div>
+ <p>Define the success and error callback, and get the default application for application/pdf mime type, change the default application of it,
+ and launch application.</p>
+
+ <pre class="example sh_javascript_dom">
+// Define the success callback for the getDefaultApplication method.
+function appSuccessCB(applications) {
+ //do something with resulting applications
+ for(var i in application) alert(navigator.service.applicationManager.isDefaultApplication(application[i]);
+ //...
+}
+
+// Define the success callback for the setDefaultApplication method
+function defaultAppSuccessCB(response) {
+ alert( "The default application has successfully changed");
+}
+
+// Define the error callback.
+function appErrorCB(response) {
+ alert( "The following error: " + response.code + ", occurred launching an application");
+}
+
+// Get the default application for the application/pdf mime type.
+navigator.service.applicationManager.getDefaultApplication('application/pdf', appSuccessCB, appErrorCB);
+
+// Change the default application for the application/pdf mime type.
+navigator.service.applicationManager.setDefaultApplication('application/pdf', defaultAppSuccessCB, appErrorCB);
+
+// Define the data object
+var data = navigator.service.applicationManager.createData(uri:'http://www.w3.org/2009/dap/applauncher.pdf',
+ mimeType:'application/pdf'});
+
+// launch an application
+navigator.service.applicationLauncher.launchApplication(data, appErrorCB);
+ </code></pre>
+
+ <!--
+ <pre class='example sh_javascript_dom'>
+// Define the success callback.
+function appSuccessCB(applications) {
+ //do something with resulting applications
+ for(var i in applications) alert(applications[i].name);
+ //...
+}
+
+// Define the error callback.
+function appErrorCB(response) {
+ alert( "The following error: " + response.code + ", occurred retrieving an applications");
+}
+
+// retrieve applications on the device
+navigator.service.applicationManager.getInstalledApplications(appSuccessCB, appErrorCB);
+
+// launch an application
+navigator.service.applicationLauncher(application,appErrorCB);
+ </pre>
+-->
+ </div>
+
+</section>
+
+<section>
+ <h2>Security and Privacy Considerations</h2>
+ <p class="note">This section is under development.</p>
+
+ <p>The API defined in this specification can be used to launch the application on device. This information can
+potentially compromise user privacy and a conforming implementation of this specification MUST provide a mechanism that protects the user's privacy and
+this mechanism should ensure that such operations MUST be authenticated.
+ </p>
+
+ <section>
+ <h2>Privacy considerations for implementers of Application Launcher API</h2>
+
+ <p>A conforming implementation of this specification MUST provide a mechanism that protects the user's privacy and this mechanism SHOULD ensure that privacy
+information is not revealed without user's informed consent.
+ </p>
+
+ <ul>
+ <!-- <li>Changing default application</li> -->
+ <li>Hijacking Application Launch API parameters such as URI</li>
+ </ul>
+ </section>
+</section>
+
+<section>
+ <h2>API Description</h2>
+ <p class="note">This section is under development.</p>
+
+ <section id="ApplicationLauncher">
+ <h2><code>ApplicationLauncher</code> interface</h2>
+
+ <p>The <code>ApplicationLauncher</code> interface offers methods concerned with launching applications on the device.</p>
+
+ <dl title="[NoInterfaceObject] interface ApplicationLauncher" class="idl">
+ <dt>PendingOp launchApplication () </dt>
+ <dd>Launches a native application installed in the local device with URI and mime type of the data.
+ <dl class="parameters">
+ <dt>Data data</dt>
+ <dd>An object containing the URI and mime type of the data</dd>
+ <dt>optional AppErrorCB? appErrorCB</dt>
+ <dd>Function to call when the asynchronous operation fails</dd>
+ </dl>
+ </dd>
+ <dt>PendingOp launchApplication () </dt>
+ <dd>Launches a native application installed in the local device with the information of the application.
+ <dl class="parameters">
+ <dt>Application application</dt>
+ <dd>An object containing the least information of the native application</dd>
+ <dt>optional AppErrorCB? appErrorCB</dt>
+ <dd>Function to call when the asynchronous operation fails</dd>
+ </dl>
+ </dd>
+ </dl>
+ </section>
+
+ <section id="Data">
+ <h2><code>Data</code> interface</h2>
+
+ <p>The <code>Data</code> interface contains URI and mime type of the data.</p>
+
+ <dl title="[NoInterfaceObject] interface Data" class="idl">
+ <dt>attribute DOMString uri</dt>
+ <dd>URI of the data</dd>
+ <dt>attribute DOMString mimeType</dt>
+ <dd>Mime type of the data</dd>
+ </dl>
+ </section>
+
+<section id="Application">
+ <h2><code>Application</code> interface</h2>
+
+ <p>The <code>Application</code> interface captures various information of the application which is installed on the device.</p>
+
+ <dl title="[NoInterfaceObject] interface Application" class="idl">
+ <dt>readonly attribute DOMString id</dt>
+ <dd>The unique id to specify the application</dd>
+ <dt>attribute DOMString name</dt>
+ <dd>The name of the application.</dd>
+ <dt>attribute DOMString description</dt>
+ <dd>The description of the application</dd>
+ <dt>attribute DOMString location</dt>
+ <dd>The path that application installed</dd>
+ <dt>attribute DOMString executableFile</dt>
+ <dd>The executable file of the application</dd>
+ <dt>attribute DOMString installedDate</dt>
+ <dd>The date application installed</dd>
+ <dt>attribute DOMString recentUsedDate</dt>
+ <dd>The date application recently used</dd>
+ <dt>attribute unsigned short applicationStatus</dt>
+ <dd>The current application state(e.g., running, background, off)</dd>
+ <dt>attribute unsigned short networkAccessibility</dt>
+ <dd>The network accessibility of the application</dd>
+ <dt>const unsigned short RUNNING = 0;</dt>
+ <dd>The application is running on the device</dd>
+ <dt>const unsigned short BACKGROUND = 1;</dt>
+ <dd>The application is running on the background of the device</dd>
+ <dt>const unsigned short OFF = 2;</dt>
+ <dd>The application is not running on the device</dd>
+ <dt>const unsigned short NOT_USING_NETWORK = 0;</dt>
+ <dd>The application doesn't have authority to access device's network</dd>
+ <dt>const unsigned short WIFI = 1;</dt>
+ <dd>The application is able to access network only for WIFI network</dd>
+ <dt>const unsigned short 3G = 2;</dt>
+ <dd>The application is able to access network only for 3G network</dd>
+ <dt>const unsigned short WIFI_AND_3G = 3;</dt>
+ <dd>The application is able to access network for bot WIFI and 3G network</dd>
+ </dl>
+ </section>
+
+ <section id="ApplicationManager">
+ <h2><code>ApplicationManager</code> interface</h2>
+ <p class="note">setDefaultApplication can cause security problems since the method can affect the configuration of the OS to be changed.
+ </p>
+
+ <!--
+ <p class="issue">The actual object of which the API will be hanging off is still under discussion (e.g. <code>navigator.service</code> vs from
+ <code>navigator.device</code>); see <a href="http://www.w3.org/2009/dap/track/issues/67">ISSUE-67</a></p>
+ -->
+
+ <p>The <code>ApplicationManager</code> interface offers methods that manages application in the device.</p>
+
+ <dl title="[NoInterfaceObject] interface ApplicationManager" class="idl">
+ <dt>Data createData () </dt>
+ <dd>Creates data object that contains URI and mime type of the target data.
+
+ <dl class="parameters">
+ <dt>DOMString uri </dt>
+ <dd>URI of the target data </dd>
+ <dt>DOMString mimeType </dt>
+ <dd>Mime type of the target data </dd>
+ </dl>
+ </dd>
+
+ <dt>PendingOp getInstalledApplications () </dt>
+ <dd>Returns an array of applications containing information of the installed applications on the device.
+ (applications that have somehow been registered in the platform).
+
+ <dl class="parameters">
+ <dt>AppSuccessCB appSuccessCB</dt>
+ <dd>Uses the response object to retrieve the array of strings with the fully qualified path to the application in the terminal file system </dd>
+ <dt>optional AppErrorCB? appErrorCB </dt>
+ <dd>Function called when an error occurs, the input parameter is an Error object with the error code giving information about the type of error that occurred</dd>
+ </dl>
+ </dd>
+
+ <dt>PendingOp findApplications () </dt>
+ <dd>Returns an array of applications that is able to execute given mime type.
+
+ <dl class="parameters">
+ <dt>DOMString mimeType</dt>
+ <dd>Mime type of the data</dd>
+ <dt>AppSuccessCB appSuccessCB</dt>
+ <dd>Function to call when the asynchronous operation completes</dd>
+ <dt>optional AppErrorCB? appErrorCB</dt>
+ <dd>Function to call when the asynchronous operation fails</dd>
+ </dl>
+ </dd>
+
+ <dt>boolean isDefaultApplication () </dt>
+ <dd>Returns true when the application is default application for a given mime type.
+
+ <dl class="parameters">
+ <dt>DOMString mimeType</dt>
+ <dd>Mime type of the data</dd>
+ <dt>Application application</dt>
+ <dd>The object contains information of application</dd>
+ </dl>
+ </dd>
+
+ <dt>PendingOp getDefaultApplication ()</dt>
+ <dd>Retrieves default application for specific mime type.
+
+ <dl class="parameters">
+ <dt>AppSuccessCB appSuccessCB</dt>
+ <dd>Function to call when the asynchronous operation completes</dd>
+ <dt>optional AppErrorCB? appErrorCB</dt>
+ <dd>Function to call when the asynchronous operation fails</dd>
+ </dl>
+ </dd>
+
+ <dt>PendingOp setDefaultApplication () </dt>
+ <dd>Sets application as a default application for specific mime type which is parameter.
+ <dl class="parameters">
+ <dt>DOMString mimeType</dt>
+ <dd>Mime type of the data</dd>
+ <dt>Application application</dt>
+ <dd>The object contains information of application </dd>
+ <dt>optional AppErrorCB? appErrorCB</dt>
+ <dd>Function to call when the asynchronous operation fails</dd>
+ </dl>
+ </dd>
+
+ </dl>
+
+ </section>
+
+ <section id="AppSuccessCB">
+ <h2><code>AppSuccessCB</code> interface</h2>
+ <!--
+ <p class="issue">The actual object of which the API will be hanging off is still under discussion (e.g. <code>navigator.service</code> vs from
+ <code>navigator.device</code>); see <a href="http://www.w3.org/2009/dap/track/issues/67">ISSUE-67</a></p>
+ -->
+
+ <p>The <code>AppSuccessCB</code> lists the applications in the device.</p>
+
+ <dl title="[Callback=FunctionOnly, NoInterfaceObject] interface AppSuccessCB" class="idl">
+ <dt>void onSuccess () </dt>
+ <dd>Success callback that is used in the asynchronous operation to retrieve a list of applications.
+
+ <dl class="parameters">
+ <dt>Application[] applications </dt>
+ <dd>An array containing the list of the information of applications </dd>
+ </dl>
+ </dd>
+ </dl>
+
+ </section>
+ <section id="AppErrorCB">
+ <h2><code>AppErrorCB</code> interface</h2>
+ <!-- interface intro here -->
+
+ <dl title='[Callback=FunctionOnly, NoInterfaceObject] interface AppErrorCB' class='idl'>
+
+ <dt>void onError () </dt>
+ <dd>
+ <!-- interface description here -->
+
+ <dl class='parameters'>
+ <dt>AppErrorCB errorCB</dt>
+ <dd>The Application Launcher API related error object of an unsuccessful asynchronous operation.</dd>
+ </dl>
+ </dd>
+ </dl>
+
+ </section>
+
+ <section>
+ <h2><code>AppError</code> interface</h2>
+ <p class="note">Add Application Launcher API specific error codes...</p>
+ <p>The <code>AppError</code> interface encapsulates all errors in the manipulation of <code>Application</code> objects in the Application Launcher API.</p>
+ <dl title='[NoInterfaceObject] interface AppError' class='idl'>
+ <dt>const unsigned short UNKNOWN_ERROR = 0</dt>
+ <dd>An unknown error occurred.</dd>
+ <dt>const unsigned short INVALID_ARGUMENT_ERROR = 1</dt>
+ <dd>An invalid parameter was provided when the requested method was invoked.</dd>
+ <dt>const unsigned short NOT_FOUND_ERROR = 2</dt>
+ <dd>If no response information can be provided from the requested method. </dd>
+ <dt>const unsigned short TIMEOUT_ERROR = 3</dt>
+ <dd>The requested method timed out before it could be completed.</dd>
+ <dt>const unsigned short IO_ERROR = 5</dt>
+ <dd>An error occurred in communication with the underlying implementation that meant the requested method could not complete. </dd>
+ <dt>const unsigned short NOT_SUPPORTED_ERROR = 6</dt>
+ <dd>The requested method is not supported by the current implementation. </dd>
+ <dt>const unsigned short PERMISSION_DENIED_ERROR = 20</dt>
+ <dd>Access to the requested method was denied at the implementation or by the user. </dd>
+ <dt>const unsigned short PENDING_OPERATION_ERROR = 4</dt>
+ <dd>If the user agent is currently waiting for a callback on a current launchApplication(), getInstalledApplications(), findApplications(), getDefaultApplication(), or setDefaultApplication() operation, as defined in this specification.</dd>
+ <dt>readonly attribute unsigned short code</dt>
+ <dd>An error code assigned by an implementation when an error has occurred in Application Launcher API processing. </dd>
+
+ </dl>
+ </section>
+</section>
+
+<section class=appendix>
+ <h2>Related documents</h2>
+ <p>The API described in this document took inspiration from the following documents:</p>
+ <ul>
+ <li><a href="http://bondi.omtp.org/1.1/apis/applauncher.html" name="BONDI" id="BONDI">The BONDI applauncher Module - Version 1.1</a> </li>
+ <li><a href="http://public.wholesaleappcommunity.com/redmine/embedded/wac2pubrev/core/web-standards.html#toc-uri-schemes ">WAC Waikiki Developer Release Core Specification: Web Standards </a>
+ <li><a href="http://www.iana.org/assignments/uri-schemes.html" name="RFC4395" id="RFC4395">Uniform Resource Identifer (URI) Schemes </a></li>
+ </ul>
+</section>
+
+<section>
+ <h2>Features for Future Consideration</h2>
+ <p>This is a list of features that have been discussed with respect to this version of the API but for which it has been decided that if they are
+ included it will be in a future revision. </p>
+ <ul>
+ <li>...</li>
+ </ul>
+</section>
+
+<section class=appendix>
+ <h2>Acknowledgements</h2>
+ <p>...</p>
+</section>
+
+
+</body>
</html>
Received on Tuesday, 2 November 2010 16:41:54 UTC