Creation of a dependency to hold the defined route context/base template info

One thing came to my mind after reading @luispc1998 proposal on #22.

I have realised (as many of you surely) that such proposal's route files written in JSON-LD have to include the "@context" key with a specific value.

As it is something that is constant to all files following such pattern, I came with the idea of centralising that "@context" object into some sort of package/class/object/function thing, defining it as a dependency (say on npm for instance) associated with this repo/standard definition and using it from the apps that need it.

The reason for this is to avoid hardcoding such potentially living thing as this document is. This
would mean that whenever this standard evolves, so does the files produced by the applications using this resource. The only thing needed would be to update the dependency.

Although I don't have a clue on how this can be done yet, I will try to conduct a little research on the matter see if I can find something.