15:00:47 RRSAgent has joined #rdf-wg 15:00:47 logging to http://www.w3.org/2013/10/09-rdf-wg-irc 15:00:49 RRSAgent, make logs world 15:00:49 Zakim has joined #rdf-wg 15:00:51 Zakim, this will be 73394 15:00:51 ok, trackbot; I see SW_RDFWG()11:00AM scheduled to start now 15:00:52 Meeting: RDF Working Group Teleconference 15:00:52 Date: 09 October 2013 15:01:21 Arnaud has joined #rdf-wg 15:01:40 Zakim, this is rdf 15:01:40 ok, TallTed; that matches SW_RDFWG()11:00AM 15:01:43 Zakim, who's here? 15:01:43 On the phone I see [GVoice], OpenLink_Software 15:01:45 On IRC I see Arnaud, Zakim, RRSAgent, pfps, ivan, gkellogg, AndyS, TallTed, davidwood, yvesr, manu, trackbot, sandro, ericP 15:01:52 Zakim, OpenLink_Software is temporarily me 15:01:53 +TallTed; got it 15:01:53 Zakim, mute me 15:01:53 TallTed should now be muted 15:02:02 +Danny 15:02:28 zakim, who is here? 15:02:28 On the phone I see [GVoice], TallTed (muted), Danny 15:02:29 On IRC I see Arnaud, Zakim, RRSAgent, pfps, ivan, gkellogg, AndyS, TallTed, davidwood, yvesr, manu, trackbot, sandro, ericP 15:02:35 +Arnaud 15:02:40 zakim, gvoice is me 15:02:40 +pfps; got it 15:02:45 +Ivan 15:02:53 +PatH 15:03:00 zakim, mute me 15:03:00 Ivan should now be muted 15:03:15 +[IPcaller] 15:03:19 zakim, IPcaller is me 15:03:19 +AndyS; got it 15:03:28 PatH has joined #rdf-wg 15:03:45 -pfps 15:03:55 zakim, who is here? 15:03:55 On the phone I see TallTed (muted), Danny, Arnaud, Ivan (muted), PatH, AndyS 15:03:56 markus has joined #rdf-wg 15:03:58 On IRC I see PatH, Arnaud, Zakim, RRSAgent, pfps, ivan, gkellogg, AndyS, TallTed, davidwood, yvesr, manu, trackbot, sandro, ericP 15:04:15 + +1.415.686.aaaa 15:04:19 zakim, I am aaaa 15:04:19 +gkellogg; got it 15:04:30 + +1.540.898.aabb 15:04:31 +EricM 15:04:37 Zakim, I am aabb 15:04:37 +davidwood; got it 15:05:06 scribe: gkellogg 15:05:24 scribenick: gkellogg 15:06:00 Zakim, who is here? 15:06:00 On the phone I see TallTed (muted), Danny, Arnaud, Ivan (muted), PatH, AndyS, gkellogg, davidwood, EricM 15:06:02 On IRC I see markus, PatH, Arnaud, Zakim, RRSAgent, pfps, ivan, gkellogg, AndyS, TallTed, davidwood, yvesr, manu, trackbot, sandro, ericP 15:06:10 zakim, who is talking? 15:06:17 +??P28 15:06:18 zakim, ??P28 is me 15:06:18 +markus; got it 15:06:19 PROPOSED to accept the minutes of the 9 Oct telecon: 15:06:19 15:06:19 https://www.w3.org/2013/meeting/rdf-wg/2013-10-02 15:06:22 pfps, listening for 10 seconds I heard sound from the following: davidwood (18%) 15:06:24 zakim, EricM is temporarily Sandro 15:06:24 +Sandro; got it 15:07:33 RESOLVED: Accept the minutes of the 9 Oct telecon: https://www.w3.org/2013/meeting/rdf-wg/2013-10-02 15:07:53 http://www.w3.org/2011/rdf-wg/track/actions/pendingreview 15:08:00 topic: open action items 15:08:31 I changed the status of a number of items that appear to be done 15:10:06 davidwood: guus has an agenda item about public responses. His preferences would be that editors send an ack of receipt and create an issue for it. 15:10:23 … Other members of the group should not comment on public-rdf-comments until we've had a chance to discuss it. 15:10:53 … (either email or on telecon). We should agree if anyone other than editors will make a response. 15:11:18 pfps, are you going to be able to get on the phone soon? 15:11:23 pfps, do you want us to wait to discuss the test suite for Semantics? Will you be able to join by phone later? 15:11:32 peter, can we do the sematnics test suite or does it need phone input? 15:12:08 let's wait for a bit 15:12:12 ok 15:12:23 topic: Turtle 15:12:33 pfps, we're moving on for now, hoping you'll join us soon. 15:12:54 Zakim, please dial ericP-mobile 15:12:54 ok, ericP; the call is being made 15:12:55 +EricP 15:13:03 davidwood: issue-119, spec should reference the test suite 15:13:09 AZ has joined #rdf-wg 15:14:14 action: ericp to update Turtle ED to reference the test suite. 15:14:14 Created ACTION-306 - Update turtle ed to reference the test suite. [on Eric Prud'hommeaux - due 2013-10-16]. 15:14:31 ericp: I had to do some stuff by hand to the publication, so that needs to be copied back. 15:14:32 + +81.16.5.aacc 15:14:43 action-152? 15:14:43 action-152 -- Gavin Carothers to Create new issue for :'s in the local part of prefix names -- due 2012-03-21 -- CLOSED 15:14:43 http://www.w3.org/2011/rdf-wg/track/actions/152 15:14:44 Zakim, aacc is me 15:14:44 +AZ; got it 15:15:00 -AZ 15:15:12 ericp: We're not inventing much, and there's no current candidate for how to do this reification. 15:15:31 … Did it disappear? 15:15:33 +AZ 15:15:36 sandro: I don't think so. 15:15:59 +Souri 15:16:18 http://www.w3.org/TR/REC-rdf-syntax/#section-Syntax-reifying 2.17 Reifying Statements: rdf:ID 15:16:19 ericp: I prepose we say that there's no existing proposal for this; we're largely sticking with Turtle from before we got docs. There's no plan to do something about this, very sorry. 15:16:35 davidwood: fine with ericp giving a response. 15:16:48 zwu2 has joined #rdf-wg 15:16:50 ericp: not that WG has provided a standard for datasets and "named graphs" 15:16:57 davidwood: point him to TriG 15:17:19 action: ericp to respond to Joe Rockmore relating to issue-152 and close if okay 15:17:19 Created ACTION-307 - Respond to joe rockmore relating to issue-152 and close if okay [on Eric Prud'hommeaux - due 2013-10-16]. 15:17:44 eric: another substantial issue which none addressed. 15:18:02 … There was a question from Jan ???; is there any versioning on Turtle. 15:18:06 + +1.619.663.aadd 15:18:16 … Can I say that there is no proposal for versioning turtle. 15:18:17 zakim, +1.619.663.aadd is me 15:18:17 +zwu2; got it 15:18:37 … It would help people if using accept headers to use new or old turtle. 15:18:56 … It's possible that adding a media-type parameter would keep us from having to do another LC 15:19:04 davidwood: it would be nice to do something. 15:19:16 ericp: it would help people trying to make the transformation. 15:19:28 q+ 15:19:35 +[GVoice] 15:19:36 action: ericp to write up proposal for adding a parameter to the media type registration, if it doesn't require a new LC 15:19:36 Created ACTION-308 - Write up proposal for adding a parameter to the media type registration, if it doesn't require a new lc [on Eric Prud'hommeaux - due 2013-10-16]. 15:19:49 http://lists.w3.org/Archives/Public/public-rdf-comments/2013Apr/0057.html 15:19:52 media type games do not work. 15:19:57 -[GVoice] 15:20:09 ericp: I think it's comment 33 in the CR LC comments 15:20:12 http://www.w3.org/2011/rdf-wg/wiki/Turtle_Candidate_Recommendation_Comments 15:20:40 -EricP 15:21:07 topic: JSON-LD 15:21:08 This is a substantive change to TTL if the MIME type registration changes IMO 15:21:09 issue: media type parameter for Turtle 15:21:10 Error creating an ISSUE: an internal error occurred. Please mail with details about what happened. 15:21:20 issue: media type parameter for Turtle 15:21:20 Error creating an ISSUE: an internal error occurred. Please mail with details about what happened. 15:21:37 davidwood: what's the implication of semantics and comments not being in CR for JSON-LD PR transition? 15:22:01 issue: media type parameter for Turtle 15:22:02 Error creating an ISSUE: an internal error occurred. Please mail with details about what happened. 15:22:03 … Right now, JSON-LD and JSON-LD-API point to Concepts LC with informative semantics, schema and turtle. 15:22:15 … JSON-LD-API has norm to semantics and inform to Turtle. 15:22:18 q- 15:22:29 … I thought we could leave a norm ref to an LC doc 15:22:41 Souri has joined #rdf-wg 15:22:42 action: beat the tracker into submission and create an issue for a version media type parameter in Turtle 15:22:42 Error finding 'beat'. You can review and register nicknames at . 15:22:46 sandro: The normal rule is you can only go back one level, a PR can only point to a CR, not LC. 15:23:00 … Although, we've been moving more to "how stable is this material" 15:23:02 q+ 15:23:10 … We'd be asking for a waver on the rules to do this. 15:23:13 zakim, unmute me 15:23:13 Ivan should no longer be muted 15:23:16 +[GVoice] 15:23:23 … I think JSON-LD isn't ready due to another dependency problem. 15:23:40 … Even if we could go to PR, do we want the REC to point to something other than the other REC? 15:24:15 sandro: we can't make a change to the rec after publication. 15:24:18 ivan? 15:24:29 ack ivan 15:24:30 davidwood: we've done with LC for semantics and concepts, we just need to clean up 15:24:55 ivan: the issue is when we publish REC for JSON-LD, the clean way to do it is to publish them all together. 15:25:15 … Anything else will lead to long discussions. I think we're only talking about 1-2 weeks. 15:25:30 … An edited document needs to go through same AC voting. 15:25:49 sandro: we're talking about 2 months; they want to go no, and the rest are in December 15:27:16 ivan: I don't see this as being solvable. Going to CR now, providing we get the other docs in as well.. The publication of the REC would wait a few months, but in some sense, it looks more ridiculous if we publish a REC in Dec and an edited version a few months later. 15:27:30 sandro: not sure the world can tell the difference between PR/CR and REC 15:27:44 … I also don't think JSON-LD is ready because of Promises. 15:27:54 pfps, we are talking baout JSON publication being delayed by references to RDF. 15:28:03 ivan: I believe the dependencies go to a non-normative section. 15:28:26 … In this sense, we may have to go through a second LC until Promises is resolved. 15:28:36 davidwood: the shortest path is to move concepts and semantics to CR 15:28:56 zakim, mute me 15:28:56 Ivan should now be muted 15:29:20 … If we can get concepts & semantics to CR we can push JSON-LD docs to PR 15:29:27 Topic: LC Comments on Concepts, Semantics 15:29:27 topic: Concepts and Semantics 15:29:35 pfps, not yet. 15:29:49 ISSUE-142? 15:29:49 ISSUE-142 -- LC comment: rdfs:Graph ? comment -- open 15:29:49 http://www.w3.org/2011/rdf-wg/track/issues/142 15:29:51 davidwood: we're now looking at issue-142 15:30:42 pfps: I believe we discussed last week and declined it. 15:30:46 because nobody answered 15:30:49 :-) 15:30:53 sandro: someone was supposed to reply to him 15:30:55 zakim, unmute me 15:30:55 Ivan should no longer be muted 15:31:05 I dont think a formal reply was sent (?) 15:31:44 ivan: I think pfps is right, we forced through a resolution to close it, but we stopped there and didn't give an action to send a reply back to Jeremy 15:31:59 path: I agreed with pfps 15:32:17 ivan: we agreed that the REC will not touch anything around datasets anymore 15:33:11 action-304? 15:33:11 action-304 -- Peter Patel-Schneider to Send a proposed response to jeremy to the wg for comments -- due 2013-10-09 -- CLOSED 15:33:11 http://www.w3.org/2011/rdf-wg/track/actions/304 15:33:18 sandro: pfps took the action on this, and action-304 on pfps to send to WG 15:33:36 pfps: that's been done (I think) 15:33:59 http://lists.w3.org/Archives/Public/public-rdf-wg/2013Oct/0097.html 15:34:09 path: the email thread ended with everyone agreeing, but no-one doing anything 15:35:26 sandro: meta-comment, please put "-" between "issue" and number so tracker can pick them up. 15:35:57 pfps: Jeremy's comment in issue-38, and who to track in issue-142 15:36:16 path: issue-142 quotes from Jeremy's comments, but doesn't mention OWL. 15:36:31 davidwood: what I see in Jeremy's comments was issue-35 15:36:45 sandro: I believe he said that one was supplanting the other. 15:36:56 pfps: then something is messed up with ??? 15:36:59 Looking at http://www.w3.org/2011/rdf-wg/wiki/Concepts_and_Semantics_Last_Call_Comments 15:36:59 I think this response is for ISSUE-151: https://www.w3.org/2011/rdf-wg/track/issues/151 15:37:31 davidwood: the LC Comments say that pfps proposed to issue-38, which relates to issue-151. 15:37:32 ISSUE-38 and ISSUE-35 are very similar 15:37:57 path: at some level, they're the same issue. 15:38:10 sandro: I think in our reply we can address several at once. 15:38:23 ISSUE-35 is about rdfs:Graph while ISSUE-38 is more generally about any vocabulary that would allow to talk about graphs 15:39:01 davidwood: how about combining issue-35, issue-38, issue-142, and issue-151 15:39:29 pfps: I would like to excise the owl:imports issue from the other bits. If we don't, it will continue to infect every other issue. 15:39:51 … I'd like to get a clean break on owl:imports and say that the WG isn't going to touch that. 15:40:20 sandro: I don't think that's the specific issue, just an example. You need to say how it works with RDF 15:40:45 davidwood: The proposed response is that it's out of scope for this WG 15:40:58 sandro: it's not, owl:imports is specifically, but the issue it raises isn't 15:41:16 Peter's proposed response: http://lists.w3.org/Archives/Public/public-rdf-wg/2013Oct/0097.html 15:41:49 sandro: I agree with this response, but it disagrees with pfps 15:42:02 -[GVoice] 15:42:07 That's my message! 15:42:15 Further, if you look at the top two lines of http://www.w3.org/2011/rdf-wg/wiki/Concepts_and_Semantics_Last_Call_Comments I think you will agree that that the response column entries are swapped. 15:42:45 s/this response/what davidw is saying/ 15:43:00 davidwood: pfps' proposed response to Jeremy says that the practice ... 15:43:03 +[GVoice] 15:43:16 … The WG won't be addressing this, and it should be raised against OWL. 15:43:52 … sandro and I said the response is insufficient, as Jeremy is just using this as an example to illustrate his point on graph naming. We need to respond to that, and not on owl:imports specifically. 15:44:29 pfps: if we're doing owl:imports and graph names in issue-38, then I think it is about owl:imports. 15:44:47 … How can this not be about owl:imports 15:45:02 path: because the only relevant point is that owl:imports references a graph. 15:45:21 sandro: he's not saying that owl:imports doesn't work, but it doesn't work when you put it in a dataset 15:45:43 … Datasets are a new thing, and we should say how existing stuff, like owl:imports, works with the new stuff we're creating. 15:46:00 davidwood: Jeremy's saying that the new stuff breaks owl:imports 15:46:30 In owl:imports it refers to a g-box. 15:46:38 owl:imports does not force the imported thing to denote a graph at all 15:46:38 path: it's not that it breaks owl:imports, it breaks the presumption that owl:imports that references a graph. 15:46:46 q+ 15:46:54 pfps: owl:imports doesn't work that way, it's very delicate. 15:46:59 zakim, unmute me 15:46:59 Ivan was not muted, ivan 15:47:19 +1 pfps 15:47:25 … Whatever the common practice is seems to be working, but it has nothing to do with RDF per-say, but with the OWL layer on top of RDF. 15:47:43 … The RDF WG does nothing to prevent this from working, and shouldn't do anything else about it. 15:47:47 ack ivan 15:48:22 ivan: we are arguing over what a reaction might be. Let's send the response back to Jeremy; strictly speaking pfps is right. 15:48:49 … I expect that Jeremy will respond by saying that the real issue is about datasets; Let's not put words into Jeremy's mouth. 15:49:13 sandro: can we handle the other issue first, so it's clear we're not going to do anything about datasets (issue-142) 15:49:29 zakim, mute ivan 15:49:29 Ivan should now be muted 15:49:34 somehow the issues got conflated, which may have been my mistake somewhere 15:49:50 davidwood: we should respond to issue-35 and issue-142 first 15:50:08 … Do you have a proposed response for issue-35? 15:50:17 pfps: I may have mixed up the issues. 15:51:03 will do 15:51:13 davidwood: would you take a look at the issues and make sure they're referenced on the summary page? 15:51:33 ISSUE-147 15:51:33 ISSUE-147 -- LC comment: Definition of "Generalized RDF" -- open 15:51:33 http://www.w3.org/2011/rdf-wg/track/issues/147 15:52:02 q+ 15:52:22 sandro: is the connects on issue-147 reflected in the ED? If so, we can send a response to say we accepted your wording. 15:52:41 davidwood: I think he wanted to move the definition to semantics. 15:53:02 path: we decided to not move it to semantics, but there was some wording from AZ that I think we should use on Concepts. 15:53:17 … This avoids the main objection of david booth's 15:53:31 so someone has to make the change to concepts and send out the message - my proposed response is now in concepts but Pat didn't like that 15:53:52 … The advantage of this wording is that it avoids david's objection. One should not say that a generalized triple/graph is a triple/graph 15:54:09 … In general, it's appropriate to be in concepts, and not semantics 15:54:24 davidwood: in section 7 of concepts, there's a note. 15:54:37 the latest version of concepts has my proposed wording 15:54:39 … This says that use is non-standard and may result in interoperability problems. 15:55:08 … That note was put in place based on david's phraseology. This issue is a separate request to move to semantics. 15:55:20 -[GVoice] 15:55:23 path: I agree we shouldn't do this. 15:55:55 … He also doesn't like the wording, which is still in the concepts draft. I think we can better phrase this, as suggested by AZ and modified by me in email. 15:56:07 +[GVoice] 15:56:25 http://lists.w3.org/Archives/Public/public-rdf-wg/2013Oct/0030.html 15:57:14 That wording is fine by me. 15:57:18 issue: davidwood to make an editorial change to concepts in answer to issue-147 15:57:18 Error creating an ISSUE: an internal error occurred. Please mail with details about what happened. 15:57:47 issue: davidwood to make an editorial change to concepts in answer to action-147 15:57:47 Error creating an ISSUE: an internal error occurred. Please mail with details about what happened. 15:58:27 close issue-157 15:58:27 Closed issue-157. 15:58:36 "the error is in the message" - Marshall McLuhan 15:58:57 RRSAgent, pointer? 15:58:57 See http://www.w3.org/2013/10/09-rdf-wg-irc#T15-58-57 15:59:25 action: davidwood to make an editorial change to concepts in answer to issue-147 15:59:25 Created ACTION-309 - Make an editorial change to concepts in answer to issue-147 [on David Wood - due 2013-10-16]. 15:59:35 close issue-158 15:59:35 Closed issue-158. 16:00:08 issue-148? 16:00:08 issue-148 -- LC comment: IRIs do *not* always denote the same resource -- open 16:00:08 http://www.w3.org/2011/rdf-wg/track/issues/148 16:00:25 -[GVoice] 16:00:35 issue-149? 16:00:35 issue-149 -- LC comment: Intuitive summary needs to be scoped to interpretations -- open 16:00:35 http://www.w3.org/2011/rdf-wg/track/issues/149 16:01:01 path: my preferred response to issue-149 is to simply delete the section. 16:01:19 +[GVoice] 16:01:25 … It's a short 2-3 paragraphs with an intuitive understanding that's causing more problems than it's solving. 16:01:51 -Arnaud 16:02:01 I think that David's response is acceptable. 16:02:08 -AndyS 16:02:22 pfps: I would prefer putting in davids ??? 16:02:50 davidwood: I think he'd' prefer putting in david woods suggestion rather than just removing. 16:02:56 I'm happy with David's response, but if Pat wants to rip out the section, then let's try that. 16:03:04 path: I would rather not do that. There's a long history to this. 16:03:34 +1 16:03:34 … I think putting this in could cause more problems than it solves 16:03:39 +1 16:03:55 davidwood: it's for path and pfps to work out as editors 16:04:07 pfps: question is, who to respond? 16:04:19 path: my response would be that we just remove the section. 16:04:44 pfps: my proposed response could be changed to respond 16:05:13 action: pfps to respond to david black on issue-149 16:05:13 Created ACTION-310 - Respond to david black on issue-149 [on Peter Patel-Schneider - due 2013-10-16]. 16:06:31 I think that all we need is direction from the chairs as to who to ask 16:06:35 s/ask/ack/ 16:06:36 issue-150? 16:06:36 issue-150 -- LC Comment: references and acknowledgements -- open 16:06:36 http://www.w3.org/2011/rdf-wg/track/issues/150 16:07:57 davidwood: removal of editors was a ReSpec problem that would be addressed, but I haven't figured it out yet. 16:07:57 I believe this was a 'private' response, that was not added to tracker... 16:08:44 respec supports this 16:08:49 sandro: if you think it's a problem, sent to spec-prod 16:09:00 davidwood: it used to flow through, and doesn't any more. 16:09:10 sandro: spec-prod@w3.org 16:09:18 … Or look through archives. 16:09:50 http://lists.w3.org/Archives/Public/public-rdf-wg/2013Sep/0052.html 16:10:00 pfps: quick update on test suite 16:10:05 topic: semantics test-suite 16:10:14 pfps: I've got my part done, but waiting for landing page. 16:10:35 … AZ has a set of "torture tests", but it might be good to try to run them through an existing implementation first. 16:10:48 that explains how to fix your respec issue 16:10:58 path: is it the intention that all RDF engines should pass this, or is it just a collection of "hard problems" 16:11:21 sandro: everything that claims to be an RDF simple-entailment reasoner needs to pass, but do we define this? 16:11:44 path: some of AZ's tests were rather obscure. An engine that couldn't handle them would still be useful. 16:12:12 Zakim, please dial ericP-mobile 16:12:12 ok, ericP; the call is being made 16:12:14 +EricP 16:12:23 … They depend on very arcane properties of different datatypes. For example, two datatypes that only have one item in their intersection, which can force classes to be singletons. 16:12:38 … This is clever, but maybe not to useful for an actual implentation 16:13:00 AZ: We did this in 2004 someplace. 16:13:13 sandro: it was in RDF tests, which we're not bringing forward. 16:13:21 AZ: we need chair guidance for how to proceed 16:13:36 s/AZ/sandro/ 16:13:39 sandro: this comes back to cygri's point about semantics being optional, but we didn't get consensus. 16:13:40 az/pfps 16:14:30 has to go to another meeting. Bye guys. 16:14:43 -zwu2 16:14:46 sandro: most systems which handle RDF don't think of themselves as entailment- or consistency-checkers 16:15:05 … There could be some code which would be different if semantics was different 16:15:17 … Nothing about value-spaces of datatypes. 16:15:33 pfps: there should be code which at least looks up the class hierarchy. 16:15:44 path: I don't think you'd expect RDF reasoners to do that. 16:15:55 -AZ 16:16:05 the first RDF working group was before we were born 16:16:29 sandro: that was on RDFS, not RDF, right? 16:16:33 pfps: yes. 16:16:47 sandro: for non-RDFS, simple entailment ... 16:17:05 datatypes are now in basic RDF, not an extension to RDFS 16:17:11 pfps: the tricky ones from AZ were RDFS and positivie/negative integer, which intersect on a singleton 16:17:53 path: in addition, you take that singleton and say some very strange things, like an rdf:Property is a subclass of it 16:18:15 sandro: you're assuming there's a conformance clause? 16:18:35 path: I'm worried that people will take the test suite and fail it and be upset, which they shouldn't be 16:18:48 … We include datatypes in basic RDF now. 16:19:05 sandro: my point is that most implementations that claim to be RDF but not RDFS don't do such reasoning. 16:19:19 … I think RDF-Concepts defines such a system. 16:19:30 davidwood: yes it does, but not say anything about that. 16:19:56 +??P27 16:20:05 Zakim, ??P27 16:20:05 I don't understand '??P27', AZ 16:20:07 Zakim, ??P27 is me 16:20:07 +AZ; got it 16:20:11 … In relation to blank-nodes, we talk about systems for implementing skolemization, but don't define what that is. 16:20:32 sandro: I think Pat has something in mind, and it makes sense to define what such a system must do. 16:20:45 path: why are we publishing test cases? What's the point? 16:20:59 sandro: it only makes sense if we think people are implementing something here. 16:21:10 I updated them because someone thought that it was a good thing to do. 16:21:11 davidwood: we're running out of time today. 16:21:55 -davidwood 16:21:56 -Souri 16:21:57 -gkellogg 16:22:00 -Ivan 16:22:06 -AZ 16:23:04 -markus 16:24:28 http://www.w3.org/TR/owl2-conformance/#Tool_Conformance 16:47:32 -Sandro 16:47:34 -[GVoice] 16:47:37 -EricP 16:47:38 -PatH 16:47:47 -TallTed 16:52:47 disconnecting the lone participant, Danny, in SW_RDFWG()11:00AM 16:52:49 SW_RDFWG()11:00AM has ended 16:52:49 Attendees were TallTed, Danny, Arnaud, pfps, Ivan, PatH, AndyS, +1.415.686.aaaa, gkellogg, +1.540.898.aabb, davidwood, markus, Sandro, EricP, +81.16.5.aacc, AZ, Souri, zwu2, 16:52:50 ... [GVoice] 18:37:34 Zakim has left #rdf-wg