This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Can XSLT help with overlapping structures (was: XML slice design)


In some cases it actually makes sense to markup two overlapping structures.
This is however a problem in XML (and SGML for that matter) because of the
nesting rules. When working with TEI I encountered two possible ways of
solving the problem of overlapping structures: using empty elements to mark
one of the structures (used by Sydney), for example page breaks, or using
elements that you indicate as being interrelated and together representing
an element in one of the structures. (In TEI I used SPANs for this)

In Sydney's case this method would look something like this: 

<div type="chapter">
<page nr="1"><!-- or span type="page" nr="1" -->
<p>...</p>
</page>
<div type="part">
<page nr="1">
<p>...</p>
<note>...</note>
<list><item>...</item></list>
</page><!-End of first page -->
<page nr="2">
<qa>...</qa>
</page><!-End of second page -->
</div>
<div type="part">
<page nr="3">
<p>...</p>
<note>...</note>
</page><!-End of third page -->
</div>
</div>

Maybe there are similar, but more elegant solutions. In this case you could
create output pages based on page numbers: create a new output page for each
new number. 

But still ... it wouldn't be easy to create page-based output from this
using XSLT, would it? 

Linda


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]