W3C home > Mailing lists > Public > public-html-xml@w3.org > February 2011

HTML/XML TF Minutes 1 Feb 2011

From: Norman Walsh <ndw@nwalsh.com>
Date: Tue, 01 Feb 2011 11:31:08 -0500
To: public-html-xml@w3.org
Message-ID: <m24o8nd8dv.fsf@nwalsh.com>
See http://www.w3.org/2010/html-xml/2011/02/01-minutes


                                   - DRAFT -

                              HTML/XML Task Force

Meeting 6, 01 Feb 2011


   See also: [3]IRC log


           Norm, John, Henri, Yves, Michael





     * [4]Topics

         1. [5]Accept this agenda?
         2. [6]Accept minutes from the previous meeting?
         3. [7]Use case 06
         4. [8]Use case 7: Forgiving error handling for XHTML-style markup
         5. [9]Changes to other use cases in the past week
         6. [10]Next steps?
         7. [11]Any other business?

     * [12]Summary of Action Items


  Accept this agenda?



  Accept minutes from the previous meeting?

   -> [14]http://www.w3.org/2010/html-xml/2011/01/25-minutes


   The task force notes with regret Michael Kay's decision to resign from the
   task force.

   We thank him for his efforts.

  Use case 06

   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

  Use case 7: Forgiving error handling for XHTML-style markup

   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

   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.,

  Changes to other use cases in the past week

   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> [15]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.

  Next steps?

   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

   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.

  Any other business?

   Norm: I propose we meet in two weeks, on 15 February, with, I hope, a
   document to review.


Summary of Action Items

   [End of minutes]


    Minutes formatted by David Booth's [16]scribe.perl version 1.135 ([17]CVS
    $Date: 2011/02/01 16:29:52 $


   Visible links
   1. http://www.w3.org/
   2. http://www.w3.org/2010/html-xml/2011/02/01-agenda
   3. http://www.w3.org/2011/02/01-html-xml-irc
   4. http://www.w3.org/2010/html-xml/2011/02/01-minutes#agenda
   5. http://www.w3.org/2010/html-xml/2011/02/01-minutes#item01
   6. http://www.w3.org/2010/html-xml/2011/02/01-minutes#item02
   7. http://www.w3.org/2010/html-xml/2011/02/01-minutes#item03
   8. http://www.w3.org/2010/html-xml/2011/02/01-minutes#item04
   9. http://www.w3.org/2010/html-xml/2011/02/01-minutes#item05
  10. http://www.w3.org/2010/html-xml/2011/02/01-minutes#item06
  11. http://www.w3.org/2010/html-xml/2011/02/01-minutes#item07
  12. http://www.w3.org/2010/html-xml/2011/02/01-minutes#ActionSummary
  13. http://www.w3.org/2010/html-xml/2011/02/01-agenda
  14. http://www.w3.org/2010/html-xml/2011/01/25-minutes
  15. http://hsivonen.iki.fi/test/moz/xml-data-block.html
  16. http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
  17. http://dev.w3.org/cvsweb/2002/scribe/

Received on Tuesday, 1 February 2011 16:31:43 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:58:27 UTC