[quote user="Barry Lothian"]Model name (Cell name) equivalent to what the text represents and contains 1 text element per cell[/quote]
That could work, but has disadvantages...
- Non-standard: nobody else uses that data structure
- Depends on explicit design of cells, possibly nested, each having a single text component
- You need your own API to find named cells and update the contained text element
- No reporting tools: text is still text
Tags have an existing, supported API that many of us understand. Once you take the text-in-cell approach, you're on your own. For example, using MicroStation's built-in tag tools, you can query a titleblock to see its data. Using text-in-cell there's no equivalent tool, other than eyeballing the text in MicroStation.
My main observation is that you've reinvented the wheel. Text-in-named-cell is another way of saying 'schema'. You've invented your own way to formalise data definition.