semantic dissonance in uniprot

I was playing with RDF gathered from UniProt this morning and stumbled on something that made me a little sad.  Apparently molecules like the rigor mortis (rig) protein from Drosophila (depicted at right)  have been isolated from "a young sporophyte contained within a seed". This seems a little strange for a fruit fly protein.

In the RDF, I see triple 1: (Protein Q86BY9, isolated from , uniprot tissue 229 (Tissue Embryo))
http://purl.uniprot.org/uniprot/Q86BY9 (subject)
http://purl.uniprot.org/core/isolatedFrom (predicate)
http://www.uniprot.org/tissues/229 (object)

and triple 2: uniprot tissue 229, is the same as, plant ontology term PO:0009009 (embryo)
http://www.uniprot.org/tissues/229 (subject)
http://www.w3.org/2002/07/owl#sameAs (predicate)
http://purl.uniprot.org/po/0009009 (object)

Even if the sacrificial fruit flies were found inside some poor young sporophyte, this probably still would not make sense.  I hate bashing Uniprot because the fact that they have bothered to produce RDF versions of their records is a useful and unusual trait for a major bioinformatics institute and has enabled a lot of my work, BUT..  RDF/etc.  are really much more useful when some attention is paid to the definitions associated with their constructs.  OWL:sameAs means that 'two URI references actually refer to the same thing: the individuals have the same "identity"'.  Having live statements that say that a fly protein was isolated from "a young sporophyte contained within a seed" is probably not such a great thing.  

Perhaps we would be better off if the W3C would introduce the relationship "OWL:kindOfSimilar" .  Its likely that RDF/OWL providers like UniProt use OWL:sameAs in these situations because its the built-in predicate that comes closest to expressing what they mean.  Maybe if we gave them something else to use in the many cases where similarity exists but is not absolute things on the semantic Web would make more sense.  (Perhaps we would also be rewarded with standardized ways to quantify the confidence or degree of such relationships as well.)

Note to Uniprot: say what you mean!

Note to semantic Web people: make it easier for them to say 'squishy' things like "sort of similar to"!  Reality is analogue, deal!  

Connotea + Semantic Web = E.D.

What do you get when you combine social tagging with terms from web-accessible ontologies?

E.D. the Entity Describer

ED helps people use terms from ontologies* as their connotea tags.
Is it useful, interesting, a total waste of time? I'm not really sure yet, but it seemed like it would be fun. If you have some time, please do give it a try and let me know what you think! Details about installation etc. here

---

* Here 'ontology' just refers to any OWL/RDF document. The 'terms' are the rdfs:labels for the classes or the actual class name if the labels are missing. E.D. only "understands" rdfs:label and rdfs:subClassOf. It would make more sense to follow a SKOS model as the only semantics we plan to use are "broader-than" and "narrower-than"; but, since the large majority of OWL ontologies that we are interested in use subClassOf even when they mean skos:narrowerThan , we do the same within E.D. Support for ontologies/thesauri that are encoded with the SKOS ontology will be added as the need arises.