Well, at first blush, the relationships can easily be used to generate
related links, displayed somewhere as determined by the rendering. I
tried to provide a few examples of different types of relationships that
could be possible between them.
For a more concrete example: Lets say you are building TDG. For the
reference pages assembly, you could relate all of the component pages
(book, part, preface, chatper, appendix, glossary, bibliography,
article) with a "component" relationship.
You could have another for section types, another for meta, etc.
It's a way of applying a taxonomy to content instances, if you will. The
See Also section in TDG, for example, could be generated from the
relationships and easily updated from one file, rather than maintained
at each content chunk.
I was just hoping we could demonstrate a simple example of it.
Best regards,
--Scott
Scott Hudson
Senior XML Architect
+1 (303) 542-2146 | Office
+1 (720) 663-SCOT [7268] | Gvoice
Scott.Hudson@flatironssolutions.com
http://www.flatironssolutions.com
On 11-Dec-09 2:35 PM, Norman Walsh wrote:
> Scott Hudson