W3C home > Mailing lists > Public > semantic-web@w3.org > March 2019

Re: Solomon''s curse and search Bias

From: Thomas Passin <tpassin@tompassin.net>
Date: Mon, 4 Mar 2019 09:00:58 -0500
To: Paola Di Maio <paoladimaio10@gmail.com>, Sherman Monroe <sdmonroe@gmail.com>
Cc: "schema.org Mailing List" <public-schemaorg@w3.org>, SW-forum <semantic-web@w3.org>, public-aikr@w3.org, Kingsley Idehen <kidehen@openlinksw.com>, Hugh Williams <hwilliams@openlinksw.com>, vios <vios@dev-team.com>
Message-ID: <384fd135-345a-f16d-659e-784dff3a20d1@tompassin.net>
On 3/4/2019 6:54 AM, Paola Di Maio wrote:
> Sherman and Thomas P
> thanks a lot for sharing your search journey with friendly narrative and
> about this project. Looks really neat!
> I am still thinking about the need to carry ot some structured data 
> search on open web via  general search engines tho.  I hope Google may 
> consider adopting your architecture or at least some of these ideas 
> which in principe work at least within a closed data set,

The kinds of things you are trying to explore can also be approached 
using a framework of library science, and specifically the concepts of 
"navigation" and "collocation".  Collocation means that items that are 
somehow similar can be found "near" each other in some sense of the word 

For a look an an attempt to provide good navigation and collocation for 
a small private data set, you could look at my paper "Browser bookmark 
management with Topic Maps" for the Extreme Markup Languages conferences 
from 2003 -


This work was my effort to get the most out of very limited amount of 
information, namely, titles of web pages. The viewpoint behind the work 
derived from the library science concepts of collocation, navigation, 
and "subject language".  To quote from my paper: "A subject language is 
a vocabulary for describing the subject of a work in such a way that it 
can be recognized and thereby found — that is, to provide navigation 
capability for a collection."

Another point to keep in mind is that a good user interface must be very 
different for a small project as contrasted with one that encompasses a 
large collection of data.  Just for a tiny example, a pick list for ten 
items can be usable whereas one for 10,000 items is not.  A UI for a 
large data set is hard to design even if your system has good 
collocation and navigation properties.

Received on Monday, 4 March 2019 14:01:31 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 08:45:58 UTC