Soni L.
Soni L.
you can see it defined under [IANA considerations - JSON-LD 1.1](https://www.w3.org/TR/json-ld11/#iana-considerations), where it says: > Fragment identifiers used with [application/ld+json](https://www.w3.org/TR/json-ld11/#application-ld-json) are treated as in RDF syntaxes, as per [RDF 1.1...
unfortunately, if you're using `application/ld+json; profile="https://www.w3.org/ns/activitystreams"` (instead of `application/activity+json`), then you're using JSON-LD. thus, if they're supposed to be synonymous... it would be unfortunate to handle them differently.
it might be useful to raise this issue on art@ietf or thereabouts, then. they probably know more about this stuff than we do.
(sorry for the force push, forgot to rebase)
somehow we have managed to break the `lint` task. that's a new one.
(CIFuzz failing is expected because CIFuzz is stored out-of-tree, see https://github.com/google/oss-fuzz/tree/master/projects/wabt - this should actually be changed if we're understanding the oss-fuzz documentation correctly, but either way it'll require coordination...
we think we should migrate the fuzzers from oss-fuzz into wabt first, seems like a better idea.
Arguably wasmtime's "nothing on stack" is a little better, and we should maybe improve that in wabt. But between the lack of line numbers and the lack of spans, in...
here's something that would help a lot, and we don't have an equivalent to compare it to: when a component import fails, print the expected and real types
you support standalone wasm, but standalone wasm is unusable without custom imports