-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow provision of label for navDate, navPlace #1315
Comments
One for the Newspapers WG to bounce around @kestlund @glenrobson More discussion in #1296 |
It seems that if we opted for adding a |
I think we need to be pretty clear on this one for 3.0, as it wouldn't be backwards compatible. If we're not comfortable doing it now, we should close the issue as |
I'm still a strong 👎 on this. I think there's a strong use case for engaging with those questions, but I think it should not be as part of the core IIIF specification. |
Community call 12/20: defer |
Not needed for navDate, will solve if navPlace is undefered. |
Editors agree at Naples to reopen for 4.0 |
Not that adding it to navDate would be a breaking change for the main prezi spec between 3.0 and 4.0 -- currently this would be the /only/ such change. |
Editors agree - no labels for navDate/navPlace. It's for dropping pins into a timeline or a map for the resource that has the property -- so the label is the label of that resource. |
Spawned #2303 for further uses of nav* properties on annotations |
(Splitting from #1296)
In order to allow appropriate representation of a human readable label for the point on a timeline, calendar or map, it would be advantageous for the content provider to include this label directly, associated with the data that allows the point to be plotted. Date labels should not be modified to the viewers locale in terms of timezone, but should be modified in terms of language (en: January vs fr: Janvier). The internationalization expectation in IIIF is that the resource will provide the translations.
For example, the date label "January 1st 410, 00:00:00" is not really appropriate compared to "410 AD". Or "34 Quai du Louvre, 75001 Paris, France" compared to just "Paris".
The text was updated successfully, but these errors were encountered: