Use remote context instead of embedded one

[acka47]

See #87 (comment)

[acka47]

https://github.com/skohub-io/skohub-vocabs/blob/master/src/context.js has to be published somewhere and referenced it in every vocab/concept description instead of embedding the whole context.

The context should be created for each SkoHub instance separately, e.g. https://skohub.io/context.jsonld & https://openeduhub.github.io/context.jsonld

Right, @literarymachine?

[literarymachine]

The context should be created for each SkoHub instance separately, e.g. https://skohub.io/context.jsonld &
https://openeduhub.github.io/context.jsonld
Right, @literarymachine?

Not sure how to best approach this yet. Which part of the "SkoHub" instance is responsible to deploy the context? Manual deployment? We could also create a context file when a vocab is built with skohub-vocabs and deploy it along with the vocab. This would result in many copies of the context being made available, but each vocab build would remain self-contained.