You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Attributes that express the language of external resources should not use the HTML lang and XML xml:lang language attributes, but should use a different attribute when they represent metadata (which indicates the intended use of the resource rather than the language of a specific range of text). more
This may be relevant for the link element. Should we add a hreflang attribute (like in HTML)?
Dave Cramer: PR 1497
… this is designed for the links in the package file
… if we're linking to external metadata, we can determine the language of the file
… consistent with other vocabularies
… this would be new, and wouldn't break anything
… any comments?
Ben Schroeter: Trying to understand the usage of this?
Dave Cramer: Say you have a multi-lingual epub, multiple metadata records
… norwegian canadian dictionary that has one record in norwegian and one in canadian english
… if the UI is set in one language, it can know to present the correct metadata to the user
… the RS doesn't have to determine the vocab from the resource, it can determine before download
… a hint
Ben Schroeter: Ok
Dave Cramer: I'm not aware of a RS that does this
Brady Duga: You can link to external metadata records? /sarcasm
Dave Cramer: We can write a test for it, but no RS will test it
Ben Schroeter: And where will you find a Norwegian-Canadian dictionary...
Brady Duga: This PR does add another untestable conformance requirement
Dave Cramer: I feel we're a little bit stuck here
… it's an i18n best practice
… if we say we're going to have linked metadata, we should have this
… we put this in, we get tests, the concept gets marked as at-risk at CR
… I think we should accept the PR, then see what testing shows us
Proposed resolution: Close 1488, accept PR 1497(Wendy Reid)
Activity
iherman commentedon Feb 9, 2021
The issue was discussed in a meeting on 2021-02-04
List of resolutions:
View the transcript
6. Missing
hreflangattributeSee github issue #1488.
Dave Cramer: 1488
… missing
hreflangattribute… see issue
… there is a PR from Matt
See github pull request #1497.
Dave Cramer: PR 1497
… this is designed for the links in the package file
… if we're linking to external metadata, we can determine the language of the file
… consistent with other vocabularies
… this would be new, and wouldn't break anything
… any comments?
Ben Schroeter: Trying to understand the usage of this?
Dave Cramer: Say you have a multi-lingual epub, multiple metadata records
… norwegian canadian dictionary that has one record in norwegian and one in canadian english
… if the UI is set in one language, it can know to present the correct metadata to the user
… the RS doesn't have to determine the vocab from the resource, it can determine before download
… a hint
Ben Schroeter: Ok
Dave Cramer: I'm not aware of a RS that does this
Brady Duga: You can link to external metadata records? /sarcasm
Dave Cramer: We can write a test for it, but no RS will test it
Ben Schroeter: And where will you find a Norwegian-Canadian dictionary...
Brady Duga: This PR does add another untestable conformance requirement
Dave Cramer: I feel we're a little bit stuck here
… it's an i18n best practice
… if we say we're going to have linked metadata, we should have this
… we put this in, we get tests, the concept gets marked as at-risk at CR
… I think we should accept the PR, then see what testing shows us
Dave Cramer: Progress!
… on i18n issues at least
… thanks everyone
Dave Cramer: see you all in the comment section
murata2makoto commentedon Feb 16, 2021
I do not like the hreflang attribute. Metadata or HTTP headers for the referenced contents should specify the used language.
I know that this is not always possible. But hreflang is not a solution but a hack.