14:56:51 RRSAgent has joined #rdfa 14:56:51 logging to http://www.w3.org/2008/05/29-rdfa-irc 14:57:13 rrsagent, please make record public 14:57:17 Zakim has joined #rdfa 14:57:21 zakim, this will be rdfa 14:57:21 ok, Ralph; I see SW_SWD(RDFa)11:00AM scheduled to start in 3 minutes 14:57:29 Meeting: RDF-in-XHTML Task Force 14:58:08 Agenda: http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008May/0211.html 14:59:05 -> http://www.w3.org/2008/05/15-rdfa-minutes.html previous 2008-05-15 14:59:48 SW_SWD(RDFa)11:00AM has now started 14:59:55 +??P14 15:00:01 zakim, p14 is ShaneM_ 15:00:04 sorry, ShaneM, I do not recognize a party named 'p14' 15:00:12 Zakim, ??P14 is ShaneM 15:00:12 +ShaneM; got it 15:00:24 +[IPcaller] 15:00:35 zakim, I am ?[IPcaller] 15:00:35 sorry, msporny, I do not see a party named '?[IPcaller]' 15:00:39 +Ralph 15:01:03 zakim, I am [IPcaller] 15:01:03 ok, msporny, I now associate you with [IPcaller] 15:01:34 Steven has joined #rdfa 15:01:40 Chair: Manu 15:01:43 Regrets: Michael 15:01:52 doh. I was in the wrong channel all afternoon! 15:01:57 zakim, dial steven-617 15:01:57 ok, Steven; the call is being made 15:01:59 +Steven 15:02:34 markbirbeck has joined #rdfa 15:02:45 zakim, code? 15:02:45 the conference code is 7332 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), markbirbeck 15:03:27 + +0208761aaaa 15:03:34 zakim, i am aaaa 15:03:34 +markbirbeck; got it 15:08:16 scribenick: ralph 15:08:24 ACTION: Ben followup with Fabien on getting his RDFa GRDDL transform transferred to W3C [recorded in http://www.w3.org/2007/11/15-rdfa-minutes.html#action01] 15:08:26 -- continues 15:08:34 ACTION: Manu to reach out to Slashdot and attempt to get RDFa integrated into Slashdot. [recorded in http://www.w3.org/2008/05/08-rdfa-minutes.html#action10] 15:08:36 -- continues 15:09:55 [DONE] ACTION: Mark to move _:a bnode notation to normative section [recorded in http://www.w3.org/2008/04/03-rdfa-minutes.html#action05] 15:10:09 ACTION: Michael to create 'RDFa for uF users' on RDFa Wiki [recorded in http://www.w3.org/2008/03/13-rdfa-minutes.html#action12] 15:10:12 -- continues 15:10:26 ACTION: Michael to determine which useless-triples test cases to remove and which to add. [recorded in http://www.w3.org/2008/05/08-rdfa-minutes.html#action12] 15:10:28 -- continues 15:10:40 I have made the request to generate http://www.w3.org/2008/05/29-rdfa-minutes.html Ralph 15:11:04 Topic: Response to TAG 15:11:31 Steven: I don't really understand DanC's point 15:12:00 Mark: the idea of "Follow your nose" seems to mean "let's leave HTML and XHTML untouched but add something else" 15:12:11 ... but we _are_ changing XHTML1 15:12:21 ... reading the TAG minutes I get the impression that Tim is open to this 15:13:10 ... others seem to worry about folks who may accidentally use our new attributes without intending to do so 15:13:35 ... we should take a stand that these new attributes should be used only for the purpose of generating triples 15:13:51 Steven: and furthermore, doing this does not change the meaning of any existing HTML page 15:14:00 ... it just formalizes what the page really means 15:14:10 Manu: is there a concern about the HTML5 series? 15:14:27 ... at one point they said that while this may be good for XHTML, @profile does not exist for HTML5 15:14:33 Shane: that's not our problem 15:14:39 Ralph: I agree with Shane 15:14:54 +1 15:15:02 Shane: I had an off-line discussion with NoahM and perhaps someone else 15:15:23 ... Tim definitely concurred with adding this to core XHTML1 15:15:34 ... and proposed annotating the namespace document to say this 15:15:55 ... some were concerned that this means every XHTML document currently on the Web then should generate triples 15:16:12 ... there was a suggestion that there be an announcement mechanism that tells parsers they _should_ generate triples 15:17:34 Ralph: why isn't this a problem for the consumer of the document rather than the author of the document? 15:17:49 ... I agree with Steven's comment that XHTML always has _meant_ this 15:18:08 ... so the author shouldn't be telling the client whether it should or shouldn't generate triples 15:18:12 ... the client decides that 15:18:24 Manu: running fuzbot for a while, it seems every page does generate triples 15:18:53 Shane: so fine, and we should update the media type spec to say that we now generate triples 15:19:01 ... this will make it clear that this is a big step 15:19:12 My argument for not requiring @profile or DTDs: 15:19:14 http://microformats.org/wiki/rel-license 15:19:23 Steven: I don't agree with the argument that the media type must say that the document is used to generate triples 15:19:31 +1 Steven 15:19:43 ... the media type just identifies the type of document; it doesn't say how you should process it 15:19:58 Shane: in the RDF cases, the media type does say [something about] how to process it 15:20:04 Mark: that may be the TAG's point 15:20:24 ... the question "should we waste time processing this document if it doesn't contain RDFa" is one of two 15:20:59 ... the second is "if we process a document as if it contains RDFa, are we acquiring statements that people did not intend to make"? 15:21:09 ... the second is what the TAG is currently debating 15:21:29 ... a third question might concern @rel='license' 15:21:45 ... they're suggesting that we should *not* process @rel='license' 15:22:06 ... this means that >1M documents won't have this clear semantics 15:22:27 ... we can make all these documents available to RDFa easily 15:22:43 ... it's crazy to say none of these documents assert a license currently 15:22:58 Shane: as a group, we've agreed on this here 15:23:14 ... we only need to address the 'follow your nose' question; it's about how discovery works on the Web 15:23:22 ... related to 302 discussion 15:24:12 ... the TAG appears to have a whole big environment in mind, of which RDFa is a small part, and they want to know how this fits 15:24:31 ... how does a document containing RDFa say that it contains RDFa? 15:24:42 ... Tim says "they all do" 15:25:12 Mark: we think the interpretation of a document [is specified] even if the author didn't previously sign a contract 15:25:29 ... we're saying "here is an RDF interpretation of billions of documents that have [already] been published on the Web" 15:25:42 ... and we hope people will publish even more [data] than they have already done 15:25:46 Ralph: +1 15:26:03 Shane: it's not about imposing processing; it's about _permitting_ processing 15:26:22 ... the TAG's argument is that they don't see an explicit instruction and therefore can't map this into their world view 15:27:41 Ralph: does the TAG not believe that it is sufficient to have updated the XHTML1 namespace document? 15:27:53 Shane: there are two ways to update the namespace document; prose and with the GRDDL profile 15:28:02 ... the prose is more interesting to me 15:28:18 ... you go from the media type to the namespace document, not to the modularization document 15:29:41 ... we should propose to the TAG that we will follow Tim's recommendation and update the namespace document, both the prose and the machine-readable and all documents of type XHTML1 have RDF triples 15:29:44 Ralph: +1 15:29:50 STeven: +1 15:29:56 "Published specification: 15:29:56 The text/html media type is now defined by W3C Recommendations; 15:29:56 the latest published version is ..." 15:30:23 (THat's from the rfc for text/html) 15:30:33 s/TH/Th/ 15:30:44 ACTION: Shane draft a TAG response along the lines of "we will update the namespace document, both the prose and the machine-readable and all documents of type XHTML1 have RDF triples" 15:31:14 Topic: Test Cases 15:31:21 http://rdfa.digitalbazaar.com/rdfa-test-harness/ 15:32:17 -- test 105; inner @rel neither CURIE nor LinkType 15:32:41 Manu: oops, seems I broke the test case harness 15:32:47 15:32:47 15:32:47 xmlns:dc="http://purl.org/dc/elements/1.1/"> 15:32:47 15:32:48 Test 0105 15:32:50 15:32:52 15:32:54
15:32:56 Ben created this page. 15:32:58
15:33:00 15:33:02 15:33:32 ASK WHERE { 15:33:32 _:a . 15:33:32 } 15:34:18 Manu: _:a should be changed to ?a 15:34:40 ... we should verify that the object is a bnode 15:34:49 ... so nees a FILTER 15:34:53 s/nees/needs/ 15:34:54 ASK WHERE { 15:34:54 l> ?a . 15:34:54 FILTER IsBlank(?a) 15:34:54 } 15:35:31 Mark: to be a full test, we should check that there's not a triple with myfoobarrel as a predicate 15:35:38 Manu: we can't do that in a single query 15:35:57 Mark: could use NOT 15:36:13 Manu: I'll investigate 15:36:54 ... there are other tests that don't verify the absence of a triple 15:37:11 Mark: do we need @about="" ? 15:37:22 Steven: doesn't do any harm 15:37:57 RESOLVED: test 105 accepted, with change to check for absence of myfoobarrel triple 15:37:59 +1 15:38:07 15:38:07 15:38:07 xmlns:dc="http://purl.org/dc/elements/1.1/"> 15:38:07 15:38:08 Test 0106 15:38:10 15:38:12 15:38:14
15:38:18 Manu created this page. 15:38:20
15:38:22 15:38:24 15:38:25 -- test 106; chaining with empty value in inner @rel 15:38:46 ASK WHERE { 15:38:46 ?a . 15:38:46 FILTER IsBlank(?a) 15:38:46 } 15:38:54 Manu: add similar absence test to 106 15:39:39 Ralph: no predicate to check for absence in this case 15:41:02 Mark: a parser might blindly generate a predicate URI of http://purl.org/dc/elements/1.1/ 15:41:19 Is there an empty CURIE? 15:41:20 Ralph: even thought that wouldn't be a [semantically] valid predicate name 15:41:26 s/thought/though/ 15:41:28 Mark: yep 15:41:29 I was thinking of the xhv namespace, Ralp. 15:41:44 s/Ralp./Ralph./ 15:41:46 [yep, I copied the wrong test!] 15:41:50 s/test/text/ 15:42:07 s|http://purl.org/dc/elements/1.1/|http://www.w3.org/1999/xhtml 15:42:22 Manu: we could test that there is no triple containing "Manu" as an object 15:42:29 Mark: yes, that's more sensible for both 106 and 105 15:42:54 RESOLVED: test 106 accepted, with change to check for absence of triples containing manu.html as either subject or object 15:43:23 Topic: handling of literals in test harness 15:43:48 Manu: we currently have 4 tests that fail; 100-103 because the literals are compared character by character 15:44:06
15:44:09 ... even though the test is correct, the harness considers ''' and '"' to be different 15:44:12
15:44:42 ... also, our test doesn't cover the case that
and
are equivalent 15:44:56 ... I propose that we add two versions of each test; one in short form and one in long form 15:45:14 Ralph: sounds reasonable to me to duplicate the tests for the convenience of implementors 15:45:24 ASK WHERE { 15:45:24 'Some text here in bold and an svg rectangle: '^^ 'Some text here in bold and an svg rectangle: '^^ . 15:45:27 } 15:45:29 ax-ns#XMLLiteral> . 15:45:31 } 15:45:33 Manu: ^ SPARQL for test 100 15:45:42 ... this is nearly impossible [for a human] to read 15:45:47 ASK WHERE { 15:45:47 'Some text here in bold and an svg rectangle: '^^ . 15:45:47 } 15:46:11 Manu: the idea would be to include UNION statements where '"' is exchanged for ''' 15:46:31 15:46:39 ... and has both self-closed and explicit close tags 15:46:48 ... for the convenience of both sax-based and DOM-based parsers 15:46:52 ... any objections? 15:46:55 [no objections] 15:47:06 Manu: I propose to update test 100-103 to add all four cases 15:47:31 Shane: I don't really object but I point out it's an "interesting" combinatorial problem to add all the cases to the SPARQL 15:47:45 Manu: modified proposal; only add those requested by implementors 15:48:10 Shane: also add a comment to the tests so when new implementors come along they know why they might be failing 15:48:50 PROPOSE: Add implementors valid XML Literals to TC 100-103 and add comments to tell other implementors that the tests may fail due to XML Literal issues. 15:49:26 PROPOSE: Add valid cases of XML Literals as requested by implementers to TC 100-103 and add comments to tell other implementors that the tests may fail due to XML Literal issues. 15:49:46 ok 15:49:52 RESOLVED: Add valid cases of XML Literals as requested by implementers to TC 100-103 and add comments to tell other implementors that the tests may fail due to XML Literal issues. 15:50:13 http://www.w3.org/2006/07/SWD/track/issues/120 15:50:17 Topic: ISSUE-120 15:50:33 Manu: I believe we've resolved this 15:51:10 Shane: the resolution was a minor change in the document ~1 month ago 15:52:13 Mark: this was a case of reading the text two possible ways, where one way was really awkward 15:53:58 ... the problem I thought people were raising was that although the second [myfoobarrel] line does not generate a triple, it may also cause the first [dc:creator] line to not generate a triple 15:54:20 ... we should be more explicit that the nested element does complete the first triple even though it doesn't contain a valid @rel 15:54:38 ... I argued this was clear in the spec by interpretation of step 5 15:55:04 ... the wording is changed to refer to the presence of @rel attribute rather than to a @rel value 15:55:05 PROPOSE: Resolve ISSUE-120 having made a minor change to the Syntax Document specifying that the presence of a @rel generates an incomplete triple 15:55:31 PROPOSE: Resolve ISSUE-120 having made a minor change to the Syntax Document specifying that the presence of a @rel is sufficient to complete and incomplete triple. 15:55:46 http://htmlwg.mn.aptest.com/viewcvs/viewcvs.cgi/rdfa-syntax/Overview.mhtml.diff?r1=1.228&r2=1.229 15:55:51 RESOLVED: Resolve ISSUE-120 having made a minor change to the Syntax Document specifying that the presence of a @rel is sufficient to complete an incomplete triple. 15:56:14 http://www.w3.org/2006/07/SWD/track/issues/103 15:56:24 Topic: ISSUE-103 15:56:47 Manu: our email discussion boils down to "let's not change anything" 15:57:09 -> http://www.w3.org/2006/07/SWD/track/issues/103 ISSUE-103 a URI-centric approach to CURIEs 15:57:18 Shane: the argument is that CURIEs are _not_ URIs 15:57:34 ... the implication of being a URI is that they could be used over the wire, but they can't be used over the wire 15:58:00 Mark: and we've suggested that languages that currently use QNAMEs could migrate over time to using CURIEs 15:59:12 Shane: in the TAG's recent CURIE Last Call comments they say that the CURIE syntax is too rich for use in SPARQL 16:00:18 Steven: and we're trying to fix that 16:00:26 PROPOSE: Resolve ISSUE-103, CURIEs are not URI schemes, they are a macro expansion mechanism. No need to change the Syntax document. 16:00:30 s/that/that limitation in other languages/ 16:01:09 There are queries you would like to make that SPARQL cannot do, and CURIEs fix that 16:01:18 Mark: I'd like my email comment to be included; this is QNAME-like 16:01:34 PROPOSE: Resolve ISSUE-103, CURIEs are not URI schemes, they are a macro expansion mechanism. No need to change the Syntax document. CURIEs are also QName-like, allowing legacy languages to migrate forward cleanly. 16:02:20 Ralph: +1 16:02:21 +1 16:02:29 time 16:02:34 RESOLVED: ISSUE-103 closed, CURIEs are not URI schemes, they are a macro expansion mechanism. No need to change the Syntax document. CURIEs are also QName-like, allowing legacy languages to migrate forward cleanly. 16:04:08 Ralph: in SWD WG meeting, Ben was asked to confirm that the XHTML2 WG will be able to resolve a CR transition request by Tuesday 10 June 16:04:45 Shane: yes, XHTML2 WG will be able to resolve this by 11 June 16:04:55 Steven: but there's an XForms WG meeting on the 11th 16:05:33 Shane: XHTML2 WG will be able to resolve CR transition request by 17 June 16:05:51 ... and we should discuss the CR exit criteria 16:06:03 Steven: I propose "2 implementations that pass all tests" 16:06:13 Shane: we've had a request that there also be an XSLT implementation 16:06:36 ... however, I do not believe that such an implementation is possible 16:07:00 -markbirbeck 16:07:10 Steven: the minimum requirement is that there are 2 implementations of all features, and they don't all even have to be in one implementation 16:07:12 [adjourned] 16:07:16 -[IPcaller] 16:07:40 -Steven 16:07:41 -ShaneM 16:07:42 -Ralph 16:07:42 SW_SWD(RDFa)11:00AM has ended 16:07:43 Attendees were ShaneM, [IPcaller], Ralph, Steven, +0208761aaaa, markbirbeck 16:07:52 rrsagent, please draft minutes 16:07:52 I have made the request to generate http://www.w3.org/2008/05/29-rdfa-minutes.html Ralph 16:07:57 Mark? 16:08:08 Shane, he's on Skype apparently 16:08:14 ahh ok 16:08:25 I need him for that impl report 16:09:26 i/Ralph: in SWD WG meeting/Topic: CR Transition Scheduling 16:09:29 rrsagent, please draft minutes 16:09:29 I have made the request to generate http://www.w3.org/2008/05/29-rdfa-minutes.html Ralph 16:09:32 ShaneM has left #rdfa 16:09:39 zakim, bye 16:09:39 Zakim has left #rdfa 16:10:27 rrsagent, bye 16:10:27 I see 5 open action items saved in http://www.w3.org/2008/05/29-rdfa-actions.rdf : 16:10:27 ACTION: Ben followup with Fabien on getting his RDFa GRDDL transform transferred to W3C [recorded in http://www.w3.org/2007/11/15-rdfa-minutes.html#action01] [1] 16:10:27 recorded in http://www.w3.org/2008/05/29-rdfa-irc#T15-08-24 16:10:27 ACTION: Manu to reach out to Slashdot and attempt to get RDFa integrated into Slashdot. [recorded in http://www.w3.org/2008/05/08-rdfa-minutes.html#action10] [2] 16:10:27 recorded in http://www.w3.org/2008/05/29-rdfa-irc#T15-08-34 16:10:27 ACTION: Michael to create 'RDFa for uF users' on RDFa Wiki [recorded in http://www.w3.org/2008/03/13-rdfa-minutes.html#action12] [3] 16:10:27 recorded in http://www.w3.org/2008/05/29-rdfa-irc#T15-10-09 16:10:27 ACTION: Michael to determine which useless-triples test cases to remove and which to add. [recorded in http://www.w3.org/2008/05/08-rdfa-minutes.html#action12] [4] 16:10:27 recorded in http://www.w3.org/2008/05/29-rdfa-irc#T15-10-26 16:10:27 ACTION: Shane draft a TAG response along the lines of "we will update the namespace document, both the prose and the machine-readable and all documents of type XHTML1 have RDF triples" [5] 16:10:27 recorded in http://www.w3.org/2008/05/29-rdfa-irc#T15-30-44