Alex: The browsers do support xml:base, and HTML5 describes the right behavior, but it's not clear what happens when you programmatically change the base URI.

14:18:33 [Norm]

...You actually have to find and re-resolve the URIs on the elements.

14:19:06 [Norm]

Murray: Are you suggesting that if you didn't rely on base URIs, that is if you provide the fully qualified URIs, that generally the browsers do what they need to do except for recursive XIncludes?

14:19:40 [Norm]

Alex: No. I'm saying that Firefox does the right thing. The other browsers I tested don't do the right thing. But that's a bug and I've filed them.

14:20:05 [Norm]

...And the HTML5 spec says that what Firefox is doing is the right thing.

14:20:43 [Norm]

...What's not supported is programmatically changing the base URI to effect descendent attributes. For example, after an img src has been resolved, changing the base URI on an ancestor won't cause the img src to be recomputed.

14:21:26 [Norm]

Murray: Are there utilities for doing base URI resolution? Like a unix filter that will expand URIs and give you back the fully qualified URIs?

14:21:59 [Norm]

Alex: You could *write* one. There isn't a standard API in the browser to do this.

14:22:11 [Norm]

Norm: XProc has a step to do this.

14:23:03 [Norm]

Alex: Because we have the base URI property, we can control it. What the host language does is up to them and should be made clear.

14:23:22 [Norm]

...We should make it clear that the right semantic is that you resolve the URI against the base URI of the element and xml:base controls that.

14:23:28 [Norm]

...There's no magic.

14:23:34 [Norm]

...That's pretty much what the HTML5 spec says.

14:24:55 [Norm]

Further discussion of the behavior of the base URI

14:32:28 [Norm]

Some discussion of what it means, or should mean, to change the xml:base value after a document is ... yeah, is what? parsed? rendered?

14:34:48 [Norm]

ACTION: Paul to put the discussion of dynamic changes to xml:base on the XML Core agenda

14:38:43 [Norm]

Topic: Transclusion in HTML5

14:39:38 [Norm]

Henry: This was background to Alex's concern in this area. Coming from a completely different perspective, the members of the team were saying that they need XInclude functionality without knowing it.

14:39:42 [Norm]

...It was really just as background.

14:40:00 [Norm]

...We'd had this discussion of whether XInclude should be int he profile we're hoping to sell to the browsers.

14:40:51 [Norm]

Murray: Years ago, I imagined a world where you could use entities to pass along secret messages. No one would rely in them so they wouldn't show up in most tools.

14:41:29 [Norm]

...But every now and then someone would read a document that used an entity to include a secret message.