Java Reference
In-Depth Information
Transparency is essential to the open source process at Eclipse, yet this is some-
what different from the specification development process at the OMG [21].
Perhaps this is an area in which the two organizations can influence one another.
If the development of a reference implementation were done in the open, it
follows that the developing version of the specification itself must be available.
Otherwise, there would need to be a serial process of first developing the speci-
fication, publishing it, and then implementing it, which eliminates the benefits of
validating the specification while developing an implementation in parallel.
Can the process of developing standards be done in a more open and trans-
parent manner, with an emphasis on addressing the needs of a developing refer-
ence implementation? Alternatively, could Eclipse support a model whose source
is not open until it reaches a required level of alignment with ongoing specifica-
tion work?
In summary, the promise of MDA can be realized to a large extent today using
the capabilities provided by the Eclipse Modeling Project. As MDA encompasses
a collection of specifications that align well with the implementation goals of the
Eclipse Modeling Project, the future of delivering a solid open source infrastruc-
ture for MDA tooling seems bright.
Practically speaking, many challenges remain before realizing the statement
in the Modeling project's charter related to its relationship with standards bod-
ies such as the OMG. A relationship that is too informal will not likely yield the
desired results, whereas a relationship that is strictly defined and enforced will
likely limit the progress of implementation. The right balance will clearly benefit
both of these organizations, their members, and, ultimately, the customers of
standards-based commercial products.
Search WWH ::
Custom Search