The way I think of it: o The DRI document is a bag into which various Aspects throw possibly-useful data for which they are responsible.
o The Theme selected for a page *consumes* the DRI document and writes a new XHTML document, possibly using data which it has picked out of the DRI document. o The DRI document has structure so that *Themes* can navigate it. That structure has no essential connection with the structure of the final page rendered to the user. Themes do selection and layout. o There are DRI elements whose names sound like those of XHTML elements, but e.g. dri:div and xhtml:div are not the same object and instances can be related in any way that is useful to the Theme. The DRI document is a very abstract idea of what the final page may contain. The point of having an intermediate representation is to separate content generation from page layout. -- Mark H. Wood, Lead System Programmer [email protected] Asking whether markets are efficient is like asking whether people are smart.
pgpHDaz4ZfI8w.pgp
Description: PGP signature
------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
