Dominik Moritz

But this wouldn't, right? ```py x = alt.X('foo').title('foo') xx = x.title('bar') ```

In the last example, would this work? ```py x = alt.X('x').bin(maxbins=20) chart1 = alt.Chart(data).encode( x=x ) assert chart1.x.bin.maxbins == 20 xx = x.bin(maxbins=30) # does this work??? chart2 = alt.Chart(data).encode(...

I agree this api would be super nice and that breaking the access as you suggested makes sense. I guess there may be some benefit to maintaining backwards compatibility and...

Vega probably makes more sense. If you give me admin permissions, I can move it.

It would be great to get this update in so that the examples on the Altair website work again (https://github.com/altair-viz/vega_datasets/issues/43).

Did you want to make a release for Vega datasets 1 with versioned CDN links (I can't check right now so excuse me if you've already done it).

@jakevdp We actually support it with `resolve`. Check out https://github.com/vega/vega-lite/blob/master/examples/compiled/layer_bar_dual_axis.svg. However, you're right that it is a bit controversial and you have to be very careful when using independent scales.

@jakevdp I completely agree. There are bigger fish to fry. Usually, a second chart/ a faceted chart is better than a dual axis chart with different scales.

Sorry for not being very clear. I meant to say that I get errors because the browser tried to get data from `https://jakevdp.github.io/pdvega/...` instead of `https://altair-viz.github.io/pdvega/...`. ![screen shot 2018-11-19 at...

I absolutely agree that improving data serialization would be a huge improvement. The way I see it, Altair is a Python API to generate Vega-Lite specs and these specs can...