[Nepomuk] Nepomuk and lyrics stuff

Ignacio Serantes kde at aynoa.net
Wed Mar 20 16:11:24 UTC 2013


There are several places to obtains lyrics in a predictable format with an
API, for example LyricWiki, even with support to multiple languages. One
example with kana, rōmaji and English versions here: 宇多田ヒカル ー
光<http://lyrics.wikia.com/%E5%AE%87%E5%A4%9A%E7%94%B0%E3%83%92%E3%82%AB%E3%83%AB_(Hikaru_Utada):%E5%85%89>
.

There is too a file format to store synchronized lyrics,
http://en.wikipedia.org/wiki/LRC_(file_format) and there are several
servers offering this lyrics format.

The problem here is not obtaining lyrics but how reliable is the subtitle
because basically that databases are created by people like the Wikipedia.

Finally there are a bunch of lyrics fetchers because are easy to implement
and even I wrote two, one deprecated for Amarok 2 written in jscript, and
the one I used in my daily basics written in python.

On Wed, Mar 20, 2013 at 4:52 PM, <phreedom at yandex.ru> wrote:

> On Среда 20 марта 2013 16:06:39 Ignacio Serantes wrote:
> > Extracted from ontology documentation:
> >
> > Plain-text representation of the content of a InformationElement with all
> > markup removed. The main purpose of this property is full-text indexing
> and
> > search. Its exact content is considered application-specific. The user
> can
> > make no assumptions about what is and what is not contained within.
> > *Applications
> > should use more specific properties wherever possible*.
>
> *wherever possible*. The rationale for not adding a specific property like
> nmm:lyrics was that such a property might be underspecified and effectively
> useless. Also, this would mean lots of content types would get their own
> "nicely named plain-text version of the data without any strict
> serialization
> requirements" properties without any useful result either.
>
> To put "The user can make no assumptions about what is and what is not
> contained within" into musical context: typical data ripped off a lyrics
> site
> might contain lyrics only, or lyrics prepended with band, title or who
> knows
> what else, format can be quite "flexible" too, even worse if you use
> several
> lyrics sources.
>
> So, the user who knows what nmm:MusicPiece is, also knows that you can get
> a
> somewhat useful, but not machine-readable text dump in nie:plainTextContent
> which is likely to also contain lyrics, and that's exactly what you get
> from a
> typical lyrics site.
>
> Properly implemented lyrics needs a rather clean feed and who knows maybe
> it
> shouldn't even be implemented as a single text property. Maybe a
> subtitle-like
> approach "time-stamped text" is a better idea?
>
> Or, maybe I missed some important development and there's a very good
> authoritative lyrics DB with a predictable format and we should get
> started on
> defining nmm:lyrics? I don't monitor this actively...
>
> > When documentation informs you that other ontologies should be used I
> have
> > doubts.
> >
> > On Wed, Mar 20, 2013 at 2:54 PM, <phreedom at yandex.ru> wrote:
> > > On Вторник 19 марта 2013 20:22:14 Ignacio Serantes wrote:
> > > > Hi list,
> > > >
> > > > As a first step to add music lyrics to Nepomuk I will add support
> > > > for
> > > > lyrics frames in audio files in taglibextractor and this data will
> > > > be
> > > > stored in
> > > > nie:plainTextContent<
> > >
> > > http://www.semanticdesktop.org/ontologies/nie/#plainTe
> > >
> > > > xtContent> because there is no better place to store this
> > > > information.
> > >
> > > This is the proper place to store lyrics.
>



-- 
Best wishes,
Ignacio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/nepomuk/attachments/20130320/8d507735/attachment-0001.html>


More information about the Nepomuk mailing list