This is an archive of an inactive wiki and cannot be modified.

Section 0. Contact and confidentiality

Contact e-mail:,

Do you mind your use case being made public on the working group website and
No problem to make this public.

Section 1. Application 

In this section we ask you to provide some information about the application
for which the vocabulary(ies) and or vocabulary mappings are being used.

Please note:
-- If your use case does not involve any specific application, but consists
rather in the description of a specific vocabulary, skip straight to Section
-- If your application makes use of links between different vocabularies, do
not forget to fill in Section 3!

 1.1. What is the title of the application?
--- not available yet ---  

 1.2. What is the general purpose of the application?
      What services does it provide to the end-user?

We are planning to develop a semantic search that make use of mapped thesauri
to allow user to use any terminology in any of the languages the thesauri are
available and retrieve information from resources which may have been indexed
by one of the mapped vocabularies.

*1.3. Provide some examples of the functionality of the application. Try to
illustrate all of the functionalities in which the vocabulary(ies) and/or
vocabulary mappings are involved.

navigate resources, help to build boolean searches, espand searches by
languages or synonyms

1.4. What is the architecture of the application?
     What are the main components?
      Are the components and/or the data distributed across a network, or
across the Web?

-- not available yet --

 1.5. Briefly describe any special strategy involved in the processing of
user actions, e.g. query expansion using the vocabulary structure.

- concept identification
- query expansion

 1.6. Are the functionalities associated with the controlled
vocabulary(ies) integrated in any way with functionalities provided by other
means? (For example, search and browse using a structured vocabulary might be
integrated with free-text searching and/or some sort of social bookmarking or
recommender system.)

the information given the controlled vocabularies and the mappings will be
used over free text search.

 1.7. Any additional information, references and/or hyperlinks.

Section 2. Vocabulary(ies)

In this section we ask you to provide some information about the vocabulary
or vocabularies you would like to be able to represent using SKOS.

Please note:
-- If you have multiple vocabularies to describe, you may repeat this section
for each one individually or you may provide a single description that
encompasses all of your vocabularies.
-- If your use case describes a generic application of one or more
vocabularies and/or vocabulary mappings, you may skip this section.
-- If your vocabulary case contains cross-vocabulary links (between the
vocabularies you presented or to external vocabularies), please fill in
section 3!

 2.1. What is the title of the vocabulary? If you're describing multiple
vocabularies, please provide as many titles as you can.

- FAO AGROVOC Thesaurus
- FAO Agris/Caris Classification Scheme (ASC)
- FAO Technical Knowledge Classification Scheme (TKCS)
- others...

 2.2. Briefly describe the general characteristics of the vocabulary, e.g.
scope, size...

Agriculture in general, including forestry, fisheries, nutrition,
environment, etc. 
agrovoc: 35000 terms per 12 languages = 371691 terms (Descriptors and
ASC: 132 categories and subcategories
TKCS: 100 categories and subcategories
FAOTERM: 181 subjects

 2.3. In which language(s) is the vocabulary provided?
      In the case of partial translations, how complete are these?

 Total terms per language:
    AR :   25913
    CS :   38667
    DE :   25215
    EN :   39240
    ES :   41624
    FR :   38342
    JA :   38655
    PT :   36428
    SK :   25794
    TH :   25416
    ZH :   36408 

ASC, TKCS, FAOTERM: the 5 fao official languages (EN, AR, ZH, ES, FR)

*2.4. Please provide below some extracts from the vocabulary. Use the layout
or presentation format that you would normally provide for the users of the
vocabulary. Please ensure that the extracts you provide illustrate all of the
features of the vocabulary.  


EN : Cows
FR : Vache
ES : Vaca
AR : بقرات 
ZH : 母牛 
PT : Vaca
CS : krávy
JA : 雌牛  
TH : แม่โค  
SK : kravy
BT : Cattle
NT : Suckler cows
NT : Dairy cows
RT : Heifers
RT : Cow milk
RT : Milk yielding animals
RT : Females
SNR : Females

Scope Note : Use only for cattle and zebu cattle; for other species use
"Females" (15969) plus the descriptor for the species Term code: 1939

Other schemes see:

 2.5. Describe the structure of the vocabulary.
      What are the main building blocks?
      What types of relationship are used? If you can, provide examples by
referring to the extracts given in paragraph 2.4.

AGROVOC is made up of terms, which consist of one or more words representing
always one and the same concept. For each term, a word block is displayed
showing the hierarchical relation to other terms: BT (broader term), NT
(narrower term), RT (related term), UF (non-descriptor). Scope notes are used
in AGROVOC to clarify the meaning of both descriptors and
non-descriptors.Taxonomic and geographical terms are marked for easy
searching, filtering and downloading. The structure of the AGROVOC thesaurus
in a relational database format is available here :

Descriptors are indexing terms consisting of one or more words, and
representing always one and the same concept. Descriptors are the currently
used Agrovoc Keywords. Non-descriptors are terms which help the user to find
the appropriate descriptor(s). They appear followed by a reference (USE
operator) to the descriptor, which is the preferred term and the only one
which may be used for indexing. They can be thought of as "non used synonyms"
of Agrovoc Keywords.

Table of symbols used in the word blocks of descriptors and non-descriptors
Symbol          Meaning         Type
BT      broader term    descriptor
NT      narrower term   descriptor
RT      related term    descriptor
USE     use     non-descriptor
UF      used for        descriptor

 2.6. Is a machine-readable representation of the vocabulary already
available (e.g. as an XML document)? If so, we would be grateful if you could
provide some example data or point us to a hyperlink.

 2.7. Are any software applications used to create and/or maintain the
      Are there any features which these software applications currently lack
which are required by your use case?

distributed maintenance (currently centralised), text mining on helping
terminologist to build the thesaurus, etc.

 2.8. If a database application is used to store and/or manage the
vocabulary, how is the database structured? Illustration by means of some
table sample is welcome.

see attachment 

 2.9. Were any published standards, textbooks or written guidelines followed
during the design and construction of the vocabulary?
      Did you decide to diverge from their recommendations in any way, and if
so, how and why?

the thesaurus has been built is the early 1980s, so during the years
different standards have been followed. 

 2.10. How are changes to the vocabulary managed?

Recently a new team for the revision of the agrovoc thesaurus has been
composed. The team consults with experts and partners all over the world for
the changes on the terms. A new distributed maintenance system is under

 2.11. Any additional information, references and/or hyperlinks.

Section 3. Vocabulary Mappings

In this section we ask you to provide some information about the mappings or
links between vocabularies you would like to be able to represent using SKOS.

Please note:
-- If your use case does not involve vocabulary mappings or links, you may
skip this section!

 3.1. Which vocabularies are you linking/mapping from/to?

AGROVOC and the Chinese Agricultural Thesaurus

*3.2. Please provide below some extracts from the mappings or links between
the vocabularies. Use the layout or presentation format that you would
normally provide for the users of the mappings. Please ensure that the
examples you provide illustrate all of the different types of mapping or

For AGROVOC-CAT originally the mapping has been represented in excel,
subsequently it has been represented using OWL. Files are available if
needed. For AGROVOC-NAL the work is currently ongoing.

 3.3. Describe the different types of mapping used, with reference to the
examples given in paragraph 3.2.

SKOS mapping

 3.4. Any additional information, references and/or hyperlinks.