E&S CVS Commit: PEAK - Beginning implementation of a full MOF 1.3.1 metamodel. We'll need this

pje at eby-sarna.com pje at eby-sarna.com
Fri Dec 20 18:29:01 EST 2002

Module Name:	PEAK
Committed By:	pje
Date:		Fri Dec 20 23:28:47 UTC 2002

Added Files:
	PEAK/src/peak/metamodels: MOF131.py
	PEAK/src/peak/model: datatypes.py

Log Message:
Beginning implementation of a full MOF 1.3.1 metamodel.  We'll need this
to process current/valid OMG metamodels for UML, CWM, etc.  Plus, it'll be
a good basis for generating Python code.  UML and other high-level design
metamodels are too abstract for easy code generation, but MOF is designed
to be a very concrete representation of a program's implementation model.
We'll generate MOF models from UML models before generating artifacts such
as Python code or DDL.  MOF is also the basis of XMI, so in general it
should be useful to have around.

Unfortunately, the 600+ lines of code I've written so far only fully
implement maybe 2-3 of the 23 MOF classes, just sketching the inheritance
hierarchy and contents rules for the rest.  I've got about another 50 pages
of MOF spec to implement yet, and some of what I've done I still need to
go back and add a bit into 'peak.model' to support properly.  :(  The good
news is that this is a good test of 'peak.model', and it'll help us to get
through the coming refactoring of 'peak.model'.

To view diffs of this commit, you can use the following URL(s):

To generate a diff of this commit:
cvs rdiff -r0 -r1.1 PEAK/src/peak/metamodels/MOF131.py
cvs rdiff -r0 -r1.1 PEAK/src/peak/model/datatypes.py

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.

More information about the source-changes mailing list