Ticket #181 (new potential innovation)
Dependencies between Renderings
|Reported by:||cmueller||Owned by:||vzholudev|
|Priority:||minor||Milestone:||zzz Future zzz|
|Keywords:||Cc:||nmueller, clange, kohlhase|
|Due to close:||Include in GanttChart:||no|
|Dependencies:||Due to assign:|
In my discussion with mathematician, I was pointed to the following use case that I have already discussed with Normen and Michael via eMail. I am attaching a description and their responses below. I am adding this use case as I believe that we might want to model dependencies between rendering e.g. to also support a scenario described by Christoph in ticket:178.
Request by a mathematician: A system should warn you if you want to reuse an already used notation or letter. This is a very critical aspect as we make use of a lot of symbols but only have a limited amount of notations/ letters. However, choosing could notation is essential for mathematical writings.
me: I assume that this services requires a notion of equality on the side of MathML expressions or rather renderings elements (of different prototypes) that produce the same MathML output and should thus not be used in combination.
Normen: This rather relates to consistency checking than to MoC, but, yes, that would be worthwhile. Sounds interesting, although I am not sure on which ntn constituent the equality should be defined.
me: I assume that a notation of equality on the side of prototypes allows us to find similarities of the represented objects, of the semantics of objects.
me: On the rendering side it helps to detect if there are very similar or even equal presentations for different symbols. Authors want to avoid that as it confuses the reader.
Michael: Since we have largely eliminated the choice of notations from the documents themselves to higher levels, I do not think that MoC has much to offer here. The consistency is guaranteed by the presentation process and the CoPs?, I would say.
me: I am by no means an expert of MoC, but I see it on different levels. Maybe Normen's work would not directly cover this kind of "consistency" checking. But we can build on his conceptual findings and technical support to provide MoC on other layers, i.e. during the rendering. So based on Normen's work it is easier for us to define equality between renderings (or the respective MathML expressions).