<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Hi, <br>
<br>
some feedback, veeery late, I wasn't aware to the thread until
today.<br>
<br>
Antoni - many things here relate to decisions you did in the past,
could you comment and send your answer to <a class="moz-txt-link-abbreviated" href="mailto:nepomuk@kde.org">nepomuk@kde.org</a> or to
Sebastian?<br>
<br>
It was Sebastian Trüg who said at the right time 04.04.2011 14:14
the following words:
<blockquote cite="mid:4D99B640.8000506@kde.org" type="cite">
<pre wrap="">Hi guys,
before creating tons of tickets for SDO I would like to discuss some of
the issues I see with the ontologies. So here goes. Please comment.
* Would it make sense to create "nco:hasContactMedium
rdfs:subPropertyOf nie:hasLogicalPart" (in that case
nco:ContactMedium would have to be made a nie:InformationElement.).
The alternative is nao:hasSubResource. But how are the two properties
related?
</pre>
</blockquote>
<br>
I tried to clear this up in ticket:<br>
<a class="moz-txt-link-freetext" href="https://sourceforge.net/apps/trac/oscaf/ticket/98">https://sourceforge.net/apps/trac/oscaf/ticket/98</a><br>
<br>
<blockquote cite="mid:4D99B640.8000506@kde.org" type="cite">
<pre wrap="">
* Should nie:hasPart and nie:hasLogicalPart be subproperties of
nao:hasSubResource?
</pre>
</blockquote>
nie:hasPart: according to the proposed new definition (see above),
the nco:containsContact and ncal:component, ncal:attach properties
would not allow nie:hasPart to be a subpropetry of
nao:hasSubResource. subresources should only be used in parts that
can't "live" without their super. for example, address details
inside an nco Contact.<br>
<br>
<br>
<blockquote cite="mid:4D99B640.8000506@kde.org" type="cite">
<pre wrap="">
* Should we not use nfo:Website as range for a property like
nco:websiteUrl
* nie:created should NOT be a sub property of nao:created. The latter
refers to the RDF resource while the former refers to the DataObject
* Should we deprecate ncal:comment in favor of nie:comment?
</pre>
</blockquote>
The property as such has a small reason to be as a subproperty of
nie:comment because it makes it easier to parse/serialize between
RFC2445 and between NCAL. <br>
I would propose to interpret, when reading data, a nie:comment as
ncal:comment if no ncal:comment is given, and when writing data to
write ncal:comment.<br>
(does this sound like a good idea?)<br>
I would propose to subproperty them.<br>
<blockquote cite="mid:4D99B640.8000506@kde.org" type="cite">
<pre wrap="">
* Why is ncal:cutype not expressed via actual rdf types?
</pre>
</blockquote>
because then the range of ncal:cutype would be rdfs:Class and that
would really suck. because you wouldn't know what values would fit.<br>
(and making the class a subclass of rdfs:class is calling for
trouble because suddenly they will only be rdfs:Classes if
"inference=on" and then .... chaos! also having them as instances
makes it easy to i18n them) <br>
The types are defined here, for example:<br>
<a class="moz-txt-link-freetext" href="https://sourceforge.net/apps/trac/oscaf/browser/trunk/ontologies/ncal/ncal.trig#L1311">https://sourceforge.net/apps/trac/oscaf/browser/trunk/ontologies/ncal/ncal.trig#L1311</a><br>
<br>
<br>
<br>
<blockquote cite="mid:4D99B640.8000506@kde.org" type="cite">
<pre wrap="">
* in what relation does ncal:attachmentUrl stand to nie:url? Is it
required at all?
* ncal:timestamp seems redundant when we have nie:contentCreated.
Should we make it a subproperty and deprecate it?
* Maybe we even need fixed cardinality of 1 for the ncal:NCalDateTime
properties
* nco:imStatus has a string range. That is just awful. Especially since
there is also nco:imStatusMessage which can be used to store an
arbitrary message. nco:imStatus should have a resource range with a
dedicated nco:ImStatus type and predefined instances.
* nao:creator like the other nao properties should refer to the creator
of the resource itself (in the database) as compared to the creator
of the content (of a nie:informationElement or nie:DataObject). This
includes files. Thus, properties like nco:creator should NOT be
sub-properties of nao:creator.
* We need a property to state who created the content of a
nie:InformationElement. We have nco:creator but it refers to
DataObjects.
</pre>
</blockquote>
actually, I think thats an error in the rdfs:comment. <br>
The domain is nie:InformationElement, and reading the
sub-properteies ("nexif:artist") it is obvious that it means the
creator of the infomration element, and not the data object. So I
propose to change the comment:<br>
<a class="moz-txt-link-freetext" href="https://sourceforge.net/apps/trac/oscaf/ticket/99">https://sourceforge.net/apps/trac/oscaf/ticket/99</a><br>
<blockquote cite="mid:4D99B640.8000506@kde.org" type="cite">
<pre wrap="">
* nfo:Website: I think it should be a nie:DataObject. The comment
states that it can be interpreted as a HTMLDocument and it does not
make any sense to interpret a IE as IE.
</pre>
</blockquote>
Good one. don't know. Would depend on the examples how its used so
far.<br>
<br>
hth<br>
Leo<br>
<br>
<blockquote cite="mid:4D99B640.8000506@kde.org" type="cite">
<pre wrap="">
That is all. Please comment at least on a few of them.
Cheers,
Sebastian
_______________________________________________
Nepomuk mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Nepomuk@kde.org">Nepomuk@kde.org</a>
<a class="moz-txt-link-freetext" href="https://mail.kde.org/mailman/listinfo/nepomuk">https://mail.kde.org/mailman/listinfo/nepomuk</a>
</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>