RE: [xml-dev] [ Revision #2 ] 15 elementary truths about XML

[cbullard@hiwaay.net]

When building training materials, particularly using behavioral  
chaining (see B.F. Skinner) the discipline is to make no assumptions  
so the questions begin something like this:

**********************************************************

The game is chess.  You have checkmate.  You have
a) Won
b) Lost.

Pick one.

*********************************************************

That is an actual example from a chess course. It is known as reverse  
chaining: begin from the end state and work backwards to the beginning  
states.

When Roger is writing material, he often works this way and as is  
pragmatic, starts from the simplest concepts and we try to help him do  
this as much as
is possible.

What is obvious to us is not obvious to others.  I work for a somewhat  
technically deficient logistics department.  I have to explain even  
the most
simple concepts to technical writers, their supervisors and the  
program managers.  In my experience, there is no such thing as too  
simple an explanation of XML.

And the failure of American universities to grasp the importance of  
adequate XML training for technical writers is sustained and abysmal.   
They turn out editors who can memorize Word style sheets but they fail  
when it comes to providing enough knowledge to bridge the gap between  
writers and elementary computer science concepts.   Roger fills the  
gap.  Ken fills the gap.

And that is a good thing.