- From: Mobile Web Best Practices Working Group Issue Tracker <sysbot+tracker@w3.org>
- Date: Wed, 16 Apr 2008 17:27:46 +0000 (GMT)
- To: public-bpwg@w3.org
ISSUE-245 (ADC The Un-Dead): ADC, A Wooden Stake and Some Garlic Needed [Mobile Web Applications Best Practices] http://www.w3.org/2005/MWI/BPWG/Group/track/issues/ Raised by: Jo Rabin On product: Mobile Web Applications Best Practices I find myself in strong agreement with Mr McCathieNevile. [Whoa! Hang on .... OK - having carried out a preliminary sanity check, I still find myself in strong agreement] The reason we dropped ADC was exactly as he says. There is no real prospect of resurrecting it, in my opinion. As discussed previously, and as mentioned en passant in the Abstract of the document, it is to a substantial degree a follow up to BP1, especially where it teasingly says: "Exploit Device Capabilities" but then doesn't say what type of capabilities nor how to exploit them. So this document should i) enumerate the capabilities, (that's sort of what the first appendix is there for I think, so we can list what a DDR would have to store) ii) suggest how to determine their presence (other than by looking it up in a DDR) and c) say how you can use them to good effect. This process I think also covers Jeff's 1990's style points about upgrading and degrading gracefully. So 1996 or not - that's absolutely what we are saying is good practice. Jo this is a follow up to the thread at http://lists.w3.org/Archives/Public/public-bpwg/2008Apr/0024.html
Received on Wednesday, 16 April 2008 17:29:32 UTC