1. AGROVOC -FAO’s multilingual thesaurusas a building block for linked open data<br />Gudrun JOHANNSEN1,Ahsan MORSHED1, SachitRAJBHANDARI1, Armando Stellato 3 ,Thomas Baker2 ,MargheritaSINI1 and Johannes KEIZER1<br />1FAO of the UN, Italy; 2WC3-SKOS working group, 3Universitá di Roma “Tor Vergata”<br />
2. Do we need Thesauri?<br />Yes!And Why:<br />
3. <ul><li>Born as tools to assure consistency in the indexing of library collections
4. Thesauri were based on “terms”, but terms represented already concepts in a non explicit way
5. Hierarchical and associative relationships represented generic ontological domain knowledge
6. Candidate building blocks for the semantic web</li></ul>Thesauri in the past and now<br />
7. The Linked Data Universe: http://www.linkeddata.org<br />4<br />
8. <ul><li>The Semantic Web isn't just about putting data on the web. It is about making links, so that a person or machine can explore the web of data. With linked data, when you have some of it, you can find other, related, data.
9. Like the web of hypertext, the web of data is constructed with documents on the web. However, unlike the web of hypertext, where links are relationships anchors in hypertext documents written in HTML, for data they links between arbitrary things described by RDF,. The URIs identify any kind of object or concept. But for HTML or RDF, the same expectations apply to make the web grow:
10. Use URIs as names for things
11. Use HTTP URIs so that people can look up those names.
12. When someone looks up a URI, provide useful information, using the standards (RDF*, SPARQL)
13. Include links to other URIs. so that they can discover more things.
14. Simple. In fact, though, a surprising amount of data isn't linked in 2006, because of problems with one or more of the steps. This article discusses solutions to these problems, details of implementation, and factors affecting choices about how you publish your data. </li></ul>http://www.w3.org/DesignIssues/LinkedData.html<br />
15. <ul><li>http://www.w3.org/2007/Talks/0221-Bangalore-IH/</li></ul>RDF as a common format for merging data<br />
17. Finding things related to “genes” across databases<br />Source: Joanne Luciano, Mitre, and the W3C HCLS IG<br />
18. Linking DataSets<br /><ul><li>Have you seen Thomson Reuters Open Calais Service? ()
19. Standard Vocabularies can become the glue between different data sets
20. (everything linked through http://aims.fao.org/aos/agrovoc?c_2367#concept)
21. Our goal: OpenAgro!</li></li></ul><li><ul><li>Name/Identy determination in unstructured texts
22. Using Agrovoc as a controlled vocabulary
23. Structured RDF files that can be used to link data
24. Developed by IIT Kanpur for AgroPediaIndica
25. Prototype under testing with excellent results</li></ul>AgroTagger<br />
53. SKOS and SKOS-XL presentation <br /><ul><li>SKOS presentation where there is no need to apply any type of relationship between lexical units.
54. SKOS-XL presentation needs to apply the relationship between lexical units so that it can be understood clearly. This property is compared with OWL inverse property.
55. SKOS-XL , with the need to define labels as resources, as with concepts, schemes and collections. This defines a special type of lexical entity which is assigned a literal chain which can be repeated for various units. So, the prefLabel and altLabel can be distinguished easily in the multi-lingual thesauri .
56. SKOS-XL gives more flexible semantic than SKOS for modeling the vocabularies, specially multi-lingual thesaurus like AGROVOC </li></li></ul><li>The Conceptserver Workbench<br />
57. <ul><li>Is a web-based working environment for managing the AGROVOC Concept Server
58. Facilitate the collaborative editing of multilingual terminology and semantic concept information
59. It includes administration and group management features
60. It includes workflows for maintenance, validation and quality assurance of the data pool
61. The CS is accessible freely to everybody to facilitates collaborative editing </li></ul>The workbench<br />
62. Architecture of the System<br />
63. Concept/Term Management<br />
64. Concept Relationship<br />Can create the concept-concept relationship<br />Inverse relationship is also created automatically<br /><ul><li>Ex: If we create A affect B, then B is affected by A relationship is also created</li></li></ul><li>Concept Image<br /><ul><li>Name of the image with description
65. URL will point to the image which will open in an external
66. Provide the source of the image
67. Can add more translation in different language</li></li></ul><li>Concept Definition<br /><ul><li>Add definition to the selected concept
68. Add translation in different languages
69. Provide the source of the definition
70. Creation and modified date are set automatically</li></li></ul><li>Visualization of concepts and Relationships in the Workbench<br />
71. AGROVOC Web Services<br />
72. The road map<br /><ul><li>The AGROVOC concept scheme in it’s proprietary OWL has been published on June 5, 2010 on version 1.0 of the concept server workbench
73. At the moment a patch to version 1.0 of the workbench is developed to make it possible to export AGROVOC SKOS
74. AGROVOC SKOS will be published as linked data.
75. With version 2.0 of the workbench SKOS will become the native format for AGROVOC</li></li></ul><li>Giving it a try…….<br />A demo version of the AWB: http://188.8.131.52:55234/agrovocdevv10d/ With all functionalities, availabe to users for testing purpose.Latest stable release version 1.0 : (read/write) http://184.108.40.206:55381/agrovocv10i/Latest stable release version 1.0 (Read only): http://220.127.116.11:55481/agrovocv10i/ (Visitors only with only view privilege)<br />
76. <ul><li>Getting UN vocabularies as building blocks for the Linked Data Universe
77. UNBIS thesaurus covers a broad range of international policy and development issues
78. AGROVOC very specialized, but they do overlap partly
80. Promoting together UNBIS Thesaurus and AGROVOC