This is exactly what I'm doing in nepoogle.
On Tue, May 21, 2013 at 6:26 PM, Vishesh Handa <[email protected]> wrote: > > > > On Tue, May 21, 2013 at 9:22 PM, Ignacio Serantes <[email protected]> wrote: > >> Hi, >> >> Are you meaning something like these? >> >> http://img7.imageshack.us/img7/1456/nepoogle12.png >> >> Could be solved without adding a new ontology and, as you can see a >> contact could be several things. If you finally add this subtype you must >> consider the next: >> >> 1) nmm:Artist must include performers but also any kind of artists: >> actors, directors, painters, conductors, producers, etc... >> 2) Two known applications must be updated to support this change: >> nepomuk-webminer and bangarang. >> 3) A conversion tool must be written. >> > > uhh. yeah. I guess I should just do a query such as - > > select distinct ?p where { ?r ?p <nepomuk:/res/sdfasdfa> . } > > and then infer the type of contact from there. > > >> >> >> >> On Tue, May 21, 2013 at 5:19 PM, Vishesh Handa <[email protected]> wrote: >> >>> Hey guys >>> >>> I would like to introduce nmm:Artist as a sub-type of nco:Contact which >>> could be used in place of the nco:Contacts that are created when indexing >>> music files. >>> >>> The advantages would be that one could show "Artist" instead of >>> "Contact" when it pops up in the search result. This would not change the >>> domain or range of any other property. >>> >>> Opinions? >>> >>> -- >>> Vishesh Handa >>> >>> _______________________________________________ >>> Nepomuk mailing list >>> [email protected] >>> https://mail.kde.org/mailman/listinfo/nepomuk >>> >>> >> >> >> -- >> Best wishes, >> Ignacio >> >> >> _______________________________________________ >> Nepomuk mailing list >> [email protected] >> https://mail.kde.org/mailman/listinfo/nepomuk >> >> > > > -- > Vishesh Handa > -- Best wishes, Ignacio
_______________________________________________ Nepomuk mailing list [email protected] https://mail.kde.org/mailman/listinfo/nepomuk
