Bug
Topics with names in non-language scope are not found
Issue description
A topic which has a name which is scoped by anything but an accepted browser language is not found in the search. E.g. if a topic representing this year's christmas eve, the 24th of December 2008 has a name _2008-12-24_ in the scope _ISO 8601_. This name will not be found in any of the searches, if the user searches for _2008_.
Developer comments
This issue turns out to be difficult. Currently the search looks for names which are unconstrained or scoped by the languages which are given in the browser settings. Now if i do not follow this strategy, the search will give the user many names he does not understand in a store which is run in many languages. This is something i do not want. The underlying problem is that Topincs makes the assumption that only languages and role types can act as scoping topics for names. This is, of course, debatable.
I think this is just part of a bigger problem with scope. It leaves too many things open or lets say it leaves them between humans, which is not necessarily a bad thing. It does make sense to me (as a person) that the name is scoped by ISO 8601, but what does it mean to a processing application?
Can any topic be a scoping topic? Or should only reified statements (with the reifee present) be allowed as scoping topics and thus act as "antecedens" for the scoped statement? Together with some context (a topic map), the implied statements are chosen.
If i put _British English_ in the scope of a name, i do use a topic and by this usage i give it a certain meaning. Is this the same subject as the language that is spoken in the UK?
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.