<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=iso-8859-1"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
        {mso-style-name:msonormal;
        margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
span.EmailStyle20
        {mso-style-type:personal;
        font-family:"Calibri",sans-serif;
        color:#365F91;}
span.EmailStyle21
        {mso-style-type:personal-compose;
        font-family:"Calibri",sans-serif;
        color:#365F91;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#365F91'>Yes, but you have to start somewhere!<o:p></o:p></span></p><p class=MsoNormal><span style='color:#365F91'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#365F91'>There is a quote out there (whether accurate or not) that if Henry Ford had asked his customers what they wanted, they would have asked for a faster horse. Who would ever have thought of a self-driving car, or even a flying car… well, many, actually – and they made it happen!<o:p></o:p></span></p><p class=MsoNormal><span style='color:#365F91'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#365F91'>My point is that you have no idea what an exercise of this manner will spin off as a result of the effort – that is why it is called “research”. The goal is a lofty one, but there will be huge wins in scientific language AI along the way. Who knows, it may be necessary for multi-year journeys for lay-person trips to Mars, if something goes wrong with the spaceship along the way (communication delays will be prohibitive to effect any value from Earth; AI will be required for local support).<o:p></o:p></span></p><p class=MsoNormal><span style='color:#365F91'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#365F91'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#365F91'>Cheers,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#365F91'><br>Don<o:p></o:p></span></p><p class=MsoNormal><span style='color:#365F91'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:#365F91'>-----------------------------<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;color:#7F7F7F'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;color:#7F7F7F'>Donald Samulack, PhD<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;color:#7F7F7F'>President, U.S. Operations<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;color:#7F7F7F'>Cactus Communications, Inc.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;color:#7F7F7F'>Editage, a division of Cactus Communications</span><span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;color:#7F7F7F'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#365F91'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> goal-bounces@eprints.org [mailto:goal-bounces@eprints.org] <b>On Behalf Of </b>Heather Morrison<br><b>Sent:</b> Thursday, July 12, 2018 1:49 PM<br><b>To:</b> Global Open Access List (Successor of AmSci) <goal@eprints.org><br><b>Subject:</b> [GOAL] Why translating all scholarly knowledge for non-specialists using AI is complicated<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div id=divtagdefaultwrapper><div><p class=MsoNormal><span style='font-size:12.0pt;color:black'>On July 10 Jason Priem wrote about the AI-powered systems "that help explain and contextualize articles, providing concept maps, automated plain-language translations"... that are part of his project's plan to develop a scholarly search engine aimed at a nonspecialist audience. The full post is available here:<o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:12.0pt;color:black'><a href="http://mailman.ecs.soton.ac.uk/pipermail/goal/2018-July/004890.html">http://mailman.ecs.soton.ac.uk/pipermail/goal/2018-July/004890.html</a> <o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:12.0pt;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;color:black'>We share the goal of making all of the world's knowledge available to everyone without restriction, and I agree that reducing the conceptual barrier for the reader is a laudable goal. However, I think it is important to avoid underestimating the size of this challenge and potential for serious problems to arise. Two factors to consider: the current state of AI, and the conceptual challenges of assessing the validity of automated plain-language translations of scholarly works.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;color:black'>Current state of AI - a few recent examples of the current status of AI:<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;color:black'>Vincent, J. (2016). Twitter taught Microsoft's AI chatbot to be a racist asshole in less than a day. The verge. <o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:12.0pt;color:black'><a href="https://www.theverge.com/2016/3/24/11297050/tay-microsoft-chatbot-racist">https://www.theverge.com/2016/3/24/11297050/tay-microsoft-chatbot-racist</a> <o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:12.0pt;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;color:black'>Wong, J. (2018). Amazon working to fix Alexa after users report bursts of 'creepy' laughter. The Guardian <a href="https://www.theguardian.com/technology/2018/mar/07/amazon-alexa-random-creepy-laughter-company-fixing">https://www.theguardian.com/technology/2018/mar/07/amazon-alexa-random-creepy-laughter-company-fixing</a><br><br>Meyer, M. (2018). Google should have thought about Duplex's ethical issues before showing it off. Fortune <a href="http://fortune.com/2018/05/11/google-duplex-virtual-assistant-ethical-issues-ai-machine-learning/">http://fortune.com/2018/05/11/google-duplex-virtual-assistant-ethical-issues-ai-machine-learning/</a><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;color:black'>Quote from Meyer: <o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:12.0pt;color:black'>As prominent sociologist Zeynep Tufekci <a href="https://twitter.com/zeynep/status/994233568359575552" target="_blank">put it</a>: “Google Assistant making calls pretending to be human not only without disclosing that it’s a bot, but adding ‘ummm’ and ‘aaah’ to deceive the human on the other end with the room cheering it… horrifying. Silicon Valley is ethically lost, rudderless and has not learned a thing.”<o:p></o:p></span></p></div><div><p><span style='font-size:12.0pt;color:black'><o:p> </o:p></span></p><p><span style='font-size:12.0pt;color:black'>These early instances of AI applications involve the automation of relatively simple, repetitive tasks. According to Amazon, "Echo and other Alexa devices let you instantly connect to Alexa to play music, control your smart home, get information, news, weather, and more using just your voice". This is voice to text translation software that lets users speak to their computers instead of using keystrokes. Google's Duplex demonstration is a robot dialing a restaurant to make a dinner reservation. <o:p></o:p></span></p><p><span style='font-size:12.0pt;color:black'><o:p> </o:p></span></p><p><span style='font-size:12.0pt;color:black'>Translating scholarly knowledge into simple plain text so that everyone can understand it is a lot more complicated, with the degree of complexity depending on the area of research. Some research in education or public policy might be relatively easy to translate. In other areas, articles are written for an expert audience that is assumed to have spent decades acquiring a basic knowledge in a discipline. It is not clear to me that it is even possible to explain advanced concepts to a non-specialist audience without first developing a conceptual progression. <o:p></o:p></span></p><p><span style='font-size:12.0pt;color:black'><o:p> </o:p></span></p><p><span style='font-size:12.0pt;color:black'>Assessing the accuracy and appropriateness of a plain-text translation of a scholarly work intended for a non-specialist audience requires expert understanding of the work and thoughtful understanding of the potential for misunderstandings that could arise. For example, I have never studied physics. I looked at an automated plain-language translation of a physics text I would have no means of assessing whether the translation was accurate or not. I do understand enough medical terminology, scientific and medical research methods to read medical articles and would have some idea if a plain-text translation was accurate. However, I have never worked as a health care practitioner or health care translation researcher, so would not be qualified to assess the work from the perspective of whether the translation could be mis-read by patients (or some patients).<o:p></o:p></span></p><p><span style='font-size:12.0pt;color:black'><o:p> </o:p></span></p><p><span style='font-size:12.0pt;color:black'>In summary, Jason and I share the goal of making all of our scholarly knowledge accessible to everyone, specialists and non-specialists alike. However, in the process of developing tools to accomplish this it is important to understand the size and nature of the challenge and the potential for serious unforeseen consequences. AI is in very early stages. Machines are beginning to learn on their own, but what they are learning is not necessarily what we expected or wanted them to learn, and the impact on humans has been described using words like 'creepy', 'horrifying', and 'unethical'. The task of translating complex scholarly knowledge for a non-specialist knowledge and assessing the validity and appropriateness of the translations is a huge challenge. If this is not understood and plans made to conduct rigorous research on the validity of such translations, the result could be widespread dissemination of incorrect translations. <o:p></o:p></span></p><p><span style='font-size:12.0pt;color:black'><o:p> </o:p></span></p><p><span style='font-size:12.0pt;color:black'>best,<o:p></o:p></span></p><p><span style='font-size:12.0pt;color:black'><o:p> </o:p></span></p><div id=Signature><div id=divtagdefaultwrapper><p><span style='font-size:12.0pt;color:black'>Heather Morrison<o:p></o:p></span></p><p><span style='font-size:12.0pt;color:black'>Associate Professor, School of Information Studies, University of Ottawa<o:p></o:p></span></p><p><span style='font-size:12.0pt;color:black'>Professeur Agrégé, École des Sciences de l'Information, Université d'Ottawa<o:p></o:p></span></p><p><span style='font-size:12.0pt;color:black'><a href="mailto:Heather.Morrison@uottawa.ca">Heather.Morrison@uottawa.ca</a><o:p></o:p></span></p><p><span style='font-size:12.0pt;color:black'><a href="https://uniweb.uottawa.ca/?lang=en#/members/706">https://uniweb.uottawa.ca/?lang=en#/members/706</a><o:p></o:p></span></p></div></div></div></div></div></div></body></html>