[prev in list] [next in list] [prev in thread] [next in thread] 

List:       nepomuk
Subject:    Re: [Nepomuk] [RFC] Better Full text search
From:       Christian Mollekopf <chrigi_1 () fastmail ! fm>
Date:       2013-05-04 14:44:40
Message-ID: 1889713.VVuAQLpY0a () localhost ! localdomain
[Download RAW message or body]

On Saturday 04 May 2013 16.38:54 Ivan Čukić wrote:
> > It's actually a property specifically for this purpose:
> > "Plain-text representation of the content of a InformationElement with all
> > markup removed. The main purpose of this property is full-text indexing
> > and
> 
> And title/album/author is the *content* of a song? Not from my POV, but I
> guess it is open to different interpretations.
> 

Yes, it's a somewhat lax interpretation ;-) IMO what the paragraph tries to 
tell us is that this is a property is here to support fulltext searching, and 
that it should never be used to store data which is user visible (or even 
editable). 

> > search. Its exact content is considered application-specific. The user can
> > make no assumptions about what is and what is not contained within.
> 
> Ok, this clause does provide a 'this can be used for hacks' statement.
> 

Indeed.

Cheers,
Christian
_______________________________________________
Nepomuk mailing list
Nepomuk@kde.org
https://mail.kde.org/mailman/listinfo/nepomuk

[prev in list] [next in list] [prev in thread] [next in thread]