Hi, Adam-
I really like this idea. Of course there are scripts out there that do
most (all?) of this, but exposing it as an interface seems useful to me.
I proposed something similar in my SVG Params spec [1][2][3], though
yours is better thought out. One difference is that I was specifically
looking at parameters, not merely as a function of the URL, but through
any mechanism that the language provides; for example, HTML can pass
parameters into a file referenced through the <object> element with
child <param> elements. Do you think there's some way to reconcile that
with your proposal?
[1] http://www.w3.org/TR/SVGParam/
[2] http://dev.w3.org/SVG/modules/param/master/SVGParam.html
[3] http://dev.w3.org/SVG/modules/param/master/SVGParamPrimer.html
Regards-
-Doug Schepers
W3C Team Contact, SVG and WebApps WGs
Adam Barth wrote (on 9/17/10 2:05 PM):
On Fri, Sep 17, 2010 at 10:27 AM, Adam Barth<[email protected]> wrote:
On Thu, Sep 16, 2010 at 3:25 PM, Darin Fisher<[email protected]> wrote:
On Thu, Sep 16, 2010 at 6:31 AM, Julian Reschke<[email protected]>
wrote:
That sounds good to me. In general I think it would be great if there were
standard APIs for URI/IRI construction, parsing and resolution...
Yes, that sounds pretty good to me too.
This has annoyed me for a while too. I'll write up a spec.
Here's a sketch:
https://docs.google.com/document/edit?id=1r_VTFKApVOaNIkocrg0z-t7lZgzisTuGTXkdzAk4gLU&hl=en
Adam
