- From: Mandyam, Giridhar <mandyam@quicinc.com>
- Date: Wed, 30 Jan 2013 01:54:37 +0000
- To: Jo Rabin <jo@linguafranca.org>, "public-coremob@w3.org" <public-coremob@w3.org>
Thanks to the editors for all of their work in coming up with this latest version. My apologies if I am repeating comments, or raising issues that have already been addressed. -Giri Mandyam, Qualcomm Innovation Center General comments on the latest draft: 1) Section 1, Introduction. "Compile related conformance test suites." I realize this is simply quoting from the charter, but I think the charter should be slightly modified to read "Compile related conformance and performance test suites." 2) Section 1.5, Aspirational nature of the document. "quality of implementation" could be better defined, particularly what "implementation" means. I think "implementation" should consider the browser + OS + CPU. 3) Section 2.4, Find the nearest subway station. I think we should put in a requirement on geolocation accuracy. Currently the Geolocation API spec does not provide guidance on how to implement the enableHighAccuracy flag. I think that implementations that ignore this flag or do something unintended (e.g. use Cell ID when this flag is set and a GPS measurement is available) should not be considered conformant. This however means adding conformance requirements to the Geolocation spec that do not exist as far as I can tell. 4) Section 2.5, Read an online magazine. "While on the subway, she is able to read the daily news, watch a video, ...". What if the video is DRM protected and requires network access? Also, I think Req. 10 should be applicable in this case. 5) Section 2.6, View a regular Web site. Is there an implicit requirement that the browser should be able to change the header User Agent string (i.e. to avoid retrieving the mobile version of the bank web site)? 6) Section 3.4, Multimedia. Req. 18. Regarding the 30 fps "must" requirement, this is dependent on how we define "implementation" (see my 2nd comment above) and under what conditions the fps measurement is taken. Moreover, how fps is measured would need to be defined. I think in practice the best you can do with this requirement is make it a "should". -----Original Message----- From: Jo Rabin [mailto:jo@linguafranca.org] Sent: Wednesday, January 23, 2013 11:03 AM To: public-coremob@w3.org Subject: "Pre-Final" Draft of Coremob - 2012 and dial-in details for telecon to advance to "Final" Hi Mobsters, We've published an updated draft of Coremob - 2012 [1] reflecting comments on this list re the earlier draft [2]. If you are interested in a diff-marked copy, then we have that for you [3]. [1] http://coremob.github.com/coremob-2012/ED-coremob-20130123.html [2] http://coremob.github.com/coremob-2012/ED-coremob-20121222.html [3] http://j.mp/UVkCXb This document is now in its final form (modulo an editorial change to update the references to the latest or published versions). As previously mentioned we will be holding a telecon next Wednesday, 31 Jan, at 2pm UTC to advance the document to "Final" and to deal with some loose ends on Issues and Actions. With thanks once again to Financial Times Labs for donating the conference bridge, the details follow. Thanks Jo Date: 2013-01-31T14:00:00Z [0600 US Pacific, 0900 US Eastern, 1400 UK/Ireland, 1500 Western Europe, 2200 Korea] Duration: 60 minutes (max, probably much shorter) Phone: +44 20 7897 0143 (International, non-toll free) Toll-free: see http://labs.ft.com/confcall/ Code: 1066262383 IRC: irc://irc.w3.org:6665/#coremob IRC Web interface: http://irc.w3.org/ - join channel #coremob
Received on Wednesday, 30 January 2013 01:55:07 UTC