w3c / w3c/json-ld-api

Which context should be used to get the term definition in compaction algorithm step 6?

Open
#502 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

defer-future-version Errata spec:bug spec:substantive
Dominant language
HTML
Stars
106
Forks
40
PR merge metrics
No merged PRs in 30d

Description

I was trying to get my implementation of the compaction algorithm to pass test c013 and I think that the spec may be misleading. Step 5 reverts active context if there is a previous context (unless dealing with a value or simple @id reference). Step 6 then looks for a term definition for active property in active context. When following this my code fails test c013 which has a nested property-scoped context inside the type-scoped context. Looking at the code of jsonld.js, it seems that library uses the context passed into the algorithm (called type-scoped context in the algorithm). If I do the same then my code passes and no other tests break (that aren't already broken ;-) - so is the jsonld.js implementation correct?

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

Compare algorithm steps 5 and 6 with test c013 and the context handling in jsonld.js, focusing on the nested property-scoped context inside the type-scoped context. Trace which context each implementation uses, then clarify the specification or implementation so the intended behavior is explicit and c013 passes consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
data
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 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.