See also: IRC log
http://www.w3.org/2010/html-xml/2011/02/01-agenda
Accepted.
-> http://www.w3.org/2010/html-xml/2011/01/25-minutes
Accepted.
The task force notes with regret Michael Kay's decision to resign from the task force.
We thank him for his efforts.
Norm: That was Michael Kay's but he's not likely to finish it now.
MChampion: I was never sure why
that was a separate use case from case 4, XML in HTML.
... What's special?
Henri: I think one of the main
differences between XForms and other XML is that an island is
generally understood to be one subtree somewhere.
... SVG and MathML are self-contained subtrees. XForms
intermingles with the source tree and the semantics.
Norm: I don't feel competent to speak about XForms, does anyone?
MChampion: I'll take a stab at
it.
... Was there any discussion of a solution?
... Other than namespaces?
John: Yes: don't. Politely described as "managing expectations".
Henri: Specifically about XForms,
rather than the general issue of widespread vocabulary mixing,
there are a couple of solutions.
... IBM and web backplane have a JavaScript solution that
serves invalid HTML and then fixes it up with JavaScript
... Orbeon and Lotus also have server-side solutions.
Norm: There are also client-side solutions that work in a similar way, such as XSLTForms
MChampion: Sorry to interrupt the agenda, but I see the TAG is talking about this next week, does anyone know what that's about?
Norm: Oh, sorry, I should have said. Since their f2f meeting is nearby, I agreed to come in and give an update. I don't think there's likely to be more to it than that, but I couldn't say for sure.
<Yves> the TAG agenda is indeed mostly a status report
Norm: I think this was Noah's new
one from last week.
... I think this nets out to XML with error recovery or XHTML
with error recovery.
Anne: His use case was more a generic one of mine.
Norm: It could be done, but I'm not sure what else to say. It couldn't be the same error recover as HTML, I assume, because it would know less about the tags.
Anne: Yes, that sounds right to me.,
MChampion: I meant to update use case 2, but I haven't gotten to it yet.
Henri: For research and documentation purposes, I did a small demo of XML in HTML using the script tag.
<hsivonen> http://hsivonen.iki.fi/test/moz/xml-data-block.html
Norm: Thanks, Henri, that's very cool. You said it works in latest Firefox, Opera, Chrome, Safari, and IE9.
Henri: The latest version of all the top browsers.
Norm: I started with use cases
because it wasn't clear what else we could do. Now we have the
use cases and solutions, to some extent, for them.
... Is the answer to the question what is the problem, "there
is no problem."
John: There are solutions but they aren't written down.
Henri: I think writing them down would be a good next step.
Norm: Does anyone have any other thoughts for next steps?
John: We need an editor.
Norm: I'll take a first stab at that..
Anne: The use cases are quite disjoint; they don't really overlap that much; they're all different kind of problems.
John: True
Norm: Yes, I think there's an editorial challenge there, but there are different problems and they'll have to be described differently.
Henri: I think the nature of the use cases we found happens to be that they are rather disjoint. That's just the nature of the beast.
Norm: I propose we meet in two weeks, on 15 February, with, I hope, a document to review.
Adjourned.