Hi there,
I was reading the Lukas thesis about Magritte. By the way...
congratulations for that nice document Lukas.
I have questions about Magritte beign useful for generating views of the
model. Note I said views and not view of the model because I think is
interesting to generate more than one unique view for it. I have several
examples in wich this feature is desirable. Most are user based. With user
based I mean the user's role should determinate the observation. An
organization's anOperator should see something of aDocumentModel but
aManager should see diferent and probably more details of the same
aDocumentModel and aDirector should see just metrics about that
(aDocumentModel).
I see that one could manipulate the design to "force" aDocumentModel to
be of different species for each observer but the cost is undesirable
complication, reality-virtuality mismatch and identity mess (made worst with
and RDBMS mapping in the middle). I don't like the dark side.
I think is possible a better approach but until now I was unable to see
a clear way on how Magritte could help with multiple description request.
The descriptions for the objects are deducted from class side #descriptionXX
of the objects wich collaborates with MADescriptionBuilder but it's cache
seems to be designed to store only one description per object.
Do you think that to extend Magritte to support several descriptions per
object should be the best approach to this problem?
thanks,
Sebastian Sastre