- From: Dailey, David P. <david.dailey@sru.edu>
- Date: Mon, 6 Oct 2008 14:18:46 -0400
- To: <bhopgood@brookes.ac.uk>
- Cc: <public-svg-ig@w3.org>
Perhaps the new revisions at http://www.w3.org/Graphics/SVG/IG/wiki/Links_to_existing_materials#Links_by_SVG_category take into account what Bob (here) and Rob (earlier) were saying about orthogonal organizations. I've also put in a few examples of some of the things just to illustrate, but clearly other hands will find other things in the sifting. D ________________________________ From: bhopgood@brookes.ac.uk [mailto:bhopgood@brookes.ac.uk] Sent: Mon 10/6/2008 1:10 PM To: Dailey, David P. Cc: public-svg-ig@w3.org Subject: Re: Categories of topics concerning SVG David, If by SMIL you mean SVG's Declarative Animation I would call it that. If I saw SMIL I would expect it to be about the SMIL functionality NOT in the SVG namespace ;-) We have quite a lot of examples we use locally and one section we have is Application Areas which is subdivided into Cartography, Engineering, Science, Charts, Visualisation, Graphics Art. The emphasis here is on the way SVG is used in that area rather than the specific facilities it uses. Bob > > Having recently developed three somewhat similar classifications of SVG > content, it reminded me that the dormant librarian in each of us yearns > for consistency. It made me wonder if there might be a canonical > classification of SVG topics. I believe there are good reasons for not > following the organization of the Spec here. http://www.w3.org/TR/SVG/ > breaks things into 23 chapters (and while 23 is a perfectly admirable > number) but methinks the person on the street trying to find information > might not want the third of her 23 chapters to be "the Rendering Model." > (just a guess). SVG Tiny has 19 chapters (still a prime number!) but 3 is > still "the Rendering Model." In writing the book > (http://www.w3.org/Graphics/SVG/IG/resources/StateOfArt-Dailey.html) I > made a very conscious decision not to follow that organization since the > work was intended for at least some who are new to the subject. The book > is of course not intended to be comprehensive, so I'm not suggesting that > its table of contents is the desired taxonomy. > > Ultimately the question is how do people trying to find information about > SVG look things up? Perhaps our Google friends could spare a bit of there > 870 petabytes of data (just guessing) to answer the question of what words > co-occur most frequently with searches for "SVG"? Looking at either > completions in the google search bar in Firefox, or at "Google trends" > surrenders no obvious insights. > > A current start on such a list of categories might be: > > Basic drawing primitives > Colors, Gradients and Patterns > Clipping and Masking > Transforms, Groups and Use > Filters > SMIL > Events and Interactivity > DOM methods and JavaScript > Layout and CSS > Zooming, panning and viewBox > Fonts > Relations to other technologies (HTML, XML, AJAX, XSLT) > Comparisons to similar technologies (Flash, Silverlight, Bitmaps) > Editing and Authoring Tools > > It is clear that the top-level categorization should be relatively finite > (George Miller's magic number 7 plus or minus 2 comes to mind) though > Dewey chose 10 (because of fingers) and Library of Congress chose 21. Do > you see obviously missing categories? Categories that ought to be > combined? > > Perhaps the enumeration of categories should be different from context to > context, but the thought that consistency in our collective cataloging on > the wiki might be desirable came to mind. If one were to see my desk, one > would not get the impression that I am fastidious about such matters. > > David > > >
Received on Monday, 6 October 2008 18:22:30 UTC