Repetition modeling in A12 applications: the case for data modeling

Aim of this topic: discussion of modeling techniques

Specific Topic Repetions in A12
Repeated structures can be modeled in A12 in two ways:

  1. overview model repetition views (outside the data model, one level)
  2. and nested data and detached/inline repeat modeling (done in the data model and with nesting level up to some arbitrary limit defined at data modeling time).

The pros and cons of these techniuqes (or better : when to use which one) are described - including examples - in a wiki, the rationale can be found here <INTERNAL_LINK>

The baseline (summarized in above wiki) goes pretty much in direction of using 2), ie. data modeling as often as possible. Thus, in discourse:

  • I would like advertize such modeling techniques
  • and on the other hand give others the option to discuss these issues - and of arguing differently
  • in other words : exchange information on best practices a as we started some time ago in <INTERNAL_LINK>

Hi Jürgen,

Impressive publication :smiley:

I am currently thinking about how to make engines more flexible. One topic is to make it very easy to transform A12 documents on-the-fly. You could use it to provide the same business data for different engines. I hope that this would enable projects to not have to choose between overview and form engine, but to be able to use both depending on the characteristics of the use case, e.g. amount of data.