-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible mistake in Context Processing Algorithm #518
Comments
(I believe 5.1.1 is the step you meant). I think 5.1.1 should check result instead of active context, so the paragraph could read as follows: | If override protected is |
@iherman Should this be marked as Editorial, given our general policy about tests winning out over algorithm text? |
I imagine the next step (5.1.2) may need to talk about setting |
I do not think so. If my understanding is correct, the normative description of the algorithm changes, which may, potentially, affect other implementations (even though the change is not far-reaching). |
Summary: Update the Context Processing Algorithm steps 5.1.1 and 5.1.2 to look for protected term definitions in result not active context and to initialize result to an initial active context as follows:
|
Hi,
Step 5.5.1 of the Context Processing Algorithm says:
The verification is done on
active context
(the input context of the algorithm) and notresult
(the context being built). as far as I understand, this means that the following context, given in compact#tpr01 should be accepted:...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?The text was updated successfully, but these errors were encountered: