Hi Shivani,
Like any PHP/MySQL this code read from your (triple-store) database and
generates an HTML file.
In this case you should read all this data exactly like we do now. Maybe
you will need to re-arrange the order a bit but nothing more.
Fetching external data should be done on the client (html/javascript) to
reduce the page load time.
So my thoughts for this idea are
1) get the data from a backend. The backend can be the current vsp code, a
completely new one or even use SPARQL as a backend (completely
html/javascript app but slower), either of the 3 options are valid
2) display the data we have in our store.
3) start loading/displaying other sources with javascript
The problem with the VSP code is that it works only in Virtuoso and it's
not portable. So, although re-using the code is always a good choice I
would try to make the app as independent as possible from the actual VSP.
That means that most developement should take place in html/javascript
part. So, in case we want to switch backend in the future it will be as
easy as possible
I hope I cleared things a bit :)
Cheers,
Dimitris
On Tue, Apr 16, 2013 at 4:09 AM, Shivani Poddar
<[email protected]>wrote:
>
> Hi Dimitris,
>
> 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
>>>
>>
>>
> As a part of my implementation strategy I think it would be feasible to
> edit the code you directed me at :
>
>
> https://github.com/dbpedia/dbpedia-vad-i18n/blob/master/dbpedia/vsp/description.vsp#L272
> ,
> Here using SPARQL (for the technologies used) I would aim at querying for
> (say) images in the RDF database. These add ons to the current set would
> enrich the user display.
>
>
>
>>
>> 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 :)
>>
>>
> I looked at the VSP code provided , as of now I realize an understanding
> with respect to the reading of various objects via SPARQL and writing it
> onto the http page we are creating here.
>
> Please indicate if I am correct in taking this trail of thought. I would
> eventually like to submit my project proposal along the same lines
> (Ofcourse with numerous iterations to it)
>
> Regards,
> Shivani
>
>>
>>
>> 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
>>
>
>
>
> --
> 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
>
>
--
Dimitris Kontokostas
Department of Computer Science, University of Leipzig
Research Group: http://aksw.org
Homepage:http://aksw.org/DimitrisKontokostas
------------------------------------------------------------------------------
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
