Hi Felix, Mmmm... Your proposal sounded good to me first. Then I thought what if we have several <rules> elements? Then some of the 'xlinked' rules need to be processed before some of the embedded rules since we are processing the <rules> in the order we find them. For example we have: <file> <head> <its:rules xlink="xlinkedrules1.xml" ...> <its:translateRule embeddedrule1 .../> </its:rules> <head> ... <footer> <its:rules xlink="xlinkedrules2.xml" ...> <its:translateRule embeddedrule2 .../> </its:rules> </footer> <file> The precedence order would be: Embeddedrule2 Xlinkedrule2 Embeddedrule1 Xlinkedrule1 Then any external rule associated with tool specific mechanism So we should really have: ----- 2- Global selections in documents (using a rules element) Inside each rules element the precedence order is: a- Any rules inside the rules element b- Any rules linked via the XLink href attribute 3- Global selections in an external file (using a rules element), linked via a tool-specific mechanism ----- Actually this a and b is also valid for #3. maybe there is a better way to express this? -yvesReceived on Friday, 12 January 2007 13:52:09 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:12:48 GMT