Language of Text in Webform

Owned by Lauren Stewart
Dec 14, 2023
3 min read

BNC Webform is currently set up to create “simplified” ONIX: the typical needs for the expected case in North American book metadata. Where Language is concerned, Webform supports a “simple” and single instance of what, in the “full” standard, can be used to describe over 10 separate language related concepts. Further, the “full” standard supports additional values that can “flavour” the language entry for regional values as well as provide information about scripts used in its display.

There are options available to clients interested in supporting Language more widely than what is currently supported in BNC Webform.

What follows is a quick overview:

In BNC Webform, Language of Text describes:

  • The language to book is written in, but;

  • it also defines the expected readership of the book.

Generally, it’s a one-to-one thing. The book is in a language and the readership of the book speaks that language and is looking to read books in that language. That means that retailers and online sellers display books to their customers on the assumption that the language of text defines who should discover the book. For most examples, this will be seen as true: language of readership = language of text.

Where it can go wrong is a case like a book is intended for English speakers but, for example, Spanish is provided as the language of text. Then the book will be “sold to” Spanish speakers, when it exists for English speakers learning Spanish. For such an example, Language of Text should be “eng” for English but the subject becomes language instruction for Spanish, even though the bulk of the book’s text may be written in Spanish.

We have a page that explores this in more depth: https://booknetcanada.atlassian.net/wiki/spaces/UserDocs/pages/24445036

The main case we expect users to need is a “bilingual” or “multilingual” book, or books that are equally intended to be read in two (bi) or more (multi) languages. And assuming that is the case then Language of Text is simply provided as two (or more) language codes. In the “full” standard, Language entries are repeated for each language and where BNC Webform’s lack of support for more than one entry is a problem.

As mentioned above, there are options available to clients interested in supporting multiple languages though product metadata. But we would also like feedback on your needs in language support: we need help to ensure we can support publishers properly, particularly insofar as representing Indigenous language and culture in product metadata is concerned. Moreover, we recognize that Indigenous publishers may be publishing material in languages that, to varying degrees, are endangered and not well document, described, nor understood in the dominant culture, one that that ONIX and its codelists represent. 

  • Oral culture being re-written into text is something that may need special support that needs better definition. Are there coding or concepts to be developed to improve support for Indigenous books?

  • Language codes may not available to properly describe Indigenous languages adequately

    • The ONIX language codelist is based on ISO language codes: we are aware that these settler-created standards are a poor representation of Indigenous languages. We need your help: if any information on the codelist is confirmed as inaccurate, or if there is contradictory information that can be cited as accurate, please let us know by emailing us at standards@booknetcanada.ca.

  • Scripting codes are definitely not available (nor have we had any requests)

  • Looking at the dual aspect of Language of Text, we should also be concerned that we accurately defining the potential readership as well as accurately describing the language. Endangered languages need the support of the widest possible readership and a narrow focused Language of Text may not be ideal.

As a market representative for these lands now called “Canada,” BookNet advocates for changes in product metadata and works with international standards organizations. We advocate to get the right codes in place. 

Get in touch with BookNet’s standards team at standards@booknetcanada.ca to have your voice heard.