Gregg Kellogg

> What was the reason to exclude integers ? > Was it a bad case of copy and paste in the writing ? > Indeed some cases like language demand...

Round-tripping through RDF does impose some restrictions, but the general intent is to allow round-tripping between Expanded and Compacted modes. I think there is another case where we were not...

Looking at this again, i think it's inappropriate to consider this an Erratum, as it is not an error in the spec, rather an enhancement request to be considered in...

Yes, the default should be `false`, which is consistent with the warning that it may go away in the future.

Summary: The default value of the [produceGeneralizedRdf](https://www.w3.org/TR/json-ld11-api/#dom-jsonldoptions-producegeneralizedrdf) option should be `false`, not `true`.

Summary: Update description of round-tripping in B.1.3 with a note about lossy conversion discouraging the use of native numbers where this might be an issue.

The IRI validation for output is actually done in the toRdf algorithm, and this is exclusively a toRdf test (https://w3c.github.io/json-ld-api/tests/toRdf-manifest.html#tli12). If you were to just run the expansion algorithm on...

I'm not sure why you find "invalid IRI" a blurry concept, as RFC3987 describes the ABNF to validate an IRI ("well-formed IRI" might be considered a synonym). But, this has...

If you could do a PR with some specific test changes, it would help. We can evaluate the potential algorithmic changes once that is settled.

> Hi, > > in compaction test 0066, some IRIs are to be compacted relative to the document base IRI. The base IRI is `https://w3c.github.io/json-ld-api/tests/compact/0066-in.jsonld` and an examples of IRIs...