ISSUE-281: MWA should disclose their capabilities in HTTP requests, to allow service adaptation

DiscloseCapabilities

MWA should disclose their capabilities in HTTP requests, to allow service adaptation

State:
CLOSED
Product:
Mobile Web Applications Best Practices
Raised by:
Bryan Sullivan
Opened on:
2008-09-26
Description:
The MWABP should make recommendations on the use of Widget interface features and Javascript functions (e.g. XMLHttpRequest) to achieve what the MWBP comments to the Widgets 1.0 Requirements were attempting to promote, e.g. interoperability, through:
(a) identification of the widget in HTTP requests (user-agent header)
(b) disclosure of Widget and device capabilities (Profile and Accept headers)

Example:
var client = new XMLHttpRequest();
client.open('GET', 'http://dcd.server.com/channel?ID=21');
client.setRequestHeader('User-Agent', 'DCD Widget/1.0');
client.setRequestHeader('Accept', 'application/vnd.oma.dcd, multipart/mixed, multipart/related');
client.setRequestHeader('Profile', '"http://megawidgets.com/dcd-widget1.0.rdf"');
client.send();

These methods ensure that the capabilities of Web Applications are disclosed (or at least the application identity is disclosed, which is useful as a lookup key for detailed info in a DDR), and thus the Content Provider can adapt services appropriately. Web Applications are expected to have diverse purposes/capabilities and use diverse content types, so it's important that we carry forward and extend as needed the "adapt services to device capabilities" guidance that we provided for browsers in BP1. Because these capabilities may not be disclosed by default though the underlying platform features (XHR or other native HTTP request API), the Web Application developer should be prepared to disclose them directly.
Related Actions Items:
No related actions
Related emails:
  1. [minutes] Tuesday 7 July 2009 teleconf (from fd@w3.org on 2009-07-07)
  2. RE: ISSUE-281 (DiscloseCapabilities): MWA should disclose their capabilities in HTTP requests, to allow service adaptation [Mobile Web Applications Best Practices] (from rotan.hanrahan@mobileaware.com on 2008-10-16)
  3. Re: ISSUE-281 (DiscloseCapabilities): MWA should disclose their capabilities in HTTP requests, to allow service adaptation [Mobile Web Applications Best Practices] (from jrabin@mtld.mobi on 2008-10-16)
  4. RE: ISSUE-281 (DiscloseCapabilities): MWA should disclose their capabilities in HTTP requests, to allow service adaptation [Mobile Web Applications Best Practices] (from rotan.hanrahan@mobileaware.com on 2008-10-16)
  5. RE: ISSUE-281 (DiscloseCapabilities): MWA should disclose their capabilities in HTTP requests, to allow service adaptation [Mobile Web Applications Best Practices] (from BS3131@att.com on 2008-10-16)
  6. ISSUE-281 (DiscloseCapabilities): MWA should disclose their capabilities in HTTP requests, to allow service adaptation [Mobile Web Applications Best Practices] (from sysbot+tracker@w3.org on 2008-09-26)

Related notes:

No additional notes.

Display change log ATOM feed


Jo Rabin <jo@linguafranca.org>, Daniel Appelquist <daniel.appelquist@vodafone.com>, Chairs, Dominique Hazaël-Massieux <dom@w3.org>, François Daoust <fd@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 281.html,v 1.1 2011/01/10 15:19:48 dom Exp $