13:50:13 RRSAgent has joined #rdfa 13:50:13 logging to http://www.w3.org/2010/08/05-rdfa-irc 13:50:15 RRSAgent, make logs world 13:50:15 Zakim has joined #rdfa 13:50:17 Zakim, this will be 7332 13:50:17 ok, trackbot; I see SW_RDFa()10:00AM scheduled to start in 10 minutes 13:50:18 Meeting: RDFa Working Group Teleconference 13:50:18 Date: 05 August 2010 13:50:25 Agenda: http://lists.w3.org/Archives/Public/public-rdfa-wg/2010Aug/0006.html 13:50:29 Chair: Manu 13:50:55 Present: Knud, Manu, Shane, Mark 13:53:02 Regrets: Ivan 13:58:04 ShaneM has joined #rdfa 13:58:18 SW_RDFa()10:00AM has now started 13:58:25 +Knud 13:58:33 markbirbeck has joined #rdfa 13:58:39 am I scribing today? 13:58:43 tinkster has joined #rdfa 13:58:55 +manu 13:59:01 + +44.785.583.aaaa 13:59:09 Scribe: Knud 13:59:12 zakim, aaaa is me 13:59:12 +tinkster; got it 13:59:24 zakim,mute me 13:59:24 tinkster should now be muted 13:59:57 I muted my phone 14:00:51 :) 14:01:13 I'm usually lurking and listening anyway 14:01:43 zakim, who is on the call? 14:01:43 On the phone I see Knud, manu, tinkster (muted) 14:01:53 zakim, code? 14:01:53 the conference code is 7332 (tel:+1.617.761.6200 tel:+33.4.26.46.79.03 tel:+44.203.318.0479), markbirbeck 14:02:46 zakim, unmute me 14:02:46 tinkster should no longer be muted 14:03:02 Silly of me to waste time trying the London number... 14:03:24 i can hear me echoing back 14:03:25 I can hear toby 14:03:29 hmm 14:03:43 +??P10 14:03:46 zakim, i am ? 14:03:46 +markbirbeck; got it 14:03:55 hmm, my audio isn't working now? 14:03:59 no 14:04:02 I'll dial back in. 14:04:15 +ShaneM 14:05:03 zakim, who's here? 14:05:03 On the phone I see Knud, manu, tinkster, markbirbeck, ShaneM 14:05:05 On IRC I see tinkster, markbirbeck, ShaneM, Zakim, RRSAgent, trackbot, manu, Knud 14:05:15 + +8014aabb 14:05:21 zakim, I am ??bb 14:05:21 sorry, manu, I do not see a party named '??bb' 14:05:24 zakim, I am bb 14:05:24 sorry, manu, I do not see a party named 'bb' 14:05:32 zakim, aabb is me 14:05:32 +manu; got it 14:05:32 yes 14:05:41 everyone's echoing. 14:06:01 zakim, mute me 14:06:01 tinkster should now be muted 14:06:09 zakim, who is making noise? 14:06:14 zakim, unmute me 14:06:14 tinkster should no longer be muted 14:06:19 zakim, mute me 14:06:19 markbirbeck should now be muted 14:06:20 manu, listening for 10 seconds I heard sound from the following: manu.a (100%), Knud (57%) 14:06:28 zakim, mute me 14:06:28 Knud should now be muted 14:07:11 no other issues 14:07:13 zakim, unmute me 14:07:13 markbirbeck should no longer be muted 14:07:19 Topic: ISSUE-31: setMapping API location (on Benjamin) 14:07:24 TOPIC: ISSUE-31: setMapping API location 14:07:47 setMapping call should either be duplicated or be moved from context to document interface 14:08:00 document.setMapping("foaf", "http://xmlns.com/foaf/0.1"); 14:08:07 document.data.context.setMapping("foaf", "http://xmlns.com/foaf/0.1"); 14:08:51 manu: document.setMapping could be an alias to context.setMapping 14:09:28 http://lists.w3.org/Archives/Public/public-rdfa-wg/2010Jun/0054.html 14:10:09 mark: still open as to how to implement this 14:10:24 document.setMapping("foaf", "http://xmlns.com/foaf/0.1/"); 14:10:24 var people = document.getItemsByType("foaf:Person"); 14:10:24 ... as long as programmers can get to setMapping via document 14:11:43 manu: would like to keep the idea of context 14:12:07 ... also, some people might be concerned that we pollute the document interface too much 14:12:20 q+ 14:12:35 ack markbirbeck 14:12:38 you are there, mark 14:12:47 Is {document.setMapping("foaf","http://xmlns.com/foaf/0.1/");var people=document.getElementsByType("foaf:Person");} any easier than {var FOAF="http://xmlns.com/foaf/0.1/";var people=document.getElementsByType(FOAF+"Person");} ?? 14:12:51 -manu.a 14:13:12 +manu.a 14:13:16 ack markbirbeck 14:13:49 q+ 14:14:03 ack markbirbeck 14:14:58 mark: now remembers that we steered clear of putting too much into document interface 14:15:19 var context = document.data.context; 14:15:34 context.setMapping("foaf", "http://xmlns.com/foaf/0.1")? 14:15:37 ... so maybe we should rethink how we give people access to something like setMapping 14:15:40 so, people would just do that. 14:16:44 ... there could also be a context parameter to getElementsByType 14:17:28 ... would therefore like to withdraw the suggestion to move setMapping to document 14:18:03 no objection from me 14:18:08 fine 14:18:22 PROPOSAL: Close ISSUE-31 and have Mark re-submit an alternative mechanism to make mappings easier to use. 14:18:33 +1 14:18:34 +1 14:18:35 +1 14:18:37 +1 14:18:43 +1 14:18:47 RESOLVED: Close ISSUE-31 and have Mark re-submit an alternative mechanism to make mappings easier to use. 14:19:02 TOPIC: ISSUE-30: hasFeature clarifications (on Mark) 14:19:19 http://lists.w3.org/Archives/Public/public-rdfa-wg/2010Jun/0053.html 14:19:40 Mark: hasFeature already exists in the DOM in other specs 14:20:00 q+ to discuss RDFa version number 14:20:00 ... our use of it should be aligned, e.g., with respect to the version number 14:20:03 ack manu 14:20:03 manu, you wanted to discuss RDFa version number 14:20:37 manu: mostly agrees with proposal, except: we now want to make RDFa versionless 14:20:56 ... so, just check if RDFa support is available, not a specific version 14:21:31 mark: maybe we should change feature string to "rdfa_api" 14:22:13 document.hasFeature("rdfa-api 1.1") 14:22:37 document.hasFeature("rdfaapi", "1.1") 14:23:03 document.hasFeature("rdfa-api 1.0") 14:23:20 oh woops, Mark is correct 14:23:47 mark: api version is in sync with RDFa core? 14:23:54 document.hasFeature("rdfa-api, "1.1") 14:24:56 So, something like this: document.implementation.hasFeature("rdfa-api, "1.1") 14:25:31 mark: we should not say "we provide hasFeature", but instead "when you call hasFeature, this should happen:" 14:25:43 ... this is in line with how other specs do it 14:26:30 14:26:36 This is boilerplate text: 14:26:38 http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-BBACDC08 14:27:42 tinkster: yeah, that. I really wanted that feature. 14:29:17 PROPOSAL: Bring hasFeature() in line with the DOMImplementation interface, use "rdfa-api" as the feature string, and "1.1" as the version. 14:29:25 +1 14:29:28 +1 14:29:35 +1 14:29:40 http://www.w3.org/TR/DOM-Level-2-Core/introduction.html#ID-Conformance 14:31:10 http://www.w3.org/TR/SVG/feature.html 14:31:12 RDFaApi 14:33:32 "rdfa-api" could be considered a relative URL reference with base http://www.w3.org/TR/. 14:34:09 +1 14:34:24 general discussion on what to use as the feature string: URI, camel case, hypen, ... 14:34:36 s/hypen/hyphen 14:34:45 consistency is the hobgoblin of little minds 14:35:49 PROPOSAL: Bring hasFeature() in line with the DOMImplementation interface, use "RDFaAPI" as the feature string, and "1.1" as the version. 14:36:13 +1 14:36:13 +1 14:36:14 +1 14:36:17 +1 (though I'd still prefer 'rdfa-api') 14:37:05 http://www.w3.org/TR/DOM-Level-2-Core/introduction.html#ID-Conformance 14:37:36 +1 14:37:44 RESOLVED: Bring hasFeature() in line with the DOMImplementation interface, use "RDFaAPI" as the feature string, and "1.1" as the version. 14:38:09 TOPIC: ISSUE-32: TypedLiteralConverter improvements (on Mark) 14:38:15 http://lists.w3.org/Archives/Public/public-rdfa-wg/2010Jun/0055.html 14:38:18 http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#feature-detection 14:38:45 RDFa.API 14:40:32 q+ to point out that we allow functions already. 14:41:12 Mark: we should make very clear how callback functions/methods should be implemented 14:41:39 We already allow callback functions for TypedLiteralConverters: http://www.w3.org/2010/02/rdfa/sources/rdfa-dom-api/#idl-def-TypedLiteralConverter 14:42:44 ack manu 14:42:44 manu, you wanted to point out that we allow functions already. 14:42:58 ... also, people might only want to define one callback function for different datatypes, so the callback function should have a parameter to say what it should convert 14:43:25 ... finally, we should define how the callback reacts when conversion is not possible (exception, return null, etc.) 14:43:36 first class functions 14:45:25 ... for the third point, the parameter should say what the function is converting _to_ 14:45:32 q+ to discuss point 3 14:45:34 ack manu 14:45:34 manu, you wanted to discuss point 3 14:47:10 var converter = function (value) { return new String(value) }; 14:47:10 document.data.context.registerTypeConverter("xsd:string", converter); 14:47:51 document.data.context.registerTypeConverter("xsd:string", 14:47:55 function (value) { return new String(value) } 14:47:55 mark: if there is one function per conversion type, then we wouldn't need the extra parameter. 14:47:59 ); 14:48:23 ... when we want to allow one function for all conversion types, then we need an extra parameter 14:48:46 http://esw.pastebin.com/m9CXB8qh 14:50:37 PROPOSAL: Add a parameter to convertType() that indacates the type that is being converted. 14:50:44 converted to 14:50:56 + 14:51:00 +0 14:51:03 +1 14:51:14 +1 14:51:17 s/indacates/indicates/ 14:51:27 abstain - I don't grok the issue 14:51:36 +1 14:52:19 RESOLVED: Add a parameter to convertType() that indicates the type that is being converted. 14:52:44 we are resolving this issue with a string of different proposals 14:53:33 "23 elephants"^^xsd:integer 14:53:41 Sub-Topic: ISSUE32, point 2 14:54:00 q+ 14:54:49 ack tinkster 14:56:56 "23 blah"^^my:foo 14:57:45 (I'm a bit lost about scribing at the moment) 14:58:26 q+ to end the call. 15:00:41 ack manu 15:00:41 manu, you wanted to end the call. 15:00:55 -tinkster 15:00:57 -markbirbeck 15:00:59 -Knud 15:01:04 -manu.a 15:01:06 -ShaneM 15:01:11 zakim, who is on the call? 15:01:11 On the phone I see manu 15:01:17 zakim, drop manu 15:01:17 manu is being disconnected 15:01:18 SW_RDFa()10:00AM has ended 15:01:20 Attendees were Knud, manu, +44.785.583.aaaa, tinkster, markbirbeck, ShaneM, +8014aabb 15:01:50 manu, will you wrap the minutes up in the right format? 15:01:57 yup :) 15:02:01 Thanks for scribing Knud :) 15:02:02 brilliant, thanks! 15:02:21 no problem 15:06:47 ShaneM has left #rdfa 15:47:04 trackbot, bye 15:47:04 trackbot has left #rdfa 15:47:06 zakim, bye 15:47:06 Zakim has left #rdfa