03:20:49 the reason why adding statements to http://rdfspace.net/wiki/test4.rdf#a would cause an error is because of parser bug, I think. 03:21:53 By the way, some of n3 statements can't be serialized in RDF/XML. 03:22:14 Some of which n3 statements? 03:23:01 Yes, that's the problem. 03:23:39 It seems that ffox gives rdf parser a valid document whcih has a special form 03:23:53 like : 03:23:53 XML Parsing Error: mismatched tag. Expected: . 03:23:53 Location: https://192.168.10.30:7071/zimbraAdmin/?debug=1 03:23:54 Line Number 1, Column 999:Apache 03:23:57 <timbl> ... 03:24:09 <timbl> See http://www.zimbra.com/forums/administrators/1646-zimbra-admin-login-problem.html 03:24:14 <timbl> anyway. 03:24:24 <timbl> That is a problem with how it handles XML erors. 03:25:33 <kennyluck_> So...Let's any other problem so far? 03:25:43 <kennyluck_> Did you try edit other documents? 03:25:46 <timbl> Well, I got distracedt by that one :) 03:27:14 <timbl> Yes, it generated XML which happens to parse as RDF it seems, but with a preictae which can't be serialized in RDF/XML. 03:27:26 <timbl> other documents .. give me an example 03:27:50 <kennyluck_> examples in http://dig.csail.mit.edu/2007/wiki/tabulator#n3 03:28:48 <kennyluck_> by the way, in general, N3 allows statements that are not serializable in RDF/XML. The serializer should deal with that. 03:29:25 <kennyluck_> throw "This document can not be represented in RDF/XML" or so on 03:29:26 <timbl> Whcih serialier? The rdf/xml one? 03:29:31 <kennyluck_> Yes 03:29:42 <timbl> It should thow an erro... doesm't it? 03:29:53 <timbl> Or it could try and extend RDF/XML 03:30:06 <timbl> The cwm serializer used to do that 03:30:17 <kennyluck_> Sounds cool 03:31:04 <timbl> Well, messing with a standard doesn't help normally. 03:31:31 <timbl> We could could presure on the community to extend RDF/XML to handle thse things. 03:32:19 <kennyluck_> Well, for now, we need a user friendly way to reject these actions. 03:33:06 <timbl> Hmm. 03:33:22 <kennyluck_> Say, oshani found that when you clicked the RDF/XML for a N3 only document (TAMI) there's a problem. 03:33:29 <kennyluck_> RDF/XML pane 03:33:30 <timbl> I'm not sure what algae would do .. we would hav to fix algae too. 03:33:47 <timbl> the RDF/XML pane could catch the error and display it. 03:35:47 <kennyluck_> By the way, the error document is actually serializable in RDF/XML right? 03:36:05 <timbl> What did you say the passsword was for te test? 03:36:47 <kennyluck_> user:passwd tabulator:laputa 03:38:11 <timbl> I think I saved it back ... <http://rdfspace.net/wiki/test4.rdf#a> a Person 03:39:17 <timbl> Neat! Wel done! 03:39:36 <timbl> So it manages auth ok 03:40:23 <timbl> So now people can edit WebDav spaces wit tabulator. 03:41:13 <kennyluck_> Still lots of parser+serializer problem, I believe 03:41:43 <kennyluck_> Try an N3 one 03:41:50 <kennyluck_> http://rdfspace.net/wiki/test.n3#a 03:42:46 <timbl> When I look at the 'under th hood' access for http://rdfspace.net/wiki/test4.rdf I can look at the contents view but the 'about view' gives an uncught error. 03:45:18 <timbl> 'uri has no properties' in ur.ks 03:45:32 <DanC_lap> DanC_lap has quit (Read error: 113 (No route to host)) 03:46:20 <kennyluck_> This is a bug I noticed, I can fix that. 03:46:44 <kennyluck_> But I don't quite understand what 'nullabout' is in the data pane of http://rdfspace.net/wiki/test4.rdf 03:46:56 <timbl> That is weird. 03:47:38 <timbl> i have seen it before, but I don't see it now. 03:50:10 <timbl> Ah now I see it 03:51:31 <kennyluck_> And I still see strange behavior when you refresh a document 03:54:28 <timbl> ah .. nullabout 03:54:41 <timbl> from parsing <rdf:Description about="http://rdfspace.net/wiki/test4.rdf#a"> 03:54:48 <timbl> it should be rdf:about 03:55:13 <timbl> serializer bg and parse erro not found in rdf paser 03:56:53 <timbl> fiexed the sreilizer bug ... testing before i check it in 04:01:16 <timbl> parser bug is ner // Property Attributes 04:11:25 <timbl> Ok, now I have saved back a better test4.rdf 04:12:33 <timbl> $ svn commit -m "Bug in parser (don't parse xml error message DOM) and serializer (rdf:about was missing hte rdf:)" 04:12:33 <timbl> Sending js/rdf/query.js 04:12:34 <timbl> Sending js/rdf/rdfparser.js 04:12:34 <timbl> Sending js/rdf/serialize.js 04:12:34 <timbl> Transmitting file data ... 04:12:35 <timbl> Committed revision 12863. 04:12:37 <timbl> $ 04:12:47 <kennyluck_> Cool 04:13:45 <timbl> I get a werid error after I save. 04:13:54 <timbl> in the error console 04:14:10 <timbl> Error: no element found 04:14:10 <timbl> Source File: http://rdfspace.net/wiki/test4.rdf 04:14:10 <timbl> Line: 1, Column: 1 04:14:10 <timbl> Source Code: 04:14:10 <timbl> ^ 04:14:28 <kennyluck_> commit -m "m: check the updatable document of a bnode properly" 04:14:38 <kennyluck_> Commited revision 12864 04:14:48 <timbl> What does that do? 04:15:22 <kennyluck_> So that you don't get error like uri has no property. 04:15:47 <kennyluck_> And you are supposed to be able to edit bnodes if you are using DAV. 04:16:25 <kennyluck_> (The only reason I can think of, that DAV might be better) 04:16:59 <timbl> :) 04:17:11 <timbl> Well, in the SPARQL case you should be able to edit bnodes. 04:17:33 <timbl> It is just a question of working out how much of the graph to send back to identify the bnode. 04:17:50 <kennyluck_> Sure, I think we talked about this during the summer. 04:17:57 <timbl> I saw some code whcih looked like it had been written to do that but I guess it didn't work. 04:18:28 <timbl> userinput.js: // generate path and nailing from current values 04:18:37 <timbl> "nailing" 04:19:11 <timbl> I am heading to bed now, anyway. 04:19:20 <kennyluck_> Oh, good night. 04:19:37 <timbl> I Keep up the good work. 04:19:45 <timbl> s/I// 04:19:50 <kennyluck_> OK. 06:23:42 <kennyluck_> kennyluck_ has quit () 13:12:56 <DanC_lap> DanC_lap (n=connolly@CPE-69-76-220-64.kc.res.rr.com) has joined #dig 14:03:05 <timbl> timbl has quit () 15:39:39 <sandro> sandro has quit ("Getting off stoned server - dircproxy 1.0.5") 15:40:16 <sandro> sandro (n=nnnnnnns@homer.w3.org) has joined #dig 15:54:10 <timbl> timbl (n=timbl@pool-96-237-56-114.bstnma.fios.verizon.net) has joined #dig 16:21:25 <lkagal> lkagal (n=lkagal1@79.68.171.66.subscriber.vzavenue.net) has joined #dig 16:48:03 <DanC_lap> DanC_lap has quit (Read error: 113 (No route to host)) 17:21:34 <timbl> timbl has quit () 18:57:49 <timbl> timbl (n=timbl@pool-96-237-56-114.bstnma.fios.verizon.net) has joined #dig 19:41:12 <kennyluck> kennyluck (n=kennyluc@SIMMONS-FOUR-TWENTY-FOUR.MIT.EDU) has joined #dig 19:59:04 <kennyluck_> kennyluck_ (n=kennyluc@SIMMONS-FOUR-TWENTY-FOUR.MIT.EDU) has joined #dig 19:59:04 <kennyluck> kennyluck has quit (Read error: 104 (Connection reset by peer)) 20:13:21 <DanC_lap> DanC_lap (n=connolly@kci-host64.cust.wifi.sprintpcs.com) has joined #dig 20:21:28 <kennyluck_> kennyluck_ has quit () 20:23:28 <jar> jar (n=chatzill@65-78-28-29.c3-0.arl-ubr1.sbo-arl.ma.cable.rcn.com) has joined #dig 20:38:13 <DanC_lap> DanC_lap has quit (Read error: 110 (Connection timed out)) 21:13:05 <timbl_> timbl_ (n=timbl@pool-96-237-56-114.bstnma.fios.verizon.net) has joined #dig 21:13:05 <timbl> timbl has quit (Read error: 104 (Connection reset by peer)) 21:17:42 <DanC_lap> DanC_lap (n=connolly@kci-host180.cust.wifi.sprintpcs.com) has joined #dig 22:24:56 <DanC_lap> DanC_lap has quit (Read error: 110 (Connection timed out)) 22:49:15 <yosi_s> yosi_s (n=chatzill@static-71-243-122-114.bos.east.verizon.net) has joined #dig 23:47:06 <harveyj> harveyj has quit ()