W3C home > Mailing lists > Public > public-bpwg-comments@w3.org > April to June 2006

Re: Comments on Draft 13 January 2006

From: <dom@w3.org>
Date: Wed, 12 Apr 2006 17:05:09 +0000 (GMT)
To: Werner Egipsy Souza (Jataayu Software) <werners@jataayusoft.com>
Cc: public-bpwg-comments@w3.org
Message-Id: <20060412170509.5575B66385@dolph.w3.org>

[Sorry for the duplicate]

  Dear Werner Egipsy Souza (Jataayu Software) ,

The Mobile Web Best Practice Working Group has reviewed the comments you
sent [1] on the Last Call Working Draft [2] of the Mobile Web Best
Practices 1.0 published on 13 January 2006 Thank you for having taken the
time to review the document and to send us comments!

This message holds the disposition of the said comments on which the
Working Group has agreed. This disposition has been implemented in the new
version of the document available at:
http://www.w3.org/TR/2006/WD-mobile-bp-20060412/

Please review it carefully and let us know if you agree with it or not
before 3 May 2006. In case of disagreement, you are requested to provide a
specific solution for or a path to a consensus with the Working Group. If
such a consensus cannot be achieved, you will be given the opportunity to
raise a formal objection which will then be reviewed by the Director
during the transition of this document to the next stage in the W3C
Recommendation Track.

Thanks,

For the Mobile Web Best Practice Working Group,
Philipp Hoschka
Dominique Hazaƫl-Massieux
W3C Staff Contacts

 1. http://www.w3.org/mid/43E76F40.3070605@jataayusoft.com
 2. http://www.w3.org/TR/2006/WD-mobile-bp-20060113/


=====

Your comment on 2.7 Advantages:
_3.7 Advantages:_
The mobile device has added advantages compared to a desktop or a
laptop, which are:

1. Always On:This device is always on, and always has phone
connectivity. Hence websites have the ability to directly connect
a user with a phone number, or IP address, if the requirement
exists.
2. Accessibility to near field devices, via infrared, Wi-fi,
bluetooth and USB(but this option is far less used!), such as car
audio systems, music players, cameras, gaming devices.
3. Added capability for Wearable computing , where the mobile device
may communicate with other devices, using the means mentioned above.

Working Group Resolution:
1. Always on is a feature of many devices aside from Mobile Devices. Data
connectivity from mobile devices is usually only established on demand by
an active application. 

2 and 3. We think that these aspects are out of scope of the Mobile Web.

----

Your comment on [URIS] Keep the URIs...:
_5.3.1 URLs of Site Entry Points_



Here, if URLs for a menu system running into more than 5 pages can 

follow a URL syntax containing page numbers such as:



http://wap.hephail.com:81/categories.php?page=59&category=11



then it becomes easy for the user to navigate between pages, just by 

changing the page number on the URL, through the bookmark. Of course, if 

the browsing application itself could provide a page browser using this 

syntax, the user\'s task of navigating through pages would be much easier



Working Group Resolution:
The Best Practice is about site entry points, to which this technique
doesn't really apply.



----

Your comment on [NAVBAR] Provide min...:
_5.3 Navigation and Links



_All the URLs for each page, must be listed in the options(or right 

click) menu, so that if a user he/she wants to go to a URL on the page, 

he/she just has to scroll through the options(or right click) menu to 

reach the required URL.

then it becomes easy for the user to navigate between pages, just by 

changing the page number on the URL, through the bookmark. Of course, if 

the browsing application itself could provide a page browser using this 

syntax, the user\'s task of navigating through pages would be much easier

Working Group Resolution:
This is a user agent issue and so out of scope. We do recommend use of
access keys which can achieve the same goal of easing navigation.

----

Your comment on [LINK_TARGET_ID] Cle...:
_5.3.7 Link Target Identification



_The cost of following a link,as in the case of articles, should be
identified in the number of pages which are required by the article, as is
done by the BBC Wap page.



Hence we get a link at the bottom of the first page of the article, which
says \"_Continued Page 2/4_\".

The user is then able to choose whether he/she wants to read a 4 page
article, or whether he/she should look for another article. 









Working Group Resolution:
We think this suggestion would be a good fit for a technique related to
this best practice; we welcome techniques contributions in our wiki at:

http://www.w3.org/2005/MWI/BPWG/techs/

----
Received on Wednesday, 12 April 2006 17:14:05 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:01:49 UTC