Json-ld playground and possibly other json-ld processing libararies require that the server responds with proper content-type header "application/json" or "application/ld+json". So right now the UN context url can't be recognized as valid json-ld context.
Side note: the edi3 server, where the context file was prevoiusly hosted, has the correct header:
Currently UN json-ld context located at https://service.unece.org/trade/uncefact/vocabulary/uncefact.jsonld and on GET request the server responds with empty content-type header:
Json-ld playground and possibly other json-ld processing libararies require that the server responds with proper content-type header "application/json" or "application/ld+json". So right now the UN context url can't be recognized as valid json-ld context.
Side note: the edi3 server, where the context file was prevoiusly hosted, has the correct header: