Seems like we are near our goal but I will take a short break and I will not available again until next Tuesday so don't expect a response by me until I will back home.<div><br></div><div>If we will do some changes to ontologies I think that is a good opportunity to solve the issues with nmm:MusicAlbum I commented in other mail:</div>
<div><ol><li>Album cover</li><li>Album performer, for collaborative albums or recompilations</li><li>Total tracks per set and per box set</li></ol><div>And other one I forgot it, the problem associated with albums with the same name but different artists. Actually this is a mess because only one resource is created.</div>
</div><div><br></div><div>Bye.<br><div><br></div><div><div><div><div class="gmail_quote">On Wed, Apr 4, 2012 at 8:20 PM, Andrew Lake <span dir="ltr"><<a href="mailto:jamboarder@gmail.com">jamboarder@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Yup, double typing is exactly what I had in mind. It cuts down on a<br>
proliferation of new classes and more simply reflects what actually<br>
happens in the real world - resources on the users computer can be of<br>
multiple types (rdf:type has no maxCardinality that I can recall).<br>
Applications already have to deal with this possibility.<br>
<br>
The query would be simple:<br>
1. If the user wants live performances of any type then use:<br>
?r rdf:type nmm:LivePerformance<br>
2. If the user wants TV show live performances use:<br>
?r rdf:type nmm:LivePerformance<br>
?r rdf:type nmm:TVShow<br>
3. If the user wants Music Video live performances use:<br>
?r rdf:type nmm:LivePerformance<br>
?r rdf:type nmm:MusicVideo<br>
4. If the user wants Music live performances use:<br>
?r rdf:type nmm:LivePerformance<br>
?r rdf:type nmm:MusicPiece<br>
5. if the user wants a concert of any type use:<br>
?r rdf:type nmm:Concert<br>
6. if the user wants a concert movie use:<br>
?r rdf:type nmm:Concert<br>
?r rdf:type nmm:Movie<br>
7. if the user wants a concert TV show use:<br>
?r rdf:type nmm:Concert<br>
?r rdf:type nmm:TVShow<br>
<br>
Even better, if nfo:Media is ever expanded to include new types such<br>
as (Books, AudioBooks, Plays, Spoken Word, etc.) this live performance<br>
ontology wouldn't need to be updated again.<br>
I really think we can get all the benefits we need without introducing<br>
media-specific live performance types.<br>
<br>
Hope this helps,<br>
Andrew<br>
<div class="HOEnZb"><div class="h5"><br>
On Wed, Apr 4, 2012 at 10:49 AM, Sebastian Trüg <<a href="mailto:sebastian@trueg.de">sebastian@trueg.de</a>> wrote:<br>
> looks very nice indeed. Would you thus propose to double-type live<br>
> performance videos with nmm:MusicVideo and nmm:LivePerformance?<br>
><br>
> How about the attached layout instead.<br>
><br>
> We simply derive the live video and audio from the same live base class.<br>
> That way we can easily query all live performances, be it audio or video.<br>
> Also I added an intermediate class nmm:MusicVideo and the badly named<br>
> nmm:MusicVideoVideo which is supposed to be typical music videos as you<br>
> get from performers for mtv and stuff.<br>
> That way we can also easily query for videos that contain music in any form.<br>
><br>
> What do you think?<br>
><br>
> Cheers,<br>
> Sebastian<br>
><br>
> On 04/04/2012 07:26 PM, Andrew Lake wrote:<br>
>> nmm:TVShow is a subclass of nfo:Media so yes, it should be okay to do that. :-)<br>
>><br>
>> peace and much respect,<br>
>> Andrew<br>
>><br>
>> On Wed, Apr 4, 2012 at 10:23 AM, Ignacio Serantes <<a href="mailto:kde@aynoa.net">kde@aynoa.net</a>> wrote:<br>
>>> Assuming that nmm:TVShow could be used instead nfo:Media seems good for me<br>
>>> :).<br>
>>><br>
>>><br>
>>> On Wed, Apr 4, 2012 at 6:36 PM, Andrew Lake <<a href="mailto:jamboarder@gmail.com">jamboarder@gmail.com</a>> wrote:<br>
>>>><br>
>>>> Thanks for taking the time to put this together Sebastian.<br>
>>>><br>
>>>> I wonder if it would be possible to push a simpler class<br>
>>>> nmm:LivePerformance up above the media type (audio/music/video).<br>
>>>> Perhaps just subclassed from nfo:Media, since we could have audio or<br>
>>>> video live performances. Then perhaps we could just add the type to<br>
>>>> any existing audio, music, video, tv show, etc. resource to indicate<br>
>>>> it is a live performance. A concert then is just a special type of<br>
>>>> live performance that can have multiple live performances. It might<br>
>>>> even have unique properties like location, numberOfPerformers,<br>
>>>> tourStops, etc.<br>
>>>><br>
>>>> Based on what you came up with and Ignacio's comments, I've attached a<br>
>>>> png that captures what I'm thinking might work.<br>
>>>><br>
>>>> Hope this helps,<br>
>>>> Andrew<br>
>>>><br>
>>>> On Wed, Apr 4, 2012 at 4:41 AM, Ignacio Serantes <<a href="mailto:kde@aynoa.net">kde@aynoa.net</a>> wrote:<br>
>>>>> In a second view I have some remarks:<br>
>>>>><br>
>>>>> Why nmm:MusicVideo is related to nmm:LiveMusicPerformance? There are<br>
>>>>> totally<br>
>>>>> independent without any relation.<br>
>>>>> nmm:MusicVideo must be related to many nmm:MusicPiece as<br>
>>>>> nmm:LiveMusicPerformance. This is a very uncommon case but there is a<br>
>>>>> few<br>
>>>>> music video clips related to more than on song.<br>
>>>>> I'm assuming a 0:n cardinality because I have several live performances<br>
>>>>> related to a nmm:MusicPiece I don't own.<br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>>> On Wed, Apr 4, 2012 at 10:40 AM, Sebastian Trüg <<a href="mailto:sebastian@trueg.de">sebastian@trueg.de</a>><br>
>>>>> wrote:<br>
>>>>>><br>
>>>>>> Hi guys,<br>
>>>>>><br>
>>>>>> I quickly drew little diagrams trying to summarize again. Please tell<br>
>>>>>> me<br>
>>>>>> what I missed:<br>
>>>>>><br>
>>>>>> 1.png is the example of a concert which is split into live performances<br>
>>>>>> or certain music pieces. Still missing are the DataObject parts. There<br>
>>>>>> could be a filedataobject for all of them or only for the concert. in<br>
>>>>>> the latter case the rest would be embedded data objects or we need<br>
>>>>>> something new like "part of a dataobject".<br>
>>>>>> 2.png is the relationship between the classes.<br>
>>>>>><br>
>>>>>> Cheers,<br>
>>>>>> Sebastian<br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> --<br>
>>> Best wishes,<br>
>>> Ignacio<br>
>>><br>
>>><br>
>><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Best wishes,<div>Ignacio</div><div><br></div><br>
</div></div></div></div>