-
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
Issue with order of processing nesting keys in Expansion #295
Comments
Could be optionally ordered as other loops do, but not necessary for interop, given instructions on comparing results. |
@gkellogg doesn't tn004 depend on the ordering here? |
If you see the note on JSON-LD Object comparison, it says that arrays are compared without regard to order. Of course it also says that if the |
@kasei I added words to order nesting-key if As always, please respond if this satisfies your concern. |
#297 looks reasonable, thanks. I had missed the wording about test comparisons and instead got caught up by the title of the test ("Test tn004 Appends nested values from all |
Yes, the "in term order" should be dropped from that test entry, as it's inconsistent with the optional ordering of the algorithm. Ordering can be very expensive, and prohibits many streaming implementations. |
Test tn004 seems to rely on nesting keys being processed in lexicographic order. However, Expansion step 14 does not specify any order on the iteration:
I believe this should instead be:
The text was updated successfully, but these errors were encountered: