[Dev] parcel.xml changes

[Morgen Sagen]

Jeffrey (and others),

I left the "describes=" attribute inside each parcel element for now, 
but you and I need to talk about what to do next in terms of 
XML-to-HTML document generation.  As you can see, our parcels now have 
real URIs for namespaces, and there were a couple tweaks to syntax, 
such as itemName becoming itsName (to match the repo API).

Also, I'm not sure if this is important to your XSLT transforms, but 
remember that a parcel's URI doesn't necessarily have match it's 
repository path (or file system path) -- however, OSAF parcels will 
most likey follow this pattern, just so there's not another hierarchy 
to keep in mind:

    filesystem:  chandler/parcels/osaf/contentmodel/parcel.xml
    repo path:  //parcels/osaf/contentmodel
    parcel's registered namespace:  
http://osafoundation.org/parcels/osaf/contentmodel

I could (and third party parcels will) make up my own namespace, such 
as http://morgen.com/foo/bar and have my parcel register it (by placing 
a <namespace value="http://morgen.com/foo/bar" /> inside my <Parcel>), 
and that URI would be how others would refer to me.

If you don't specify a <namespace> in your parcel, the parcel will be 
assigned a namespace equal to your parent's namespace plus your parcel 
name appended.  So for the OSAF parcels, we only need to assign 
<namespace> to //parcels/osaf, and all the children will automatically 
have the right namespace assigned.  I mention this, Jeffrey, so that 
you know not to assume every parcel.xml will have a <namespace> in it.  
If that's a problem, let me know.

So I would like to remove the "describes=" attribute if the doc 
generator no longer requires it.

Thanks,
~morgen