Open mdeagen opened 4 years ago
I think the complication with this is that data is handled slightly differently between the two, and data transformations are a lot more common in Vega.
On Wed, Sep 16, 2020 at 12:25 PM mdeagen notifications@github.com wrote:
This issue was discussed informally a while ago, but the SPARQL/Vega editor should support both Vega and Vega-Lite specifications. The type of specification is included in the $schema field of the specification.
The bug is that, if a Vega specification is inserted as the spec, the chart preview displays the text "Invalid Vega-Lite specification."
Vega support will enable more complex viz capabilities such as network/tree diagrams, isocontour plots, word clouds, etc.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/tetherless-world/whyis/issues/236, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAETCEPNG3K4ZHU4R6CAFT3SGDRIVANCNFSM4RPCXAXA .
-- Jamie McCusker (they/them/theirs)
Director, Data Operations Tetherless World Constellation Rensselaer Polytechnic Institute mccusj2@rpi.edu mccusj@cs.rpi.edu http://tw.rpi.edu
In that case, it would probably make sense to have a separate view for nm:VegaChart that would supersede the default view for sio:Chart (nm:VegaLiteChart).
Would be nice-to-have, but there are other resource views that should be prioritized above this (like sio:BibliographicResource).
This issue was discussed informally a while ago, but the SPARQL/Vega editor should support both Vega and Vega-Lite specifications. The type of specification is included in the $schema field of the specification.
The bug is that, if a Vega specification is inserted as the spec, the chart preview displays the text "Invalid Vega-Lite specification."
Vega support will enable more complex viz capabilities such as network/tree diagrams, isocontour plots, word clouds, etc.