There already is a separate Meta model!

[Cory Casanave <cory-c@dataaccess.com>]

I have been watching all the dialog about the need for a specification Meta
model and it's degree of alignment with the collaboration model.  It seems
we are missing an important point - the TP is already using another Meta
model, one not derived or aligned with the collaboration model at all.  This
model is used to drive the execution engine of the TP layer.

I have strong doubts that the collaboration model will ever be used to drive
the execution engine.  What we are in danger of, by our continued thrashing,
is that there will be NO relation between the execution model and business
modeling.  It will be a BIG WIN for EbXml to be able to show business
modeling (which is how I think of the collaboration + REA model) with a firm
mapping down to such an execution model - lets not loose this advantage with
religious wars.

Unless we get our act together the current (TPA) execution model will go
forward as part of the first EbXml release and will be very hard to unroot.
We will be forced to adapt the business semantics to meet the capabilities
of the implementation rather than the other way around.  

So, the assertion is that we WILL HAVE an intermediate model, one way or
another.

That it would be far better to cooperate to make this integrate with
business modeling and the execution model.

Discussions of "it is or is not the same model" are useless.

You have at-most a month, after that the technology implementation will have
gone to far.

Karstens model is the only base line to proceed from.  If there are missing
semantics, work it out.

If we succeed we will be able to keep a traceable path from business
modeling to execution & compatibility with RosettaNet, CGI,
TMForum, UN/EDFACT, ect


Regards,
Cory Casanave