+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 don't have a better answer for
that issue.
Let's just define data in python and be done with it. :-)
On Jun 24, 2005, at 5:02 PM, Phillip J. Eby wrote:
Now that all Chandler parcels are using the schema API, we have the
option of getting rid of the messy 'http:' URIs for defining parcel
namespaces. I'd like to propose that we move to a "parcel:" URI
scheme, of the form "parcel:osaf.framework.blocks" This would let
us use the same names in parcel.xml as we would use in Python code,
making the namespaces easier for humans to read, write, and remember.
Basically, we would go from this:
<core:Parcel xmlns:core="http://osafoundation.org/parcels/core";
xmlns="http://osafoundation.org/parcels/osaf/framework/blocks";
xmlns:main="http://osafoundation.org/parcels/osaf/views/main";
xmlns:detail="http://osafoundation.org/parcels/osaf/
framework/blocks/detail"
xmlns:amazon="http://osafoundation.org/parcels/osaf/
examples/amazon"
xmlns:doc="http://osafoundation.org/parcels/osaf/examples/
amazon">
To this:
<core:Parcel
xmlns:core="parcel:core"
xmlns="parcel:osaf.framework.blocks"
xmlns:main="parcel:osaf.views.main"
xmlns:detail="parcel:osaf.framework.blocks.detail"
xmlns:amazon="parcel:osaf.examples.amazon"
xmlns:doc="parcel:osaf.examples.amazon">
Any thoughts?
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
