Menu
▾
▴
Re: [Jonto-users] R: Jeromedl customization: localization of taxonomies, wordnet vocabulary, and indexing properties
|
From: Sebastian K. <seb...@de...> - 2007-12-14 10:00:57
|
Giuseppe, just a short sum up: 1) yes this is the way to do it - just copy the structure for yourself =20= - and please include reference in JOnto_base/src/context.properties. =20 The format is -> full Java path to the Context class =3D name of the =20 Context getting method (singleton implementation) 2) We will need to wait for Matuesz 3) yes, I clearly understand you. I was hoping to do such a thing with =20= Polish a long time ago. I just have never find enough time to proceed. =20= Together with Mateusz we have initiated a research that can be extend =20= to cover this topic [http://library.deri.ie/resource/YuynUqdU]. The =20 idea is to mine the translations based on the co-occurrence of various =20= tags used. That is just one way to handle that - and do some cool =20 research at the same time :) Cheers, S. On 14 Dec 2007, at 09:43, Giuseppe Bux wrote: > Hi Sebastian! > Thank you for your quick answer. > Please find inline my additional comments and questions. > > Cheers, > > Giuseppe > > -----Messaggio originale----- > Da: Sebastian Kruk [mailto:seb...@de...] > Inviato: gioved=C3=AC 13 dicembre 2007 23.55 > A: Giuseppe Bux > Cc: Mariusz Cygan; Devel JeromeDL; jon...@li...; Mateusz =20= > Kaczmarek; Maciej D=C4=85browski; mar...@li... > Oggetto: Re: Jeromedl customization: localization of taxonomies, =20 > wordnet vocabulary, and indexing properties > > Giuseppe, > > a quick answer to your questions (although might not be complete): > > 1) JeromeDL uses JOnto project [http://sf.net/projects/jonto] (yet > another from my Corrib cluster) to handle controlled vocabularies. > Hence to deliver new taxonomy you just need to have it in a properties > file or RDF file (e.g. SKOS compliant), and you simply need to > implement two interfaces in java and package it. The whole process > does not take much effort. @Mateusz - could you provide a step by step > description on a wiki? > > Well! I did the svn checkout of the project, so I have available the =20= > various jonto projects on controlled vocabularies. > For each *_vocabulary project I view a common src module structure, =20= > where are included the *.ntriples and *.properties files, as well =20 > the *_Context.java and the *_Parser.java. Are these the properties/=20 > rdf files and the two java interfaces you mention above? So, if it =20 > is right, should I replicate a similar project for my own =20 > vocabulary? A step by step description of the process, by @Mateusz, =20= > could effectively help me. > > 2) with wordnet it is more tricky - JOnto uses JWNL library to handle > WordNet dictionary. I was always hoping to be able to use other > national dictionaries - but we never had time to test it. However, the > infrastructure is there - and what I would suggest to do is to split > current wordnet module into an abstract/base dictionary module and > implementation modules, e.g., for wordnet. Depending on how much time > Mateusz can contribute to the either we can do that or your team. > > An initial contribution from Matzeus could be the provision of some =20= > guidelines for splitting the wordnet module. > > 3) Answer to this question I leave to Mariusz, Maciej, and MarcOnt > team :) > > Hope it was useful, > > Yes, it was useful enough! > However my issue about metadata localization would extend the =20 > problem of the simple addition of new user dictionaries, towards a =20 > more large problem of managing simultaneously, as synonyms, words =20 > with the same concept but in different language (ex. the English =20 > word "apple", and the correspondent Italian word "mela"). I think =20 > this is one of the main problems of effective social inter-language =20= > indexing/bookmarking in shared digital libraries. > > Giuseppe > > Cheers, > > S. > > > On 13 Dec 2007, at 16:50, Giuseppe Bux wrote: > >> Hi Sebastian, Mariusz! >> I would start customization of my local instance of Jeromedl, by >> localizing taxonomies, wordnet vocabulary, and indexing properties. >> Localization will be targeted to an Italian audience. Here in the >> following my envisaged approach and questions about. Please give me >> your kind comments and suggestions. >> >> 1) Localizing taxonomies: localization should be done by >> enriching some selected current taxonomy dictionary (ex. DDC, Dmoz, >> ACM, =E2=80=A6) with synonyms in local language (i.e. in Italian). = This in >> order to manage domain indexing and related resource searching, by >> using either English or local (i.e. Italian) terms defined in each >> selected dictionary. To do that, I would follow steps should be as >> follows: >> >> a. To extract the RDF description of each dictionary from the >> Sesame-Jonto repository, by a query template as follows: >> Select distinct * >> from {uri} p {value} >> where p=3D <http://www.w3.org/2004/02/skos/core#prefLabel> AND uri >> like "*http://www.corrib.org/jonto/acm/*" >> >> obviously, for each query, the =E2=80=9Clike=E2=80=9D value of the = =E2=80=9Cwhere=E2=80=9D >> construct must be adapted to the uri of the given taxonomy. >> >> I have some troubles with the sesame response, i.e.: the query >> response in html format gives the expected sesame tabular form, >> while the response in rdf format gives me a plain list such as: >> uri p value uri p value General Literature uri p value General =20 >> =E2=80=A6=E2=80=A6.. >> >> I need instead a rdf/XML description: How can obain it? Could you, >> eventually, provide me with the download site of RDF/XML >> descriptions of the dictionaries stored in the sesame-Jonto >> repository? >> >> b. To initiate a dictionary customization project in an RDF >> editor, such as Marcont portal or Prot=C3=A8g=C3=A8, by instantiating = it with >> the extracted rdf description of the given dictionary and with the >> definition of synonyms of its terms, in local language. >> c. To update the sesame-jonto repository with the new rdf >> description of the given dictionary. >> >> The =E2=80=9Cmodify=E2=80=9D actions of sesame should support the = updating =20 >> process. >> >> 2) Localizing wordnet vocabulary: it should be done simply by >> replacing the current wordnet English vocabulary with a >> correspondent commercial bi-language wordnet vocabulary (in my >> case: Ital-Wordnet): does jeromedl implementation gives specific >> constraints to do that? >> >> 3) Localizing indexing properties: this should be done by >> predefining additional marcont properties and make them available, >> in the resource uploading form, for selection and instantiation >> as xmarcont properties. Really a best approach should be to manage >> the original marcont ontology for its localization as above for the >> dictionaries: what about this topic in the Marcont project? >> >> Not more to describe. >> >> Looking for your kind comments and suggestions, >> >> Cheers, >> Giuseppe >> >> >> >> >> > > -------------------------------------------- > -- Sebastian Ryszard Kruk > -- Lead Researcher, Project Manager > -- Semantic Infrastructure Lab, eLearning Cluster > -- Digital Enterprise Research Institute=20 > -- National University of Ireland, Galway=20 > -- mailto: seb...@de... > -- GG: 335067, Jabber: s_...@ch... > -- Skype: sebastiankruk > -- WWW: http://www.sebastiankruk.com/=20 > -- mobile (IRL): +353 85 7126591 > -- VoIP (PL): +48 52 5110114 > -------------------------------------------- > > -------------------------------------------- -- Sebastian Ryszard Kruk -- Lead Researcher, Project Manager -- Semantic Infrastructure Lab, eLearning Cluster -- Digital Enterprise Research Institute=20 -- National University of Ireland, Galway=20 -- mailto: seb...@de... -- GG: 335067, Jabber: s_...@ch... -- Skype: sebastiankruk -- WWW: http://www.sebastiankruk.com/=20 -- mobile (IRL): +353 85 7126591 -- VoIP (PL): +48 52 5110114 -------------------------------------------- |