...
Content

* Tree I/O

Z3 Adapters for Import/Export

Marshall Product

* Heart of the system

* Sidnei did the initial work on the system, it supports all Archetypes Based Content generically.

* Kapil extended workflow and security

* Marshalling is a framework and a layer. It supports WebDAV It defines a way for you to create marshallers that are used dynamically. An example is iCal serialisation. Now you can register your own namespaces in the marshaller. It archives References as well. It is not a product but a name for the software stack.

Hard Bits

Content is easy but applications probably are not. It is useful out of the box. There can be side effects on content. On creation it could send out an email and in an import export scenario this can be a pitfall. The workflow is attached to the objects themselves. Unresolved References are possible on import. Archetype references should be resolved.

Upcoming Events

* Castle sprint this week

* San Jose II Sprint CA - End of October

Questions?

Q: Is it going to work only with 2.2, what plone versions will be supported?
A: There are various pieces: Marshall. We are going to use Five and this is why we will use Zope 2.8.

Q: XSLT, are there exports from other systems?
A: The xml is a low level representation of the object, and supporting that is definitively a supported usecase.

Q: If I have custiom content types. If I provide custom fields what happens?
A: Archetypes are generically supported. Composite content; Imagine an issue tracker you probably need to write an extra adapter for it.

Q: Binary content?
A: Zip file.

Q: Which xml implementation
A: Low level libxml.

Q: Is that libxml stuff pluggable? The generic setup? What does it do for you?
A: Replacing the xmllib marshalling layer is possible at two levels. Framework for import and export.

Q: Is it basically... Can I deploy stuff with that product, like import...
A: There is no framework and no workflow.

Q: What if we import from an external tool and there are dependencies?
A: Two step import.

A: Asic processes the task queue. At an import step it would not matter how long it takes to import as long as it is detached.

Q: Is one of your usecases trying to merge two or more servers?
A: The chances of conflict are high. Kapil is unsure if this is going to work.

A: Import is a long process, and that can still be a problem.

Q: A Question about Member Data? There is the usecase of importing 300'000 users into a plone site.
A: The original work was to support that usecase, for a newspaper that had 150'000+ users, it works for them. That is definitively a usecase.

Q: Where is the code?
A: It is the pluggable_namespace branch in Archetypes

Q: What kind of format is going to be used? Docbook?
A: Out of the box... Typically you write your own adapter. Out of the box it is coming with one atxml format.

Q: Cut and paste xml? Can desktop tools be used to author when they save xml?
A:-)