W3C home > Mailing lists > Public > public-bpwg@w3.org > November 2009


From: Jeff Sonstein <jxsast@rit.edu>
Date: Tue, 3 Nov 2009 06:45:51 -0400
Cc: Public BPWG <public-bpwg@w3.org>
Message-Id: <023D5915-D294-451F-A980-5D0ECB5B12BA@rit.edu>
To: Jo Rabin <jrabin@mtld.mobi>
On Nov 3, 2009, at 6:12 AM, Jo Rabin wrote:

> 5. AOB
> Review of and tidy up of ISSUEs and ACTIONs - we have no open ISSUEs  
> and we have a handful of open actions on DKA, JeffS and Adam (hint  
> hint).


I thought we had finished w this & closed it...
last I remember
the text now in the document
(courtesy the hacking-and-slashing
  I mean "fine editing"
  of Adam <grin/>)
was something everyone could at least "live with"

while I would *like* to be providing more detailed guidance to  
I can *live with* just saying what is in the document at this point:

-----  snip  ----- What it means

Canvas and SVG provide alternative options for incorporating graphics  
in a Web application. Support for these technologies varies across  
devices so in many cases the choice of which technology to use will  
depend on the target devices for a given application.

The Canvas element defines a drawable bitmap region onto which  
JavaScript can be used to render simple graphic primatives. In  
contrast, SVG is an XML language for defining vector graphics -- the  
nodes and elements are added to a DOM and can be modified later using  
SVG is well-suited for graphics that must be scalable and whose  
components need to be modified (e.g. panning and zooming a map)  
whereas Canvas is best suited for cases where a static bitmap is  
sufficient (e.g. drawing a scatter-chart, visual effects, reflections  

In most cases Canvas is faster and should be preferred if it meets  
requirements. However, since Canvas generates a flat bitmap it is not  
inherently accessible and so should not be used as the sole means of  
conveying information.
-----  snip  -----

my only teenie quibble
would be with the last sentence
which I think might better be changed from:

"it is not inherently accessible and so"

to instead read:

"it is inherently not accessible as it is not part of the DOM, and so"

can we close this out at this mtg?


"Workers were called,
   and human beings came."
- Max Frisch -

Prof. Jeff Sonstein

Received on Tuesday, 3 November 2009 10:46:29 UTC

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