Application type | Template | Data |
---|---|---|
Invitation template | invitation.ott | Anne.xml |
Jean.xml | ||
Marcel.xml | ||
Pierre.xml | ||
Listing containing several blocks | Fiche_signaletique.ott | fiche_signaletique.xml |
Several looks from the same data | Section.ott | gedooo.xml |
Lignes.ott | ||
Colonnes.ott | ||
Etiquettes.ott | ||
Paragraphe.ott |
This table alone can demonstrate the very weak coupling between data and presentation. Indeed, you can consider several data flow for one template, which is relatively common with merge/mailing applications, but you can also consider several templates for the same data flow.
The OpenOffice.org user can create templates without knowing the data model of the application. He has just to know the structure of the information he want to present.
The developer or the power user responsible of the data extraction doesn't care about the information presentation. He has just to agree with the OOo user about the structuring of the information.