[Dev] Proposal: simplify parcel XML namespaces
Phillip J. Eby
pje at telecommunity.com
Fri Jun 24 18:28:24 PDT 2005
At 05:45 PM 6/24/2005 -0700, Morgen Sagen wrote:
>+1 and -1
>
>+1 because as it stands now (pje correct me), 3rd party parcels also
>live under the "http://osafoundation.org/parcels" namespace umbrella,
>which doesn't really make sense. For example, if I implement a parcel
>whose package is morgen.myparcel, its namespace name would be "http://
>osafoundation.org/parcels/morgen/myparcel". So I am in favor of
>dropping the "osafoundation.org/parcels" part.
>
>-1 because I think libxml2 won't be happy about the "parcel:" scheme,
>but I would have to experiment.
I already did the experiment; implementing support for a "parcel:"
namespace shortcut in application.Parcel is only four lines of
code. Getting rid of the http: cruft would take a bit more work, though.
>Let's just define data in python and be done with it. :-)
One step at a time. :)
More information about the Dev
mailing list