getLangDictionaryValue should take a list about tincanjs HOT 5 OPEN

We could leave it as a string, and have it parse accept-language format. Then, browser based consumers could potentially just read that preference out of the browser and pass it directly.

from tincanjs.

Also, the spec calls for the LRS to respect the accept-language header when pulling statements

from tincanjs.

But didn't we end up saying "what's the point of leaving out any languages?" when statements are fetched?

from tincanjs.

I don't recall that. If sparse = true in the statement query, language filtering isn't optional.

from tincanjs.

I like the accept-language idea as a pass to this method, not sure how hard the parsing is but can look into that. The second discussion probably begs a new issue on the various get calls adding a 'language' property to the configuration object for said calls that would populate the header. (I'll open a separate issue for it.)

from tincanjs.