(closes #555) Fall back to default logic in useNativeTypes mode for RDF numbers which are not JSON numbers

[anatoly-scherbakov]

This is my second attempt to fix this issue after #619.

---

Preview | Diff

[gkellogg]

Minor changes, but this direction seems like the way to go.

[anatoly-scherbakov]

• Todo: implement <ins> & <del> tags

[w3cbot]

This was discussed during the #json-ld meeting on 15 January 2025.

View the transcript

w3c/json-ld-api#625

anatoly-scherbakov: this is the new version of w3c/json-ld-api#619 ; thanks gkellogg and pchampin for your suggestions.

gkellogg: it's a fairly small change.
… However, it is not purely editorial, so it should be turned into a candidate amendment, with <ins>s, <del>s...
… It has to be done manually, not much automation is available for that.

anatoly-scherbakov: I can not wrap a whole block in <ins> or <del>, right?

bigbluehat: correct, they are 'inline'. Is there a specific class to use?

gkellogg: there are other things to put in place. Respec documentation for them is not great, but there are examples in the same doc.

anatoly-scherbakov: what is the use-case for this marking?

gkellogg: it is there for reviewers of the specification, because we are editing a published Recommendation.

anatoly-scherbakov: an HTML diff will not be enough for the reviewers?

gkellogg: no, they do not expect to look at HTML raw code.
… You can look at the W3C process documents that describes the requirements for these things.

<gkellogg> https://www.w3.org/policies/process/#candidate-amendments

bigbluehat: this is required until we recharter. The alternative is to keep a bunch of open PR and merge them only after we recharter.
… I don't know why TallTed's tick is not green.
… In the DID WG, we are using a list of code owners.

---