{ "version": "https://jsonfeed.org/version/1.1", "title": "chem-bla-ics", "description": "Chemblaics (pronounced chem-bla-ics) is the science that uses open science and computers to solve problems in chemistry, biochemistry and related fields.", "home_page_url": "https://chem-bla-ics.linkedchemistry.info/", "feed_url": "https://chem-bla-ics.linkedchemistry.info/2008/03/03/metabolomics-ontologies-skos-ified.json", "icon": "https://chem-bla-ics.linkedchemistry.info/assets/images/chem-bla-ics_logo.png", "language": "en", "authors": [ { "name": "Egon Willighagen", "url": "https://orcid.org/0000-0001-7542-0286", "_orcid": "0000-0001-7542-0286" } ], "items": [ { "id": "https://doi.org/10.59350/ne3f5-6kt41", "url": "https://chem-bla-ics.linkedchemistry.info/2008/03/03/metabolomics-ontologies-skos-ified.html", "title": "Metabolomics Ontologies: SKOS-ified the ArMet specification", "content_html": "

The MetWare project \nis going to make use of ontology\ntechnologies to control the content of the database, and a first step is to convert our MetWare database design\ninto something using a formal ontology language. I have played with OWL\nin the past (see for example\nits use in Bioclipse ),\nbut was not overly happy with it in all situations.

\n\n

Then I read about SKOS, Simplified Knowledge Organisation System. Unlike OWL, SKOS is less strict on relations\nbetween concepts being marked up. Often these concepts are loosely bound, instead following a strict is_a hierarchy.\nArMet is a Metabolomics knowledge system which does not have a strong hierarchy, and SKOS seemed to me to be the most\nsuitable markup candidate. So, I SKOS-ified the ArMet specification, resulting in this rather simple document.\nThe document is SKOS, but has an associated skos2html.xsl\nXSLT stylesheet, so that Firefox converts it to XHTML on the fly.

\n\n

An entry looks like:

\n\n
<skos:Concept rdf:about=\"GenotypeID\">\n  <skos:prefLabel>genotypeID</skos:prefLabel>\n\n  <skos:definition>A unique identifier for the genotype.</skos:definition>\n  <skos:broader rdf:about=\"GenotypeProperty\"/>\n</skos:Concept>\n
\n\n

The full SKOS specification allows capturing much of what we want to do, including i18n via the label system, loos hierarchical relations via\nskos:broader, and the concepts of skos:Collection to aggregate concepts. Where needed, it allows borrowing from other languages. For example,\nto link concepts from MetWare to the original ArMet specification owl:sameAs can be used.

", "summary": "The MetWare project is going to make use of ontology technologies to control the content of the database, and a first step is to convert our MetWare database design into something using a formal ontology language. I have played with OWL in the past (see for example its use in Bioclipse ), but was not overly happy with it in all situations.", "date_published": "2008-03-03T00:00:00+00:00", "date_modified": "2025-08-17T00:00:00+00:00", "tags": ["bioclipse","metware","ontology","semweb","owl","xml"], "authors": [ { "name": "Egon Willighagen", "url": "https://orcid.org/0000-0001-7542-0286" } ] } ] }