14:50:39 RRSAgent has joined #rdfa 14:50:39 logging to http://www.w3.org/2011/02/24-rdfa-irc 14:50:41 RRSAgent, make logs world 14:50:41 Zakim has joined #rdfa 14:50:43 Zakim, this will be 7332 14:50:43 ok, trackbot; I see SW_RDFa()10:00AM scheduled to start in 10 minutes 14:50:44 Meeting: RDFa Working Group Teleconference 14:50:44 Date: 24 February 2011 14:57:10 Steven has joined #rdfa 14:57:44 Agenda: http://lists.w3.org/Archives/Public/public-rdfa-wg/2011Feb/0160.html 14:57:59 Chair: Manu 14:59:48 SW_RDFa()10:00AM has now started 14:59:56 +??P13 14:59:58 zakim, I am ??P13 14:59:59 +manu1; got it 15:00:06 +Benjamin 15:00:36 zakim, dial ivan-voip 15:00:36 ok, ivan; the call is being made 15:00:37 +Ivan 15:02:36 +??P17 15:03:23 ShaneM has joined #rdfa 15:03:32 zakim, who is here? 15:03:32 On the phone I see manu1, Benjamin, Ivan, ??P17 15:03:33 On IRC I see ShaneM, Steven, Zakim, RRSAgent, Benjamin, ivan, tinkster, manu1, webr3, manu, trackbot 15:03:39 zakim, ??P17 is ShaneM 15:03:39 +ShaneM; got it 15:04:14 zakim, who is on the call? 15:04:14 On the phone I see manu1, Benjamin, Ivan, ShaneM 15:04:29 Regrets: Toby 15:05:31 zakim, call steven-617 15:05:31 ok, Steven; the call is being made 15:05:33 +Steven 15:05:56 scribe: Benjamin 15:06:15 Topic: HTML WG ISSUE-120 Coordination 15:06:40 http://www.w3.org/html/wg/wiki/ChangeProposals/RDFaPrefixesNoChange 15:06:56 markbirbeck has joined #rdfa 15:07:05 manu: Ivan, Tobi, and Manu have updated the proposal and send it to the HTML working group 15:07:11 zakim, code? 15:07:11 the conference code is 7332 (tel:+1.617.761.6200 tel:+33.4.26.46.79.03 tel:+44.203.318.0479), markbirbeck 15:07:28 ... we think we are ready 15:08:00 +??P5 15:08:07 zakim, i am ? 15:08:07 +markbirbeck; got it 15:08:15 sorry I'm late... 15:09:34 Topic: Preparation for 2nd Last Call 15:09:54 manu: I believe that we have discussed all of the last call issues 15:10:23 ... does anybody know unadressed issues? 15:10:41 (deep silence...) 15:10:51 http://lists.w3.org/Archives/Public/public-rdfa-wg/2011Feb/0044.html 15:10:53 ... nobody knos any 15:11:11 s/knos/knows/ 15:11:11 Yep. 15:11:28 I will send my mails tonight or tomorrow a.m. 15:13:04 manu: Shane can you give a status on your issues? 15:14:27 shane: Issue 70 is still outstanding 15:15:02 Steven: Will send his responses to his issues tonight. 15:17:52 zakim, mute me 15:17:52 Ivan should now be muted 15:18:39 shane, is there anything waiting on me for the document? 15:18:46 shane: Implemented changes on RDFa Core and HTML+RDFA documents 15:19:45 shane: You can point to a live version of a spec in last call responses 15:20:43 manu: we should ask people to review solved issues in live versions of specs before end of the second last call 15:21:40 shane: I could make two versions of the specs, one for us and one we agree upon to show others 15:21:59 manu: anything esle about last call? 15:22:07 silence 15:22:17 Topic: RDF and RDFa API next steps 15:22:37 q+ 15:23:19 ack ivan 15:23:20 ack ivan 15:23:29 manu: Maybe we should invite other people that are familiar with web developements and RDF for working on the RDFa API, RDF API topics 15:24:16 just to be clear - I will also turn up. I just might not add much value. 15:24:37 shane will contribute less to the APIs 15:25:07 Steven: will contribute less to the APIs 15:25:45 Benjamin: I am interested in contributing to the APIs 15:26:24 markbirbeck: I am interested in contributing to the APIs We should also invite Python programmers to contribute. 15:26:51 Ivan: our emphasis should be on the WebApps/JavaScript people. 15:26:55 ivan: Our emphasis should be on web development, Java script people 15:28:13 manu: We should be account RDF/JSON activities when working on the APIs 15:28:39 s/should be/should/ 15:29:36 ivan: I try to invite |firstname| Steiner to join us 15:29:45 Thomas Steiner 15:29:55 s/|firstname|/Thomas/ 15:32:06 manu: We shouold try to contact other people, after the charter is accepted 15:32:26 s/shouold/should/ 15:33:16 Topic: RDFa API Review 15:33:20 manu: anything else about high level issues on the RDFa API? 15:33:25 silence 15:33:46 manu: Any missing features or bugs? 15:34:10 http://www.w3.org/2010/02/rdfa/sources/rdfa-api/ 15:35:23 manu: we have to spend work into property groups and projections 15:35:41 manu: especially work on terminology 15:36:43 markbirbeck: I took nearly all projection-related things from SPARQL 15:37:02 ivan: Should we refer to SPARQL instead of defining it ourself 15:37:19 mark: it is more conceptually related 15:38:52 ivan: Mark, you defined a subset of sparql in the RDFa API, maybe we should use and refer to the terms of SPARQL then. 15:39:47 ivan: this might minimize our own work 15:41:25 manu: we have to check details on projections if it is possible to map it to SPARQL specifications 15:42:18 ivan: We should define our query patterns in a TURTLE like syntax -- that is close to SPARQL 15:43:20 manu: The use of SPARQL might confuse web developers 15:44:05 ivan: we should focus on use the simple parts of SPARQL in our approach. 15:44:44 markbirbeck: My idea was to query with a JSON structure and syntax. 15:46:28 ivan: We should not put complex SPARQL features such as optionals to our query approach 15:46:28 "?s" 15:46:34 "Ivan" 15:46:42 add(a, b) 15:47:48 ivan: we should not provide features such as UNION, OPTIONAL, SUBSELECT 15:48:47 manu: We should further discuss on querying objects in the RDFa API 15:49:59 ivan: There is a similarity between TURTLE syntax and SPARQL patterns. Now there is an emerging JSON serialization of RDF, and our JSON related query features. 15:50:19 ... both, TURTLE syntax and JSON syntax should be allowed 15:51:33 TOPIC: RDF API Review 15:51:40 http://www.w3.org/2010/02/rdfa/sources/rdf-api/ 15:52:20 manu: A prose describing design criterias is missing 15:53:15 ... Nathan and I want a more generalized graph mechanism than RDF allows. 15:54:01 ... these graphs may not be serializable in RDF/XML - we have to coordinate with the RDF working group 15:55:06 ivan: The RDF WG is out of scope of a generalized graph mechanism such as using blank nodes in predicates, or literals as subjects. 15:56:21 ivan: A number of RDF environments already provide such generalized graph mechanisms. 15:59:17 ivan: Often intermediate steps in these systems use versions of graphs that are also not serializable, e.g., for supporting reasoning. When serializing the graph, the generalized graph mechanism are ignored. 16:00:11 ivan: It is not a problem to let serializers be silent on generalized graph mechanisms. 16:00:37 ivan: Graph literals are heaviliy discussed at the moment so we should skip them 16:01:09 q+ 16:01:35 ack benjamin 16:01:49 Benjamin: We should also solve the issue of Term and Prefix maps 16:02:54 ivan: Why are these maps on the API level 16:04:00 manu: they make programming easier as they save code. 16:04:22 q+ to end the telecon 16:04:41 manu: JS developers want to use terms more than prefixes. 16:05:04 I sent my last call replies, by the way 16:05:06 Bye 16:05:13 -Steven 16:05:15 -ShaneM 16:11:42 about="foo" 16:12:21 about="next" 16:15:13 @about="foo" would be a reference to a sibling document to the current document, which is not that common. 16:15:30 I think people are probably thinking of @about="#foo" as the more common one. 16:15:48 @about="./foo" 16:16:24 @about="[foo]" 16:18:18 zakim, make minutes 16:18:18 I don't understand 'make minutes', Benjamin 16:18:50 -manu1 16:18:51 -markbirbeck 16:18:59 zakim, drop me 16:18:59 Ivan is being disconnected 16:19:00 -Ivan 16:19:03 -Benjamin 16:19:04 SW_RDFa()10:00AM has ended 16:19:05 Attendees were manu1, Benjamin, Ivan, ShaneM, Steven, markbirbeck 17:06:19 hey guys, sorry I missed todays meeting :( not been too well the past couple of weeks 17:10:15 ShaneM has left #rdfa 17:12:13 Sorry to hear that Nathan - hope you feel better soon. :) 17:15:44 likewise mate 17:24:57 sorry nathan... take a long week-end off and rest! 17:53:00 webr3 has joined #rdfa 18:22:28 webr3 has joined #rdfa 18:23:04 Zakim has left #rdfa 18:47:39 RRSAgent, bye 18:47:39 I see no action items