Naming service for the Invisible Internet Protocol

I think the rest of the information infrastructure should be developed 
on top of the Resource Description Framework (RDF) [1]  coupled with a 
DHT. RDF is flexible and powerful and it's gaining lots of support from 
the W3C. The Name Service idea as well as the URI idea (ie 
i2p://jeremiah:www/) work very well within RDF -- it's designed to 
handle URIs. RDF is also very good for other distributed services we'll 
later want to have. It would make a great basis for a keyserver, for 
example, and I have confidence that many centralized services can be 
replaced with RDF + trust metrics.

While RDF doesn't have a massive amount of supporting software at the 
moment, it's well thought out and (I think) it will work truly shine in 
a DHT setting.

I've been planning to work on DHT with support for RDF and various 
trust levels for a while now, but haven't had the time. I'd be more 
than willing to help with this and to explain it.

For those who don't know anything about RDF, it's a standardized way of 
expressing information that, along with a DHT, has the power to work 
like a giant relational database.

-Jeremiah

[1] http://www.w3.org/RDF/