163 Matching Annotations
  1. Sep 2023
    1. adding

      by adding

    2. with


    3. adding also

      also adding

    4. the Web Annotation Data Model, for

      Should the link target be https://www.w3.org/TR/annotation-model/#classes? That seems more pertinent to me.

    5. close up

      "close-up" (and anywhere else "close up" appears as a noun)

    6. attribute

      "property" (and elsewhere that "attribute" is used for a IIIF property)

    7. Tagging, however,

      Tagging. However,

    8. fragment as

      fragment, as

    9. the link of the Canvas

      Canvas id

    10. target

      make this into code formatting

    11. create

      "use" (to avoid repetition)

    12. page it is pointing at

      the correct place.

    13. the area of sections

      a chapter entry

    14. You

      As another possibility, you

    15. In

      For one example, in

    16. conference the

      conference, where the

    17. being


    18. Textual Body


    19. In the case


    20. In the case


    21. Page To

      AnnotationPage. To

    1. authored by a specific person

      If you go with something from Fixtures as part of adding a Service to the Manifests, this might need to get adjusted.

    2. The

      lowercase T

    3. thumbnail

      format as code

    4. Example

      Add Annona. Though the UX is not great, it does support the principle of Collections, pulling in full Manifests from stub entries in the Collection's Manifest

    5. collection


    6. Collections, however

      Collections; however OR Collections. However

    7. full


    8. as an ordered IIIF Presentation resource

      "together in a unified and coherent IIIF Presentation interface."

    9. are already digital objects represented by Manifests

      "already has a digital representation and a Manifest,"

    10. digital

      dele, to help readers go from realia to digital collection

  2. Mar 2023
    1. Canvas per page Mirador, Annona, Universal Viewer, Clover


    2. Febtruary

      => March

    3. the viewer

      "the viewer and any customizations or extensions"

  3. Nov 2022
  4. Oct 2022
    1. One colleague and fellow beneficiary of LIS diversity initiatives has created a mentorship group for students of color

      Is there a way to make connections with similar groups for technologists of color &c.?

    2. Being a nonwhite librarian playing at whiteness is an isolating and lonely practice

      Some cautious parallels to make with gender and disability where race is not part of the identity mix

    3. those applicants who find success in these diversity programs are those who can successfully replicate necessary whiteness

      Small wonder that white women are the primary beneficiaries of affirmative action.

    4. A genderqueer applicant who has since changed names and gender identities

      A good point -- how can applications be open and welcoming to people whose names have changed? Is there a model or the start of one in the attitudes toward women who have professional experience under more than one name, where the name changes are unrelated to gender-based change?

    1. Public Domain Dedication (CC0 1.0 Universal)

      Authors thought there was no need for this. The CC PD is for the metadata, you've got a credit/reference, and the copyright statement at the object page is Public Domain

  5. Aug 2022
    1. canvas


    2. (image, layer etc. etc.)

      The Use Case seems like a good place to link out to the Presentation API 3.0 for the explanation of "content resource", but I think it should be the last sentence, which would allow you to remove this parenthetical.

    3. annotations

      Same as preceding. I lean toward "Annotations", but I won't die for that flag.

    4. annotations

      I think this should be "Annotations" to refer to the IIIF concept, but it's hard to be certain.

    5. to a band of a multi-spectral acquisition stack

      If I think about it, I understand why "acquisition" is here, but I think it's a distraction. I advise removing it and having "to one of a multi-spectral set of images."

    6. a detail of a painting which is visible only

      "a painting detail that is only visible" (rewording in part to make clear why it takes 'that' over 'which')

    7. We might be tempted to apply

      "It might seem like" (cookbook does not frequently use the editorial "we" outside of the Example text)

    8. We want to tag only a portion of the image thus the motivation of the annotation must be tagging the body of the annotation must be TextualBody containing a text describing what we see in that portion of the X-Ray image, hence the format of the annotation must be text/plain.

      Split into two sentences. I think I would write it this way:

      We want to tag only a portion of the image and thus the motivation of the Annotation must be tagging. The body of the annotation must be a TextualBody — with a format of text/plain — that contains the text of our annotation.

    9. image thus

      "image, thus"

    10. must be TextualBody

      "must be a TextualBody"

    11. X-Ray

      My dictionary has either "X-ray" or "x-ray"

    12. to images part of a composition like in the recipe 0036.

      To go with the comment about editorial "we" and also with my comment about recipe titles over numbers:

      "could be applied to images that are part of a composition, as in the recipe, 'Composition from Multiple Images'."

    13. like 0021-tagging or 0266-full-canvas-annotation add

      Better to use recipe titles, since the numbers at this point are just arbitrary associations with GitHub issue numbers: "like 'Simple Annotation — Tagging' or 'Simplest Annotation'"

    14. Currently no viewers are supporting this feature.

      Move to "Example" section

    15. annotations

      I would read this better if it were the last property in the item

    16. specify


    1. The way this recipe will address is that of pointing to the region of interest in a separate and independent manifest from the resource’s primary IIIF manifest.

      The way this recipe will address that is by leveraging a IIIF image's Image Service to cover a Canvas with just the region of interest.

  6. Jul 2022
    1. | View in Mirador | View in Universal Viewer

      Remove viewers, add note about not working.

    2. xywh=


    3. 2015


    4. 2015


    5. View in Mirador

      Add UV

    6. 2015

      2080 (and in 29)

    7. height": 4999, "width": 3536

      Match to cropped dimensions

    8. least three ways

      Ensure structure is kept t/o recipe, see Glen's writing at https://glenrobson.github.io/iiif_stuff/meme_challenge/

    9. To paint the

      Add text along the lines of "Compare this to . . ." Maybe move into

    1. which

      "that" (this is an American English v British English issue, I believe)

    2. which

      "that" (this is an American English v British English issue, I believe)

    3. service which

      "service, which"

  7. May 2022
    1. Currently the cookbook uses Mirador 3 and UV version 3.

      Redundant with first sentence of this section?

    1. Notes

      Add note that you can have a service-less image, with the direct link to the fragment. You lose tiled zooming.

    2. to see the image region that should be displayed

      "to see an example of a non-painting annotation" or smth like that

    3. Example

      Conform text to new use case with newspaper

    4. Annotation

      Brief explanation of difference between painting annotations and non-painting

    5. When

      Consider whether relevant or distracting. If kept in, elaborate what kind of annotation, why this distinction matters.

    6. Implementation

      Discuss contrast with annotation, difference between targeting a region and pulling in only a region

  8. Apr 2022
    1. structure

      structure, to refer to a manifest property?

    2. subsequently bound together

      bound together some time after publication [printing? creation?] I don't know that it really matters for the use case per se, but it might be easier for people with modest experience with this kind of object to understand.

    3. Sammelband where

      Sammelband, where (adding comma)

    1. Represent Canvases in a Manifest as Geographic Areas in a Web Mapping Client Using navPlace

      Proposed in cookbook authors' call for Maps group discussion: Mapping Canvases in a Manifest

    2. a web mapping platform.

      "platform that provides the ability to [x, y, z]." Where x, y, and z are functionalities core to the distinctiveness of this recipe.

  9. Mar 2022
  10. Jan 2022
  11. Oct 2021
    1. Elixer

      Elixir [and elsewhere]

    2. doesn’t

      doesn't always

    3. which


    4. IIIF-image

      no hyphen

    5. artefacts

      Unless I'm ignorant of something (which happens all the time), this is the British English spelling, and we are generally using US English spellings.

    6. This configuration is not ideal in most cases as it offers the client no size choice and, if the sizes provided are too small to meet the client’s thumbnail requirements, this will have significant impact on processing time if the client is forced to do the resizing since it is more efficient to downsize an image than to request the perfect size.

      Awkwardly long. Maybe:

      This configuration is not ideal in most cases as it offers the client no size choice. Further, if the sizes provided are too small to meet the client’s thumbnail requirements, this will have significant impact on processing time. When a client must resize thumbnails, it is more efficient to downsize an image than to request the perfect size.

    7. height and width

      "height, and width"

  12. Jun 2021
    1. Challenges the library faced include lack of vendor involvement and how to move forward when it is discovered that a provider’s business ventures could harm our library patrons or their families.

      I like the addition of "or their families". We are enmeshed.

    1. { "id": "https://preview.iiif.io/cookbook/0021-tagging/recipe/0021-tagging/annotation/p0001-tag", "type": "Annotation", "motivation": "tagging", "body": { "type": "TextualBody", "value": "Germany" }, "target": "https://preview.iiif.io/cookbook/0021-tagging/recipe/0021-tagging/canvas/p1" }

      Should this be in an annotations property of the Canvas, Manifest, or AnnotationPage?

  13. May 2021
  14. Apr 2021
  15. Mar 2021
    1. Example

      Add note about UV display adjusted for TZ

    2. | View in Mirador


    3. 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.

    6. periodical articles (journal, magazine, etc.)

      change to "resources"

  16. Feb 2021
  17. Jan 2021
    1. that will be displayed to the end user by a client

      "that a client will display to the end user" More active phrasing.

    2. the over all object

      "the entire resource"

    1. “language code/array”

      ' "language code/array of values" pair '? Noting because to me this reads currently as "language code + language array" because of spacing.

    2. included as single-string array

      "included as a single-string array " [only missing article "a"]

    3. variant titles

      Broader reading level perhaps to say "title variants".

  18. Dec 2020
  19. Nov 2020
  20. Aug 2015
    1. When it comes to understanding the intricacies of teaching, Douglas McKee and Edward O’Neill are two peas in a podcast.

      Legume pun FTW.