Hi Stian,
We recently had this discussion too, and then it was said to be
intended use from a CHEMINF perspective...
On Wed, Jan 7, 2015 at 12:14 PM, Stian Soiland-Reyes
<
st...@mygrid.org.uk> wrote:
> I would expect a 'preferred
> name' to be a property, not a class - why is it defined as a class in the
> ontology if it is really meant to be used as a property?
I guess this is the design decision of CHEMINF: it captures
"descriptors" of things (chemicals) and models these as OWL
ontologies. I do not see why "preferred name"s should be any different
from other things describing that chemical.
That is besides the question about whether this can be used as a
property, which was new to me last summer too.
> Is there a rdf:value or similar property that should be used to provide the actual
> literal synonym? If so, with which property should we relate ops:OPS1769270
> to the synonym instance?
Do any of these examples come close to what you mean?
https://code.google.com/p/semanticchemistry/wiki/Examples
Yeah, that is a decision design in line with many other ontologies.
The downside is clear, but it has the advantage that you can fix the
title/label without getting conflicts with the URI... there may be
other advantages I forgot...
But they are hard to remember and the reason why I added a few tables
to the above Examples page...
Egon
--
E.L. Willighagen
Department of Bioinformatics - BiGCaT
Maastricht University (
http://www.bigcat.unimaas.nl/)
Homepage:
http://egonw.github.com/
LinkedIn:
http://se.linkedin.com/in/egonw
Blog:
http://chem-bla-ics.blogspot.com/
PubList:
http://www.citeulike.org/user/egonw/tag/papers
ORCID: 0000-0001-7542-0286
ImpactStory:
https://impactstory.org/EgonWillighagen