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
There's no mention of @context in the API documentation. This is due, in part, to the realization of the complexity of context management across multiple specifications that are linked, but should not be tied together: IIIF/api#1571
Given the ActivityStreams focus, the only entries a context needs beyond the default AS context, is the IIIF classes for the objects. However, we need to decide (per #12 etc.) what the scope of those classes is.
The documentation is, however, incomplete without some sort of decision on this.
The text was updated successfully, but these errors were encountered:
I think I would be fine at this stage to put an editor's note pointing to here, acknowledging that we are aware of the issue and will work on it once the spec is more mature, re. the full list of elements that we want to include. This would save some effort that would have to be re-done afterwards, partly.
Would it be ok on your side?
There's no mention of
@context
in the API documentation. This is due, in part, to the realization of the complexity of context management across multiple specifications that are linked, but should not be tied together: IIIF/api#1571Given the ActivityStreams focus, the only entries a context needs beyond the default AS context, is the IIIF classes for the objects. However, we need to decide (per #12 etc.) what the scope of those classes is.
The documentation is, however, incomplete without some sort of decision on this.
The text was updated successfully, but these errors were encountered: