Showing posts with label reference. Show all posts
Showing posts with label reference. Show all posts

2015-12-01

Backtracking signs


This image has been for some years now my avatar on various places on the Web. I've chosen it obviously because it's a nice image taken in my dear mountains, but also as an illustration of what Quine called the inscrutability of reference.
This image is a sign, elle nous fait signe. To each of you, depending on your experience and culture, it will evoke something different and particular  - or nothing at all. But does it only evoke, or does it represent something? Could a machine figure what it is? I would be curious to submit this image to some automatic description algorithm. Would we get something like tracks in the snow in a winter mountain landscape? That would not be bad. If it succeeds in adding several people wearing snowshoes, I would be most impressed. And I would be really baffled if it could guess how many people have passed, and in which direction.

Now let's take it as a support for an exercise in backtracking. Let's move a few steps towards the genesis of this image, trying to figure out its deeper meaning. Someone shot this image on a fair winter day (supposing it's a genuine photograph and not one of those fancy computer-generated graphics). In either case what you are viewing here and now is just a reconstruction on the screen of your device of a pack of bits, a file uploaded to Google servers from my computer, this local file being itself a resized and trimmed copy of an original one generated by a numeric camera. Several copies, deconstructions and reconstructions happened since the original shot.
Now just trust me it's a "genuine" photograph of some "real" landscape, and imagine yourself back at the scene, along with the photographer. Given the point of view, he's certainly on the tracks himself. Does he follow the tracks let by another group of walkers? Does he belong to this group? Is he looking back at its own tracks? Has he followed the same track way up and down, and the several people who seem to have passed here were actually the same person, once walking up and once down, or maybe several times up and down? Whatever. Who could answer those questions now, except the one who shot the image? Days, months, seasons and years have passed since. Later on the same day other walkers have come following the tracks or crossing them and messing the signs. A few days after a new snow fall has erased them all, and in April the winter memories have vanished in the streams joyfully cascading down. And another summer, and another winter. Going back there now won't tell you anything about those tracks, even if the landscape looks quite the same, even if some walker has taken today the same path, letting similar tracks.

But figuring the genesis of the image itself is not the end of the backtracking. I've chosen this image to represent me on the Web, among thousands of possible images. How can you interpret this choice? Is it a track of mine, captured by someone else, a track of someone else taken by me, my own track taken by myself, a far-fetched form of selfie? Maybe nothing of the sort. Maybe I found this image somewhere on the Web and thought it looked like me, someone who walks, and is often no more where you expected to meet him.

I could answer all those questions, but I won't. I'd rather imagine you wondering as you would wonder, hopefully, finding some perfect pebble stone on the seashore, about the long story it silently tells, the slow cooking of rock in the depth of Earth and its upraising over millions of years, the sudden earthquake or storm or the patient bite of ice cracking the rock, the fall off the cliff, the long rolling travel downstream to the sea, the patient work of currents, tides and waves until this unique morning where its glow on the sand have captured your eyes.

Think about it, just every thing is somehow akin to this image of a track or that pebble stone. Telling stories, giving time its depth by linking us to the past as so many threads. Trees and rocks, bowls, clothes, jewels, printed words and texts. And every so-called Web resource. They are not just sitting idly here and now, but are signs worth backtracking.

2013-12-10

Content negotiation, and beyond

I had in the past, and for many years, looked at content negotiation with no particular attention, as just one among those hundreds of technical goodies developed to make the Web more user-friendly, along with javascript, ajax, cookies etc. When the httpRange-14 solution proposed by the TAG in 2006 was based on content negotiation, I was among those quite unhappy to see this deep and quasi-metaphysical issue solved by such a technical twist, but three months later I eventually came to some better view of it. Not only content negotiation was indeed the way to go, but this decision can be seen now as a small piece in a much bigger picture.
Content negociation has become so pervasive we don't even notice it any more. Even if a URI is supposed to have a permanent referent, what I GET when I submit that URI through a protocol is dependent on a growing number of parameters of the client-server conversation : traditional parameters pushed by the client are language preference, required mime type (the latter being used for the httpRange-14 solution), localisation, various cookies, and user login. Look at how http://google.com/+BernardVatant works. This URI is a reference for me on the Web (at least it's the one I give those days to people wanting a reference), but the representation it yields will depend on the user asking it : anonymous request, someone being logged on G+ but not in my circles, someone in my circles (and depending on which), someone having me in her circles etc, and of course of the interface (mobile, computer). This will look also differently if I call this URI indirectly from another page, like in a snippet etc.  
This kind of behavior will be tomorrow the rule. Every call to any entity through its URI will result in a chain of operations leading to a different conversation. And not only for profiles in social networks, not only for people, alive or dead, but for every entity on the web : places, products, events, concepts ... 
Imagine the following scenario applied to a VIAF URI for example. VIAF stores various representations of the same authority, names in various languages, preferred and alternative labels for the matching authority in a given library. I can easily imagine a customized acces to VIAF, where I could set my preferences such as my favourite library or vendor, with default values based on my geolocation (as already today in WorldCat) and/or user experience, parameters for selection of works (such as a period in time, only new stuff, only novels ...). The search on a name in VIAF would lead to a disambiguation interface if needed, and once the entity selected, to a customized representation of the resource identified under the hood.
This kind of customized content negotiation will not necessarily be provided by the original owner of the URI. In fact there certainly are a lot of sustainable business models around such services which would run on top of existing linked data. A temporal service would extract for any entity a time line of events involving this entity, e.g., events in the life of a person or enterprise, or various translations and adaptations of a book, life cycle of a product ... A geographical service would show the locations attached to an entity, like distribution of offices of a company or its organisational structure. And certainly the most popular way to interact with the entity will be to engage in the conversation with it, as we engage in conversation with people. In both pull and push mode. I would not say like Dominiek ter Heide that the Semantic Web has failed. But I agree it could. Things on the Web of Data have to go dynamic, join the global conversation, or die of obsolescence. 

2013-08-09

Thou shalt not take names in vain

This is certainly too serious a subject for a Friday night in the middle of August, but that's a good time for old ideas to be written down. And indeed this has been on my mind for so long, at least since I realized that common nouns such as english timeword, windows, apple, caterpillar, shell, bull, french orange, printemps, champion, géant, carrefour, german kinder, and many more, had been "borrowed" from the language commons to become brands. This is in principle forbidden by various trademark legislations, but there are subtle workarounds. I have always considered such practices as unacceptable enclosures in the knowledge commons. They might look anecdotic, leading to rather silly cases, but some borderline practices from major Web actors show that this affair is more important that it could seem at first sight.
One could argue that the market gives back words to the commons, lists of generic or genericized trademarks are easy to find, in a variety of languages. But curiously enough,  the other way round, systematic lists of common nouns used as trademarks I could not find either in Wikipedia or anywhere else. Note sure if they could get any longer than the former, in any case the lists I proposed to start on Wikipedia were proposed for deletion a few minutes after creation by zealous wardens of the Wikipedia Holy Rules, for lack of notability of the subject. Forget about it, I'm now trying to figure how to query DBpedia to get such a list, but the distinction between a proper name and a common noun is no more explicit in DBpedia descriptions and ontology than it is in Wikipedia.
Anyway, this is not necessarily the most important aspect of the way information technologies can impact, misuse and abuse our language commons at large. There is quite a lot of rules or guidelines one could imagine for that matter, some already explicited by laws even if tricky to enforce, some yet to be specified, not to mention being enforced. There is something deeply anchored in our culture about the fair use of names, coming certainly from the way they are rooted in our religions, hence I have only a slight compunction to take inspiration below from one of the most holy and ancient set of rules. Apologies to believers who might read the following as blasphemy uttered by an old agnostic, and disclaimer to everyone else : those were not cast in stone by any god on any mountain. But if the first and main item in this list seems clearly inspired by the Third Commandment, well, yes it is, and not only in form. The underlying claim is that every word, every name, carries along with it enough history and legacy to be honoured. Those who don't care that much about such religious considerations can read this as pragmatic deontological guidelines for a fair, efficient and sustainable use of names in our information systems at large, and on the Web in particular.

Here goes, ten items of course to stick to the original format. 
  1. Thou shalt not take names in vain
  2. Honour the many meanings of a name, for they belong to the Commons
  3. Acknowledge linguistic and semantic diversity, polysemy and synonymy
  4. Do not steal names from the Commons to be your proper names
  5. Do not sell and buy names, for they belong to the Commons
  6. Do not hide yourself or your products under false names
  7. Do not use names against their common meaning 
  8. Do not enforce your own meanings upon others
  9. Expose your meanings to the Commons, for they will be welcome
  10. Share your own names with the Commons, for they will thrive forever
I won't dwelve today in the details of each of those, some might look quite cryptic and need to be expanded in further posts. Just a remark on the first (and most important) one. The "take in vain" used by the King James version of the Bible has been replaced in more recent translations by "misuse". I prefer the former, which conveys the notion that whenever you use the name, it's not for nothing or something without importance and consequence. When you use a name, you should have well thought about its meaning. In French you would translate at best "Tu ne prendras pas les noms à la légère."

2008-05-18

Managing Co-reference (Was: A Semantic Elephant?)

One more public thread on SW list on our favourite issue. But some interesting points to note in the current discussion, well summed up by Aldo Gangemi at mid-course.
  • We definitely need some property or mechanism, weaker than owl:sameAs, to assert that two URIs have similar referents.
  • The semiotic aspects of co-reference are more and more acknowledged, even by formal logic gurus.
Hopefully this thread will eventually have some follow-up on some standardization track.

2005-11-21

Identity, Reference and the Web

A challenging workshop to be held in Edinburgh in May 2006. I've been invited today by the co-chair Harry Halpin to participate in the Program Committee. From the "Goal and Theme" section of the description.
URIs are the primary mechanism for reference and identity on the Web. To be useful, a URI must provide access to information which is sufficient to enable someone or something to uniquely identify a particular thing and the thing identified might vary between contexts. There is no doubt that as mechanisms for identifying web pages the URI has been wildly successful. Currently, URIs can also be used to identify namespaces, ontologies, and almost anything. However, important questions are the interpretation and use and meaning of URIs have been left unquestioned ...
Exactly indeed, what we are about here ... Interesting to see also Pat Hayes in the co-chairs list. I remember that quite a while ago in a private communication, Pat had stressed the fact that identity issues had been "sadly overlooked" so far by current Semantic Web technologies.

2004-11-19

Web Proper Names

SWAD Forum is definitely the place to monitor those days. After introduction of Subject Indicator in SKOS-Core, Alistair Miles launched a very lively thread "Working around identity crisis" which has attracted Harry Halpin of University of Edinburgh to introduce yesterday in the debate an amazing paper called "Web Proper Names: Naming Referents on the Web".
The paper proposes a process, leveraging the statistical results yielded by search engines, to define and name bottom-up equivalence classes of URIs, which all together 'probably' are about the same thing. The concept is somehow similar to the notion of Subject Identity Measure, since the probability of sameness can be quantified.

2004-08-17

Reference by Description

Quite close to the previous post :

"How we refer to something is very important in exchanging information about that thing. If the two parties cannot agree on how to refer to a thing, they cannot exchange information about it."

http://tap.stanford.edu/tap/rbd.html

[2015-02-09] Yet another dead link ...