Standards work is slow: mailing lists, issue threads, and meetings where a single property name can take three sessions. So the fair question is why I spend so much of my time on it instead of writing code people can use tomorrow.
The honest answer is that I want RDF to cover a broad range of use cases. Not the range it covers well today, but the range people actually show up with. What keeps that range narrow comes from several directions: tools that don’t exist, habits in the community, and specifications. Not every specification limits anything, but some are written in a particular mindset, and that mindset is very hard to fix afterwards.