Allow processing model of @type to be customized

[gkellogg]

I think the root cause of the issue is that @type has its processing model constrained by the specification, rather than by interpreting the context (and hence @vocab). As @dlongley says, it's compacting to a relative URL rather than a prefixed compact IRI.

Is anyone willing to propose changing the definition of @type? Otherwise I think we have to close the issue as wontfix.

Original issue: precedence of @vocab for compaction too strong? #526.

[dlongley]

I don't think we should change this. My opinion is wontfix.

[gkellogg]

If we've opened the door for @type to have @container: @set, then we might open it to have @vocab: null as well, but this seems like a can of worms, and only serves to make the language more complicated, so I also support wontfix

[azaroth42]

Resolution on WG call of 2018-08-17: Close won't fix. The use case can now be accomplished with longer, scoped contexts and the precedence has other ramifications beyond this particular scenario.