search

IIIF / api

Source for API and model specifications documents (api and model)
http://iiif.io/api
106 stars 54 forks source link

A IIIF or An IIIF? #772

Closed azaroth42 closed 8 years ago

azaroth42 commented 8 years ago

We should be consistent. Currently we have 15 "a IIIF" and 11 "an IIIF" in the site.

tomcrane commented 8 years ago

Newcomers will read "eye eye eye eff". Old-timers will read "triple-eye eff". Although it will grate more for the old-timers, I vote for "an IIIF" as less of a trip hazard for a newcomer.

tpendragon commented 8 years ago

Best issue ever.

zimeon commented 8 years ago

I think I would also go with "an IIIF" as better for newcomers. (It is gonna catch us out though...)

jpstroop commented 8 years ago

@tpendragon you must have missed the camel vs. snake issue. #179

azaroth42 commented 8 years ago

Could we solve the newcomer issue by adding a terminology section, or at least adding a parenthetical (pronounced "Triple-Eye-Eff") at the top of the spec?

tomcrane commented 8 years ago

We could have it as "a IIIF" in 2.1 but with a large and prominent warning that it will be deprecated in favour of "an IIIF" in a future version.

tpendragon commented 8 years ago

:+1: to a "pronounced" clause. We don't need another code4lib.

tomcrane commented 8 years ago

Until last week I had never read code4lib as anything other than lib rhymes with bib (and that's bib as in bibliographic, not bib as in imbibe...) :beers:

jpstroop commented 8 years ago

Yeah, I've never understood code4libe

zimeon commented 8 years ago

I think we are heading toward https://www.youtube.com/watch?v=Y6lJGD3Q9Qs ... if it were code4libe it would have ***ing e in it ;-)