<div>Hi,</div><br><div class="gmail_quote">On Thu, Mar 22, 2012 at 6:59 PM, Sebastian Trüg <span dir="ltr"><<a href="mailto:sebastian@trueg.de" target="_blank">sebastian@trueg.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On 03/22/2012 02:24 PM, Ignacio Serantes wrote:<br>
> Hi,<br>
><br>
> I want to add to Nepomuk information from my library of music videos,<br>
> lives and concerts and I wonder how I could do this.<br>
><br>
> This is the basic information for a music video stored in the file name:<br>
> [MV] Artist(s) - Song(s) (year).ext<br>
><br>
> so next relations are required:<br>
> nmm:performer (1-n)<br>
<br>
</div>that we already have. but I suppose it would go on the actual nmm:MusicPiece<br></blockquote><div><br></div><div>I don't think so because this music video could be a cover, or even a parody, or maybe there is more than one version, and I talking about cases I known and maybe there are others, so music video performer could not be the same of the music piece.</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
> nmm:musicPiece (1-n)<br>
<br>
I imagine this would like a nmm:MusicPiece to the nmm:MusicVideo. Then I<br>
think it should be a subPropertyOf nie:hasLogicalPart.<br></blockquote><div><br></div><div>I don't like so much the subProperty idea because I will need a join to get data. With nmm:musicPiece I can build a query with a relation.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><br>
> and the next properties:<br>
> nie:contentCreated<br>
<br>
</div>that we have<br>
<div><br>
> extra information, like album title, could be retrieved or stored<br>
> following nmm:performer or nmm:musicPiece. I don't know if there is a<br>
> music video with more than a song but there is no problem to have a n<br>
> cardinality.<br>
><br>
> This is the basic information for a music live stored in the file name:<br>
> [LIVE] Artist(s) - Song(s) - Program - Date.ext<br>
><br>
> so next relations are required:<br>
> nmm:performer (1-n)<br>
> nmm:musicPiece (1-n)<br>
<br>
</div>the same as above I suppose.<br>
<br>
> nmm:tvshow (1-1)<br>
<br>
why tvshow?<br></blockquote><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><br>
> extra information, like emission date must be stored in a nmm:TVShow<br>
> resource and a nmm:TVSeries resource must be created to.<br>
<br>
</div>what does live music have to do with tv shows?<br></blockquote><div><br></div><div>Because music lives are performed in one place, basically in tv shows. All of my lives are related to tv shows or are full concerts. </div>
<div><br></div><div>This is an example live performed in South Korean show named Music Core, <a href="http://www.youtube.com/watch?v=4CYiR8yt7-w">http://www.youtube.com/watch?v=4CYiR8yt7-w</a>, and I have over 700 of this in my hard drive from this and other shows.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
What you would do is introduce a new type nmm:LiveMusicVideo or<br>
something like that as a subclass of nfo:Video.<br>
<div><br>
> This is the basic information for a concert stored in the file name:<br>
> [CONCERT] Artist(s) - Song(s) - Place - Date.ext<br>
><br>
> nmm:performer (1-n)<br>
> nmm:musicPiece (1-n)<br>
><br>
> and the next properties:<br>
> nie:contentCreated<br>
><br>
> and in this case I need a property to store the location and maybe more<br>
> things, I have over ten concerts so I have not thought much about this :).<br>
<br>
</div>Should be fairly simple to add. Maybe it would make sense to again<br>
introduce a new sub-type to nmm:MusicPiece to differentiate between<br>
"normal" music files and concerts. The same is probably true for live<br>
recordings (without video).<br></blockquote><div><br></div><div>This is related with covers and parodies and I think that this could be easily solved with the genres like in audio files.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><br>
> There is other information relevant to me stored actually in tags, like<br>
> if performance is a cover or a special version or the country, but lets<br>
> begin with the basic.<br>
<br>
</div>interesting. Might make sense to look at the <a href="http://last.fm" target="_blank">last.fm</a> ontology here.<br></blockquote><div><br></div><div>I don't know this ontology.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><br>
> The fact is seems like I need something like nmm:MusicLive,<br>
> nmm:MusicVideo and nmm:MusicConcert ontologies and I'm not sure if this<br>
> changes are possible.<br></div></blockquote><div><br></div><div>So you suggest nmm:LiveMusicVideo and not nmm:MusicLive. Following this logic proper names will be:</div><div><br></div><div>nmm:LiveMusicVideo, nmm:ConcertMusicVideo and, maybe, nmm:VideoMusicVideo :?. I'm not strong in English names so for me is good if I could store the information I want.</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
<br>
</div>sure they are. We can always add stuff that makes sense. :)<br>
<br>
Cheers,<br>
Sebastian<br>
<br>
_______________________________________________<br>
Nepomuk mailing list<br>
<a href="mailto:Nepomuk@kde.org" target="_blank">Nepomuk@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/nepomuk" target="_blank">https://mail.kde.org/mailman/listinfo/nepomuk</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Best wishes,<div>Ignacio</div><div><br></div><br>