I've published some Ponderings on RDF Path that I've been scribbling down. RDF Path languages have tended, to date, to be incompletely specified and murky. This one is still under-specified, but I think it solves a lot of the murkiness that has arisen from people conflating (or ignoring) the node and arc difference.
I also sent a message to www-rdf-comments regarding an N-Triples inconsistency, and got a reply from Dave Beckett under two hours later. How's that for service?
Both of the above were spin-offs of an RDF API that I'm working on, in Python, of course. I've already rumoured it a few times, notably on #rdfig to bijan, who seems to be thinking about using it. It's the next step on from the interesting Eep3, built with the same goal of usability. It's got some interesting stuff in it, but I'm wondering how best to document it and deliver it. It needs a catchy name, too.