Relationship to the RDF/JS Dataset interface(s)

This may be way too late... however. I wonder whether it is possible to bring the types defined in 9.2 RDF Dataset Interfaces to the interfaces defined in the RDF/JS: Dataset specification 1.0 and RDF/JS: Data model specification, as worked on by the RDF JavaScript Libraries Community Group. After all our interfaces are very close to the CG's interfaces, although the latter might be a bit convoluted (in RDF/JS a Quad consists of three Term-s, as opposed to strings, Term has its own interface).

This may lead to a backward compatibility issue (I do not know) and may force to change the implementations a bit. But getting closer to a Javascript community is useful.

@rubensworks, I believe you are active in that CG (or at least your colleagues are), any feeling about this?

Again, it may be too late, but acknowledging this relationship in the document, hinting at a possible alignment in future versions may be useful.

Start by reading section 9.2, “RDF Dataset Interfaces,” alongside the RDF/JS Dataset 1.0 and Data model specifications linked in the issue. Compare the interfaces and identify backward-compatibility implications; done would be a decided approach for documenting or pursuing alignment, rather than an unresolved question about future versions.