Related to w3c/json-ld-syntax#174.

How do you handle expansion test tm008? Previously, the context passed to expanding values includes those for the type index, but now the expansion algorithm removes those terms.

It seems to me that the object value needs to be changed before it's expanded to include the type index as a value of @type (or its alias) so that it will be considered there. This makes type map processing different than for other indexes.

FWIW, my solution was to pass a fromMap flag to expansion when expanding values of a map, which will note clear these term definitions.

@gkellogg,

FWIW, my solution was to pass a fromMap flag to expansion when expanding values of a map, which will not clear these term definitions.

Sorry, only just now seeing your question -- and I agree with your solution. I was previously passing a flag insideTypeContainer that would prevent the clearing of the term definitions, but it wasn't general enough for the new test case you added that combined indexes and type containers. I've updated my implementation to use an insideIndex flag that has the same meaning as your fromMap flag -- and jsonld.js now passes your new test as well. Thanks!

JFYI, I'm planning on merging this PR on Monday to move things forward with the VC @context.

I’ll have an update to the API PR today, probably won’t get to the syntax. Until after WWW.