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

Re: ACTION-660: Input to BP2, Scope and Criteria

From: Sean Owen <srowen@google.com>
Date: Thu, 14 Feb 2008 19:05:10 -0500
Message-ID: <e920a71c0802141605r4be881e5u2b60e4c760792feb@mail.gmail.com>
To: "Sullivan, Bryan" <BS3131@att.com>
Cc: BPWG-Public <public-bpwg@w3.org>

On Thu, Feb 14, 2008 at 5:50 PM, Sullivan, Bryan <BS3131@att.com> wrote:
>  Re "anything that's not (X)HTML over HTTP is probably well out of
>  scope": I don't think we want to be so limited. Web applications can be
>  expressed in a variety of languages/schemas for which the basic issues
>  of mobile use are the same. Syndication applications (e.g. ATOM/RSS
>  readers and content upload applications) are an example of a web
>  application that does not use XTHML (or at least have to).

Good example, and this is beginning to crystallize what it is we might
be talking about. XHTML over HTTP (and CSS, Javascript, and so on)
seems in scope. I could imagine having something to say about RSS,
sure. Anything else? I can't think of much that's in somewhat common
use that is relevant to mobile.


>  have expressed yours ((X)HTML web browsers), and I have others (phonetop
>  widgets operating outside the browser sandbox). This will come out as we
>  back up the statement "The focus of the BP2 document is on producing
>  Best Practices that apply to the browser sandbox, while recognising that
>  they may have broader applicability to the Web Runtime (CSS, HTML,
>  Javascript, DOM, Persistent Storage, additional libraries, no browser
>  chrome, cache, etc.), esp Mobile Widgets". What applies to the browser
>  sandbox, if it can be reasonably applied outside the browser sandbox,
>  will benefit from consideration of similar requirements outside that
>  sandbox.

Yeah let's start having this discussion then. Storage, libraries,
widgets -- what do we have in mind here? The widgets bit is probably
particularly important to home in on. What particular existing
technology are we talking about here? I am not sure I know of anything
in common use for which one might plausibly name best practices, or
practices, yet.

If the gist of this is, that we're talking about XHTML and CSS and
Javascript that might be consumed by a range of mobile devices and
technologies, then fine. We agree we're talking about resources, not
agents, so we can do away with the discussion of what the consumers
will be to a large extent. The best practices will then be about XHTML
and HTTP and CSS and Javascript and RSS? then I think we are in the
same ballpark.

Does anyone else have thoughts here... I wonder if I am off base given
other discussions that have gone on.
Received on Friday, 15 February 2008 00:05:26 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:42:57 UTC