[Phoenix] UniZH sample broken with regard to location paths

[Thomas Comiotto]

Hi Andi

>
> So, just to be clear: on your system, document/content is in a 
> namespace then, no?
>

No it's not. What lenya is doing is to envelope

  - document source
  - navigation
  - metadata (sometimes)

by a null namespaced root fragment like this

<document>
   <navigation xmlns="nav" xmlns:nav="nav">
     ..
   </navigation>
   <content>
     <documentsource xmlns="foo" xmlns:foo="foo">
       <bar/>
     </documentsource>
   </content>
</document>

This envelope is not editable of course, so the current unizh neutron 
implementation uses a view template:

<document>
   <navigation>
     ..
   </navigation>
   <content>
     <xi:include href="foo.xml"/>
   </content>
</document>

If the unizh sample is to be fixed then by adding the missing view 
template. BTW, the yulup sourcenode resolver does not account for view 
templates yet but that's easy to add:

  - check if a view template is provided. Implemented
  - if so, aggregate the template. Implemented
  - apply the sourcetagger to the template instead of the source (keep 
in mind that the stylesheet fits the aggregated template). Implemented
  - _yulup_location_path data will correspond to the aggregated template 
now. To obtain a source location path you need to extract the relevant 
path segments by a template lookup mechanism that removes template 
specific location path segments - this should support multiple document 
sources (currently not possible because neutron lacks resource 
identifiers). Not yet implemented

--
Bests
Thomas