Torture tests and canonical examples

I've added the following to the wiki:
[note from dpd -- I've never wiki-ed before, so I don't quite know the proper past tense of the verb, nor proper protocol for leaving one's footprints -- however ...] Take a look at http://srufaculty.sru.edu/david.dailey/svg/newstuff/Newlist.htm These are a collection of examples developed for writing the book. By and large I think they should all work according to the spec, though in some cases, there remains superfluous code (javascript put in to draw axes and the like -- templates carried from one example to the next that are no longer needed as the context changes and so forth). Those examples, or the simple code illustrated in the various sections of the book, provide examples of code and pictures of what it [should] (I think) look like. 
By way of torture tests, the examples with compound filters are quite torturous, living up to the name. 
 
They were designed as sort of simplest examples to investigate certain features. It might make most sense to just cut and paste from the book -- put into the wiki and then test, critique and evaluate. If flaws in the examples are found, I need to know so that that feedback gets back into the book.
 
In addition to torture tests, I think we've talked about a slightly different collection of "best practices"
 
I'm thinking here of something I might call canonical examples -- things for which the code cannot be made any simpler. (which, from my experience, helps with actually teaching someone to do something).
 
Any suggestions on where to put such a thing? A new page perhaps? 
 
What I have in mind is something like :
 
<svg xmlns="http://www.w3.org/2000/svg">
<circle r="9"/>
</svg>
I claim that this is the simplest svg file (in terms of keystrokes) that should actually render properly in all user agents.
The claim may be wrong (note that if I say r="50" the visible quarter circle may be more visible.
cx and cy, are, I think optional attributes defaulting to 0. The NS declaration is required in at least FF.
It has to be well formed XML, and all the other basic shapes have more required attributes (I think).
 
I have a few of these for submission and discussion.
 
Given the lack of traffic thus far on this list, maybe it makes more sense to discuss through e-mail rather than
wiki, until some consensus is reached? You wiki veterans know better than me.
 
cheers
David

Received on Saturday, 6 September 2008 17:08:25 UTC