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
This is the first time the Change Discovery specification has gone through the TRC and it is hoped we are nearing a stable version of the specification and there has already been some implementation experience with early versions of this API.
The Change Discovery API allows machine to machine communication to enable harvesting of IIIF content. It is based on the W3C Activity Streams standard.
Proposed Solution
The Discovery TSG would like the TRC to support the version of the specification linked above. Once this is approved we will encourage implementation and start moving the specification to a full 1.0 release.
The text was updated successfully, but these errors were encountered:
As per 04/15/2020 TRC discussion, note that 3.5 is mostly non-normative, but we don't use the explicit "this section is non-normative" language by convention. However, we can add a paragraph stating that any implementation that obtains the same results as the algorithm described here is conformant to the spec.
Per usual editorial policy, publication of this Discovery spec (currently called 0.5) as a beta for implementation should be done as 0.9 (see e.g. https://iiif.io/api/auth/0.9/)
Links
Background and Summary
This is the first time the Change Discovery specification has gone through the TRC and it is hoped we are nearing a stable version of the specification and there has already been some implementation experience with early versions of this API.
The Change Discovery API allows machine to machine communication to enable harvesting of IIIF content. It is based on the W3C Activity Streams standard.
Proposed Solution
The Discovery TSG would like the TRC to support the version of the specification linked above. Once this is approved we will encourage implementation and start moving the specification to a full 1.0 release.
The text was updated successfully, but these errors were encountered: