13:33:14 RRSAgent has joined #rdfa 13:33:15 logging to http://www.w3.org/2010/05/27-rdfa-irc 13:52:29 trackbot, prepare telecon 13:52:31 RRSAgent, make logs world 13:52:33 Zakim, this will be 7332 13:52:33 ok, trackbot; I see SW_RDFa()10:00AM scheduled to start in 8 minutes 13:52:34 Meeting: RDFa Working Group Teleconference 13:52:34 Date: 27 May 2010 13:53:13 markbirbeck has joined #rdfa 13:53:23 Agenda: http://lists.w3.org/Archives/Public/public-rdfa-wg/2010May/0114.html 13:53:24 ShaneM has joined #rdfa 13:53:28 Chair: Manu 13:53:41 Present: Manu, Shane, Mark 13:54:01 Regrets: BenA 13:55:23 Steven has joined #rdfa 13:58:13 tinkster has joined #rdfa 13:59:13 SW_RDFa()10:00AM has now started 13:59:20 +tinkster 13:59:24 zakim, mute me 13:59:24 sorry, tinkster, muting is not permitted when only one person is present 13:59:33 +[IPcaller] 13:59:36 zakim, why's that? 13:59:36 I don't understand your question, tinkster. 13:59:40 zakim, +IPcaller is manu 13:59:40 sorry, manu, I do not recognize a party named '+IPcaller' 13:59:42 zakim, mute me 13:59:42 tinkster should now be muted 13:59:43 zakim, dial ivan-vip 13:59:43 I am sorry, ivan; I do not know a number for ivan-vip 13:59:45 zakim, IPcaller is manu 13:59:45 +manu; got it 13:59:54 zakim, dial ivan-voip 13:59:54 ok, ivan; the call is being made 13:59:55 +Ivan 13:59:59 zakim, unmute me 14:00:00 tinkster should no longer be muted 14:00:50 zakim, dial steven-617 14:00:50 ok, Steven; the call is being made 14:00:52 +Steven 14:00:58 mhausenblas just posted this link on #swig - http://rdfa.info/2010/05/27/newsweek-using-rdfa/ 14:01:19 +McCarron 14:01:34 +[MIT528] 14:02:10 Benjamin has joined #rdfa 14:02:11 Knud has joined #rdfa 14:02:22 "the spirit is willing, but the flesh is weak" -> "the wine was good, but the meat was bad" 14:02:27 +Knud 14:02:29 dongmei has joined #rdfa 14:02:54 "out of sight, out of mind" -> "invisible, insane" 14:03:20 zakim, code? 14:03:20 the conference code is 7332 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), markbirbeck 14:03:22 +BenjaminA 14:04:09 zakim, who is noisy? 14:04:20 Steven, listening for 10 seconds I heard sound from the following: manu (44%), Ivan (44%), Knud (24%), BenjaminA (4%) 14:04:49 zakim, mute Knud 14:04:49 Knud should now be muted 14:05:01 damn, it's always me! 14:05:04 +markbirbeck 14:05:04 sorry knud, it is you:-( 14:05:29 scribe: Steven 14:05:45 rrsagent, make minutes 14:05:45 I have made the request to generate http://www.w3.org/2010/05/27-rdfa-minutes.html Steven 14:05:59 clap clap clap clap to Toby 14:06:04 rrsagent, make log public 14:06:36 zakim, who is here? 14:06:36 On the phone I see tinkster, manu, Ivan, Steven, McCarron, [MIT528] (muted), Knud (muted), BenjaminA, markbirbeck 14:06:38 On IRC I see dongmei, Knud, Benjamin, tinkster, Steven, ShaneM, markbirbeck, RRSAgent, Zakim, manu, kennyluck, ivan, trackbot 14:07:06 Topic: @@ 14:07:38 Tinkster: [describes rdfa checker] 14:07:39 s/@@/check.rdfa/ 14:08:02 -> http://www.w3.org/2001/sw/wiki/CheckRDFa entry about check.rdfa on the tool list at W3C 14:08:10 http://check.rdfa.info/ 14:08:12 http://check.rdfa.info/ 14:08:32 tinkster: Not handling non-ascii well yet 14:08:40 http://check.rdfa.info/check?url=http://www.newsweek.com/&version=1.0 14:09:15 Manu: I ran it on newsweek; cool! 14:09:44 tinkster: The display is valid rdfa too 14:10:15 Mark: Hmm, run the output through itself? 14:10:17 http://check.rdfa.info/check?url=http://check.rdfa.info/check?url=http://www.newsweek.com/&version=1.0 14:10:31 Steven: Lol 14:10:33 Internal Server Error... :) 14:11:20 Manu: Live editing mechanism? 14:11:27 Does it handle redirects? Often useful to pass shortened URLs in. 14:11:30 ... to generate rdfa for the user 14:12:10 ... quick and dirty way to generate rdfa 14:12:24 Steven: Yes it handles redirects 14:13:05 Manu: anyone working on that? 14:13:17 markbirbeck, it should handle redirects i think. 14:13:26 Steven: Put on rdfa.info as a posting? 14:13:37 Manu: I don't have access 14:13:45 Mark: Huh? You should! 14:13:58 ... Toby, do you? 14:14:05 Toby: No. 14:14:41 Mark: I shall ping Ben, to add everyone 14:15:16 ACTION: Mark to add people to rdfa.info 14:15:16 Created ACTION-30 - Add people to rdfa.info [on Mark Birbeck - due 2010-06-03]. 14:15:29 Topic: RDFa DOM API progress 14:15:31 http://www.w3.org/2010/02/rdfa/drafts/2010/ED-rdfa-dom-api-20100526/ 14:15:44 Manu: I have made changes based on Ivan's feedback 14:16:10 ... now we have intro, basic concepts, and that is enough to start using it 14:16:17 ... the rest is detail 14:16:36 ... I did skip over Ivan's email. Ivan is this good foryou? 14:16:48 s/foryou/for you/ 14:17:02 Ivan: I only have small problems. I sent another mail an hour or so ago 14:17:07 ... please see that 14:17:12 ... no major issues 14:17:35 ... biggest issue is that I got confused between "high" and "low" 14:18:12 Manu: Any other comments? 14:18:51 ... FPWD in a week? 14:19:07 ... I'll send to the group Monday, and a strawpoll next Thursday 14:19:37 ... By the way, there are new concept diagrams 14:19:50 ... and a couple of added sections 14:19:57 q+ 14:20:09 ack Benjamin 14:20:43 Benjamin: It reads fluently. I agree with Ivan's restructuring ideas, minor issues; really cool. See my mail 14:21:25 Topic: Issue 25 14:21:28 issue-w5? 14:21:33 issue-25? 14:21:33 ISSUE-25 -- Halt generation of triples in sub-trees when a @profile document cannot be retrieved -- open 14:21:33 http://www.w3.org/2010/02/rdfa/track/issues/25 14:22:00 http://lists.w3.org/Archives/Public/public-rdfa-wg/2010May/0122.html 14:22:31 Toby: We allow profiles that define prefixes and keywords. 14:22:47 .... If the profile is not retrievable or other problems 14:23:03 ... then we can't be sure how to interpret children 14:23:49 ... in that case we should ignore child elements 14:24:05 ... Ivan and I disagree about what to do with incomplete triples 14:24:19 ... I say use bnodes, he says don't complete 14:24:27 q+ 14:24:32 ... I don't have a strong opinion 14:24:38 Ivan: Simplicity! 14:25:20 q- 14:25:25 Toby: We can complete with a relative URI, but not absolute, because we don't know if it is a CURIE or not 14:25:29 Manu: Yes, I agree - simplicity! 14:25:30 Q+ 14:25:42 ack markbirbeck 14:25:53 Mark: Why if it's relative can we distinguish? 14:25:59 ... it might be a token 14:26:08 TOby: If it's got a slash ot something.... 14:26:13 s/TO/To/ 14:26:28 Mark: This helps only for processing 14:26:51 q+ 14:26:57 ... why not create a new named graph for the stuff you're not sure about 14:27:10 ... then you cancome back later and fix up 14:27:17 s/can/can / 14:28:30 Steven: Can't users who need to do that jsut do it 14:28:37 s/jsut/just/ 14:28:42 s/it/it?/ 14:28:56 Mark: I'm worried about text preventing people from doing it 14:29:14 ... if it says you must fail, then you can't fix up 14:29:26 ack ivan 14:29:30 Toby: I'm OK with wording that allows both 14:29:55 Ivan: Named graphs are fine, but in practice most processors produce one graph 14:30:05 ... no standard for named graphs 14:30:19 q+ 14:30:45 ack markbirbeck 14:30:50 ... so it shouldn't be required to produce a named graph 14:31:26 Mark: I didn't mean to enforce it. Just allow it as an option for processing 14:31:37 The spec currently says this: 14:31:37 This specification does not say anything about what should happen to the triples generated, or whether more 14:31:37 triples might be generated during processing than are outlined here. However, to be conforming, an 14:31:37 RDFa processor MUST act as if at a minimum the rules in this section are applied, and a single 14:31:37 RDF graph produced. As described in the RDFa Processor Conformance section, 14:31:38 ... I have tons of named graphs in my processor 14:31:40 any additional triples generated MUST NOT appear in the default graph. 14:32:21 Mark: People should be allowed to do this 14:32:26 q+ 14:32:31 Ivan: I don't have a problem with that 14:32:33 ack tinkster 14:32:56 Toby: You can't always tell what is missing from a given profile 14:33:06 Mark: Yes 14:33:40 Ivan: If the profile doesn't work, nothing more is generated in the default graph seems like a good position 14:33:44 Mark: Yeah 14:34:13 Shane: I'm happy to put that in, but even if we don't, it is still allowed (see the quote above) 14:35:00 Not quite...current proposal is this: 14:35:05 "The suggested solution, originally from Jeni Tennison is that when 14:35:05 parsers encounter a profile URI that cannot be retrieved, they should 14:35:05 not process that subtree." 14:35:05 Manu: SO all incomplete triples are not added to the default graph 14:35:11 s/SO/So/ 14:35:42 Toby: Sibling elements are OK, so don't clear incomplete triples 14:36:29 q+ to ask about non-RDFa, but XHTML profiles. 14:37:31 PROPOSAL: When a @profile cannot be retrieved, all incomplete triples cannot be completed by the element that contains the non-retrievable @profile. The subtree containing the non-retrievable @profile must not be processed. 14:37:34 Toby: Just treat it as if the element wasn't there 14:37:46 +1 14:37:58 Steven: should not? 14:38:42 Mark: No more triples should be added to the default graph 14:38:49 ... for that subtree 14:39:07 PROPOSAL: When a @profile cannot be retrieved, all incomplete triples that cannot be completed by the element that contains the non-retrievable @profile. The subtree containing the non-retrievable @profile must not generate triples to be placed into the default graph. 14:39:19 +1 14:39:42 (the first sentance doesn't make much sense) 14:39:55 PROPOSAL: When a @profile cannot be retrieved, all incomplete triples must not be placed in the default graph. The subtree containing the non-retrievable @profile must not generate triples to be placed into the default graph. 14:39:59 ... the current element and its children must not cause triples to be placed into the default graph. 14:40:52 PROPOSAL: When a @profile cannot be retrieved, the current element and its children must not cause triples to be placed into the default graph. 14:41:39 ack tinkster 14:41:39 tinkster, you wanted to ask about non-RDFa, but XHTML profiles. 14:41:54 q+ to discuss profile parsing 14:42:14 Toby: If we retrieve the profile and it has zero triples, is in another format 14:42:18 Ivan: SHould be OK 14:42:23 Toby: Edge case? 14:42:29 Ivan: No. 14:42:33 s/SH/Sh/ 14:42:46 Ivan: Profiles can be used for other things too 14:43:51 ack shanem 14:43:51 ShaneM, you wanted to discuss profile parsing 14:43:51 ... the error case is only for non-retrievable, and or non-syntactic profiles 14:44:02 q+ 14:44:25 Shane: I don't think we can legislate this 14:44:38 ... the term is "available" 14:44:41 PROPOSAL: When a @profile is not available, the current element and its children must not cause triples to be placed into the default graph. 14:44:50 ... if the profile is not available, then problem 14:45:06 q+ 14:45:07 ... if it is available, and produces no terms, then that is not a problem 14:45:11 q+ 14:45:52 Ivan: If I get a profile with a bug, that is a bug, so we can't legislate 14:46:12 ack ivan 14:46:39 Mark: I don't think we can resolve this on the phone, but we need somnething like "when profile is not available" 14:46:41 ack markbirbeck 14:46:54 PROPOSED: If any referenced RDFa Profile is not available, then the current element and its children must not place any triples in the default graph. 14:47:08 ... Javascript parser can't go to different domains, so it might have a hardwired list 14:47:22 ... and 'available' might mean something else 14:47:25 ack steven 14:47:34 If we require that all RDFa profiles contain this triple: { <> rdf:type rdfa:Profile . }, then once a profile is retrieved, we can verify that it has worked OK. 14:47:42 +1 to steven 14:47:47 +1 to steven 14:47:52 +1 14:48:09 +1 to tinkster too - that's clever 14:48:18 Steven: A profile is like zero. No reason to disallow it 14:48:42 +1 14:48:45 +1 14:48:48 +1 14:48:56 s/profile/profile that has no additions/ 14:48:57 +1 14:49:00 +1 14:49:09 +1 14:49:23 +1 14:49:25 [+1s are to SHanes proposal above] 14:49:30 s/SH/Sh/ 14:49:33 q+ 14:49:34 I'd like to come up with some examples of available-but-unusable profiles; I'll try to post them to the mailing list soon. 14:49:37 (side issue) 14:49:54 @Steven: shh yourself. 14:50:02 RESOLVED: If any referenced RDFa Profile is not available, then the "current element" and its children must not place any triples in the "default graph". 14:50:58 Ivan: I will answer Jenny officially 14:51:06 s/Jenny/Jeni/ 14:51:10 s/Jenny/Jeni/ 14:51:13 ACTION: Ivan to reply to Jenny about @profile unavailable 14:51:13 Created ACTION-31 - Reply to Jenny about @profile unavailable [on Ivan Herman - due 2010-06-03]. 14:51:27 s/Jenny/Jeni/ 14:51:43 Topic: @@ 14:51:45 http://www.w3.org/2010/02/rdfa/track/issues/23 14:51:59 s/@@/issue 23/ 14:51:59 s/@@/Issue 23 order in profile processing/ 14:52:04 http://gmpg.org/xmdp/description#html4hints 14:52:09 issue-23? 14:52:09 ISSUE-23 -- @profile order - RDFa Core 1.1 versus HTML 4.01 and XMDP -- open 14:52:09 http://www.w3.org/2010/02/rdfa/track/issues/23 14:52:27 Toby: HTML4 says only the first URI in the list is used 14:52:29 Toby's e-mail proposal for ISSUE-23: http://lists.w3.org/Archives/Public/public-rdfa-wg/2010May/0123.html 14:53:24 Toby: SOlution to process the URIs in reverse order 14:53:28 +1 14:53:29 s/SO/So/ 14:53:29 +1 to this solution 14:53:40 Steven: Fine 14:53:55 Mark: You don't have to describe it as processing in reverse order 14:54:47 Manu: It doesn't necessarily match with CSS and Javascript evaluation 14:55:02 Mark: I think we're covered, see my mail 14:55:41 ... the L to R/ R to L is bound to the language itself 14:56:08 ... programmers aren't expecting a general rule 14:56:30 Manu: When shal we resolve this? 14:56:33 Ivan: Now 14:56:42 s/shal/shall/ 14:56:54 Mark: Let mManu roll it over, since he's the main objecotr 14:57:08 Manu: I'd be happier to leave it 14:57:14 s/cotr/ctor/ 14:57:25 s/mM/M/ 15:00:02 Steven: I am talking on RDFa at webandbeyond.nl next week, ~600 attendees 15:00:16 Ivan: I am in Seattle soon, giving a talk on RDFa 15:00:36 SHane: WHitespace resolution from last week 15:00:37 http://www.w3.org/2010/02/rdfa/meetings/2010-05-20#resolution_1 15:00:45 s/SH/Sh/ 15:00:49 s/WH/Wh/ 15:01:15 Ivan: COre defines what whitespace is for RDFa 15:01:20 s/CO/Co/ 15:02:01 Shane: HTML5 has a intricate definintion for whitespace 15:02:13 s/nint/nit/ 15:02:33 Shane: We should watch for that 15:03:01 Manu: Not a danger; HTML5 is not the only language that uses RDFa 15:03:20 http://www.w3.org/TR/html5/infrastructure.html#set-of-space-separated-tokens 15:03:36 Manu: We need to be compatible 15:03:44 +q 15:04:32 -McCarron 15:04:36 Dongmei: This is my last call with you. Thanks! 15:05:24 [ADJOURN] 15:05:38 -[MIT528] 15:05:47 zakim, list attendees 15:05:56 -tinkster 15:06:00 -Ivan 15:06:06 -markbirbeck 15:06:10 -Knud 15:06:17 -Steven 15:06:22 As of this point the attendees have been tinkster, manu, Ivan, Steven, McCarron, [MIT528], Knud, BenjaminA, markbirbeck 15:14:54 -manu 15:14:55 -BenjaminA 15:14:57 SW_RDFa()10:00AM has ended 15:14:58 Attendees were tinkster, manu, Ivan, Steven, McCarron, [MIT528], Knud, BenjaminA, markbirbeck 16:19:26 ShaneM has joined #rdfa 16:55:28 zakim, bye 16:55:28 Zakim has left #rdfa 16:55:30 rrsagent, bye 16:55:30 I see 2 open action items saved in http://www.w3.org/2010/05/27-rdfa-actions.rdf : 16:55:30 ACTION: Mark to add people to rdfa.info [1] 16:55:30 recorded in http://www.w3.org/2010/05/27-rdfa-irc#T14-15-16 16:55:30 ACTION: Ivan to reply to Jenny about @profile unavailable [2] 16:55:30 recorded in http://www.w3.org/2010/05/27-rdfa-irc#T14-51-13 16:55:33 trackbot, bye 16:55:33 trackbot has left #rdfa