-
Notifications
You must be signed in to change notification settings - Fork 34
What is the purpose of from map
in the Expansion Algorithm?
#478
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
Comments
Step 13.8.3.6 of the Expansion Algorithm should pass As noted in the algorithm introduction, it is used to control reverting to a previous context, which can interfere with the semantics of index- id- and type-maps. Removing it from my implementation causes expand#tc013 and expand#tm008 to fail, along with the toRdf versions of these tests. |
This issue was discussed in a meeting.
View the transcriptRob Sanderson: #478Gregg Kellogg: We have a flag “from map” that was not used, but it is actually used, but got lost. It is required for inherited scoped context. If an implementation does not use this, it can not pass the tests. So this would require restoring the use of this flag to fix this. Proposed resolution: Add back from_map to 13.8.3.6 to recursive call for scoped contexts per api #478 (Rob Sanderson) Gregg Kellogg: +1 Rob Sanderson: +1 Ruben Taelman: +1 Benjamin Young: +1 Pierre-Antoine Champin: +1 Resolution #4: Add back from_map to 13.8.3.6 to recursive call for scoped contexts per api #478 |
…e from map parameter to properly manage reverting active contexts. Fixes #478.
@timothee-haudebourg This is fixed in #481. Please let us know if that satisfies your concern. |
It's fine for the text, although it would be nice to have a test that catches the correct use of |
…e from map parameter to properly manage reverting active contexts. Fixes #478.
The Expansion Algorithm requires a boolean
from map
variable as input. Its value is never changed across the expansion algorithms and is always set tofalse
. There are only 3 occurrences of this variable in the whole API document. It doesn't seem to be used.The text was updated successfully, but these errors were encountered: