78 Matching Annotations
  1. Sep 2023
  2. Apr 2023
  3. Nov 2022
  4. Aug 2022
  5. Jan 2022
  6. Jun 2021
    1. In this case, the objective of the consuming application is to find accurate, machine-readable descriptive information that might be used to build an index, and thus the application should use the IIIF Presentation API seeAlso property to retrieve such a description if available.

      Again, accurate, machine-readable descriptive information should be found in the presentation manifest's seeAlso property.

    2. Activities may be published about content that has access restrictions. Clients must not assume that they will be able to access every resource that is the object of an Activity, and must not assume that it has been deleted if it is inaccessible.

      The client cannot assume that all content is free of access restrictions. Furthermore, it cannot be assumed that a resource has been deleted if it is inaccessible.

    3. Whenever an “Add” Activity is encountered, it is semantically similar to a “Create” Activity in that it is the first time that resource is mentioned in the stream. It is, therefore, expected that if there is an “Add”, then there may not be a “Create” for the same resource occurring before it. Similarly, there will be no more references to the resource after a “Remove” or “Delete”.

      In an aggregation service, a resource cannot have a Create before an Add. If a resource is marked as Removed or Deleted, it can't have any other references to it.

    4. "type": "Update",

      All level 0 have a type of "Update." Level 0 assumes that the list is reindexed to remove references to deleted resources.

    5. This specification does not include a subscription mechanism for enabling change notifications to be pushed to remote systems.

      I assume a previous specification supported a subscription mechanism that could notify a remote system when something had been published, updated, or deleted.

    6. Work that is out of scope of this API includes the recommendation or creation of any descriptive metadata formats, and the recommendation or creation of metadata search APIs or protocols. The diverse domains represented within the IIIF community already have successful standards fulfilling these use cases. Also out of scope is optimization of the transmission of content, for example recommendations about transferring any source media or data between systems

      Things out of scope: recommendation of descriptive metadata formats or the transmission of content. For instance, what would transmission of av look like.

  7. Mar 2021
    1. Use “01” for an unknown or inexact month or day, and “00” for any unknown or inexact time portion.

      "Use a midpoint for any unknown portion. For instance, if only the year is known, use a date in the middle of the year, and if the datetime is known down to a day, use noon for the time."

    1. nesting items within other items

      "nesting one items property array within another items property array"

      where "property" may be sacrificed for readability, I think

    1. to group the volumes together

      Group them how / where? I'm reading this as "to present the volumes together in a IIIF viewer" or similar, with an implication later in the sentence of changing "while maintaining . . . " to something like "while allowing the user to browse each volume separately [as well]".

    1. http://iiif.io

      Should be https

    2. 1987-01-01T05:00:00Z

      Add to implentation notes above: "If the exact time is not known, then “00:00:00” should be used. Similarly, the month or day should be 01 if not known."

      And change here to 00:00:00

    3. lack of viewer support at this

      "lack of viewer support for date-aware navigation for single manifests"

    4. consumption by

      consumption only by

    5. entries

      Put bit about defaulting to zeroes here.

  8. Feb 2021
  9. Nov 2020
  10. Sep 2018
  11. Aug 2018
  12. Feb 2017
  13. Nov 2016
    1. a specific area of the picture has been selected and rotated

      How can I comment on that specific area? According to http://iiif.io/api/presentation/2.0:

      Although normally annotations are used for associating commentary with the thing the annotation’s text is about, the Open Annotation model allows any resource to be associated with any other resource, or parts thereof, and it is reused for both commentary and painting resources on the canvas.

    2. development of the IIIF technology
  14. Jul 2015
    1. Users need digital collections that contain interoperable content or functionality that facilitates comparative analyses of digital materials.

      Enter IIIF for images