<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On May 9, 2011, at 4:24 AM, Mikel Egaņa Aranguren wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Just to add to the discussion, puning can be used to model clases as instances. In fact, a common pattern I'm seing and I'm using is to use puning and have a class hierarchy, each class having an instance with the same URI, so one can refer to each class as a class or as an instance, depending on the context.<br></span></blockquote></div><div><br></div>The punning feature in OWL2 is very nice indeed. But one should not forget that depending on the use the subject (or object) is either the class *or* the instance. I.e., there is a "class view" of the resource identified by the URI, and an instance view. This is different from referring to a class as an instance. So things you say about the URI using object properties you say about the instance identified by that URI, just as you would if you used a generated instance URI, and the rules that apply to that are no different from the rules that apply if you said those things about an instance with a randomly generated URI. For example, if you say conflicting things about it, you still say these about one and the same instance, not "some", possibly different, instances.<div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>-hilmar <br><div> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><font class="Apple-style-span" face="Monaco" size="3"><span class="Apple-style-span" style="font-size: 11px; ">-- </span></font></div><div><font class="Apple-style-span" face="Monaco" size="3"><span class="Apple-style-span" style="font-size: 11px; ">===========================================================</span></font></div><div><font class="Apple-style-span" face="Monaco" size="3"><span class="Apple-style-span" style="font-size: 11px; ">: Hilmar Lapp -:- Durham, NC -:- informatics.nescent.org :</span></font></div><div><font class="Apple-style-span" face="Monaco" size="3"><span class="Apple-style-span" style="font-size: 11px; ">===========================================================</span></font></div><div><br class="webkit-block-placeholder"></div></div></span><br class="Apple-interchange-newline"> </div><br></div></body></html>