[Zope3-dev] question on design approach

[Garrett Smith]

I'm trying to prototype a schema-like feature in Zope 3 (not Z3 schemas,
but similar):

- Schemas can be created TTW and stored as site management components

- Content objects can be created from a particular schema using the
standard add mechanism

- While schema definitions are stored locally (placeful), the schemas
are global -- so definitions defined in /foo can be used to create
components in /bar.

My preliminary design/thinking is:

- Use a global service to handle schema registration, enumerate
available schemas, create components, etc.

- Schema components will register with the global service when they're
created, unregister when deleted.

- The global service will work with the factory service and zmi menu to
tap into Zope's default 'add content' mechanism.

Does this approach seem sensible? Is anyone else doing something like
this? Comments much appreciated :-)

 -- Garrett