w3c / w3c/json-ld-api

Meaning of "ordered by" in Node Map Generation step 6.12

Open
#586 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Editorial editorial:class 2 ErratumRaised spec:editorial
Dominant language
HTML
Stars
106
Forks
40
PR merge metrics
No merged PRs in 30d

Description

Recent versions of the "Latest editor's draft" have changed many of the references of "lexicographic [order]" to "Unicode code point order" which is great.

I'm having trouble getting my implementation to pass toRDF test c019 because, I think, I'm not sure what Node Map Generation step 6.12 means when it states: "Finally, for each key-value pair property-value in element ordered by property perform the following steps:" ... what does "ordered by property" mean? Should I sort the properties by "Unicode code point order" before executing steps 6.12.x or should the properties be processed in the order they were originally inserted into the 'element' being processed?

If I sort the properties by "Unicode code point order" then the test fails because my generated blank node names created in step 6.2 are out of order. I just wanted to make sure I understood the meaning of the phrasing "ordered by property" before I simply stop sorting the properties--which does make the test pass, but leaves me worried I'm missing something.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read the latest editor's draft around Node Map Generation step 6.12 and compare its wording with the toRDF test c019. Determine whether “ordered by property” requires Unicode code point order or preserves insertion order, then clarify the specification so the intended behavior and test result are unambiguous.

Written by the indexing model from the issue text.

Assessment

Tech stack
json
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.