[Zope3-dev] Zope 3 Alpha 1 in 2002
maxm
maxm@mxm.dk
Wed, 30 Oct 2002 11:45:16 +0100
Jim Fulton wrote:
> I'm created the road map in CVS in doc/ROADMAP.txt:
>
> http://cvs.zope.org/Zope3/doc/ROADMAP.txt?rev=HEAD&content-type=text/vnd.viewcvs-markup
- Object Hub, which tracks object locations, allowing
location-independent object references
- Indexing service, supporting pluggable indexes and searching
It might be that it is allready thought out that way, but I cannot see
it from the roadmap. But shouldn't there be a sort of "meta data register" ?
If we have an objecthub, and we have an indexing service, and at some
time we will get a relationship manager. Both the indexing service and
the relationship manager will need to store metadata for objects.
When I say metadata I really mean something like indexes in the current
catalog. Dublin Core has nothing to do with this.
But since metadata will be used by several modules, wouldn't it be for
the best if it was isolated in it's own module?
Here I think of some kind of object manager that keeps a mapping of oid
to metadata objects. If this then subscribes to events from the Object
Hub, that would be all that was needed to keep summary/meta data in
lightweight objects.
So if an index query or a relation returns an oid, they can both get
lightweight metadata from the same object.
lightObject = metadatas.get(oid)
lightObject.title_or_id
>>> some object title
Well I hope you get my point.
regards Max M