- From: Heiko Braun <ike.braun@googlemail.com>
- Date: Thu, 25 Oct 2012 09:14:28 +0200
- To: Sebastian Feuerstack <Sebastian@Feuerstack.org>
- Cc: public-mbui@w3.org
Received on Thursday, 25 October 2012 07:15:01 UTC
Thanks for the explanation Sebastian. Referencing the other models through "Entity" makes a lot of sense to me. But maybe "EntityContext" is a more appropriate term? Nevertheless I now have a much better understanding how the models cooperate. Not only does the "EntityContext" allow to associate different models at various stages (Task, AUI, CUI, Final), but it does also provide a reasonable way to distinguish mandatory and optional model references. Regards, Heiko On Oct 24, 2012, at 1:16 PM, Sebastian Feuerstack <Sebastian@Feuerstack.org> wrote: > AUI model to an "entity" that every other model element from every model > is related to > (e.g. by inheritance or association) and that is used to define mappings > (and/or transformations) between elements of models. > > In my opinion, documentation, the domain model, the localization, and even > the behaviour are not part of the AUI model (because these concepts are > relevant for > other models as well) but could be connected in an elegant way by using > mappings.
Received on Thursday, 25 October 2012 07:15:01 UTC