Written elsewhere as "timed text format". Should be consistent.

"the rendering property" "the linking property rendering"

"is"

Need type per spec?

No "@"

As an implementation note, I think we are wanting to push a little harder for our preferred case, but certainly without excluding or shaming ppl who have their reasons for doing it a different way.

Implementation Note: Using Thumbnails

Aim to drop by Editor time

Use this rather than identify

Add note about UV display adjusted for TZ

remove

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

en-dash (et seq.)

Manifest

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

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

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]".

Serial comma, so "label, or description"

Should be https

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

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

consumption only by

Put bit about defaulting to zeroes here.

change to "resources"

en-dash

en-dash

The seeAlso

MODS

"XML, JSON,"

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

"the entire resource"

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

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

Broader reading level perhaps to say "title variants".

"other than just a Point" Not going to die about this one.

change to "implications for"

for clients to

contain these

are

dele

For which you have

I'm inclined to say "a creator field" rather than assert that the field itself is defined by the English label value.

"descriptive metadata field labels"?

dele

"with the Manifest"?

Need to use the baseURL Jekyll property?

values (or whatever way stays consistent with labels previously.

requiredStatement

"no assigned language"?

"image of the painting commonly known as . . ."

label

Legume pun FTW.