Hi Georg,
Yes that is absolutely correct. The archetypes act as a constraint on the
RM so must always be compliant with the RM, and whatever underlying
archetype class is selected. Same applies to templates. Practically
speaking this does still give us a huge amount of flexibility, especially
as w
Hallo,
I have a question about the degree of freedom in defining archetypes:
Archetypes are not composed but rather specified by constraining the
base classes from the reference model. Hence no new/custom field members
can be definied in the definition of a new archetype but only the field
memb
2 matches
Mail list logo
