Skip to content

Conversation

@anatoly-scherbakov
Copy link

@anatoly-scherbakov anatoly-scherbakov commented Jan 18, 2026

@pchampin
Copy link
Contributor

Following w3c/json-ld-api#677.

I think you meant: "following w3c/json-ld-api#676".
The issue you point to is on a similar, but distinct topic:

Copy link
Contributor

@pchampin pchampin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @anatoly-scherbakov . To be complete, this PR also needs to

  • remove the div #change_api_638 between lines 443 and 449 of index.html, which describes the Candidate Correction
  • line 13891 of index.html, replace the link to #change_api_638 with the text that was in the div removed above

Copy link
Contributor

@pchampin pchampin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

with suggested change

Copy link
Contributor

@davidlehn davidlehn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see the ci workflow here comments out the comparison with the wg common files such as https://github.com/w3c/json-ld-wg/blob/main/common/terms.html. Anyone know why? That check still exists in the api repo. The idea at one point had been to update those common docs then sync here.

Co-authored-by: David I. Lehn <[email protected]>
@pchampin
Copy link
Contributor

I see the ci workflow here comments out the comparison with the wg common files such as https://github.com/w3c/json-ld-wg/blob/main/common/terms.html. Anyone know why? That check still exists in the api repo. The idea at one point had been to update those common docs then sync here.

I think this deserves an issue of its own: #480.

Co-authored-by: Pierre-Antoine Champin <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

4 participants