See also: IRC log
<mhausenblas> jar, is the reason?
<jar> but I think a good thing has happened: based on David's email I think he and I are in agreement on what the document is about!
Michael: Still working on motivation
<jar> access log analysis
Michael: One use case is server
access log analysis.
... RDF is nice for that because it enables SPARQL access, but it doesn't scale well because there are lots of log entries.
<jar> HTTP over SPARQL as a use case?
jar: I'm looking at HTTP over SPARQL use case.
michael: We are looking at that also. I'll send a reference.
jar: This is different from what
i was thinking. i'm suggesting http over sparql. If you only
had a sparql connection and you wanted to do http
... proxying through the sparql query to do http.
jar: it's a thought experiment.
it forces you to phrase your request in sparql and represent
your response in rdf, which is essentially what dbooth's ont
and rules and my shell script are doing.
... it's just a way to formulate the problem.
harry, i just gave you the dialin info by private chat. got it?
harry: I just sent jonathan some notes on the ont.
we seem to be in agreement our focus should be on proposing a small ont and rules that indicate what a server is saying (in RDF) when it returns various response codes, such as 200, 301, 302, 303, etc.
harry: the main comment i had on the ont is that we may need to flesh it out to deal with some of these codes, like redirection.
dbooth: how about focusing on one code at a time?
jar: notion of 'resource residing at a location' needs to be understood.
dbooth: to me, that simply means that a client could expect to receive representations when doing requests of that location.
harry: this particular location issue we tried to deal with in IRW by having a location property between the resource and what we call the server.
jar: I would say when you send the request uri to the server it calculates a rep of the thing identified and the server transmits it back to the client. the server is competent to send reps.
<jar> the server is the source of the response (representation)
jar: ian hickson has said the same thing.
dbooth: i think representing the server will make it easier to explain some of the codes.
AGREED: We'll represent the server that sends reps on behalf of resources.
<jar> so, the 'representation' is synthesized by the server by combining info from the resource with info that it has (e.g. ads, knowledge of how to encode)
dbooth: Suggested work plan: for each http code, collect the suggested rdf assertions (perhaps written in prose) that people have proposed, so we can discuss them one code at a time.
michael: Suggest starting with 200, 400, 500, 301, 404, 409 are the top seven listed in the restful WS book by sam ruby.
<mhausenblas> From http://oreilly.com/catalog/9780596529260
<hhalpin> Obviously, 303 being of interest :)
dbooth: also should include 302 and 303.
Also include: 201, 204 (lower priority),
205 very low priority, 206 low priority,
300, 304, 307,
jar: litmus test should be whether the code says anything about the resource.
<jar> ACTION: mhausenblas to research difference between 400 in 2616 vs. 400 in actual use [recorded in http://www.w3.org/2009/11/17-awwsw-minutes.html#action01]
<trackbot> Sorry, couldn't find user - mhausenblas
<scribe> ACTION: Michael to look into code 400 about whether we should include it [recorded in http://www.w3.org/2009/11/17-awwsw-minutes.html#action02]
<trackbot> Created ACTION-28 - Look into code 400 about whether we should include it [on Michael Hausenblas - due 2009-11-24].
<jar> hhalpin: 409 is interesting
<hhalpin> but I suggest 410 is also very interesting.
<hhalpin> Then the only other one I see of interest is 503.
<hhalpin> take care! got another meeting!
<jar> ACTION jar to research meaning of 417
<trackbot> Created ACTION-29 - Research meaning of 417 [on Jonathan Rees - due 2009-11-24].
<mhausenblas> and added reference to report
<mhausenblas> cya next week
s/dunno - just from his last mail, though//
s|I don't see anything at http://www.w3.org/Guide/1998/08/teleconference-calendar#D20091117||
s/but next week ... maybe he's forgotten about it ;)//
s|jar, is http://lists.w3.org/Archives/Public/www-tag/2009Nov/0031.html the reason?||
s/i think given that we have 3 people converged we should. in fact we are.//
This is scribe.perl Revision: 1.135 of Date: 2009/03/02 03:52:20 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/(866) 210-0476, or international dial-in: (303) 927-2988// Succeeded: s/Dial conference code: 7400898083 #// Succeeded: s/at that/of that/ Succeeded: s/michael, do you know if jonathan scheduled the teleconference bridge?// Succeeded: s/ahm, yeah, he said so ...// FAILED: s/dunno - just from his last mail, though// Succeeded: s/the usual pass code isn't working// Succeeded: s/i will try to reach amy// FAILED: s|I don't see anything at http://www.w3.org/Guide/1998/08/teleconference-calendar#D20091117|| Succeeded: s/i haven't been able to reach amy yet// FAILED: s/but next week ... maybe he's forgotten about it ;)// Succeeded: s/now I know why :)// Succeeded: s/digging out TAG mail that might explain it ...// Succeeded: s|http://lists.w3.org/Archives/Public/www-tag/2009Nov/0031.html|| Succeeded: s/hence I guess jar gave priority to the other action and somehow decided that it is not necessary to meet every week now// Succeeded: s/just my 0.02€ ;)// Succeeded: s/i'll see if i have a mobile phone number for him// Succeeded: s/calling his mobile...// Succeeded: s/that was quick .... or coincidence? :)// Succeeded: s/hi sorry i dropped the ball here.// Succeeded: s/i haven't been able to reach amy// FAILED: s|jar, is http://lists.w3.org/Archives/Public/www-tag/2009Nov/0031.html the reason?|| Succeeded: s/let's meet by irc until amy or someone gets us a zakim slot?// Succeeded: s/oh, so we do want to meet? :)// Succeeded: s/i haven't been able to reach amy// FAILED: s/i think given that we have 3 people converged we should. in fact we are.// Succeeded: s/but i have done no more work.// Succeeded: s/here, i'll give you my teleconf number....// Succeeded: s/well, is there much to discuss or are we mainly supposed to produce text?// Succeeded: s/For participants:// Succeeded: s/(1) Dial// Succeeded: s/(3) When prompted, speak name, then press #// Succeeded: s/(4) Hang up when finished// Succeeded: s/i'll try dialing in now// Succeeded: s/dbooth: international dial-in: (303) 927-2988 ... ahm without the 001 for US?// Succeeded: s/"leader has not yet arrived"// Succeeded: s/muzack still.// Succeeded: s/muzack// Succeeded: s/still connecting....// Succeeded: s/michael, you will need the country code 1// Succeeded: s/dunno - just from his last mail, though// Succeeded: s|I don't see anything at http://www.w3.org/Guide/1998/08/teleconference-calendar#D20091117|| Succeeded: s/<mhausenblas> ta// Succeeded: s/<mhausenblas> yeah// Succeeded: s/but next week ... maybe he's forgotten about it ;)// Succeeded: s/<mhausenblas> ok// Succeeded: s/<jar> no it's not.// Succeeded: s/<mhausenblas> good// Succeeded: s/<jar> i think given that we have 3 people converged we should. in fact we are.// Succeeded: s/<mhausenblas> wonderful// Succeeded: s/<dbooth> (2)// No ScribeNick specified. Guessing ScribeNick: dbooth Inferring Scribes: dbooth Present: David Michael Harry Jonathan Got date from IRC log name: 17 Nov 2009 Guessing minutes URL: http://www.w3.org/2009/11/17-awwsw-minutes.html People with action items: mhausenblas michael[End of scribe.perl diagnostic output]