[Dev] PyCon Report
Katie Capps Parlante
capps at osafoundation.org
Thu Mar 31 20:38:41 PST 2005
Yes, a validator would help. The design of parcel xml makes that
slightly tricky, as the definition of new Kinds would need to define the
xml schemas. Each parcel that defines new Kinds defines a new namespace.
We could of course define an xml schema for the core items (Kind,
Attribute, etc.). We could also define xml schemas for common Kinds in
the framework (Blocks, WakeupCallers).
And yes, we've gotten feedback that this might be something of an abuse
Alternatively, we could define a different xml schema for CPIA that was
better suited to ui layout.
Keep in mind that parcel xml is just a mechanism to load items into the
repository -- the parcel loader parses the xml and makes standard api
calls to the repository. We could come up with alternative ways of
loading items into the repository -- Phillip Eby and others have been
thinking about such alternatives.
Nicholas Bastin wrote:
> On Mar 31, 2005, at 1:14 AM, Katie Capps Parlante wrote:
>> one more pycon report:
>> I found the sprints to be very rewarding, a good use of two days. We
>> split up into two groups, where we had one or two volunteers and one
>> or two osaf helpers in each group. One pair worked on a delicious
>> parcel and one pair worked on a flickr parcel.
>> Lessons learned about writing chandler parcels
>> (+) Debugging xml is a real pain. Watching people try and find a typo
>> in a namespace really makes one wince.
> I don't really know anything about the internals of Chandler, but don't
> you have a schema? If you have schemas for each kind of XML document
> that you need to produce, debugging is pretty easy - the validator will
> tell you what is wrong with your document.
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> Open Source Applications Foundation "Dev" mailing list
More information about the Dev