William Will
2002-09-27 17:55:45 UTC
Hi there,
according to my understanding MDR 1.0 will only try to achieve usage as a
caching mechanism for metadata, and not as a form of primary storage. I'm
trying to understand the reasoning behind this, since it puts considerable
constraints on MDR's usability.
Essentially any application that derives metadata must dump this information
to XMI or some other format at some reasonably short time interval in order
to prevent data loss. I can also see the lack of primary storage
functionality as being a problem for any type of modeling tool that is
actually used to input mappings/metadata between different metamodels.
According to my understanding the ability to model and operate on multiple
levels of models was to be one of the main features of the MOF/MDR
combination...
So, are there any plans to make MDR with the current bTree storage a
reliable primary storage mechanism? I think some of the main promise of MDR
lies in this area of functionality.
Cheers,
William Will
according to my understanding MDR 1.0 will only try to achieve usage as a
caching mechanism for metadata, and not as a form of primary storage. I'm
trying to understand the reasoning behind this, since it puts considerable
constraints on MDR's usability.
Essentially any application that derives metadata must dump this information
to XMI or some other format at some reasonably short time interval in order
to prevent data loss. I can also see the lack of primary storage
functionality as being a problem for any type of modeling tool that is
actually used to input mappings/metadata between different metamodels.
According to my understanding the ability to model and operate on multiple
levels of models was to be one of the main features of the MOF/MDR
combination...
So, are there any plans to make MDR with the current bTree storage a
reliable primary storage mechanism? I think some of the main promise of MDR
lies in this area of functionality.
Cheers,
William Will