In some json-ld using applications, input may be consumed with a default/limplied context, which ensures robustness in case not all participants are "json-ld aware". These are generally not formally specified (except possibly in the "profile", which is a vague thing if there ever was one) but are understood between applications.
Similarly, it may be the case that some ocap-ld applications have "implied caveats", which are not explicitly stated, but which may be understood by all participants, or at least those processing invocations. Should we document this?
In some json-ld using applications, input may be consumed with a default/limplied context, which ensures robustness in case not all participants are "json-ld aware". These are generally not formally specified (except possibly in the "profile", which is a vague thing if there ever was one) but are understood between applications.
Similarly, it may be the case that some ocap-ld applications have "implied caveats", which are not explicitly stated, but which may be understood by all participants, or at least those processing invocations. Should we document this?