16:00:23 RRSAgent has joined #grddl-wg 16:00:23 logging to http://www.w3.org/2006/12/20-grddl-wg-irc 16:00:32 Zakim, read agenda from http://www.w3.org/2001/sw/grddl-wg/weekly-agenda 16:00:32 working on it, DanC 16:00:33 agenda+ Convene GRDDL WG meeting of 2006-12-06T11:00-0500 16:00:34 agendum 1 added 16:00:36 agenda+ Test cases for GRDDL with XML documents 16:00:37 agendum 2 added 16:00:40 agenda+ [#issue-output-formats] [DONE?] whether GRDDL transformations may produce RDF in a format other than RDF/XML 16:00:46 agendum 3 added 16:00:47 agenda+ GRDDL and (non-XML) HTML 16:00:48 agendum 4 added 16:00:49 agenda+ Cross-document Introduction 16:00:50 agendum 5 added 16:00:51 agenda+ [#issue-mt-ns] 16:00:52 agendum 6 added 16:00:54 agenda+ [#issue-base-param] 16:00:56 agendum 7 added 16:00:58 agenda+ Primer Document 16:01:02 agendum 8 added 16:01:04 agenda+ GRDDL Spec: General issues 16:01:06 agendum 9 added 16:01:10 done reading agenda, DanC 16:01:19 +DanC 16:01:39 Meeting: GRDDL Weekly 16:01:43 Scribe: briansuda 16:02:15 Zakim, who's on the phone? 16:02:15 On the phone I see ??P0, Chimezie_Ogbuji, DanC 16:02:18 Zakim, +[IPcaller] is briansuda 16:02:18 sorry, briansuda, I do not recognize a party named '+[IPcaller]' 16:02:29 Zakim, +[??P0] is briansuda 16:02:29 sorry, briansuda, I do not recognize a party named '+[??P0]' 16:02:30 yup 16:02:33 Zakim, ??P0 is briansuda 16:02:33 +briansuda; got it 16:02:37 yes 16:03:37 Agenda: http://lists.w3.org/Archives/Public/public-grddl-wg/2006Dec/0063.html 16:03:44 RRSAgent, draft minutes 16:03:44 I have made the request to generate http://www.w3.org/2006/12/20-grddl-wg-minutes.html DanC 16:03:54 RRSAgent, make record world-access 16:04:37 +??P18 16:05:06 Zakim, take up item 1 16:05:07 agendum 1. "Convene GRDDL WG meeting of 2006-12-06T11:00-0500" taken up 16:05:21 links works for me 16:05:31 RRSAgent, draft minutes 16:05:31 I have made the request to generate http://www.w3.org/2006/12/20-grddl-wg-minutes.html DanC 16:06:02 Zakim, who's on the phone? 16:06:02 On the phone I see briansuda, Chimezie_Ogbuji, DanC, ??P18 16:06:11 Zakim, ??P18 is HarryH 16:06:11 +HarryH; got it 16:06:26 yeah, i'm fie 16:06:54 agenda points to http://www.w3.org/2006/12/13-grddl-wg-minutes.html 16:08:53 regrets: BrianS, danja 16:08:54 Zakim, next item 16:08:54 agendum 2. "Test cases for GRDDL with XML documents" taken up 16:09:14 Zakim, open item 1 16:09:14 agendum 1. "Convene GRDDL WG meeting of 2006-12-06T11:00-0500" taken up 16:09:41 RESOLVED to approve http://www.w3.org/2006/12/13-grddl-wg-minutes.html as a true record 16:09:58 Zakim, next item 16:09:58 agendum 1 was just opened, HarryH 16:10:03 Zakim, close this item 16:10:03 agendum 1 closed 16:10:04 I see 8 items remaining on the agenda; the next one is 16:10:05 2. Test cases for GRDDL with XML documents 16:10:06 Zakim, next item 16:10:06 agendum 2. "Test cases for GRDDL with XML documents" taken up 16:12:11 ACTION: Fabien to post to sawsdl list relevant questions about RDF mapping and relationship to GRDDL [CONTINUES] 16:12:14 benadida has joined #grddl-wg 16:12:26 +benadida 16:12:44 http://esw.w3.org/topic/HCLS/POMROntology 16:13:36 Chime: xml primer example use-case, lightweight ontology for medical records 16:14:00 http://esw.w3.org/topic/HCLS/POMROntology#head-b91a931fb7855e7073e795b75ca71b550ed1e4c3 16:14:14 This would fulfill Dave Booth's request in our comments list: http://lists.w3.org/Archives/Public/public-grddl-comments/2006OctDec/0000.html 16:14:27 Chime: GRDDL transform, HL7 document -> RDF 16:14:41 +Murray_Maloney 16:16:11 Dan, how to fit GRDDL transformation into the document without breaking the schema? 16:16:22 namespace document is a URN, which is a slight problem. 16:16:45 Chime: schema might be closed. 16:16:58 Chime: But we could use schema annotations, don't think schema is closed to import infoitems from other namespaces. 16:17:35 Harry: plain XML would be a nice addition to the primer 16:18:05 Harry: ian is ok with additions to the primer document 16:18:19 Dan: check it into the test suite 16:18:29 ACTION: Chime's add HL7 plain XML health care use-case and check it into test suite. 16:18:54 Zakim, close this item 16:18:54 agendum 2 closed 16:18:55 I see 7 items remaining on the agenda; the next one is 16:18:56 3. [#issue-output-formats] [DONE?] whether GRDDL transformations may produce RDF in a format other than RDF/XML 16:18:58 Zakim, open item 3 16:18:58 agendum 3. "[#issue-output-formats] [DONE?] whether GRDDL transformations may produce RDF in a format other than RDF/XML" taken up 16:19:39 ACTION: DanC to add N3/turtle mime type to Atom/turtle test case. noting the unregistered status [CONTINUES] 16:19:46 Zakim, who is on the phone? 16:19:46 On the phone I see briansuda, Chimezie_Ogbuji, DanC, HarryH, benadida, Murray_Maloney 16:19:52 ACTION:DanC to write rules about XSLT 1.0 processing [CONTINUES] 16:20:22 Ben: in RDFa html metadata by providing transforms, microformats -> RDFa 16:20:50 keeps the RDFa in the DOM, so you can grab individual items 16:21:11 use GRDDL like mechanism to make RDFA 16:21:28 can this be done with the current GRDDL spec? 16:21:51 we could test this with the current test suite impl.. 16:22:15 Ben: output-issue might solve this problem 16:22:40 Ben: requires clients to request RDFa output of given profile 16:23:24 http://www.w3.org/2004/01/rdxh/spec#issue-output-formats is technically still open. 16:23:26 Dan: GRDDL transformation pointer, source document => HTML/RDFa 16:23:53 Ben: author must use specific profile to make a transformation to RDFa 16:24:07 the agent/client needs some way to know how to parse as RDFa 16:24:36 Ben: how would the client know what transformation to use? RDF, turtle or HTML? 16:25:19 Harry, browser would decipher the transformation and look for RDFa results 16:25:41 murray: GRDDL tells us how to find 1 or more transformations 16:25:50 agent is RDFa aware and GRDDL aware 16:26:15 q+ 16:26:18 agent is able to look into class attributes, link element has special @class 16:26:38 chime: RDFa, does it have a specific mimeType? 16:27:03 Ben: no special mimeType - schema or DTD instead 16:27:51 Ben: DTD mostly - murray's direction is a good one 16:28:19 find the RDFa transformation, can be done with various javascript libs 16:29:09 murray: to identify a grddl transformation can be in a LINK element 16:29:48 Dan: hCard page, profile="hcard uri here", this works for GRDDL transform 16:30:50 Murray, namespace transformation keyword, profile transformation keywork... HTML profile document could have link element with special class name for RDFa URI 16:31:24 RDFa aware user agant can follow its nose and find the correct LINK/REL uri and do correct transformation 16:31:28 that's a very specific follow your nose scenario 16:32:12 Dan: worries about choosing a good class attribute 16:32:48 (I'm worried about squatting on the author's choice of class attribute values) 16:33:17 Harrry, run all transformation, user agent chooses the right output it wants 16:33:47 murray, try not to complicate GRDDL by using existing attributes in HTML namespace 16:35:00 (brian, to attribute a comment to somebody, use a colon, not a comma) 16:36:34 Harry: mimeType for HTML RDFa not part of GRDDL 16:36:57 Ben: differenciate between transforms and/or type the transforms 16:37:32 Dan: run the transform and see what you get instead of typing 16:38:08 Ben: annotate transformation or not? 16:38:50 Annotate the transformation pre-running it 16:39:11 murray: leave it up to the agents to discover the annotation 16:39:48 Dan: GRDDL spec says all are relevant, but if you only want to run certain ones, go ahead 16:40:18 (ben, as fodder for hGRDDL testing, there's an existing hCard test: http://www.w3.org/2001/sw/grddl-wg/td/testlist2#hcard1 ) 16:40:20 ACTION: BenA to write a sample hGRDDL transformation 16:41:17 (yes, output formats is closed: http://lists.w3.org/Archives/Public/public-grddl-wg/2006Dec/att-0011/06-grddl-wg-minutes.html__charset_us-ascii ) 16:41:40 (though there are some pending actions) 16:42:06 murray: RDFa, transformation that converts to 'augments HTML RDFa with notations' 16:42:32 wouldn't you want ALL the RDF to annotate ALL of it back into HTML? 16:43:11 Ben: this could be done by keeping other GRDDL pointers 16:43:45 Dan: not all the transformation tell you where an RDF triple belongs back into the HTML 16:44:19 Zakim, next item 16:44:19 agendum 4. "GRDDL and (non-XML) HTML" taken up 16:44:28 Zakim, next item 16:44:28 agendum 4 was just opened, HarryH 16:44:37 Zakim, open item 5 16:44:37 agendum 5. "Cross-document Introduction" taken up 16:46:57 harry: pending edit, to remove the words "scrapping" 16:48:23 ACTION: HarryH to make sure edit "scraping" edit is. 16:48:36 Zakim, close this item 16:48:36 agendum 5 closed 16:48:38 I see 5 items remaining on the agenda; the next one is 16:48:39 Zakim, next item 16:48:40 4. GRDDL and (non-XML) HTML 16:48:41 agendum 4. "GRDDL and (non-XML) HTML" taken up 16:48:47 Zakim, open item 5 16:48:47 agendum 5. "Cross-document Introduction" taken up 16:49:15 Harry: what do do about this without Ian? 16:50:22 Dan: spec pretty much remains the same, otherwise the primer doesn't get the introduction 16:50:50 Murray: happy to withdraw the cross-document intro 16:51:38 ACTION: Ian to reconsider comments on cross-document introduction [WITHDRAWN] 16:51:51 Zakim, open item 6 16:51:51 agendum 6. "[#issue-mt-ns]" taken up 16:52:21 murray: given a doc with a DTD or schema or xinclude.... 16:52:53 (the HTML DTD has a default 'rect' attribute) 16:53:01 xinclude agumnets document if it is realized 16:53:25 XSLT may or maynot be all of the values if it were xinclude processed 16:53:45 might return two different RDF graphs given if or if not the includes are included 16:53:55 people have to deal with it themselves, or 16:54:11 MUST do things so you get what the author intended 16:54:18 with XI namespace 16:54:55 transformation in xi namespace, so that xinclude were incountered - discover it, and add something into result 16:55:32 I think there's a problem the xi namespace is not usually the root element. 16:55:33 DanC pointer? 16:55:40 Subject: XInclude or Not, that is the question 16:55:40 Date: Thu, 23 Nov 2006 12:24:30 -0500 (11:24 CST) 16:56:07 murray: authors intention to get with xinclude expanded 16:57:32 xinclude namespace is in the document 16:57:46 not in the same namespace, follow you nose for the subtree? 16:57:55 Dan: different GRDDL design 16:58:33 murray: not xi namespace, but explain 16:59:01 simple transform which you can include and make the result graph aware that you missed an xinclude 16:59:23 Dan: if you want you transformation to do xinclude, then make your transformations do xinclude 16:59:46 harry: not mandate any further xml processing, but instead make recommendations 17:00:17 murray: if we add a paragraph, about issues and problems 17:00:22 in the spec 17:00:56 Chime: we currently recomment xproc 17:01:04 +1 PROPOSAL: The GRDDL WG does not mandate XInclude and further XML on the source document is wanted to be run before the transformation to RDF, and write a caveat in the specification recommending XPROC when XInclude if this is the case. 17:01:12 The GRDDL WG does not mandate XInclude and further XML processing on the source document is wanted to be run before the transformation to RDF, and write a caveat in the specification recommending XPROC or using (or something like Murray's xinclude transformation) when this is the case. 17:02:18 +1 The GRDDL WG does not mandate XInclude and further XML processing on the source document is wanted to be run before the transformation to RDF, and write a caveat in the specification recommending XPROC or using (or something like Murray's xinclude transformation) when this is the case. 17:03:09 hmm... faithful-infoset 17:03:24 PROPOSAL: The GRDDL WG does not mandate XInclude and further XML processing on the source document before the transformation to RDF, and write a caveat in the specification recommending XPROC when this is the case. 17:03:40 harry: what exactly is the mimetype issue now? 17:03:46 PROPOSED: to add issue faithful-infoset (split it out of issue-mt-ns) and close it a la: The GRDDL WG does not mandate XInclude and further XML processing on the source document before the transformation to RDF, and write a caveat in the specification recommending XPROC when this is the case. 17:04:03 not me 17:04:17 not me, but I'm comfortable abstaining 17:04:20 brian, you'd rather think more? you'd rather abstain? 17:04:24 abstain 17:05:30 " 17:05:30 I don't know if this has been mentioned before, but that rather than us 17:05:30 trying to give a definitive answer on xinclude processing, we could 17:05:30 leave it to the publisher. " -- McBride 17:05:37 Wed, 13 Dec 2006 09:16:51 -0000 17:06:50 RESOLVED: to add issue faithful-infoset (split it out of issue-mt-ns) and close it a la: The GRDDL WG does not mandate XInclude and further XML processing on the source document before the transformation to RDF, and write a caveat in the specification recommending XPROC when this is the case. (benA and BrianS abstaining) 17:07:17 ACTION: Murry to draft paragraph giving us caveat for faithful infoset issue closure. 17:07:23 Zakim, next item 17:07:23 agendum 4. "GRDDL and (non-XML) HTML" taken up 17:07:34 Zakim, close item 4 17:07:36 Zakim, open item 7 17:07:38 agendum 4, GRDDL and (non-XML) HTML, closed 17:07:42 I see 3 items remaining on the agenda; the next one is 17:07:47 7. [#issue-base-param] 17:07:48 agendum 7. "[#issue-base-param]" taken up 17:08:15 PROPOSAL: Given that a base URI parameter is a parameter whose value is the base URI of the source document, the WG RESOLVES not to define a base URI parameter for transforms. 17:08:32 Dan: is ok, and results in no edits to spec 17:08:57 eRDF uses base-construct 17:09:27 harry: can't change base-parameter 17:09:50 harry: defining default para 17:10:20 http://www.w3.org/2001/sw/grddl-wg/td/testlist1#baseURI 17:10:37 -Murray_Maloney 17:11:24 RESOLVED: Given that a base URI parameter is a parameter whose value is the base URI of the source document, the WG RESOLVES not to define a base URI parameter for transforms. 17:11:44 http://lists.w3.org/Archives/Public/public-grddl-wg/2006Dec/0028.html 17:11:52 ACTION: Harry to check in Bwm's test case: http://lists.w3.org/Archives/Public/public-grddl-wg/2006Dec/0028.html 17:12:37 Zakim, open item 8 17:12:37 agendum 8. "Primer Document" taken up 17:12:39 -Chimezie_Ogbuji 17:13:04 BrianS - are you available in 2 hours or so? 17:13:07 sure 17:13:15 OK, let's try to finish some of this off then :) 17:13:32 ACTION: Harry and Brian to rewrite second part of primer to use Brian and Dan's instance data. See message from Brian and message from Harry. [CONTINUES] 17:13:45 Zakim, open item 9 17:13:45 agendum 9. "GRDDL Spec: General issues" taken up 17:14:00 (hmm... when to do another release of the GRDDL primer WD?) 17:14:36 harry: next meeting will be... 17:14:45 Topic: Next Meeting 17:14:53 RESOLVED: to cancel 27 Dec 17:15:09 anybody _want_ to meet on 3 Jan? 17:15:10 Does anyone want to meet on 3rd? 17:15:18 not perticularly 17:15:21 RESOLVED: to cancel 3 Jan 17:15:32 Next meeting: Janurary 10th 17:15:38 Zakim, pick a scribe 17:15:38 Not knowing who is chairing or who scribed recently, I propose benadida 17:15:42 Zakim, who's on the phone? 17:15:42 On the phone I see briansuda, DanC, HarryH, benadida 17:16:19 RESOLVED: to meet next 10 Jan, benadida to scribe 17:16:42 sure 17:16:48 ADJOURN 17:16:54 RRSAgent, draft minutes 17:16:54 I have made the request to generate http://www.w3.org/2006/12/20-grddl-wg-minutes.html DanC 17:16:58 -benadida 17:16:59 -HarryH 17:17:15 Chair: HarryH 17:17:18 RRSAgent, draft minutes 17:17:18 I have made the request to generate http://www.w3.org/2006/12/20-grddl-wg-minutes.html DanC 17:17:28 Zakim, list attendees 17:17:28 As of this point the attendees have been Chimezie_Ogbuji, DanC, briansuda, HarryH, benadida, Murray_Maloney 17:17:33 RRSAgent, draft minutes 17:17:33 I have made the request to generate http://www.w3.org/2006/12/20-grddl-wg-minutes.html DanC 17:17:38 sure 17:17:43 -DanC 17:17:49 -briansuda 17:17:51 SW_GRDDL()11:00AM has ended 17:17:52 Attendees were Chimezie_Ogbuji, DanC, briansuda, HarryH, benadida, Murray_Maloney 17:17:55 RRSAgent, draft minutes 17:17:55 I have made the request to generate http://www.w3.org/2006/12/20-grddl-wg-minutes.html DanC 17:18:38 I'd like you to grab that and clean it up just a bit... get rid of the dups in the TOC 17:18:51 and then mail it to public-grdd-wg@w3.org as an attachment. OK? 17:18:55 right, and i'll change and ',' to ':' 17:19:09 not a problem 17:19:18 well, to change , to :, you kinda have to grab the IRC log and run it thru scribe.perl on your machine. 17:19:31 That's an option, but it's sorta above and beyond the call of duty for a meeting of this sorty 17:19:32 sort 17:20:08 I think just cleaning up the TOC suffices... umm... lemme check the action summary... 17:20:15 benadida has left #grddl-wg 17:20:35 can i remove myself from the regrets as well? 17:20:39 yes 17:20:47 and chop off the diagnostics 17:20:51 k 17:20:59 action summary looks close enough 17:21:28 ok, enjoy. 17:21:33 happy holidays 17:21:43 Merry Christmas. 17:21:48 if you find any issues with the hg stuff, let me know 17:24:57 will do 17:25:09 now to update the GRDDL issues list with all these resolved issues... 18:32:46 ok, the issues list is up-to-date http://www.w3.org/2004/01/rdxh/spec#issues 1.180 2006/12/20 18:30:48 18:32:56 RRSAgent, stop