Hi all,
The whole purpose of the Wikidata integration was to use only the needed
data and adjust them to DBpedia (ontology).
http://www.wikidata.org/wiki/Special:EntityData/q1.nt has many triples we
don't need and missing some triples we could add. To do that we can either
built new tools or use the existing DBpedia software stack to extract what
we want and the way we want to.
Maybe in the long run RDF is the way to go but, for the purpose of GSoC I'd
vote for the DBpedia framework. Having external dependencies (Wikidata
deployments, changes) could jeopardize the whole project. Hady will have to
officially start coding in ~20 days and he needs to have a clear plan from
now. I say we can't depend on Wikidata now and Implementing issue #38 can
do only good for the framework.
Regarding the URI scheme we can use either one I don't mind but, if we
change the data maybe we should change the namespace too
Anja should also say her opinion on this, her dual role in this is a plus :)
Cheers,
Dimitris
On Fri, May 31, 2013 at 4:18 PM, Jona Christopher Sahnwaldt <[email protected]
> wrote:
> Hi Hady and everyone,
>
> Wikidata is moving fast. They decided on RDF URIs and started to
> export RDF in several formats. (Anja implemented much of this and told
> me about it a few days ago. Thanks!) Example:
>
> http://www.wikidata.org/wiki/Special:EntityData/q1.nt (Replace .nt by
> .rdf or .json for other formats.)
>
> URIs like http://www.wikidata.org/entity/Q1 cannot be dereferenced
> yet, but I guess they will be in a few days:
> https://gerrit.wikimedia.org/r/#/c/65463/
>
> Andrea used the JSON from the Wikidata XML dumps to get the
> inter-language links:
> https://github.com/dbpedia/extraction-framework/pull/35 But Daniel
> Kinzler (one of the main Wikidata developers) told me that this JSON
> format is just an internal format that we proabably shouldn't use:
> http://lists.wikimedia.org/pipermail/wikidata-l/2013-May/thread.html#2205
> Daniel also said there are better ways to get the inter-language links
> if that is all we need.
>
> I see two main questions for us here:
>
> 1. Should we use DBpedia URIs like http://data.dbpedia.org/resource/Q1
> or Wikidata URIs like http://www.wikidata.org/entity/Q1 ?
> 2. Should we wait for the Wikidata RDF dumps or try extracting data
> from the existing JSON dumps?
>
> I'd say:
>
> 1. use Wikidata URIs
> 2. wait for the RDF dumps. Or more precisely, ask the WIkidata people
> for the latest guesstimates when the dumps may be available. If they
> say it's going to take months, we'll have to consider a different
> solution.
>
> This may also mean that we currently don't need the ability to handle
> different formats in the XML dumps at all - issue #38 may be obsolete.
>
> Besides, I urge everyone involved to subscribe to
> https://lists.wikimedia.org/mailman/listinfo/wikidata-l (and maybe
> https://lists.wikimedia.org/mailman/listinfo/wikidata-tech as well).
>
> Cheers,
> Christopher
>
> On 31 May 2013 09:58, Sebastian Hellmann
> <[email protected]> wrote:
> > Hi Hady,
> > it is ok, if you try to solve problems alone first, but remember:
> > One of your tasks as a GSoC student is to annoy your mentors with
> questions
> > ;). So don't feel sorry.
> > Documentation is suboptimal, so if you are able to improve it wherever
> you
> > find a gap/difficulty, please do so.
> >
> > All the best,
> > Sebastian
> >
> > Am 31.05.2013 09:48, schrieb Hady elsahar:
> >
> > Yes #38 , i will start in the issue by today , it might take some time /
> > Questions for me to understand the whole structure of DBpedia core , the
> old
> > one and of course the new one . so sorry for annoyance in advance :)
> >
> > thanks
> > Regards
> >
> > On Thu, May 30, 2013 at 12:58 PM, Dimitris Kontokostas <
> [email protected]>
> > wrote:
> >>
> >> Hi Hady,
> >>
> >> We agreed with Sebastian to give you the following warm-up task [1].
> >> Completing this will give you a very good overview of the whole
> framework
> >> and the wikidata integration.
> >> We are of course available for help ;)
> >>
> >> Cheers,
> >> Dimitris
> >>
> >> [1] https://github.com/dbpedia/extraction-framework/issues/38
> >>
> >> --
> >> Kontokostas Dimitris
> >
> >
> >
> >
> > --
> > -------------------------------------------------
> > Hady El-Sahar
> > Research Assistant
> > Center of Informatics Sciences | Nile University
> >
> > email : [email protected]
> > Phone : +2-01220887311
> > http://hadyelsahar.me/
> >
> >
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > Get 100% visibility into Java/.NET code with AppDynamics Lite
> > It's a free troubleshooting tool designed for production
> > Get down to code-level detail for bottlenecks, with <2% overhead.
> > Download for free and get started troubleshooting in minutes.
> > http://p.sf.net/sfu/appdyn_d2d_ap2
> >
> >
> >
> > _______________________________________________
> > Dbpedia-developers mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/dbpedia-developers
> >
> >
> >
> > --
> > Dipl. Inf. Sebastian Hellmann
> > Department of Computer Science, University of Leipzig
> > Events: NLP & DBpedia 2013 (http://nlp-dbpedia2013.blogs.aksw.org,
> Deadline:
> > *July 8th*)
> > Venha para a Alemanha como PhD: http://bis.informatik.uni-leipzig.de/csf
> > Projects: http://nlp2rdf.org , http://linguistics.okfn.org ,
> > http://dbpedia.org/Wiktionary , http://dbpedia.org
> > Homepage: http://bis.informatik.uni-leipzig.de/SebastianHellmann
> > Research Group: http://aksw.org
> >
> >
> ------------------------------------------------------------------------------
> > Get 100% visibility into Java/.NET code with AppDynamics Lite
> > It's a free troubleshooting tool designed for production
> > Get down to code-level detail for bottlenecks, with <2% overhead.
> > Download for free and get started troubleshooting in minutes.
> > http://p.sf.net/sfu/appdyn_d2d_ap2
> > _______________________________________________
> > Dbpedia-developers mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/dbpedia-developers
> >
>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite
> It's a free troubleshooting tool designed for production
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap2
> _______________________________________________
> Dbpedia-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dbpedia-developers
>
--
Kontokostas Dimitris
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
_______________________________________________
Dbpedia-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dbpedia-developers
