tutorial outline

["Lauren Wood" <lauren@textuality.com>]

I had an action item to think about a tutorial outline. Here's the 
first cut.

The tutorial will cover two types of questions:
1) how do I do (i.e., task-oriented)
2) what does this mean

It will be aimed at relative beginners and point people to the spec 
for more detailed explanations rather than trying to recast all the 
answers. It will contain lots of examples. 

Outline:
0) start with saying that how to make the catalog file "work" is 
application-dependent, and give examples how current apps handle 
this. Also give an example of the PI in the document.

A) Next, tackle how to resolve the replacement text for an external 
entity. 
1) This will be done by showing a minimal simple catalog (assuming 
system IDs). Add a couple of entries and discuss what effect ordering 
has on the catalog priorities.
2) discuss what system and public mean
3) how to create entries for system and for public and for both 
system and public
4) what tasks are solved with a) delegatePublic, b) delegateSystem, 
c) rewriteSystem and put in examples. Discuss the priorities between 
them
5) how to do modularization with nextCatalog
6) what to do with prefer and Group

B) The alternate URI reference for resources
1) example using a stylesheet PI; add a couple of entries and discuss 
priotities and ordering in the catalog
2) discuss what uri actually does
3) what tasks are solved with a) delegateURI and b) rewriteURI, and 
how priorities are resolved.

c) the extras: id, xml:base

cheers,
Lauren

---  
Lauren Wood, Textuality
Chair, XML 2003 http://www.xmlconference.org