I'm trying to make use of json-ld.net expansion and contraction given the json-ld formatting I'm seeing from major retailers. Are you aware of a discrepancy that follows?

In the repo readme, the example for expansion in the installation uses this example for the json-ld to be expanded:

{"@context":{ "test":"http://www.example.org/"},"test:hello":"world"}

However the major retailers I've looked at have it in something like the following format:

{"@context":"https://schema.org/", "@type":"Product", "image":"https://exampleimage.jpeg/",
 "name":"fake product name", "sku":"2345624623", ...}

So rather than have context be an object containing name/value pairs with what looks like individualized contexts for each thing we could expand, these retailers just list a single context url that I assume is supposed to be applied to everything else in the json-ld.

The Expand() method doesn't properly process inputs that don't have context as an object. It gives the error: error loading remote context

So my question is whether I'm needing to provide something more for Expand() to properly assign context to each name/value pair in the json-ld contents based on the single context url these retailers provide, or if I'll have to tweak the incoming json-ld format in order to feed it to the expand algorithm in a way it can process properly.

Please let me know if I'm misunderstanding. I'd be happy to hop on a quick call via Zoom or whatever if that's fastest for you. Thanks so much.

The way this library is expecting the context to be formatted doesn't seem to match google's structured data examples for products, nor any of the retailers I've looked at. So it's a bit confusing. https://developers.google.com/search/docs/advanced/structured-data/product#single-product-page