On Mon, Apr 15, 2013 at 10:40 AM, Dimitris Kontokostas <
[email protected]> wrote:
>
>
> On Sun, Apr 14, 2013 at 12:38 PM, Shivani Poddar <
> [email protected]> wrote:
>
>>
>>
>>
>> On Sat, Apr 13, 2013 at 4:31 PM, Dimitris Kontokostas <
>> [email protected]> wrote:
>>
>>> Hi Shivani,
>>>
>>>
>>> We agree on the aesthetic improvement but we should not put any effort
>>>>> in the graphics design. This will come with the other improvements we/you
>>>>> suggest.
>>>>>
>>>>> Please elaborate on the kind of other improvements you would suggest
>>>> as a part of the project.
>>>>
>>>
>>> The idea is to make the display page better for the end user. We already
>>> provide links in the idea description to other linked data representations
>>> as examples to what could be the end result.
>>> A key point is to localize it and make it work for all language editions
>>> of DBpedia. An interesting addition here would be to fetch data on-the-fly
>>> from other linked sources and enrich the display.
>>> This data may come from other DBpedia language editions and/or
>>> completetly other sources (sameAs links).
>>>
>>
>> Yes, I looked through the links. So, what I understand from the idea is
>> that the final page we have not only contains (say) the English data but
>> also that from the other language resources we have from the same topic.
>> This would involve handling the Linked data too, to prevent redundancy in
>> the final display page.
>>
>
> Please note here that the goal of fetching other data is just to enrich
> the current page and not to fuse / merge sources, this is another GSoC idea
> (i18n data fusion).
> For example you could fetch extra images, types, categories, labels in
> other languages, etc
>
Yes, as the project description describes the new interface should
incorporate all the i18n editions of dbpedia.
>
> About the further tips you asked,
> -> you should also think about what technologies you are going to use to
> code this idea. Could you share your web programming experience?
>
As of now I am well conversant with php, HTML , JavaScript, jquery , Python
(used in web development frameworks mostly).
Having looked up VSP after your mention in some of the previous mails, I
find it to be very close to python and would like to extend my skill set to
maybe implement the required code for this project in VSP (considering that
its integration with the current codebase will be much simpler then.)
I am open to debating on the usage of the respective technologies though.
What would you suggest ?
> -> After you decide that, you could work on the VSP code to get familiar
> with it or look on the other example links we provided. most of them are
> open-source
>
Will do :)
Thanks a lot,
Shivani
>
> Cheers,
> Dimitris
>
>
> --
> Dimitris Kontokostas
> Department of Computer Science, University of Leipzig
> Research Group: http://aksw.org
> Homepage:http://aksw.org/DimitrisKontokostas
>
--
Shivani Poddar,
Bachelors in Computer Sciences and MS in Exact Humanities, Sophomore
International Institute of Information Technology, Hyderabad
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
Dbpedia-gsoc mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dbpedia-gsoc
