W3C home > Mailing lists > Public > public-sysapps@w3.org > May 2012

please come with some term other than "browse-by Web"

From: Michael[tm] Smith <mike@w3.org>
Date: Tue, 29 May 2012 19:03:07 +0900
To: public-sysapps@w3.org
Message-ID: <20120529100305.GB29325@sideshowbarker>
The charter for the proposed System Applications Working Group uses the
term "browse-by Web" without defining it, and that term has also popped up
in at least one thread on this list so far.

That term doesn't seem to be in common use anywhere else, so I'm assuming
it's something that was coined recently in an attempt to distinguish the
scope of the proposed new group from the scope of the WebApps WG and DAP WG.

I'd like to suggest it not be used and instead replaced by a some other
term that's more clear, or failing that, at least defined explicitly in the
charter. (I'm not just trying to bikeshed; the term seems fundamental to
the scope of the work and should reflect that scope as clearly as possible,
instead of being some newly minted opaque thing.)

Looking at the other language in the charter, I see:

  http://www.w3.org/2012/05/sysapps-wg-charter.html

  This working group differs from both the Web Applications Working Group
  and the Device APIs Working Group in that those working groups are
  focused on defining APIs that are safe to run in a browser environment.

  The working group will focus on those operating system interactions that
  cannot necessarily be exposed safely to Web applications executing in the
  traditional browser security model.

So it seems like instead of using "browse-by Web" to say what the proposed
APIs are not, it would make a lot more sense to define the scope of the
work as whatever it actually is; e.g., "browser-unsafe APIs" or
"Web-application-unsafe APIs" or "non-SOP APIs".

  --Mike

-- 
Michael[tm] Smith http://people.w3.org/mike
Received on Tuesday, 29 May 2012 10:03:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 29 May 2012 10:03:31 GMT