<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
Hello Sebastian, Bernhard, Nepomuk,<br>
<br>
The questions I saw are:<br>
* is a "Conference" so much different from an ncal:Event that it
needs its own class? <br>
Yes, I suppose so. But unless someone comes up with data that is
additional to an event and someone also has an application at hand
that actually uses this data, there is no need to extend it. (I
suppose that the answer is yes, so if someone needs it, I support
the idea of adding it!)<br>
<br>
* is a "Conference" a subclass of ncal:Event or pimo:Event?<br>
Bernhard, from the experience of our implementation at Refinder, how
would you model it?<br>
how would it be good for Refinder to model it (in case we need it,
which is possible)?<br>
<br>
<br>
kind regards<br>
Leo<br>
<br>
It was Sebastian Trüg who said at the right time 24.09.2011 09:37
the following words:
<blockquote cite="mid:4E7D88BF.9090104@kde.org" type="cite">
<pre wrap="">On 09/24/2011 12:31 AM, Andreas Cord-Landwehr wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi, first of all I want to say: I think this idea is great! (actually, I
already had KMail opened to propose such an ontology by myself when I
noticed this thread...) Well, my dream is that one day I can open
KRunner, write some words about a research topic and "magically" find my
corresponding authors, papers, conferences, and own notes...
For now I want to add some ideas that came to my mind when studying the
entity graph of the proposal (I need to say: I am quite experienced with
BibTeX, but not with the Nepomuk ontologies):
* Locally stored Files: I could not find a specific entry for locally
saved files. Me and most of my colleges store quite large archives of
PDFs on their computers and try to keep them in sync with the
corresponding bibliography descriptions. As there is also a large number
of quite expensive journals that you do not want to by twice, there is
sometimes even an advantage of a local copy compared to use a weblink.
So: what about adding support for locally saved papers.
</pre>
</blockquote>
<pre wrap="">
Its already there. bib:publishedAs can refer to a local file.
</pre>
<blockquote type="cite">
<pre wrap="">* Conferences: One of my key search terms in my personal paper database
are specific conferences. So it would be nice to have an additional
entity discribing a conference with its date/month, organization, and
place. AFAIK those values are also described by the BibTeX
meta-reference "conference".
</pre>
</blockquote>
<pre wrap="">
Well, we have ncal:Event which seems to make sense for conferences, too,
seeing they are essentially events. The question is: do we need a
subclass to ncal:Event which adds properties specific to a conference?
In other words: does a conference have properties which do not apply to
other events like a meeting or a concert or whatever?
And to make things confusing: should we make the distinction between
event types on the pimo level or on the NCAL level (CC'ing *Leo* for this).
Cheers,
Sebastian
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Leo Sauermann, Dr.
CEO and Founder
mail: <a class="moz-txt-link-abbreviated" href="mailto:leo.sauermann@gnowsis.com">leo.sauermann@gnowsis.com</a>
mobile: +43 6991 gnowsis
Where your things come together,
Join: <a class="moz-txt-link-freetext" href="http://www.gnowsis.com/about/content/newsletter">http://www.gnowsis.com/about/content/newsletter</a>
Follow: <a class="moz-txt-link-freetext" href="http://twitter.com/Refinder">http://twitter.com/Refinder</a>
Like: <a class="moz-txt-link-freetext" href="http://www.facebook.com/Refinder">http://www.facebook.com/Refinder</a>
Learn: <a class="moz-txt-link-freetext" href="http://www.gnowsis.com/about/blog">http://www.gnowsis.com/about/blog</a>
Try: <a class="moz-txt-link-freetext" href="http://www.getrefinder.com/accounts/register/">http://www.getrefinder.com/accounts/register/</a>
____________________________________________________
</pre>
</body>
</html>