Closed
Description
The purpose of the @container:@set
functionality (AFAIU) is to ensure that the output is consistent in shape. Thus if there can ever be multiple values, the structure is always an array.
There are two situations in which this functionality could be desirable but is currently not possible:
@type
As it's a keyword, we can only alias it (e.g. astype
) but not define it to have@container:@set
functionality. Meaning that there's a gotcha waiting to happen for ontologies that require or use multiple classes for a single resource instance. See playground@context
Less useful, but@context
will also compact to a single string/object when there might be multiple contexts. See playground
@context
modifying itself seems particularly strange, but the inconsistency for @type
seems solvable if the restrictions in its definition were loosened?
Original issue @type as @container:@set? #512.
(Edit: Note that the playground links demonstrate that these do not work as one might expect, due to the keyword definitions of @type and @context)