Possible mistake in Context Processing Algorithm
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Domain
- documentation
Research direction
Start with Step 5.5.1 of the Context Processing Algorithm and the compact-manifest test compact#tpr01. Compare the protected-term check against the example context and determine whether active context or result produces the specified behavior; done means the algorithm wording and the test expectation agree.
Written by the indexing model from the issue text.
Description
Hi,
Step 5.5.1 of the Context Processing Algorithm says:
If
override protectedis false andactive contextcontains any protected term definitions, aninvalid context nullificationhas been detected and processing is aborted.
The verification is done on active context (the input context of the algorithm) and not result (the context being built). as far as I understand, this means that the following context, given in compact#tpr01 should be accepted:
{
"@context": [
{
"@vocab": "http://example.com/",
"@version": 1.1,
"protected": {"@protected": true}
},
null
]
}
...but it is not. An invalid context nullification is expected to be returned. So my conclusion is that in Step 5.5.1 of the processing algorithm, result must be used to check the presence of protected term definitions, and not the original active context. Is that correct?
- Dominant language
- HTML
- Stars
- 106
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from w3c/json-ld-api
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
w3c/json-ld-api#718 · 1 reaction ·
-
w3c/json-ld-api#717 · 1 reaction · 1 assignee ·
-
needs discussion
Difficulty 3/5 1-2 days Newbie friendliness 68/100
w3c/json-ld-api#708 · 11 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
w3c/json-ld-api#701 · 3 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
w3c/json-ld-api#700 · 2 comments ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
bancolombia/sentinel#22 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
objectionary/hone-maven-plugin#1061 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
redhat-developer/rhdh-plugins#4887 · 2 comments ·