<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">There are a few pages about this.<div><br></div><div>I am finding that the version available at <a href="http://xmlns.com/foaf/spec/index.rdf">http://xmlns.com/foaf/spec/index.rdf</a> reads into Protege ok, and the HermiT reasoner does not complain about it - that being my usual test. The Owl consistency checker at <a href="http://www.mindswap.org/2003/pellet/demo.shtml">http://www.mindswap.org/2003/pellet/demo.shtml</a> highlights a couple of DL issues.</div><div><br></div><div>* Some of the social properties (icq, msn chat, etc) are functional inverse datatype properties (if two persons have the same ICQ number, then they are the same person). The problem is that there is no general way to check data literals for equality (the OLW spec, for instance, supports fractions, floats and doubles). But these properties can be blithely ignored in most cases by simple dint of not using them.</div><div><div>* name is declared to be a subtype of rdfs:label, but rdfs:label is an annotation property</div><div>* the vocabulary does not import its dependencies, and so some declarations are implied</div><div><br></div><div>Annotation properties are a bit of a bugbear. As far as I can tell, if something is an annotation property then it should only be used to describe vocabulary terms. The actual subject matter of an ontology should be described with regular properties. Thus, declaring name to be a subproperty of label is simply wrong: a thing's name is ontology, not vocabulary. The machine-level issue is that RDF can't tell the difference between the two, so OWL/RDF cannot behave according to the OWL specification in certain respects. But dcterms title and description fit the bill admirably, anyway.</div><div><br></div><div>You can use the FOAF properties and classes without explicitly importing FOAF - you can just declare them. The OWL-DL incompatibilities are not serious. On the other hand ... you may dislike the fact that there are rules in FOAF at all. Maybe two different people happen to share an organisational ICQ address. FOAF at the moment would force you to create a Organisation or Group object for the team, and assign the ICQ address to that.</div><div><br></div><div>And so yes, there are issues. The simple way to deal with it is to create TDWG terms mimicking the FOAF terms, declare them to be sameAs, and if that becomes unworkable then to break the equivalence.</div><div><br><div><div>On 03/11/2010, at 3:55 PM, Bob Morris wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">If machine reasoning is a goal, I would be wary of FOAF. An OWL2-DL, or other OWL2 tractable reasoning profile, version remains a moving target, to the best of my knowledge. The reasons that <a href="http://xmlns.com/foaf/spec/" target="_blank">http://xmlns.com/foaf/spec/</a> is not subject to tractable reasoning are relatively manageable, but I can no longer find the Zimmerman proposal for a FOAF DL version referenced in the thread ending at <a href="http://lists.w3.org/Archives/Public/public-lod/2010Jul/0378.html">http://lists.w3.org/Archives/Public/public-lod/2010Jul/0378.html</a><br>
<br>Can someone point me at a DL version of FOAF and indication that it is actively under discussion somewhere?<br><br>Thanks<br><br><br><div class="gmail_quote">On Tue, Nov 2, 2010 at 10:38 PM, Richard Pyle <span dir="ltr"><<a href="mailto:deepreef@bishopmuseum.org">deepreef@bishopmuseum.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin-top: 0pt; margin-right: 0pt; margin-bottom: 0pt; margin-left: 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex; position: static; z-index: auto; "><br>
I was thoroughly delighted to learn recently that FOAF uses terms in almost<br>
exactly the same way that I had structured my "Agents" data (right down to<br>
the same exat terms, in most cases). I plan to move forward with the FOAF<br>
terms that are relevant (thanks to John W. for pointing this out to me at<br>
TDWG).<br>
<br>
Rich<br>
<div><div></div><div class="h5"><br>
> -----Original Message-----<br>
> From: <a href="mailto:tdwg-content-bounces@lists.tdwg.org">tdwg-content-bounces@lists.tdwg.org</a><br>
> [mailto:<a href="mailto:tdwg-content-bounces@lists.tdwg.org">tdwg-content-bounces@lists.tdwg.org</a>] On Behalf Of Paul Murray<br>
> Sent: Tuesday, November 02, 2010 4:18 PM<br>
> To: Steve Baskauf<br>
> Cc: <a href="mailto:tdwg-content@lists.tdwg.org">tdwg-content@lists.tdwg.org</a><br>
> Subject: Re: [tdwg-content] Comments on Cam's RDF practical<br>
> details of recording a determination What is an Occurrence?<br>
> [SEC=UNCLASSIFIED]<br>
><br>
><br>
> On 29/10/2010, at 12:41 AM, Steve Baskauf wrote:<br>
><br>
> > I think both dwc:recordedBy for the Occurrence and<br>
> dcterms:created for some tokens should be provided.<br>
> Depending on the situation, they might be different entities<br>
> (I think John Wieczorek pointed this out in an earlier<br>
> thread). dwc:recordedBy is specifically supposed to be a<br>
> person whereas I think dcterms:creator could be a person or<br>
> an institution.<br>
><br>
> Perhaps it might be worthwhile leveraging the FOAF vocabulary<br>
> (Friend of a Friend). It's mainly meant for social<br>
> networking, but nevertheless it does contain terms such as<br>
> Person, Organisation, Group and Project. (Project is<br>
> interesting - collection activities perhaps are FOAF Projects).<br>
><br>
> The spec is here: <a href="http://xmlns.com/foaf/spec/" target="_blank">http://xmlns.com/foaf/spec/</a><br>
><br>
> We can envisage the day where, by following links on<br>
> taxonomic web pages, you could eventually find an Author's<br>
> current twitter address, or ask the semantic web "find me all<br>
> specimens of genus Tandanus collected by teams affiliated<br>
> with the university of NSW between 2005 and 2007".<br>
><br>
><br>
><br>
><br>
> ------<br>
> If you have received this transmission in error please notify<br>
> us immediately by return e-mail and delete all copies. If<br>
> this e-mail or any attachments have been sent to you in<br>
> error, that error does not constitute waiver of any<br>
> confidentiality, privilege or copyright in respect of<br>
> information in the e-mail or attachments.<br>
><br>
><br>
><br>
> Please consider the environment before printing this email.<br>
><br>
> ------<br>
><br>
> _______________________________________________<br>
> tdwg-content mailing list<br>
> <a href="mailto:tdwg-content@lists.tdwg.org">tdwg-content@lists.tdwg.org</a><br>
> <a href="http://lists.tdwg.org/mailman/listinfo/tdwg-content" target="_blank">http://lists.tdwg.org/mailman/listinfo/tdwg-content</a><br>
><br>
<br>
<br>
_______________________________________________<br>
tdwg-content mailing list<br>
<a href="mailto:tdwg-content@lists.tdwg.org">tdwg-content@lists.tdwg.org</a><br>
<a href="http://lists.tdwg.org/mailman/listinfo/tdwg-content" target="_blank">http://lists.tdwg.org/mailman/listinfo/tdwg-content</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Robert A. Morris<br>Emeritus Professor of Computer Science<br>UMASS-Boston<br>100 Morrissey Blvd<br>Boston, MA 02125-3390<br>Associate, Harvard University Herbaria<br>
email: <a href="mailto:morris.bob@gmail.com" target="_blank">morris.bob@gmail.com</a><br>web: <a href="http://bdei.cs.umb.edu/" target="_blank">http://bdei.cs.umb.edu/</a><br>web: <a href="http://etaxonomy.org/mw/FilteredPush" target="_blank">http://etaxonomy.org/mw/FilteredPush</a><br>
<a href="http://www.cs.umb.edu/%7Eram" target="_blank">http://www.cs.umb.edu/~ram</a><br>phone (+1) 857 222 7992 (mobile)<br><br>
</blockquote></div><br></div></div>
<P><br/>------<br/>If you have received this transmission in error please notify us immediately by return e-mail and delete all copies. If this e-mail or any attachments have been sent to you in error, that error does not constitute waiver of any confidentiality, privilege or copyright in respect of information in the e-mail or attachments. <br><br>
Please consider the environment before printing this email.
<br/>------<br/>
</P></body></html>