14:08:46 RRSAgent has joined #rdfa 14:08:46 logging to http://www.w3.org/2013/01/17-rdfa-irc 14:08:48 RRSAgent, make logs world 14:08:50 Zakim, this will be 7332 14:08:50 ok, trackbot; I see SW_RDFa()10:00AM scheduled to start in 52 minutes 14:08:51 Meeting: RDFa Working Group Teleconference 14:08:51 Date: 17 January 2013 14:27:31 TallTed has joined #rdfa 14:31:56 gkellogg has joined #rdfa 14:58:05 gkellogg has joined #rdfa 14:59:38 SW_RDFa()10:00AM has now started 14:59:45 +??P29 14:59:51 zakim, I am ??P29 14:59:52 +manu; got it 15:00:52 niklasl has joined #rdfa 15:01:21 +??P36 15:01:27 zakim, I am ??P36 15:01:28 +niklasl; got it 15:01:39 what's the dial-in phone #? 15:02:00 zakim, code? 15:02:00 the conference code is 7332 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), manu 15:02:11 gkellogg: ^^^ 15:02:17 +scor 15:02:35 scor has joined #rdfa 15:03:03 +gkellogg 15:03:55 ShaneM has joined #rdfa 15:05:30 zakim, dial ivan-voip 15:05:31 ok, ivan; the call is being made 15:05:31 +Ivan 15:06:17 +Shane_McCarron 15:06:18 Agenda: http://lists.w3.org/Archives/Public/public-rdfa-wg/2013Jan/0048.html 15:06:25 zakim, I am Shane_McCarron 15:06:25 ok, ShaneM, I now associate you with Shane_McCarron 15:06:57 Manu: Any updates or changes to the agenda? 15:07:07 scribenick: ivan 15:07:11 scribe: nick 15:09:27 Topic: ISSUE-143: Prefixes too complicated 15:09:29 scribe: ivan 15:09:33 http://www.w3.org/2010/02/rdfa/track/issues/143 15:09:50 manu: we have now asked for feedbacks from Tab twice 15:09:54 … no responses 15:09:59 … the wg was clear about it 15:10:15 … we are going to raise a warning whenever a prefix is overwritten 15:10:29 … I think that is all we are going on this issue 15:10:31 any prefix? 15:10:37 or just an initial context prefix? 15:11:01 ivan: any 15:11:03 thanks 15:11:29 manu: whenever you overwrite a prefix a warning is issued 15:11:44 … I will add text until the issue is closed 15:12:23 Manu: the wg decides to close this issue 15:12:58 (everybody is happy) 15:13:04 Topic: ISSUE-144: Add @itemref-like attribute 15:13:11 http://www.w3.org/2010/02/rdfa/track/issues/144 15:13:13 issue-144? 15:13:13 ISSUE-144 -- Add an @itemref-like attribute to RDFa -- open 15:13:13 http://www.w3.org/2010/02/rdfa/track/issues/144 15:13:40 manu: I changed the document, people did not like my changes, I reverted to Gregg's version 15:14:12 … when gregg wrote there was an assumption of having an object with rdfa:Prototype 15:14:12 … and then another part would have a rdfa:ref 15:14:21 … it would then 'imports' all the statements of the prototype 15:14:39 … there are some rules/pattern matching in the document to define it 15:14:59 Manu: I removed the prototyp stuff because I felt it was too meta 15:15:17 … but as Niklas said it is actually good if people know that is meta 15:15:22 s/prototyp/prototype/ 15:15:35 … I also removed some of the bnodes in the examples 15:15:46 … we did not need to do that to demonstrate the functionality 15:16:17 Manu: we are reverting to things that people had objections to 15:16:24 … any other comments 15:16:32 gregg: we should decide the terms we use 15:16:43 … rdfa:include or rdfa:ref ? 15:16:55 … right now I feel that it is a fairly complex feature 15:17:11 … the property copying and microdata side by side, the mdata feels simpler 15:17:45 niklasl: what is happening from and abstract point of view? 15:18:00 … there is a product and a general part of the product 15:18:21 gregg : rfda:ref is useful if one thinks of a protype being pulled in 15:18:28 … include is more what we are doing 15:18:47 … but include has an include pattern in mdata, and what we do is very different 15:18:55 zakim, mute ivan 15:18:56 Ivan should now be muted 15:19:01 … we do not inherit the the types from the calling point 15:19:16 manu: I am not sure web developers would really see these different 15:19:23 … so include might be o.k. as well 15:19:47 … people might look at it with fresh eye 15:20:05 gregg: include in, eg, mformats is done on a syntax level 15:20:17 manu: clone, copy, … ? 15:20:48 niklasl: I think it is better if it is declarative and not imperative 15:20:58 gregg: we are on bike shedding… :-) 15:21:20 niklas: are we waiting for feedbacks? Ie, we cannot be finalize it 15:22:20 manu: are there any objection adding this feature? 15:22:49 niklas: I am a bit hesitant, sure, it could go in 15:23:22 zakim, unmute me 15:23:22 Ivan should no longer be muted 15:24:31 zakim, mute me 15:24:31 Ivan should now be muted 15:25:23 PROPOSAL: Add the Property Copying feature into the HTML+RDFa 1.1 specification. 15:25:29 +1 15:25:30 +1 15:25:31 +1 15:25:35 +0.75 unless feedback isn't skeptic/negative (then it shouldn't fly) 15:25:38 +1 15:25:41 q+ 15:25:48 ack ivan 15:25:49 ack ivan 15:25:50 +1 15:26:41 ivan: consider rdfa:copy and rdfa:Pattern 15:27:04 rdfa:pattern, rdfa:Pattern 15:27:25 RESOLVED: Add the Property Copying feature into the HTML+RDFa 1.1 specification as an at-risk feature. 15:27:31 +! 15:27:33 +1 15:27:42 manu: after discussions rdfa:copy and rdfa:Pattern have it 15:27:43 Topic: ISSUE-145: @content override @value 15:27:53 q+ 15:27:54 http://www.w3.org/2010/02/rdfa/track/issues/145 15:27:59 ack ivan 15:28:36 q+ @datatype though 15:28:51 ivan: @value is not used in HTML5 in any meaningful way, the issue isn't @content overriding @value... it's whether to do @value processing at all. 15:28:57 ivan: the issue if there is any value processing at all 15:28:58 ack 15:29:01 ack @dattype 15:29:12 ack @dattype, though 15:29:18 ack @datatype, though 15:29:26 gregg: there is a parallel issue on whether @datatype takes precedence over @content 15:29:33 gregg: wrong 15:29:40 q? 15:29:42 q- 15:29:42 gregg: @content takes precedence over @datatype 15:29:51 (all): yes 15:29:54 ack "@datatype, though" 15:30:39 PROPOSAL: Do not process the @value attribute in HTML+RDFa 1.1. 15:30:41 +1 15:30:41 +1 15:30:46 +1 15:30:51 +1 15:30:59 +1 15:31:02 +0 I liked the effect of picking it up from but I cannot argue for it with evidence of its need.... 15:31:08 RESOLVED: Do not process the @value attribute in HTML+RDFa 1.1. 15:31:42 PROPOSAL: @content overrides @datetime when found on the same element. 15:31:47 +1 15:31:48 +1 15:31:49 +1 15:31:54 +1 15:31:59 +1 15:32:19 +1 15:32:20 RESOLVED: @content overrides @datetime when found on the same element. 15:32:40 Topic: ISSUE-146: HTML5+RDFa needs rule for implied @about="" on head/body 15:32:42 ISSUE-146? 15:32:42 ISSUE-146 -- HTML5+RDFa needs rule for implied @about="" on head/body -- open 15:32:42 http://www.w3.org/2010/02/rdfa/track/issues/146 15:33:11 manu: we had a discussion whether html+rdfa for a implied about on head/body 15:33:22 … we resolved not to do that in rdfa 1.1 15:33:27 http://www.w3.org/2010/02/rdfa/track/issues/117 15:33:28 zakim, mute me 15:33:28 Ivan should now be muted 15:33:34 q+ 15:34:12 Manu: the reason we impled @about was because the use case was a corner case 15:34:12 … we were making the processing rules more complicated for a corner case use case 15:34:31 … the root element has the url of the document as an @about for any xml element 15:34:39 … we could then remove it from head and body 15:34:57 .. (or empty @resource (in Lite)) 15:34:58 … caveat is that the @typeof alone would generate a bnode 15:35:02 ack gkellogg 15:35:09 gregg: my memory is different 15:35:16 .. we had a rule for 1.0 15:35:37 … the problem was that if somebody set a different base, and this would be overritten by that 15:36:00 … we therefore used the special rule referring the parent object for the resource 15:36:07 … and what we decided to do 15:36:17 … that is the language in xhtml+rdfa 1.1 15:36:21 q+ 15:36:28 ack @datatype 15:36:31 ack though 15:37:05 ShaneM: there is nothing in the general rule set 15:37:24 gregg: the difference here was to use the parent object 15:37:34 … that was what the group intended 15:37:42 ack ivan 15:37:43 ack ivan 15:39:03 q+ to disagree about process with regard to XHTML+RDFa 15:40:05 ack ShaneM 15:40:13 ack Shane_McCarron 15:40:13 Shane_McCarron, you wanted to disagree about process with regard to XHTML+RDFa 15:41:40 manu: it seems that the sentiment is to adopt the language from xhtml+rdfa 15:41:58 tinkster has joined #rdfa 15:44:29 PROPOSAL: Add text matching XHTML+RDFa 1.1 for special processing of HEAD and BODY into the HTML+RDFa 1.1 spec. 15:44:31 +1 15:44:32 +1 15:44:34 +1 for consistency with XHTML 1.1 (I prefer just adding an explicit @resource along with the @typeof) 15:44:39 +1 15:44:50 +1 15:45:02 +1 15:45:05 RESOLVED: Add text matching XHTML+RDFa 1.1 for special processing of HEAD and BODY into the HTML+RDFa 1.1 spec. 15:45:50 manu: we are hopefully done all the issues! 15:45:58 … we can have a telcon next week 15:46:12 .. any issues we have to solve before last call? 15:47:37 … I will prepare the document this week end, 15:47:49 …. hopefully people can read it before thu 15:47:55 … we will do a vote by email 15:48:46 Topic: PER for RDFa Core and XHTML+RDFa 1.1 15:49:17 shanem: Are there any PER dependencies for the HTML+RDFa 1.1 spec? 15:49:22 manu: No, I don't think so. 15:49:35 ivan: We should do the PERs later. 15:50:02 ivan: We should do the PRs and PERs together. 15:50:58 -Ivan 15:51:00 -gkellogg 15:51:00 -Shane_McCarron 15:51:02 -manu 15:51:04 -niklasl 15:51:09 -scor 15:51:10 SW_RDFa()10:00AM has ended 15:51:10 Attendees were manu, niklasl, scor, gkellogg, Ivan, Shane_McCarron 15:51:19 niklasl has left #rdfa 15:51:21 and hope you have a very happy rest of your birthday scor! :) 15:52:31 rrsagent, make logs public 15:56:12 trackbot: bye 15:56:12 trackbot has left #rdfa 15:56:19 rrsagent, bye 15:56:19 I see no action items