This also has the advantage that it maps to database table easier. It also makes some kinds of processing easier (no boundary detection). However, it can produce horrible document instances. I have seen multiple examples where this kind of approach trebled the number of elements and at least doubled the depth and perhaps doubled the amount of markup.
It needs to be balanced against human factors: xml is already not super terse, so adding extra levels willy nilly will not improve it.
Cheers
RickOn 21/11/2013 10:19 AM, "Costello, Roger L." <costello@mitre.org> wrote:Hi Folks,
I am reading the book that Sean McGrath recommended [1] on Jackson Structured Design. Wow, I am discovering that this book is really about XML design (and it was written in 1979).
Here are some fantastic things I've learned:
1. Böhm and Jacopini proved in 1966 that all programming problems can be solved by using only three program component types: sequence, iteration, selection.
2. Dijkstra has pointed out that data can be described by using the same types of component.
3. Design the data structure, then design the program to match the data structure.
4. The data structures control the program structure.
5. Design the data to model the end user's real world.
6. When the program structure is based upon the data structures, then the program is firmly established in the real world.
7. Programming technique is alien to the end user. The end user's demands start from the end user's real world. The program structure must reflect this real world.
8. Component types (sequence, iteration, selection) may be mixed. However, you must make sure that each XML element belongs to one and only one of the three component types.
Examples:
a. Good: BookStore consists of a list of Book elements.
<BookStore>
<Book>...</Book>
<Book>...</Book>
...
</BookStore>
BookStore is of the iteration (list) type.
b. Bad: BookStore consists of a sequence of Location and list of Book elements.
<BookStore>
<Location>...</Location>
<Book>...</Book>
<Book>...</Book>
...
</BookStore>
This is bad because BookStore is both an iteration and a sequence type. Don't mix component types in an element!
c. Good: BookStore consists of a sequence of Location and Books element. Books consists of a list of Book elements.
<BookStore>
<Location>...</Location>
<Books>
<Book>...</Book>
<Book>...</Book>
...
</Books>
</BookStore>
Now BookStore is of the sequence type and Books is of the iteration (list) type. Each are of just one component type - good!
Jackson Structured Design tells us how to do XML design. Neat!
/Roger
[1] JSP A Practical Method of Program Design by Leif Ingevaldsson
_______________________________________________________________________
XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.
[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php