Consider this jsonld document that uses a type-scoped context: https://tinyurl.com/qm8mux2
which should be equivalent to https://tinyurl.com/vfjfczx (without type-scoping).

I the latter, the @type of foaf:Document is correctly expanded, but in the former, the prefix of the type does not get expanded.

The only way around this is to specify the foaf prefix in the parent context, so it's propagated down, but that defeats the purpose of having type-scoped contexts. They are useful as a way to differentiate in properties that can have multiple types as children (so each context only applies to its type of child), but having to propagate up definitions to the parent context opens this up to ambiguities again.

We can work around this for now on our end by just using the expanded form instead of the prefix notation, but it'd be nice if this could be supported out of the box, as it'd help a lot with composeability.

Thanks a lot 🙂