Ticket #177 (reopened task)
Implementation of notation tags in the renderer output
|Reported by:||clange||Owned by:||dmisev|
|Priority:||major||Milestone:||zzz Future zzz|
|Keywords:||Cc:||nmueller, cmueller, frabe, kohlhase|
|Due to close:||2008/12/08||Include in GanttChart:||no|
|Dependencies:||Due to assign:||2008/12/01|
Notation tags in the output of the renderer should point from the XML elements that the renderer created to the renderings that were responsible for this. That makes it easiest for interactive tools (JOBAD, editors) to go from the symbol under the cursor to the rendering that was used.
As the rendering element in a notation definition never has more than one PMML child, Michael suggested to add this information to that element, by introducing a special attribute, as we do for elision. (Why not call it "ec" for "extensional context" -- @Christine, any comments?) Imagine a rendering like
<rendering context="..." xml:id="nice"> <mrow> <render name="arg1"/> <mo>$$$</mo> <render name="arg2"/> </mrow> </rendering>
Then, the PMML output generated from applying this rendering should look something like:
<mrow ec="some/url#nice"> <!-- recursively rendered first argument --> <mo>$$$</mo> <!-- recursively rendered second argument --> </mrow>
If there are no objections against this ticket, it would override #149, concerning the notation tags in the output.