You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The spec says:
"solid:instanceContainer - This predicate maps a type to a Solid container which the client would have to list to get the instances of that type."
My understanding is that this should be interpreted as
"a Solid container containing documents which the client needs to read to get instances of that type."
This interpretation provides an affirmative answer to: #30 (comment) "A container contains documents, not instances of the given type. So does it mean I have to read all documents contained in the container and consider all instances of the type found in those documents?"
This interpretation is based on:
This seems to be how it is implemented in practice at the moment
Additionally, to maintain an open world assumption, it appears that not all the documents in the container are required to contain instances of the registered type.
This may cause surprises, with clients parsing data they do not expect to parse or did not need to parse.
See e.g. NoelDeMartin/media-kraken#34 (comment)
The text was updated successfully, but these errors were encountered:
The spec says:
"solid:instanceContainer - This predicate maps a type to a Solid container which the client would have to list to get the instances of that type."
My understanding is that this should be interpreted as
"a Solid container containing documents which the client needs to read to get instances of that type."
This interpretation provides an affirmative answer to:
#30 (comment) "A container contains documents, not instances of the given type. So does it mean I have to read all documents contained in the container and consider all instances of the type found in those documents?"
This interpretation is based on:
Additionally, to maintain an open world assumption, it appears that not all the documents in the container are required to contain instances of the registered type.
This may cause surprises, with clients parsing data they do not expect to parse or did not need to parse.
See e.g. NoelDeMartin/media-kraken#34 (comment)
The text was updated successfully, but these errors were encountered: