It is unclear why this is defined as JSON-LD. There is NO documentation describing the context file (which is available at http://purl.imsglobal.org/ctx/caliper/v1p2). Has this context file been confirmed as correct?
Certification has no dependence on usage of the context file. The value for the @context will always have the same value (except for some undefined scenarios when there may be a list of context files). Why is this value supplied as part of the payload given that it will always have the same value?
It would be better to remove the @context property entirely and return the binding to pure REST/JSON.
The context file can remain and be used in those no-service based solutions where such a file would be used but the appropriate documentation should be produced.
Colin S.
It is unclear why this is defined as JSON-LD. There is NO documentation describing the context file (which is available at http://purl.imsglobal.org/ctx/caliper/v1p2). Has this context file been confirmed as correct?
Certification has no dependence on usage of the context file. The value for the @context will always have the same value (except for some undefined scenarios when there may be a list of context files). Why is this value supplied as part of the payload given that it will always have the same value?
It would be better to remove the @context property entirely and return the binding to pure REST/JSON.
The context file can remain and be used in those no-service based solutions where such a file would be used but the appropriate documentation should be produced.
Colin S.