Experimental IRC log sioc-2009-05-27

Available formats: content-negotiated html turtle (see SIOC for the vocabulary)

Back to channel and daily index: content-negotiated html turtle

These logs are provided as an experiment in indexing discussions using IRCHub.py, Irc2RDF.hs, and SIOC.

14:30:43<CaptSolo>a discussion on the SocWeb XG re vCard vocab
14:31:20<CaptSolo>thosch: can you take a look at the wiki if you get a moment?
14:31:25<CaptSolo>just a bit of spam
15:26:35<CaptSolo>hi blx
15:26:42<CaptSolo>ACTION is looking for that SIOC paper quote
15:27:34<CaptSolo>ok, that was the final sentence n the paper and is about P2P query routing
15:27:48<CaptSolo>"In the future, we intend to exploit the
15:27:48<CaptSolo>characteristics of intra- and inter-site links to guide query routing in a P2P-like
15:27:51<CaptSolo>environment."
15:28:22<CaptSolo>http://sw.deri.org/2004/12/sioc/index.pdf
15:28:56<CaptSolo>ok, that is a bit vague, i guess :)
15:32:29<blx>yes, i'm trying here to ditch the "site" concept in general
15:33:54<CaptSolo>if you don't need a term, you just don't use it
15:34:17<CaptSolo>same as someone could just reuse one concept from FOAF or SIOC and not use others (if not needed)
15:35:03<CaptSolo>ACTION made a Resume RDF vocab long time ago. someone was reusing just one property from it - to indicate sex of a person :)
15:35:51<CaptSolo>blx: it will be interesting to see what data structure you come up with
15:36:20<CaptSolo>will you need some kind of a hash-based lookup like with .magnet links?
15:36:34<blx>i am not aware of .magnet links
15:36:51<CaptSolo>if you need to sketch out concepts to use for this use case, feel free to create a page on the SIOC wiki
15:37:04<CaptSolo>blx: that's a bittorrent concept
15:37:15<CaptSolo>it is not specific to bittorrent, just used there
15:37:23<blx>reading the wikipedia entry
15:37:50<CaptSolo>magnet link contains the hash of content which you can use to look the content up on DHT
15:38:39<CaptSolo>someone played with putting RDF on bt and how you would use magnet URIs instead of HTTP uris
15:38:54<blx>sounds great
15:38:55<CaptSolo>again, not sure if it is needed for your case
15:39:02<CaptSolo>just throwing around some ideas
15:39:31<blx>i'm thinking that file sharing is something that could give rogue p2p networks an edge over centralized services
15:39:33<CaptSolo>(of course, if content changes then it would not match the same magnet uri)
15:40:01<CaptSolo>not convinced it is in file sharing though
15:40:20<CaptSolo>file sharing is already the most popular use of p2p (i guess)
15:40:35<CaptSolo>but that does not give it an edge unless you are specifically interested in file sharing
15:40:43<blx>yes, but how to get people to break with walled-in communities
15:40:55<CaptSolo>what is interesting to me is how file sharing boosts p2p developments
15:41:01<blx>i would say most people are interested in sharing music/movies with each other
15:41:12<CaptSolo>and how those can then be reused elsewhere, perhaps in more interesting use cases
15:41:32<CaptSolo>but that does not require anything more than what is already there in p2p
15:41:59<CaptSolo>people already do that. so my point is that it's not new.
15:42:00<blx>a funcion like, "hey listen to this song" with an automatic push would be very nice for example
15:42:53<CaptSolo>in that case you would need to push a message "listen to this song" to the p2p cloud
15:43:03<CaptSolo>(e.g. a group of your friends)
15:43:14<CaptSolo>and then they would pull the song from you if needed
15:43:24<CaptSolo>if all have the song already, then you just need that message
15:43:32<blx>good point
15:47:58<CaptSolo>ACTION has to do some work now
15:48:17<CaptSolo>but i am around here most of the time even when away
15:51:40<blx>have fun

Back to channel and daily index: content-negotiated html turtle