Ross, your hesitation is well-founded. There is a difference between
a translated title and a parallel title (title given in more than
one language on the piece). Also, assigning languages to titles is
tricky (ditto languages to names) -- A book in English with the
title "Marie Antoinette", or the famed "***" (book title is three
asterisks). In some cases there are titles explicitly in different
languages (UN publications are a good example), but titling is
creative and follows no rules.
Which is just echo your caution that we have to look into these
distinctions deeply before making decisions. And that the experience
of those who work on the data creation end is invaluable.
On 4/27/15 1:49 AM, Ross Singer wrote:
[log in to unmask]"
On Sun, Apr 26, 2015 at 7:33 PM Robert Sanderson
<[log in to unmask]
You wouldn't even need hasTranslatedTitle, you could
resourceA dc:title "title"@en, "titre"@fr .
I prefer something along these lines, but I think it
needs to be vetted against how translated titles actually
work before committing to it. That is, does the title have
a 1:1 relationship to language? Or is the relationship
actually something else (e.g. to region, etc.).
I'm not looking for the counterargument to be an argument
for overengineering this problem, I just want to avoid the
surprises that the publishing industry so often gives us.
[log in to unmask] http://kcoyle.net