<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Oct 28, 2010, at 7:41 PM, Matt Jones 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; "><div>Would PATO lose anything by formally defining a Quality as an instance of oboe:Characteristic and with a particular oboe:Value bound to it?</div></span></blockquote></div><div><br></div>It's maybe worth keeping in mind that in the distributed nature of the Semantic Web paradigm anybody could make that assertion, i.e., PATO:quality rdfs:subClassOf oboe:Characteristic (assuming that you did in fact not mean instance, but subclass?). Hence, if using PATO terms within OBOE-compliant data would require that, there's nothing that would stop you from simply including the assertion in your ontology.<div><br></div><div>Conversely, adding that to PATO itself would probably generate a drawn out philosophical discussion as to how compatible that would be with BFO ... (and I don't think OBOE is easily reconcilable with BFO)</div><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>