So be it, although, as a user, I feel a bit uncomfortable not having
access to my UMO keyword lists.
Alexey Parshin wrote:
> There is one important outcome of this argument. The keywords
should be
> connected to the UMO' content and not to UMO itself. This way we
may use
> content' version and language as search criteria.
> I've just committed corresponding changes in the schema.
>
> 2006/11/15, Alexey Parshin <alexeyp@gmail.com>:
>>
>> I would like to avoid an extra field. At least, as a database
>> construction. If author really wants to push certain keywords not
>> mentioned
>> anywhere in the text - he can add an annotation with such words.
>> Normally - it should be not necessary. I see no use in keywords not
used
>> in the text unless these keywords are trying to describe a binary
>> object.
>> But then we better provide a text description of such object anyway.
>> Here is
>> the example:
>>
>> <umo title="Great Wall of China>
>> <text> This is the only object build by Humanity that can be seen
>> from the
>> Moon. This is BS, BTW. I tried to look it up in Google maps and had a
>> hard
>> time finding it.
>> ....
>> </text>
>> <attachment type="picture" file="GreatWall.jpg"
>> storage="We_have_to_come_up_with_something">
>> <annotation> The picture of The Great Wall taken in 1999 from the
plane
>> </annotation>
>> <keywords> Big Grey Wall </keywords>
>> </attachment>
>> <text>... </text>
>> ...
>> </umo>
>>
>> While indexing this fragment, we may collect all the keywords from
>> <text>
>> tag contents. We may ignore everything from <attachment> but
>> <annotation>
>> and <keywords> contents.
>> Now, if the author removes a picture from this UMO, the keywords are
>> rebuilt, and we have no reference on that picture in the keywords
>> anymore
>> (in this version of the UMO).
>>
>> 2006/11/15, sergey@total-knowledge.com <sergey@total-knowledge.com>:
>> >
>> >
>> > > 3) If author needs something that associates an object or its
part
>> > with
>> > > keywords, the author should provide a short description of the
>> object
>> > or
>> > > its
>> > > part in the object text.
>> >
>> > We cannot just tell author to provide a short description of the
>> object
>> > somewhere. UI has to have required field for that purpose, for
example
>> > Short Description. But in this case we get back to having
additional
>> > field
>> > again(that purpose was served by Keywords field).
>> > If you intend to use, for example, course Content field for
keywords
>> > generation, you may end up with generation a bunch of unrelated
>> > keywords.
>> >
>> > >
>> > > --
>> > > Alexey Parshin,
>> > > http://www.sptk.net
>> > >
>> >
>> >
>> >
>>
>>
>> --
>> Alexey Parshin,
>> http://www.sptk.net
>>
>
>
>
--
Anatoly Volynets, Co-Founder
total-knowledge.com
culturedialogue.org