integer JSON value should be expanded to an IRI in presence of a base IRI
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 106
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Point 8 in IRI Expansion
https://www.w3.org/TR/json-ld11-api/#iri-expansion
says nothing about an integer JSON value that is expanded to an IRI in presence of a base IRI .
So this should be allowed, but the JSON-LD engines I know do not process an integer JSON value in this way.
I already made this issue, with an example:
https://github.com/json-ld/json-ld.org/issues/742
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.
Research direction
Start with point 8 of the JSON-LD 1.1 IRI Expansion algorithm and review the linked json-ld.org issue 742 for the example and prior discussion. Compare the stated behavior with the JSON-LD engines mentioned in the issue. Done means the specification clearly resolves integer JSON values in the presence of a base IRI and the relevant behavior is agreed by the working group.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100