14:46:08 RRSAgent has joined #html-xml
14:46:08 logging to http://www.w3.org/2011/01/11-html-xml-irc
14:46:10 Zakim has joined #html-xml
14:47:01 not sure yet whether I'll dial in
14:47:09 I have quite the headache
14:48:23 Ok. Thanks for letting me know. And I hope you feel better soon.
15:01:19 noah has joined #html-xml
15:01:26 Zakim, this will be xhtf
15:01:34 ok, darobin; I see XML_(TAG TF)10:00AM scheduled to start now
15:01:52 zakim, who is here?
15:02:04 XML_(TAG TF)10:00AM has not yet started, noah
15:02:14 On IRC I see noah, Zakim, RRSAgent, darobin, anne, hsivonen, Yves
15:02:50 weird
15:03:32 zakim, who is here?
15:03:46 XML_(TAG TF)10:00AM has not yet started, noah
15:03:52 On IRC I see noah, Zakim, RRSAgent, darobin, anne, hsivonen, Yves
15:04:01 jcowan has joined #html-xml
15:04:41 ok. Zakim didn't show me joining
15:04:45 Norm has joined #html-xml
15:05:38 zakin, who's here
15:05:42 zakin, who's here?
15:05:57 zakim, who's here?
15:06:02 XML_(TAG TF)10:00AM has not yet started, Norm
15:06:07 On IRC I see Norm, jcowan, noah, Zakim, RRSAgent, darobin, anne, hsivonen, Yves
15:06:29 MikeK has joined #html-xml
15:07:45 meeting: xml/html task force call of 11 Jan 2011
15:07:49 scribenick: noah
15:07:58 date: 11 january 2011
15:08:05 scribe: Noah Mendelsohn
15:08:09 chair: Norm Walsh
15:08:33 regrets: James Clark, Anne van Kesteren
15:08:45 mchampion has joined #html-xml
15:08:55 topic: Administrivia
15:09:08 NW: Next call will be in a week, on 18 January. Any regrets?
15:09:10 Silence.
15:09:31 topics: Use cases
15:10:00 Use case email was http://lists.w3.org/Archives/Public/public-html-xml/2010Dec/0064.html
15:10:08 NW: I've been somewhat out of touch, but have seen at least two interesting email threads: 1) xml in feeds and 2) how to detect html5
15:10:23 JC: XML or HTML?
15:10:35 NW: Well, some thread subjects said XML
15:11:01 we covered use cases 1 and 2. We didn't cover 3 and 4
15:11:50 Use case email was http://lists.w3.org/Archives/Public/public-html-xml/2010Dec/0064.html
15:12:02 Norm has joined #html-xml
15:12:20 topic: Use case #3, islands of HTML5-marked prose
15:12:29 From the email description of the use case:
15:12:35 3. I have an XML document and I want to embed islands of human prose
15:12:35 marked up with HTML5 in it because I want to be able to extract
15:12:35 those sections for use in, for example, documentation.
15:13:34 JC: In that environment, we don't have an HTML5 DOM, I think, so we don't have to deal with inconsistent DOMs
15:13:44 NW: Yes, mainly XML tools for this case.
15:14:05 JC: What limitations are there on HTML5? E.g., I know about noscript.
15:14:49 NW: (missed something about semantics) I was thinking about things like HTML5 rules that automatically add namespaces to SVG, and that won't happen in an XML toolchain.
15:15:28 JC: The XHTML5 elements mean the same as their like-named counterparts in HTML5, with the exception of NOSCRIPT
15:15:36 HS: Yes, and also ISINDEX
15:15:38 NW: Why?
15:16:12 domel has joined #html-xml
15:16:28 HS: Those are both sort of parser-managed things on the HTML side. ISINDEX as sort of a parser macro, is invalid into HTML5, and is invalid in that sense. It expands into other elements like a macro. NOSCRIPT depends on the context.
15:16:52 JC: How it's parsed depends on whether you have scripting.
15:17:25 NW: Thanks, good to know. Sounds like it's safe to set aside ISINDEX. Less sure about NOSCRIPT, but likely at worst a minor problem.
15:17:53 topic: Use case #4, HTML document with islands of XML
15:17:57 From the use case email
15:18:13 4. I have an HTML5 document and I want to embed islands of XML in it
15:18:13 because I want to be able to write JavaScript and CSS to manipulate
15:18:13 those elements, for example, in the browser.
15:19:14 NW: The HTML5 parser won't do the same thing as XML would if the element names are in the HTML5 language.
15:19:51 NW: I believe that the only workaround is to put the XML in a is parsed, and you only have a partial DOM. Seems not to make sense to do XSLT then. Hmm, but a DEFER script could make sense I guess.
15:41:13 JC: Could run multiple successively.
15:41:30 q+ to talk about circularity
15:41:39 ack MikeK
15:42:27 MK: Some of my points have been partly covered. There are a lot of potential XSLT processing scenarios, many of which can't be captured by