The goal of the GACS project is to create a Global Agricultural Concept Scheme as a hub for thesauri in the agricultural field, in multiple languages, for use in Linked Data. This presentation focuses on AGROVOC.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
1. A I M S AGROVOC GACS Working Group First meeting April 7-9,
2014
4. Goal of this presentation To tell you as much as possible
about Agrovoc 9/3/2014 4
5. Outline A bit of history of Agrovoc Agrovoc now Access
Maintenance Users Data publication workflow Editorial workflow
Copyright, license Agrovoc structure Walkaround in Agrovoc
following VB Agrovoc by domain: scientific tax, names, geographical
entities LOD Mapping 9/3/2014 5
6. AGROVOC from the beginning 1980s: AGROVOC on paper, only 3-4
language versions 1990s: AGROVOC moves to DB. More language
versions are added. Central dabatase, DB dump sent to partners for
translation > limitations in maintenance and sharing 9/3/2014
6
7. 2000s Move to semantic technologies Need to streamline
maintenance, and improve sharing over the web Adopted format is OWL
Development of Workbench 9/3/2014 7
8. Late 2000s Clear need for distinction between conceptual
level and terminological level: notion of a concept scheme
Collaboration between FAO and ICRISAT (KSI, Knowledge Sharing and
Innovation Group) Top concepts reduced from 918 to 25 Around 85,000
term relations revised Non-hierarchical relationships refined by
semantic relations Ca. 4,000 non-preferred terms changed to
preferred terms
9. 2010 until now RDF is widely accepted standard SKOS is the
RDF vocabulary for thesauri OWL shows limitations with thesauri
structure and multilinguality Workbench becomes VocBench VocBench
adopted by Biotechnology Glossary, used for bibliographic data
9/3/2014 9
10. AGROVOC now 9/3/2014 10
11. AGROVOC 2014 AGROVOC RDF/SKOS (SKOS-XL) for download live
through SPARQL endpoint and web services LOD: linked to 13
vocabularies VocBench v2.1 out in a few days 9/3/2014 11
12. Some figures Total number of concepts = ~ 32,000 20
languages published 4 under development 25 top concepts Maximum
depth hierarchy: 14 9/3/2014 12
13. How to look at AGROVOC A terminological resource A domain
model Provides a view on how concepts are related to one another,
e.g. agriculture is an activity, not say, a science, a technique,
or a religion An RDF/SKOS resource and a linked data set for use in
web based applications 9/3/2014 13
14. Strengths of AGROVOC Multilinguality Number of
(institutional) users Experience and work done towards use in open
data environment 9/3/2014 14
15. Access 9/3/2014 15
16. Agrovoc Online Browse/search New tool under development: an
SKOS explorer, Drupal module http://dev-skos-explorer.
gotpantheon.com/skos_explorer 9/3/2014 16
17. 9/3/2014 17
18. For download RDF-SKOS Agrovoc only, aka Agrovoc Core
Agrovoc LOD Other formats are no longer updated relational DB,
XML.. SPARQL endpoint Webservices 9/3/2014 18
19. live access SPARQL endpoint More used than we thought, as
per Survey Webservices In fact less used than we thought Certainly
used by big institutions/library - they count 1 for us 9/3/2014
19
20. AGROVOC maintenance 9/3/2014 20
21. In the past Institutions translating AGROVOC would get a
dump of the DB, then: Translations workflow decided internally to
the institution (who translates, who revises, ...) & totally
implicit Data sent back to FAO for inclusion in master copy
9/3/2014 21
22. Now Data is managed within VocBench Web based Implement
formalized editorial workflow Editors may get rights on languages
Agrontology URI: http://aims.fao.org/aos/agrontology Imported
vocabularies are maintained elsewhere. 9/3/2014 22
23. Manual - automatic Contribution to Agrovoc (new concepts,
translations) is largely manual ~2012 a couple of languages first
proposed by automatic translation tool (company provided), then
revised manually Some tests done for automatic extraction of
relations from text, we may continue on that in the future Mapping
automatically extracted, then validated 9/3/2014 23
24. VB 2.0 Re-engineered RDF backend, based on RDF Management
platform Semantic Turkey Support for different triple stores
Extension mechanism based on OSGi Multi scheme management. Several
skos:ConceptSchemes can be developed for the same dataset,
providing different views on the data Statistics module (a module
providing resuming information about the loaded data). Export
module: for exporting all or part of the content of a project
according to several existing RDF serialization standards Load data
module: for loading bulk data serialized in some RDF serialization
standard Ontology Import Management
(Administration-->Ontologies): to owl:import ontologies to be
used as property vocabularies for the modeled thesauri New tabs
under the concept view for covering extensively the SKOSXL standard
(note, notations) 9/3/2014 24
25. VB 2.1 out in a few days A completely rebuilt installation
mechanism - headache-free Self-installing DB, with auto-updating
scripts Wizard-driven system configuration, with import/export of
configuration profiles SPARQL module: query/update content directly
through the SPARQL query language for RDF; syntax completion &
highlight Multi scheme management: now concepts can be shared among
different schemes RSS feeds for all editing actions 9/3/2014
25
26. AGROVOC users 9/3/2014 26
27. Editors So far, one focal point per language See Agrovoc
web site Now, we are moving to editing responsibility per language,
per domain 9/3/2014 27
28. Editing rights in VocBench Now editors get rights by
language Future: maybe also by domain (or similar notion?) 9/3/2014
28
29. Users of Agrovoc libraries, information management, From
survey, also software developers, translators, managers,
researchers 9/3/2014 29
30. Communication with users Through website (form) Direct
email [email protected] AIMS bulleting Agrovoc googlegroup Just
started, not yet active 9/3/2014 30
31. Support for users For editors: VB support (user manual,
video tutorials) Syntax-oriented guidelines for editors Would like
to have more domain-oriented guidelines, also explaining the use of
Agrontology 9/3/2014 31
32. Data publication infrastructure 9/3/2014 32
33. Tools and hosting Mostly at Mimos Berhad (Malaysia)
Editing: VocBench SPARQL endpoint: Allegrograph LOD content
negotiation, Pubby for producing HTML 9/3/2014 KISAF, Rome 33
34. Data publication workflow 9/3/2014 34
35. master data -> download 1. Extraction of data from
VocBench 2. Data preparation for publication 1. Agrovoc Core 2.
Agrovoc LOD 1. Add reference to VOID file, per concept 2. Add data
of Agrovoc version 3. For LOD, add triples 3. Load files on
download site 9/3/2014 KISAF, Rome 35
36. master data -> dynamic access Agrovoc LOD into triple
store for external access 9/3/2014 KISAF, Rome 36
37. Editorial workflow 9/3/2014 37
38. Basics Formally defined: all editorial activities happen
inside VB (as opposed as via email, phone..) Roles of users Status
of elements 9/3/2014 38
39. Role of users Term editor Ontology editor Validator
Administrator Publisher 9/3/2014 39
40. Status of elements Draft Revised Validated Published
Proposed deprecated Deprecated 9/3/2014 40
41. Validation phase Dedicated module: Validation See also
module: Recent change, RSS Also, History of concepts, terms
9/3/2014 41
42. Data publication 9/3/2014 42
43. Copyright FAO languages, stays with FAO English, French,
Spanish, Arabic, Russian, Chinese Other languages, stays with the
institution that authored it Not exactly defined how it will be
with a distributed authorship, e.g. by domain Provenance? 9/3/2014
KISAF, Rome 43
44. License Agrovoc may be used for free by anyone Would like
to have a CC3.0 Although this is not official FAO policy 9/3/2014
44
45. A concept scheme 9/3/2014 45
46. Concepts and terms Distinction between conceptual level and
terminological level Concepts are represented by terms 9/3/2014
46
47. Example from AGROVOC Thesaurus 9/3/2014 47
48. Terms Thesaurus maize UF corn (maize) Corn (maize) use
Maize Concept scheme maize preferred term/ preferred label Corn
(maize) non preferred term/ alternative label 9/3/2014 48
49. SKOS Terms are turned into labels Skos:prefLabel maize@en
Skos:altLabel corn (maize)@en skos:prefLabel Mais@it skos:altLabel
granoturco@it . of the same concept = skos:Concept A concept is
identified and represented by an URI
http://aims.fao.org/aos/agrovoc/c_12332 and located, as an URL
9/3/2014 49
50. Example from VocBench 9/3/2014 50
51. 9/3/2014 51
52. Language coverage 9/3/2014 52
53. 53 0 5000 10000 15000 20000 25000 30000 35000 40000 45000
Spanish English Turkish Czech French Japanese Portuguese Chinese
German Farsi Polish Italian Hindi Russian Hungarian Arabic Slovak
Thai Lao Korean Telugu Malaysian Ukranian Indonesian Marati Series1
Number of terms per language
54. 54 0 5000 10000 15000 20000 25000 30000 35000 Marati
Indonesian Ukranian Malaysian Telugu Korean Lao Slovak Hungarian
Russian Thai Farsi Polish Hindi Italian German Arabic Japanese
Turkish French Chinese Spanish Portuguese Czech English Series1
Number of concepts with no terms per language
57. Remarks Same hierarchy for all languages Historical
reasons: English was the first language, the others were added as
translations Multiple parents allowed Ca. 1200 concepts with more
than one parent Max. depth of hierarchy = 14 9/3/2014 57
60. BT/NT in Agrovoc In tree like format: [Products] [Plant
products] [Cereals*] [Rice*, Paddy] In standard thesaurus-like
format: [Rice*] BT [Cereals*] In SKOS (simplified):
http://aims.fao.org/aos/agrovoc/c_12332 skos:broader
http://aims.fao.org/aos/agrovoc/c_6599 9/3/2014 60
61. For sake of readability... I am using the English preferred
label to talk about a concept As in: [Rice*] Instead of using its
URI Preferred and alternative labels would be written as: [Rice*,
Paddy] 9/3/2014 61
62. Thesaurus hierarchies Sometimes close to is-a relations: BT
Plant products Maize NT Dent maize NT Sweet corn Sometimes close to
containment or part-of: BT Europe BT Southern Europe Italy NT
Abruzzi NT Sicily 9/3/2014 62
63. URI Generation 9/3/2014 63
64. Alphanumeric URIs http://aims.fao.org/aos/agrovoc/c_12332
To be language independent How to chose one language over the
other? Label in that language may not be available 9/3/2014 64
65. URIs of concepts existing before the conversion to SKOS URI
is formed by appending: Namespace + c_ + the term code of the
Agrovoc term 9/3/2014 65
66. From term code to URIs 9/3/2014 66
67. About Agrovoc term codes In the DB, terms were given a
double key: a code for the term, plus a code for the language.
Then, all preferred term had the same term code + different
language code Codes had no fixed length 9/3/2014 67
68. URIs of concepts created after the conversion to SKOS URI
is formed by appending: Namespace + c_ + 13-digit automatically
generated code 9/3/2014 68
69. Concepts 9/3/2014 69
70. Top concepts and thematic organization 9/3/2014 70
71. 25 top concepts
72. # of concepts under each Top organism substances entities
phenomena activities products methods properties features objects
resources subjects systems locations groups measures state stages
technology processes factors time events site 9/3/2014 72 0 5000
10000 15000 20000 25000 strategies Series1
73. Remarks Great difference in development of hierarchy under
each top Not necessarily a problem No thematic roots Plants and
animals under organisms Agriculture is under activities (economic
activity) Forestry under subject Food under product 9/3/2014
73
74. 9/3/2014 74
75. 9/3/2014 75
76. Data and vocabulary 9/3/2014 76
77. AGROVOC data All terminological and domain information
Concepts Terms Relationships between concepts, or between terms
URIs within namespace: http://aims.fao.org/aos/agrovoc/ E.g. URI of
concept [maize]: http://aims.fao.org/aos/agrovoc/c_12332 9/3/2014
77
78. Vocabularies used in Agrovoc - 1 Vocabulary here is = The
collection of properties that are used to describe concepts, terms
and relations SKOS: to express concepts, BT/NT, RT, and matches
with other vocabularies SKOS-XL: to express labels (to be able to
make statements about labels) 9/3/2014 78
79. Vocabularies used in Agrovoc - 2 VOID: to describe the
dataset Dcterms: for date of creation and modification Foaf: for
images 9/3/2014 79
80. Vocabularies used in Agrovoc - 3 Agrontology: for
AGROVOC-specific properties and relations
http://aims.fao.org/aos/agrontology 9/3/2014 80
81. Information on concepts 9/3/2014 81
82. A look at Agrovoc through VocBench 2.0 Note that some
things present in the interface of VocBench are not really used in
Agrovoc... In the following, we follow the tabs used to show
information about concepts 9/3/2014 KISAF, Rome 82
83. Following VocBench interface 9/3/2014 83
84. Terms Tab terms 9/3/2014 84
85. Terms All terms available for that concept Terms are
clickable, more info about the term is shown The possibility of
making statements about terms is provided by SKOS-XL (more on this
later) 9/3/2014 85
86. Definitions of concepts Tab Definitions 9/3/2014 86
87. Definitions VB allows for more than one definition Can
specify source, URL Expressed with skos:definition Each definition
may have more than one translation Agrovoc only has single
definitions Its value is an URIs, like agrovoc:c_def_1328252885416
Mostly added after conversion to SKOS, ~1200 9/3/2014 87
88. Notes Tab Notes 9/3/2014 88
89. Notes general This tab collects two types of notes, that
Agrovoc inherited from its thesaurus-time Scope notes To define the
scope of applicability of concepts Editorial notes To keep track of
some editorial information 9/3/2014 89
90. Scope note Rendered by skos:scopeNote Its value is string
just text May be given in various languages Used to define the
scope of applicability of a concept = in old Agrovoc it was not
possible to give definitions, so often Scope Notes were used to
provide definitions 9/3/2014 90
91. Editorial note Rendered as skos:editorialNote In old
Agrovoc thesaurus there was no way to keep author/year of a
scientific name, so editors often sued Editorial Notes. E.g.
Skos:prefLabel Aulopus filamentosus @en Skos:editorialNote Author:
(Bloch 1792)@en Plan is to have proper encoding of author/year of
scientific names 9/3/2014 91
92. 9/3/2014 92
93. Attributes of concepts Tab Attributes 9/3/2014 93
94. Attributes Datatype properties of concepts = the value of
the property is a word, or rather, a string Currently, Agrontology
includes: isSpatiallyIncludedInState (not actually used)
isSpatiallyIncludedInCity isHoldBy ( Not actually used)
isPartOfSubvocabulary 9/3/2014 94
95. Remarks Some are currently under examination as part of the
geographical domain (ref. Otakar erba) isSpatiallyIncludedInState
(no occurrences) isSpatiallyIncludedInCity Notion of list of
concepts agrontology:isPartOfSubvocabulary Ideally we would like to
use something more standard isHoldBy is not used in Agrovoc
9/3/2014 95
96. Concept codes Tab Notation 9/3/2014 96
97. Notation Meant to keep codes of concepts skos:notation Not
used in Agrovoc (codes were given to terms) 9/3/2014 97
99. Concepts relationships Non-hierarchical relationships of a
given concept In thesauri, only RT, between terms In concept
schemes, same notion with skos:related same vagueness as RT, but
between concepts Also other, more specific related are possible
9/3/2014 99
100. Example of relationshiops concept [Oryza*] 9/3/2014
100
101. Recap In thesaurus, only RT relation At some point, the
RTs were refined ~ 160 (including inverse) Now: Number of relations
has reduced further reduction under evaluation Vocabulary
Agrontology collects Agrovoc relations Defined as an extension of
skos:related 9/3/2014
102. Example of Agrovoc relationships [Oryza sativa*]
agrontology:produces [Rice*, Paddy] Which infers: [Rice*, Paddy]
agrontology:is producedby [Oryza sativa*] [Rice*, Paddy]
skos:related [Oryza sativa*] 9/3/2014
103. Same example, seen in VocBench 9/3/2014 103
104. Agrontology Visualized in Module Relationship (called
Properties in VB 2.1) Also available as HTML from:
http://aims.fao.org/aos/agrontology 9/3/2014
105. 9/3/2014 105
106. History of changes of concept Tab History 9/3/2014
106
107. History The list of actions performed on the concept Some
data is kept in Agrovoc, i.e. date of creation, last update The
changes performed in between creation and last update are stored in
VB only 9/3/2014 107
108. Example 9/3/2014 KISAF, Rome 108
109. Images Tab Image 9/3/2014 109
110. Image A pointer to an image available online, one may give
name, source and URL of the source.
http://xmlns.com/foaf/0.1/depiction 9/3/2014 110
111. Hierarchy 9/3/2014 111
112. Summary of the hierarchy tab Hierarchy 9/3/2014 KISAF,
Rome 112
113. Hierarchy Is meant to give a quick grasp of the position
of the selected concept in the hierarchy Only parents from current
concept to its Top 9/3/2014 KISAF, Rome 113
114. Expanding on Agrovoc concept attributes - Subvocabularies
of concepts 9/3/2014 114
115. The idea behind A way to make lists of concepts Visualized
in tab Attribute (of concepts) Expressed by predicate
agrontology:isPartOfSubvocabulary Value is a char (the name of the
list) You may think of them as a flag assigned to a concept
Subvocabularies may be defined by administrators 9/3/2014 115
116. Current subvocabularies of concepts 9/3/2014 116
117. Subvocabularies currently defined Chemicals (644 concepts)
Geographical country level (247) Geographical above country level
(246) Geographical below country level (522) Fishery related terms
(259) 9/3/2014 117
118. Remarks Geographical vocabularies are currently under
examination: Country level Above country level Below country level
9/3/2014 KISAF, Rome 118
119. Information about terms 9/3/2014 119
120. Pubby html presentation of rdf 9/3/2014 120
121. Terms in SKOS In RDF/SKOS view, terms are labels of
concepts (strings) Labels are strings 9/3/2014 121
124. Terms in SKOS-XL SKOS-XL is an extension of SKOS Labels
are really objects, about which one can make statements 9/3/2014
124
125. Agrovoc is in SKOS-XL Because we want to make statements
about terms E.g. Creation date, status (drafted, ..., published)
skosxl:prefLabel for descriptors skosxl:altLabel for non
descriptors But also skos:prefLabel and skos:altLabel are generated
for various purposes E.g. Pubby 9/3/2014 125
126. History 9/3/2014 126
127. History information for terms 9/3/2014 127
128. Relationships 9/3/2014 128
129. Relationships between terms 9/3/2014 129
130. Visualize relations between terms in VB 9/3/2014 130
131. Attributes 9/3/2014 131
132. Attributes of terms 9/3/2014 132
133. Linguistic information as attribute of terms Singular,
plural forms agrontology:hasSingular, agrontology:hasPlural
Spelling variants Agrontology:hasSpellingVariant E.g. hemophilia,
haemophilia different labels? Membership to a subvocabulary of
terms Agrontology:hasTermType 9/3/2014 133
134. Notation 9/3/2014 134
135. Term codes -> notations 9/3/2014 135
136. Expanding on Agrovoc term attributes Subvocabularies of
terms 9/3/2014 136
137. The idea behind A way to make lists of terms, just like
the subvocabularies of concepts 9/3/2014 137
138. Subvocabularies of terms 9/3/2014 138
139. Subvocabularies of terms Expressed as a term, i.e.,
predicate agrontology:hasTermType In VocBench: tab Attribute of a
term Subvocabularies may be defined by administrators 9/3/2014
139
140. # terms per subvocabularies (en) Taxonomic terms for
plants: 4297 Taxonomic terms for animals: 14809 Taxonomic terms for
bacteria: 7133 Common name for viruses: 50 Taxonomic terms for
viruses: 5136 Common name for plants: 8000 Common name for
bacteria: 29 Acronym: 867 Common name for animals: 4613 Taxonomic
terms for fungi: 17830 Common name for fungi: 144 9/3/2014 140
141. Membership to a vocabulary of terms seen in VB 9/3/2014
141
142. Remark More than one membership is possible But now mostly
individual membership in the old MySQL maintenance tool it was not
possible to assign two attributes 9/3/2014 142
143. Provenance information 9/3/2014 143
144. Information in Agrovoc For concepts: date of creation
Dct:created Date of last update Dct:modified For terms Date of
creation and last update As above 9/3/2014 144
145. Information in VocBench Extra information for management
purposes User, action, change See VB modules Recent Changes and
Validation 9/3/2014 145
146. Multilinguality in Agrovoc 9/3/2014 146
147. Multilinguality Labels are marked with ISO 2 Letter
Language Code Languages as recognized by linguists En for English,
Es (Spanish) in general, independently of where it is spoken
9/3/2014 147
148. Multilinguality ISO 2 Language codes 9/3/2014 148
149. Language variations by countries English in UK, USA, OZ,
.. Spanish in Spain, Argentina, Venezuela Portuguese in Portugal,
Brazil This fact may be expressed by using ISO2 for languages + ISO
for countries 9/3/2014 149
150. Example: some terminological differences in PT (EMBRAPA)
9/3/2014 150
151. Terminological variations by regions Names for concrete
objects, or object of large use (food, plants, animals, ) tend to
vary considerably within a language, e.g. by country/state/region/
They also tend to stay over time e.g., indigenous words used after
the indigenous language is no longer spoken Reflection on
limitations of code-oriented approach 9/3/2014 151
152. Multilinguality More flexible way to support
multilinguality? accommodate the area of use of a given name Where
area may be a country, a political or geographical region, or an
aggregation of these E.g. palta is Quechua name for avocado, used
in Argentina, Bolivia, Chile, Peru, Uruguay. Connection between
linguistic and geographical information 9/3/2014 152
153. AGROVOC by domains: living organisms 9/3/2014 153
154. 9/3/2014 154
155. Scientific taxonomies 9/3/2014 155
156. Where in the hierarchy Most concepts for animal and plants
are under top concept organisms* ~ 2/3 of total concepts in AGROVOC
9/3/2014 156
157. 9/3/2014 157
158. In Agrovoc thesaurus Only BT/NT hierarchies of taxa E.g.
[Oryza*] BT [Poaceae] No specification of ranks E.g. Oryza is a
genus No formal way to specify other attributes of a scientific
name See the use of Editorial notes 9/3/2014 158
159. Elements in a scientific taxonomy and their names In case
more than one name is available for a concept, the binominal name
is preferred label 9/3/2014 159
160. 9/3/2014 160
161. Taxonomies in Agrovoc now Mostly, skos:broader Oryza
skos:broader Poacacee Also, some pairs of taxa are connected by a
number of relations in Agrontology e.g.
agrontology:includesSubGroup Note that they are subproperties of
skos:related.. Plan is to remove them 9/3/2014 161
162. Ranks in Agrovoc now Rendered by
agrontology:hasTaxonomicLevel Oryza glaberrima* hasTaxonomicLevel
species (taxa)* Values for hasTaxonomicLevel are concepts under:
Groups* Taxa* 9/3/2014 162
163. Scientific names 9/3/2014 163
164. Scientific names Binominal nomenclature Hibiscus
rosa-sinensis, Linnaeus 1753 Common names: Hibiscus, Chinese
hibiscus, 9/3/2014 164
165. What language tag for scientific names? Some people say
binominal names are Latin. No! rather latinate In Agrovoc, they are
repeated in all languages, with the corresponding language tag This
is due to historical reason, it was the only way to have scientific
names in each language version 9/3/2014 165
166. Scientific names in AGROVOC Are all labels of
skos:concepts May be preferred or alternative labels General
guideline: Scientific name is preferred under a scientific taxonomy
In case more than one scientific name is available for the same
entity, the non preferred is a synonym of the other 9/3/2014
166
167. How to mark scientific names - 1 Using a subvocabulary of
terms Predicate agrontology:hasTermType Current possible values:
Taxonomic name for [animals | Bacteria | Fungi | Plants | viruses],
and also Common names for Does not require that common names are
available 9/3/2014 167
168. How to mark scientific names - 1
agrontology:hasScientificName Applies to terms Link together
scientific and common name of the same concept, the same language
9/3/2014 168
169. Remark 1 It is a binary notion Requires a common name for
that concept! 9/3/2014 169
170. Remarks Membership to a subvocabulary is a unary notion
Our goal: unary property to mark that a term is a scientific name,
together with author and year 9/3/2014 172
171. Scientific taxonomies and common names 9/3/2014 173
172. Background At the time of the revision of Agrovoc there
was the idea to have separate hierarchies for scientific and common
sense taxonomies Connected by skos:related Under a taxonomic
hierarchy, the preferred term is always a scientific names 9/3/2014
174
173. Separate hierarchies for scientific and common sense
taxonomies * figure taken from earlier revision work on AGROVOC
9/3/2014 175
174. Example skos:related 9/3/2014 176
175. Remark Sometimes no clear separation between scientific
taxonomies and common sense taxonomies Example: Felidae (=
biological family of cats, next slide) Appears within a scientific
taxonomy But its subconcepts are not scientific
176. Example: Felidae 9/3/2014 178
177. Remark 1 It is not always possible to have clear 1-1
correspondences between scientific and common sense taxonomies
Common names are not always available One common name may be used
for very many They often are just the same as scientific names, or
similar 9/3/2014 179
178. Remark 2 Different classifications are proposed (->
scientific taxonomies). taxonomies also change over time In
AGROVOC, attempt to use a C-C relation
agrontology:formerlyIncludedIn Agavaceae*
agrontology:formerlyIncludedIn Liliaceae satisfactory?... 9/3/2014
180
179. Looking at AGROVOC by domains: geographical entities
9/3/2014 181
180. How they are expressed Agrontology:hasSubvocabulary Two
vocabularies: Geographical country level = 247 concepts
Geographical above country level 9/3/2014 182
181. Geopolitical information Agrovoc has no notion of time:
Czechoslovak Socialist Republic German Democratic Republic 9/3/2014
183
182. Physical geography Geographical above country level = 246
A variety of notions Americas Baltic States Islamic countries Lake
Kivu Atlantic Ocean Yellow Sea 9/3/2014 184
183. Geographical relations spatiallyIncludes Guyana Cuyuni
River A variety of notions Americas Baltic States Islamic countries
Lake Kivu Atlantic Ocean Yellow Sea 9/3/2014 185
184. Agrovoc on geographical entities Currently under revision
by Otakar Cerba (visitor scientist @FAO) 9/3/2014 186
185. Agrovoc LOD 9/3/2014 187
186. Mapped vocabularies 1 9/3/2014 188
187. Mapped vocabularies 2 9/3/2014 189
188. Mapping process 9/3/2014 190
189. Mapping activities @Agrovoc Intense activity around
2011-2012 Process managed internally Candidate mapping
automatically generated (using both publicly available
implementations and algorithms implemented in-house) Manual
evaluation Done by one colleague, Gudrun Publication 9/3/2014
191
190. VB and mapping Development happens within SemaGrow Project
deadline 2015 But because of internal deadline, might be ready Nov
2014, first version at least Whats needed ongoing improved
multi-project management capabilities (in Semantic Turkey), to
access data from a different project, mediated by a dedicated
Access Control policy mapping engine
191. More info SemaGrow project www.semagrow.eu Deliverable
D3.2.1- Techniques for Ontology Alignment
http://www.semagrow.eu/sites/default/files/D3.2.1-
Techniques%20for%20Ontology%20Alignment.pdf