Open grenik opened 6 months ago
It looks like type-scoped contexts are applied before @nest
ing, but maybe I missed the part of the specification that states this processing order explicitly.
As for me the spec states the opposite and should behave as I expect:
Semantically, nesting is treated as if the properties and values were declared directly within the containing node object.
And here are even some examples:
The following example works as expected (playground permalink)
is expanded to:
so the URI for
name
is taken from the type-scoped context and is...typed-name
Error:
Once I @nest the @type definition in
__metadata
wrapper object, the typed-context is not applied anymore and thus thename
is not mapped to an IRI, even though@type
is extracted:Example 1:
Playground permalinks: with and without @nest for @type.
results in typed context not being applied and the
name
being not mapped anymore:same if I specify @nest for the @type as well:
I expect the same result as in the original example on top, with
name
being mapped tohttp://example.com/vocab#typed-name