W3C home > Mailing lists > Public > public-bpwg@w3.org > February 2008

ACTION-660: Input to BP2, Scope and Criteria

From: Sullivan, Bryan <BS3131@att.com>
Date: Thu, 14 Feb 2008 13:35:52 -0800
Message-ID: <8080D5B5C113E940BA8A461A91BFFFCD05D93FEB@BD01MSXMB015.US.Cingular.Net>
To: "BPWG-Public" <public-bpwg@w3.org>

Hi all,

This is the first of a series of emails addressing ACTION-660, intended
to kick off a dialog on this list where we refine the scope of the
Mobile Web Best Practices 2.0 (BP2) as needed. Below is the current text
in the editor's draft. The goal of this thread will be to:

- clarify/improve the scope definition as needed 

- clarify/improve the "Criteria for Best Practice recommendations" as
needed. As proposed, the criteria are intended to limit the scope of BP2
to those aspects considered "essential" rather than "useful", as a way
to manage the overall work and timeline. Of course what is essential (a
value judgement) varies, but this is a pragmatically necessary step of
collective prioritization, based upon the objectives and contributions
of the various stakeholders (this being a contribution-driven activity).

It will be helpful in managing your comments if you summarize the points
at the start of emails, reference as needed to details mixed in the
thread, and mark your comments e.g. as [name].

1.4 Scope
These recommendations (BP2) follow in the footsteps of the Mobile Web
Best Practices 1.0, (BP1), for which the scope was laid out in "Scope of
Mobile Web Best Practices" [Scope] . In summary, BP1 refered primarily
to the extension of Web browsing onto mobile devices.

BP2 extends the focus to Web applications generally, which means an
application that is accessed and presented via Web technologies. Web
applications represent a spectrum of services and content, at the simple
end of which are typical Web browsing sites, presented in browsers,
which were the focus of BP1. The BP2 focus includes further
recommendations for addressing delivery context issues and for use of
advanced Web technologies, which apply both to browsers and non-browser
web runtime environments.

The recommendations refer to applications as experienced on mobile
devices. The recommendations necessarily reflect upon the processes by
which the applications are developed and delivered, and the nature of
the devices and user agents through which they are experienced. However
the main focus is upon the applications themselves, including content
that is delivered and presented through the applications.

As the goal of the document is to specify Best Practices for delivery to
mobile devices, statements that do not have a specific mobile aspect are
not included. In particular, many Web Content Accessibility [WCAG]
guidelines are general to all forms of Web access and are not repeated
here unless they have a specific mobile interpretation. Examples of
general good practice which have a specific mobile interpretation
include "Error Messages" and "Color". 

1.4.1 Phasing
As discussed in the Scope document [Scope] there are many aspects to
Mobile Web Best Practices. BP2 represents the second phase of the Best
Practices development, i.e. beyond "Traditional Web Browsing".

1.4.1 Criteria for Best Practice recommendations
The BP2 is not intended as a landscape document, e.g. a general survey
of technologies and related issues in the mobile context.
Recommendations are included here if they meet specific criteria:

- are considered essential for successful deployment of web applications
in common delivery contexts 
- are considered of fundamental importance to growth in the mobile web
application market 
- can be readily verified through compliance testing, either automated
(preferred) or manual

Bryan Sullivan | AT&T
Received on Thursday, 14 February 2008 21:36:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:09:51 UTC