15:11:31 RRSAgent has joined #rdfa 15:11:31 logging to http://www.w3.org/2010/01/14-rdfa-irc 15:11:36 zakim, this will be rdfa 15:11:36 ok, manu; I see SW_SWD(RDFa)11:00AM scheduled to start in 49 minutes 15:11:55 rrsagent, make logs public 15:11:58 rrsagent, draft minutes 15:11:58 I have made the request to generate http://www.w3.org/2010/01/14-rdfa-minutes.html manu 15:12:13 Meeting: RDFa in XHTML Task Force 15:12:17 Chair: Manu Sporny 15:12:37 Present: Manu_Sporny, Ivan_Herman, Shane_McCarron 15:12:41 Regrets: Ben_Adida 15:13:10 Scribe: Shane_McCarron 15:15:23 Agenda: http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2010Jan/0031.html 15:15:40 Previous: http://www.w3.org/2010/01/07-rdfa-minutes.html 15:16:50 rrsagent, draft minutes 15:16:50 I have made the request to generate http://www.w3.org/2010/01/14-rdfa-minutes.html manu 15:58:06 ShaneM has joined #rdfa 15:58:41 SW_SWD(RDFa)11:00AM has now started 15:58:48 +??P0 15:58:51 zakim, I am ??P0 15:58:51 +manu; got it 15:58:56 zakim, dial ivan-voip 15:58:56 ok, ivan; the call is being made 15:58:57 +Ivan 15:59:05 Steven_ has joined #rdfa 15:59:49 +ShaneM 16:01:40 Scribe: ShaneM 16:01:50 TOPIC: Action Items 16:01:55 http://www.w3.org/2010/01/07-rdfa-minutes.html 16:02:05 zakim, dial steven-617 16:02:09 zakim, who is here? 16:02:12 ok, Steven_; the call is being made 16:02:20 +Steven 16:02:28 On the phone I see manu, Ivan, ShaneM, Steven (muted) 16:02:33 On IRC I see Steven_, ShaneM, RRSAgent, Zakim, manu, ivan 16:02:44 zakim, who is muted? 16:03:09 I see no one muted 16:03:32 ACTION:  Manu to aggressively push review of test cases via mailing list [recorded in http://www.w3.org/2009/10/29-rdfa-minutes.html#action08] [recorded in http://www.w3.org/2010/01/07-rdfa-minutes.html#action02] --done 16:03:52 --done 16:04:07 ACTION:  Manu to generate spec text for pulling in external vocabulary documents. [recorded in http://www.w3.org/2009/12/03-rdfa-minutes.html#action08] [recorded in http://www.w3.org/2010/01/07-rdfa-minutes.html#action03] 16:04:08 --done 16:04:12 http://rdfa.digitalbazaar.com/specs/rdfa-vocab-20100111.html 16:04:24 ACTION:  Manu to get in touch with LibXML developers about TC 142. [recorded in http://www.w3.org/2009/12/03-rdfa-minutes.html#action09] [recorded in http://www.w3.org/2010/01/07-rdfa-minutes.html#action04] 16:04:26 --continues 16:04:36 ACTION:  Mark to generate spec text for @token and @prefix [recorded in http://www.w3.org/2009/12/03-rdfa-minutes.html#action06] [recorded in http://www.w3.org/2010/01/07-rdfa-minutes.html#action05] 16:04:38 --continues 16:04:44 ACTION:  Mark to generate spec text for pulling in external vocabulary documents [recorded in http://www.w3.org/2009/12/03-rdfa-minutes.html#action07]on07! [recorded in http://www.w3.org/2010/01/07-rdfa-minutes.html#action06] 16:04:46 --continues 16:04:52 markbirbeck has joined #rdfa 16:05:12 TOPIC: Chartering process update 16:05:14 zakim, code? 16:05:14 the conference code is 7332 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), markbirbeck 16:05:27 ivan: nothing new to report 16:05:54 +??P34 16:06:00 zakim, i am ? 16:06:00 +markbirbeck; got it 16:06:24 ivan: deadline is coming up. Need to contact a few people before then so we ensure people who expressed interest have a change to sign up. 16:06:32 s/change/chance/ 16:13:26 TOPIC: RDFa Working Group Authoring Tools 16:14:55 zakim, mute me 16:14:55 sorry, Steven_, I do not know which phone connection belongs to you 16:15:04 zakim, I am Steven 16:15:04 ok, Steven_, I now associate you with Steven 16:15:05 manu: some members have been kicking ideas around privately. looking at reSpec and CVS + something external for diffs 16:15:11 zakim, mute me 16:15:11 Steven should now be muted 16:16:28 reSpec worked reasonably well for doing the Vocabulary document 16:16:52 ivan: other tool sets seem to require installing lots of stuff - high barrier to entry 16:18:28 markbirbeck: original thought was to use Ant so it was possible to run things on different platforms... but that doesn't seem compatible with the model. 16:18:34 ack me 16:19:13 q+ 16:19:37 q+ to ask if there is room to have it produce documents annotated with RDFa? 16:19:56 ivan: need to ensure that the references it produces are up to date 16:20:03 ack Steven 16:20:44 Steven_: only fear is how we are going to produce diff-marked versions. We need some way to produce these. 16:20:46 ack ShaneM 16:20:46 ShaneM, you wanted to ask if there is room to have it produce documents annotated with RDFa? 16:21:41 ShaneM: are you authoring in HTML or wysiwyg 16:21:47 ivan: HTML(5). 16:22:14 ivan: any RDFa that is put into the code would just stay there. 16:23:07 zakim, mute me 16:23:09 Steven should now be muted 16:23:27 ShaneM: can we have it produce XHTML? Its a permitted format. 16:23:37 manu: seems like it would be a simple change. 16:24:25 s/TOPIC/Topic/ 16:25:28 ShaneM: CVS has the ability to run scripts - so we can have diffs generated automatically as part of the checkin 16:26:12 manu: we don't have a solution for PDF or for multi-page documents. 16:26:22 zakim, who is muted? 16:26:22 I see no one muted 16:26:28 zakim, mute me 16:26:28 Steven should now be muted 16:27:14 manu: a multi-page document is a document that is split into sections with a master table of contents 16:27:30 ivan: not convinced we need this because our specs are relatively small. 16:27:44 manu: having both versions is nice. Not necessarily a high priority. 16:28:40 ShaneM: W3C already uses html2ps so... if we can identify the conventions that make that work it should be fine. 16:28:58 http://html5.digitalbazaar.com/specs/rdfa.html 16:29:00 ACTION: ShaneM to identify the requirements for html2ps and see about getting reSpec to support them. 16:29:21 Topic: HTML RDFa heartbeat draft 16:30:06 http://html5.digitalbazaar.com/specs/rdfa.html#preserving-namespaces-via-coercion-to-infoset 16:30:16 manu: specified rules for maintaining namespaces in the generated DOM. 16:30:39 manu: also added informative sections describing how infoset based and dom 2 based processors work 16:30:48 http://html5.digitalbazaar.com/specs/rdfa.html#infoset-based-processors 16:31:16 http://html5.digitalbazaar.com/specs/rdfa.html#dom-level-2-based-processors 16:32:09 feedback so far is fairly positive. no one is attempting to block publication at this time. 16:34:08 ShaneM: not excited about codifying implementation algorithms 16:34:37 manu: testing people from user agent vendors seem excited about understanding the implementation methodology to limit the possibility of incompatibilities in the future. 16:34:45 markbirbeck: likes it. 16:35:40 Topic: RDFa Vocabularies 16:36:18 http://rdfa.digitalbazaar.com/specs/rdfa-vocab-20100111.html 16:37:45 manu: Discussion about CORS 16:38:35 uncertain if CORS is actually implemented in major browsers. 16:40:42 ivan: if CORS is not available, this vocab proposal seems hard to support 16:41:26 markbirbeck: had a hack for Safari that would support doing cross site retrieval via an iframe - but that didn't work in other user agents. 16:42:41 markbirbeck: content negotiation should be part of the solution. there is no need for a rich new syntax. any existing syntax should be supportable. RDFa, HTML, JSON... 16:43:10 ivan: why doesnt cross domain security apply to JSON files? 16:44:13 markbirbeck: In the same way that you can get an image from any location into a page, you can refer to a script via an src attribute on another site. The code might not run, so you use something called JSONp. You return a function call, and the parameters are the data you want to get into the host application. 16:45:07 markbirbeck: would need a convention for emitting the right format (e.g. function call with parameters) 16:46:23 manu: concern about requiring a JSON parser then to handle vocabs. 16:46:25 document.meta.addMappings( { "foaf" : "http://..." } ); 16:47:50 markbirbeck: the base format doesn't preclude parsing by non-JS environments. just need to strip off the beginning bit and parse through the name value pairs 16:47:57 q+ 16:48:18 markbirbeck: this doesn't impact authors. It effects vocabulary creators and parsers. 16:48:51 ack ivan 16:49:14 q+ 16:49:48 ivan: no problem if what we say is that at a given URI we have a JSON file. There is support for JSON in other languages like Python already. 16:50:41 ivan: not as excited about content negotiation. Seems like this is an extra complication that we don't want to force our vocabulary authors to have to deal with. 16:51:49 manu: concern about how the information would get included in the document. 16:52:00