Gregg Kellogg

Some tests still required for XHR and Node documentLoaders. Some work needed to optionally append text/html (and application/xhtml+xml) to accept headers if we can parser HTML. Perhaps some abstracted parsing...

Perhaps the webpack build is failing because it doesn't include xmldom? Should there be a way to condition tests on this? How?

@davidlehn are we waiting for something else to merge this?

Sounds like we should add another test.

> I don't recall the reason it's matching on types to do the term compaction. I think that's how it's supposed to work but I'm unsure. When compacting, it's necessary...

Try using `”@type”: “@none”` in the term definition for values you want to keep expanded when compacting, possibly also using `”@container”: “@set”`.

> Here's another good one: I created [`rdf-lmdb`](/doriantaylor/rb-rdf-lmdb) a while ago but only recently noticed, incidentally when I had a structure containing a lot of `RDF::List`s, that blank node IDs...

Please go ahead and do a PR for this, then. @no-reply may want to chime in on it.

See https://github.com/w3c/wot-thing-description/issues/894 and [playground](https://json-ld.org/playground/#startTab=tab-compacted&json-ld=%7B%22https%3A%2F%2Fwww.w3.org%2F2019%2Fwot%2Ftd%23hasPropertyAffordance%22%3A%5B%7B%22http%3A%2F%2Fpurl.org%2Fdc%2Fterms%2Ftitle%22%3A%22Switch%22%7D%5D%2C%22http%3A%2F%2Fpurl.org%2Fdc%2Fterms%2Ftitle%22%3A%2246203%22%7D&context=%7B%22%40context%22%3A%7B%22td%22%3A%22https%3A%2F%2Fwww.w3.org%2F2019%2Fwot%2Ftd%23%22%2C%22dct%22%3A%22http%3A%2F%2Fpurl.org%2Fdc%2Fterms%2F%22%2C%22properties%22%3A%7B%22%40id%22%3A%22td%3AhasPropertyAffordance%22%2C%22%40type%22%3A%22%40id%22%2C%22%40container%22%3A%22%40index%22%2C%22%40context%22%3A%7B%7D%7D%2C%22title%22%3A%22dct%3Atitle%22%7D%7D).

There was code to freeze these contests, but it was too expensive too. Might be worth doing it to see where it’s being modified and only duo when necessary.