- From: Paola Di Maio <paola.dimaio@gmail.com>
- Date: Sun, 3 Mar 2019 11:07:38 +0800
- To: ontolog-forum <ontolog-forum@googlegroups.com>, "schema.org Mailing List" <public-schemaorg@w3.org>, SW-forum <semantic-web@w3.org>, public-aikr@w3.org
- Message-ID: <CAMXe=SoicWuJiipRZYW4sJdC5u_ueaiuV5qgRC=hg59=Z9Tdag@mail.gmail.com>
I wanted to share a concern, as I know posts gets read and issued picked up and addressed in time I searched Google today for Solomon Curse, trying to find some references to some historical cause and conditions in the first house of David - not in relation to a specific race, but more in relation to the history of the modern world to see if anyone is following up the courses and recourses of history https://www.iep.utm.edu/vico/ Well, I was shocked to see that the first page of results were all about a book and its author, and nothing about history came up at all. I had to add additional words to create some context to dig up some historical references. Just wanted to point out that I am very concerned about future generations receiving a distorted version of history by heavily commercially biased search results when typing some search terms and getting only/mostly the results from one entity, rather than a representation of the plurality of meanings and contexts Bias is a known problem in searches, however I was hoping that by now we would have some mechanisms to reduce this bias? Doesn't look like it. I hope that schema.org could help that by creating metaschemas for disambiguation or other mechanism, such a representation of context which should include at least two perspectives: the domain a search term is present, and the time/chronology (to show which came first) Just a sunday morning note before digging in more confusing knowledge from search results PDM <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
Received on Sunday, 3 March 2019 03:08:41 UTC