Re: Capturing the information about the creator of a collection or a feed within the Media Ontology

Good approach. For the API, I think keeping the number of methods small
(e.g. one property = one method) would be good too. To capture the
differences you mention one could create different signatures, e.g.
getAuthor(mediaResourceURI)
getAuthor(mediaResourceURI,COLLECTIONAUTHOR)
with COLLECTIONAUTHOR being a constant for the roles. In that way, the user
of the API has both options: getting just all author information (first
method call) or only a specific one (second call).

Felix

2009/7/7 Veronique Malaise <vmalaise@few.vu.nl>

> Hello,
> The idea of the "core properties" of the Media Ontology is that they should
> be useful in several use cases, and that they are supported by different
> standards and vocabularies. We had a vote to select them, based on the most
> frequent properties present in the mapping table. The creator of a
> collection can indeed be mapped to ma:author, with a property specifying
> that the meaning or scope of "collection author" is narrower than the one of
> ma:author (and potentially *how* narrower it is). The idea is to integrate
> the mapping modularity from a specific vocabulary to the ma list, not to
> extend the core list itself.
>
> Best regards,
> Véronique
>
> On Jul 6, 2009, at 7:02 PM, Matthias Einbrodt wrote:
>
> Hello,
>
> I thought a little about the idea of capturing the information about the
> creator of a collection or a feed within the Media Ontology.
>
> To date there is actually no element within the Media Ontology that could
> capture such information. A collection or feed creator property could be
> mapped to the ma:author property but that would cause overlaps with the
> values for the creator or authors of singe media entities (videos, images
> etc.) and thus it would not be possible to search for a creator of a
> collection specifically.
>
> Therefore I want to discuss the idea of introducing a distinct Media
> Ontology property for the creators of collections / feeds / playlists.
>
> A possible use case where such a property might valuable can be found
> within the Youtube context for example where users can create several feeds
> and playlists and somene might be interested to search for the playlists /
> feeds of a certain user because he is known to create very popular and liked
> playlists.
>
> I’m looking forward hearing your opinions.
>
> Best regards
>
> Matthias Einbrodt
>
>
>