Why is the XSLT ecosystem not widely associated with data visualization? -


in 2011, mike bostock, 1 of creators of d3.js remarked on xslt:

xslt’s approach elegant, simple transformations: without high-level visual abstractions, nor flexibility of imperative programming, xslt cumbersome math-heavy visualization task (e.g., interpolation, geographic projection or statistical methods).

at time of writing question, xslt has gone through 2 major revisions, yet still not associated term 'data visualization'.

why? top few concise , concrete reasons, please, perhaps supported line or 2 of code. want better understand shortfalls central it's lack of appeal. 2 or 3 should suffice.

if mike's comments still valid, please so. again, example or 2 helpful.

should prefer little more context answers:

  • thanks tight, local bindings between data , presentation, d3.js has raised expectation quality data-driven applications can made respond dynamically , changes in data set. may think xslt ecosystem characteristics directly impede kind of behavior.

  • is xslt-controlled synchronization of transformations across multiple svg models, example in (from musicxml , other models) music notation -> dynamic score playback -> interactive instruments or theory tools) feasible? if no, in laser sharp sentence or two, why not?

btw, found useful hints among answers earlier (but wooly) question, don't specifics.

imo, because xml basic format persistance , exchange replaced json based styles. change xml related techniques xslt lost focus. think number of real-life xls-fo solutions example development.


Comments

Popular posts from this blog

Is there a better way to structure post methods in Class Based Views -

performance - Why is XCHG reg, reg a 3 micro-op instruction on modern Intel architectures? -

jquery - Responsive Navbar with Sub Navbar -