[Dev] Proposal: simplify parcel XML namespaces

[Phillip J. Eby]

At 04:07 PM 6/27/2005 -0700, John Anderson wrote:
>I don't have any problem with making changes parcel XML to make things 
>easier for developers as long as I can still create any schema and any 
>instance, not just U/I schema and instances.

Schema needs to be defined in Python, at least if we're going to try to 
drop the parcel loader down to only parsing files once.  (But see also below.)


>  And, I'd like to get a chance to obsolete it by doing a simple first 
> crack at a GUI builder, for which we'll need to have some format that we 
> can both export and import to the repository -- which would ideally be 
> the same thing parcel XML evolves into.

That might be helpful, but it might be better for that import/export format 
to be Andi's "native XML" for the repository (aka "packs").  That would 
allow it to contain schema as well as items, but without needing multiple 
passes (if I understand correctly) to load the data.  The only downside is 
that "native" XML is a bit painful to read and write, so it would not be 
ideal for hand-editing.