16:53:02 hi all. I made http://dig.csail.mit.edu/2007/wiki/Tabulator.rdf 16:53:30 so that you can write anything about the Tabulator 16:58:36 sbp is now known as sbp` 16:58:44 Hi, Kenny! Can I yet add a property to something which has no properties yet? 16:59:22 Actually you was able to do so yesterday. 16:59:43 Really? I couldn't. Let me referesh and try again 16:59:50 there is the little orange bar 17:00:13 I didn't make big changes about the UI yesterday. 17:00:20 Kenny tryy adding a property to: http://dig.csail.mit.edu/2007/wiki/test123.rdf#foo 17:01:16 done 17:04:20 loaded 17:04:46 Eh? That's new. 17:04:53 I get "Type: resource" 17:05:04 Where did that come from? 17:05:12 Yeah, you asked me to add a new property 17:05:24 Oh, so you added that. 17:05:26 ok! 17:05:34 By the way, I already made http://dig.csail.mit.edu/2007/wiki/Tabulator.rdf 17:06:15 OKenny, how did you do that? 17:06:31 Now I want to, for a different symbol in the same file. 17:06:53 soniaswim (i=soniaswi@30-7-172.wireless.csail.mit.edu) has joined #dig 17:06:55 I don't get an orange bar 17:07:16 there's the little orange bar beneath the x. 17:07:26 Not for me 17:08:15 I have foo2 on one line and x on te next, and no hovering with the mouse will bring up an orange line anywhere there. 17:09:06 This is strange. Anyway, this will be resolved as long as blue cross is used instead of orange bar. 17:09:16 I guess I'll do it right now. 17:09:21 Ok, soon I hope :) 17:09:26 That woul dbe good. 17:11:07 by the way, do you think we should direct Foo to Foo.rdf so the naming scheme resembles dbpedia and semanticWiki 17:11:31 Foo should be the subject and Foo.rdf is the document to POST to 17:12:03 No, Foo#this hsoud be the subject and Foo the document. That is better than 303 17:12:06 It is faster. 17:12:15 The .rdf" we should not use. 17:12:36 because the ".rdf" is for just rdf/xml version, there could be a generated n3 version 17:12:43 (or the other way around) 17:13:01 This does add a complication which so far I have not raised. 17:13:34 The tabuator when it does a get for Foo should get foo.rdf, with Locaton: Foo.rdf header. It should remember to save back foo.rdf 17:13:45 Yeah, this is ambiguos. So you think when a user POST to foo both foo.rdf and foo.n3 should be updated? 17:13:55 Yes. 17:14:25 In fact, though, one can generate foo.n3 (or foo.rdf) at GET time, on te server, dynmaiclly. 17:14:37 We shouldn't store both. 17:14:50 (Storing same thing in 2 places --> Bad Idea in databases in general) 17:15:04 Te two representations should both seem to change. 17:15:37 I suppose w could keep a cache in N3. 17:15:59 Might be easier to serve. 17:16:08 Hmm...but about naming, dbpedia uses dbpiedia/resource/subject 17:16:27 And it's awkward if we have wiki/Tabulator#Tabulator 17:16:42 Tabulator#this is fine 17:16:54 It's not really awkward 17:17:12 As theer will be many things in te tabulator file, I guess, liek features and help 17:17:18 and wishlists and so on 17:17:21 Oh, indeed Tabulator# is better 17:18:05 I would use mainSubject and mainSubject#minorSubject 17:18:29 remove Status 404 StatusText Not+Found 17:18:57 Sorry, that was a garbled paste. 17:19:13 A request for http://dig.csail.mit.edu/2007/wiki/test gets 404 17:19:21 apoorva (i=apoorva@31-33-202.wireless.csail.mit.edu) has joined #dig 17:19:54 Hmm-huh, somebody should fix it. 17:23:09 I am a bit surprised as the server in genarl dig.csail etc does do conntent negotiation. 17:23:52 who did that :) 17:25:14 lkagal has quit () 17:28:38 lkagal (n=lkagal1@30-5-196.wireless.csail.mit.edu) has joined #dig 17:39:58 sbp` is now known as sbp 17:45:45 soniaswim has quit (Read error: 110 (Connection timed out)) 17:49:10 apoorva has quit (Read error: 110 (Connection timed out)) 18:11:32 It may have been turned off in a specific .htaccess file for th wiki space. 18:12:15 Ah ... it isn't actually being serv ed by the web server directly at all, the data is in wikwi/data 18:30:33 m: replace orange bar with blue cross, turn off webDav for now 18:36:28 timbl, are you going to fix that .htaccess? 18:48:05 by the way, the server should response an empty file with content-type: application/xml+rdf when GET somthing that doesn't exist or it's impossible for the extension version to create new file. 18:49:34 say, a 404 page written in rdf? 19:02:38 presbrey (n=presbrey@adsl-69-208-83-49.dsl.klmzmi.ameritech.net) has joined #dig 19:03:14 presbrey has quit (Client Quit) 19:03:26 yosi_s has quit () 19:57:41 re empty file, yes, if it is one which the user coud craeet a file. 19:58:09 If its impossible fo the extension version t crete a new file, then it shoul dnot give 404 ... that soudns liek and error, but maybe I don't understand the point. 20:04:14 soniaswim (i=soniaswi@MCCORMICK-SIX-THIRTY-NINE.MIT.EDU) has joined #dig 20:04:25 soniaswim has quit (Client Quit) 20:07:59 the point is, the extension version requires content-type: application/rdf+xml to initiate the outliner. If there is no outliner, of course you can not edit at all. 20:20:28 RalphS has quit ("bye for today") 20:24:02 timbl has quit (Read error: 110 (Connection timed out)) 20:25:54 yosi_s (n=syosi@30-7-176.wireless.csail.mit.edu) has joined #dig 20:45:01 davidli has quit ("exit") 21:12:47 yosi_s has quit () 21:16:04 timbl (n=timbl@m335e36d0.tmodns.net) has joined #dig 22:35:11 lkagal has quit ()