{"id":2966,"date":"2017-06-16T22:23:40","date_gmt":"2017-06-16T22:23:40","guid":{"rendered":"https:\/\/notebooks.dataone.org\/?p=2966"},"modified":"2017-06-16T22:23:40","modified_gmt":"2017-06-16T22:23:40","slug":"week-3-protege-5-and-owl","status":"publish","type":"post","link":"https:\/\/notebooks.dataone.org\/controlled-vocab\/week-3-protege-5-and-owl\/","title":{"rendered":"Week 3: Prot\u00e9g\u00e9 5 and OWL"},"content":{"rendered":"
Moving into the third week of the project I pulled back a bit and did some background reading. The issue with the Prot\u00e9g\u00e9 5 ontology imports I decided was an issue stemming from my ignorance with regards to the software and terminology therein. To remedy this I read the book Semantic Web for the Working Ontologist: Effective Modeling in RDFS and OWL 2nd Edition<\/strong><\/em><\/a> by Dean Allemang and Jim Hendler. This book provided me with a detailed explanation of the Semantic Web. The text is filled with examples and by the end I felt fluent in the terminology. Following reading the book by Allemang and Hendler I returned to troubleshooting the Prot\u00e9g\u00e9 5 ECSO (Ecosystem Ontology) import. Previously, the ECSO import to Prot\u00e9g\u00e9 5 had been unreadable with only the ontology ID displayed (ex. TAXA_000002860<\/a>, ECSO_00002629<\/a>, etc.) not the class rdfs label (ex. mollusc<\/a>, methane<\/a>, etc.). I was able to resolve this issue by going into the Preferences in Prot\u00e9g\u00e9 and under the New Entities tab selecting \u201cend with auto-generated ID for entity label\u201d, then specifying that it should be the \u201csame as label render\u201d and changing the language to “en” for English. Following this, I changed the View in Prot\u00e9g\u00e9 to \u201cRender by annotation properties\u201d and then \u201cRender by label (rdfs:label).\u201d Of the 1,959 classes within the ECSO all but 52 classes now display their proper rdfs label. The 52 that did not properly render lack any annotation information and are \u201cnaked terms.\u201d While there are still issues with these 52 imports there does not appear to be a pattern in their OWL model construction. Currently the unlabeled classes consist of 3 ECSO, 16 ENVO (Environment Ontology<\/a>), 32 PATO (Phenotypic Quality Ontology<\/a>) and one UO (Units of Measure Ontology<\/a>) class. I will have more on this mystery next week!<\/p>\n Another goal this week was to evaluate whether the the queried search terms regarding carbon cycling on the Arctic Data Center are present in the ECSO ontology. The query term list includes those from Chapin et al., <\/em>2006 (mentioned last week), new terms have been added from results found within the database during query searches, and select terms from the Glossary of Permafrost and Related Ground-Ice Terms<\/strong><\/em><\/a> \u00a0from the National Research Council of Canada and the International Permafrost Association<\/a>. Of the 51 queried terms there were a total of 2486 search results within the ADC database. Within ECSO there are currently 2 of these 51 queried carbon-cycling related terms within the ontology. The two terms are \u201ccarbon\u201d and \u201cmethane\u201d which account for 21% of the total search results and are clearly essential terms for the ADC carbon-cycling ontology. Moving forward next week I will be focusing on knowledge modeling itself of carbon-cycling terms within ECSO in Prot\u00e9g\u00e9 5.<\/p>\n","protected":false},"excerpt":{"rendered":" Moving into the third week of the project I pulled back a bit and did some background reading. The issue with the Prot\u00e9g\u00e9 5 ontology imports I decided was an issue stemming from my ignorance with regards to the software and terminology therein. To remedy this I read the book Continue reading Week 3: Prot\u00e9g\u00e9 5 and OWL<\/span>