Test tpr19 includes a property-scoped context that includes a null value:
"protected2": {
"@id": "ex:protected2",
"@context": [
null,
{
"protected1": "ex:protected3"
}
]
},When Context Processing is called during expansion of the "protected2" key, why does the first (null) context value here not trigger the error condition in Context Processing step 5.1.1?
5 For each item
contextinlocal context:5.1 If
contextisnull:5.1.1 If
override protectedis false andactive contextcontains any protected term definitions, aninvalid context nullificationhas been detected and processing is aborted.
The design is that property scoped contexts can null out protected contexts, which was the result of some considerable WG discussions.
This is supported by step 6 of the expansion algorithm passing
truefor override protected, which allows this behavior.Issue 90 (w3c/json-ld-api#90) should shed some light on the reasoning.