Liam R E Quin:
> It's not really clear to me how to interpret (x, y, w, h) for SVG either
> - is it before or after scaling to fit an externally-supplied viewport?
> Are the units in inches or pixels or in the default coordinate space, or
> the coordinate space introduced by the top-level SVG element's viewport,
> or what? Making that clear would presumably also be a change to SVG.
We discussed in the SVG telcon today broadening SVG's id="" to allow
values other than XML Names, to align with HTML. That would mean we
would need to special case media fragment syntax and SVG view
specifications not to be interpreted as IDs, but I think that would be fine.
I don't think media fragments would "supersede" SVG, since we still need
#svgView(...) to work. So the SVG spec will need to be updated to
ensure we choose between interpreting the fragment as an SVG view
specification, a media fragment, or an ID. (Regardless of whether we
need to update the media type registration.)