Parse out the actionable tasks from review 4
Reading it again, it's probably the list in the summary:
it remains largely unclear what tasks are left to programmers
it remains largely unclear how exactly the framework should fit in a visualization library
the provided examples and discussion are not convincingly addressing the claimed benefits
the presentation of the mathematical framework lacks clarity for readers less familiar with theory on mappings from data to visualition and the leveraged topological concepts
Also think this suggestion could be a brilliant way to highlight the math vs semantics split
For the purpose the authors address, ignorance of semantics is fine. The consequences of this limitation become evident in the example shown in Figure 7. To solve the violation of equivariance, it would be perfectly sound mapping "rain" to the "closed umbrella", yielding v(rain) = v(storm) and thus reestablishing equivariance. However, in this case, the opened umbrella would never be rendered to the screen.
Parse out the actionable tasks from review 4 Reading it again, it's probably the list in the summary:
Also think this suggestion could be a brilliant way to highlight the math vs semantics split