Good luck. There's so much good stuff here, it's so basic, but there is such a vast chasm to cross.
#1 task: making every single RDF spec also have JSON-LD encodings. That's literally it. Stop using RDF. Use the equivalent but developer friendly standard.
(Personally, I really like RDFa, because it enriches HTML elements rather than serving as a data-island. But for specs, JSON-LD is the obvious encoding that developers speak!)
Actually, I would say, stop using RDF/XML and JSON-LD. The biggest mistake one could make is to think that JSON-LD is JSON. JSON is a document (tree), JSON-LD (RDF) is a graph. There be dragons if you try to parse JSON-LD graph with a JSON document parser directly.
Use Turtle instead. It will actually be easier that way, as you only need to understand how a graph data format like Turtle works. With JSON-LD, you need to understand both the RDF graph model AND how graphs are encoded in JSON documents in a standard way.
#1 task: making every single RDF spec also have JSON-LD encodings. That's literally it. Stop using RDF. Use the equivalent but developer friendly standard.
(Personally, I really like RDFa, because it enriches HTML elements rather than serving as a data-island. But for specs, JSON-LD is the obvious encoding that developers speak!)