Gregg Kellogg

See https://github.com/ruby-rdf/rdf-ldp/issues/35

- gkellogg: the only other reason to push this is conceptual purity [2:50pm] tjohnson: \* bendiken: it could be quite painful externally

The interface has always been JsonLdProcessor, going back to 1.0. In JSON-LD 1.0, WebIDL didn't have any Exposed attribute, so it wasn't relevant then. It is now, as a global,...

Note that Normalization is a different spec than JSON-LD; JSON-LD 1.0 makes some claims about blank node labeling, which is _not_ the same as normalization. JSON-LD 1.1 relaxes the requirement...

> hmmm, when I paste dr-shorthair's JSON-LD with no changes, it seems to work fine in the playground . > "@context": {"@vocab":"[http://schema.org/"}](http://schema.org/%22%7D) > also works. People can be confused because...

The problem may be because you're using a quoted URL. Try removing the quotes. [This is what I got](https://json-ld.org/playground/#startTab=tab-compacted&json-ld=%7B%7D&context=https%3A%2F%2Fwww.w3.org%2F2019%2Fwot%2Ftd%2Fv1%23).

ToRdf does it’s sorting as part of the expansion algorithm, which is actually optional. Any order to the resulting triples is an artifact of the algorithm execution. List nodes, in...

Sorry if I confused FromRdf and ToRdf, which is usually where ordering issues arise. The FromRdf algorithm, as stated, should be fairly order preserving, although if compacting or framing the...

Apologies for the disruption. Have you considered a PR to include support for the required features without such dependence on internals? To get better alignment with XPath functions, the implementations...

Also, the `< Literal` in your code is likely unnecessary for a monkey patch, but a refinement could be something else to consider.