Hi Hady,
On Wed, May 1, 2013 at 11:23 PM, Hady elsahar <[email protected]> wrote:
> Hello Dimitris,
>
> 1- considering you comment
>
> In phase 1.3 we are not sure if we will support it in the end. DBpedia
>> doesn't store any claims for facts now (sources, refs, links) so don't put
>> much effort in this from now
>
>
> do you mean that the most important for Dbpedia now is are *labels *,
> *abstracts
> *, *aliases** *& *Interwiki link*s only ?
> and the propagating live changes from wikidata to DBpedia for them only ?
>
Too many reviews and I got confused :) I didn't mean the actual claims
here, I was referring to the claim sources only. Hope this is clear now
> i see if we managed to produce a RDF version of WikiData before WikiData
> does would be very potential addition to DBpedia
> wouldn't that seem to make that part a main objective from the project ?
>
> the other alternative is waiting for WikiData to provide it's RDF version
> utilize it ( we can ask them if it's too soon no need for writing our code)
> and i guess then we wouldn't need to Parse json in WikiData Dumbs. we can
> just map their RDF to our ontology
>
Providing an RDF dump before Wikidata would be cool ;) but our main
objective is to get this right.
We have all the code available to do this with the DBpedia framework so,
waiting for the WikiData RDF dumps puts us back.
We neither know how WikiData will structure their RDF data nor we have any
ready to use tool for this conversion
>
> 2- the pull request[1] submitted by Andrea , i got that he used an Lift
> Json Parser for parsing dumbs and mapping language links of WikiData
> objects to DBpedia resources.
>
> then i saw Christopher commenting
>
> JsonWikiParser - the current InterLanguageLinksExtractor generates quads
>> for all languages, there's no special treatment for English. When we
>> extract links from Wikidata, we should generate triples stating that this
>> Wikidata item links to these Wikipedia items. Something like this:
>> <http://data.dbpedia.org/resource/Q1234> owl:sameAs <
>> http://de.dbpedia.org/resource/Foo>
>> <http://data.dbpedia.org/resource/Q1234> owl:sameAs <
>> http://fr.dbpedia.org/resource/Bar>
>>
>
> i got a little confused , but so i wanted to ask if these triples are
> already supplied in the pull request or not
>
>
> 3- i found Christopher adding new diagrams[2] for refactoring the core and
> a new issue[3] is added considering this , we would go into the
> implementation of this new core in our project ? or would our project
> mainly concentrate on the live issues ?
>
This is supposed to be a warm-up task for the student who implements this
idea. Note that if this refactoring is done, 1.1 & 1.2 will be a couple of
full work days. Also, what Christopher is stating here is in fact the
parsing of interwiki links (1.1.5 of your proposal). Adapting this after
#35 is a minor change
Any more questions?
Cheers,
Dimitris
>
>
> thanks
> regards
>
>
>
> [1] - https://github.com/dbpedia/extraction-framework/pull/35
> [2] -
> https://github.com/dbpedia/extraction-framework/pull/35#issuecomment-16187074
> [3] - https://github.com/dbpedia/extraction-framework/issues/38
> -------------------------------------------------
> Hady El-Sahar
> Research Assistant
> Center of Informatics Sciences | Nile
> University<http://nileuniversity.edu.eg/>
>
> email : [email protected]
> Phone : +2-01220887311
> http://hadyelsahar.me/
>
> <http://www.linkedin.com/in/hadyelsahar>
>
>
--
Kontokostas Dimitris
------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
Dbpedia-gsoc mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dbpedia-gsoc
