You can subscribe to this list here.
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2013 |
Jan
(1) |
Feb
(13) |
Mar
(24) |
Apr
(1) |
May
|
Jun
(2) |
Jul
(4) |
Aug
(2) |
Sep
(6) |
Oct
(1) |
Nov
|
Dec
|
2014 |
Jan
|
Feb
(10) |
Mar
(12) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
(2) |
Dec
(4) |
2015 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2016 |
Jan
|
Feb
|
Mar
(8) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
(3) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
2021 |
Jan
|
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
From: Sebastian H. <hel...@in...> - 2013-03-02 22:27:28
|
Hi Roland, IIRC bif:intersects is a feature of the commercial version. You can't simply enable it without paying. It is a geo index. Alternatively, you need to rewrite the query to filter ( int (?lat) > radius && int(?lat) < radius) Sebastian Roland Cornelissen <met...@gm...> schrieb: >Hi, >I noticed that some nice geo functions don't work at >nl.dbpedia.org/sparql, they do work at dbpedia.org/sparql. >This one f.e. : (get all universities near Enschede) > >SELECT ?m ?r ?p WHERE > { > ?m geo:geometry ?geo . > ?p ?r ?m . > ?p rdf:type dbpedia-owl:University . > FILTER (bif:st_intersects (?geo, bif:st_point (6.8951, 52.2197), 10)) > } > >Works on dbpedia.org/sparql but not on nl.dbpedia/sparql. >Could these function be enabled, that would be great. > >Thanks, >Roland > >------------------------------------------------------------------------------ >Everyone hates slow websites. So do we. >Make your web apps faster with AppDynamics >Download AppDynamics Lite for free today: >http://p.sf.net/sfu/appdyn_d2d_feb >_______________________________________________ >Dbpedia-dutch mailing list >Dbp...@li... >https://lists.sourceforge.net/lists/listinfo/dbpedia-dutch -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet. |
From: Roland C. <met...@gm...> - 2013-03-02 21:43:11
|
Hi, I noticed that some nice geo functions don't work at nl.dbpedia.org/sparql, they do work at dbpedia.org/sparql. This one f.e. : (get all universities near Enschede) SELECT ?m ?r ?p WHERE { ?m geo:geometry ?geo . ?p ?r ?m . ?p rdf:type dbpedia-owl:University . FILTER (bif:st_intersects (?geo, bif:st_point (6.8951, 52.2197), 10)) } Works on dbpedia.org/sparql but not on nl.dbpedia/sparql. Could these function be enabled, that would be great. Thanks, Roland |
From: Gerard K. <Ger...@bi...> - 2013-03-02 02:13:03
|
OK, I will do that. Thanks! But then, it seems to be wise to repeat the mappings to be done in the 'otherwise' clause in the condition with the other criteria ('templateProperty = xtp4000'). Because, if fired, it will never arrive at the 'otherwise' anymore. Regards, Gerard ________________________________ Van: Gerard Kuys [Ger...@bi...] Verzonden: donderdag 28 februari 2013 22:40 To: Dimitris Kontokostas Cc: dbp...@li... Onderwerp: Re: [Dbpedia-dutch] Conditional mapping Thank you, Dimitris, this documentation really is enlightening. One last question, however. In the example I include below, there is a condition statement with a 'case' clause. As is natural, this ends with an 'otherwise' clause. Will the program when having processed this 'otherwise' clause leave the entire condition section, or can I add another condition, one that is not dependent on the condition (as below: 'templateProperty = tpx10') to be fulfilled for the case...otherwise series? I mean this: {{ConditionalMapping | cases = {{Condition | templateProperty = tpx10 | operator = contains | value = 'ABC' | mapping = {{TemplateMapping | mapToClass = Class1 }} }} {{Condition | templateProperty = tpx10 | operator = contains | value = 'DEF' | mapping = {{TemplateMapping | mapToClass = Class2 }} }} {{Condition | operator = otherwise | mapping = {{TemplateMapping | mapToClass =Class3 }} }} {{Condition | templateProperty = xtp4000 | operator = isSet | mapping = {{ConstantMapping | ontologyProperty = opx300 | value = 'GHI' }} }} Would this work? Regards, Gerard ________________________________ Van: Dimitris Kontokostas [kon...@in...] Verzonden: donderdag 28 februari 2013 21:48 To: Gerard Kuys Cc: dbp...@li... Onderwerp: Re: [Dbpedia-dutch] Conditional mapping Hi Gerard, Although so-and-so is kind of ambiguous, for field existence you can use the 'isSet' operator Complete documentation can be found here http://mappings.dbpedia.org/index.php/Template:Condition http://mappings.dbpedia.org/index.php/Template:ConditionalMapping and examples here: http://mappings.dbpedia.org/index.php?title=Special%3ASearch&search=isset&go=Go http://mappings.dbpedia.org/index.php/Special:WhatLinksHere/Template:Condition Best, Dimitris On Thu, Feb 28, 2013 at 9:38 AM, Gerard Kuys <Ger...@bi...<mailto:Ger...@bi...>> wrote: Hi all, I looked in the document on the DBpedia mapping language, but didn't find what I looked for: How can I, in a conditional mapping, express that the condition only fires if for field so-and-so there is a (or no) value? Thank you for answering! Regards, Gerard Kuys ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Dbpedia-dutch mailing list Dbp...@li...<mailto:Dbp...@li...> https://lists.sourceforge.net/lists/listinfo/dbpedia-dutch -- Dimitris Kontokostas Department of Computer Science, University of Leipzig Research Group: http://aksw.org Homepage:http://aksw.org/DimitrisKontokostas |
From: Dimitris K. <kon...@in...> - 2013-03-01 21:05:25
|
Hi all, FYI, Sorry in advance for any inconvenience but, DBpedia Live (for Dutch) will be down for the next couple of days due to some maintenance / upgrade tasks. -- Dimitris Kontokostas Department of Computer Science, University of Leipzig Research Group: http://aksw.org Homepage:http://aksw.org/DimitrisKontokostas |
From: Dimitris K. <kon...@in...> - 2013-03-01 20:10:25
|
Hi Gerard On Fri, Mar 1, 2013 at 3:36 PM, Gerard Kuys <Ger...@bi...>wrote: > Hi Dimitris, > > The problem is about Mills and the mapping of Infobox_Molen. However, I > feel that this problem is far more general than just Mills. > > I want the mapping to do two things: > > 1. Type to the right Class. This worked quite well, except for the mapping > to WindMotors (but this is, I think, because of an owl:sameAs relation to > SustainableTechnologies, which is a totally different kind of problem. For > the rest, my (and yours!) result list of Mill objects was approved by the > Wikimedia specialist on Dutch mills, which is not the least of compliments). > It is good to hear that :) > > 2. If there is no monumentStatus property but indeed there is a > codeNationalMonument, then we can safely assume that the monumentStatus > property should be [[Rijksmonument]] for every mill that has a > codeNationalMonument and currently a blank for the monumentStatus. I would > like to do that in the mapping, but a CONSTRUCT statement might be a viable > aternative as well. > > These are two completely different conditions with different criteria, so > it is hard to combine them in the same list of conditional mappings, as you > will agree. > This is indeed very complex for the mappings. If you thing that this type of information is important we can try to extend the conditional mapping syntax, otherwise a construct would do Best, Dimitris > Regards, > > Gerard > ------------------------------ > *Van:* Dimitris Kontokostas [kon...@in...] > *Verzonden:* vrijdag 1 maart 2013 13:13 > > *To:* Gerard Kuys > *Cc:* dbp...@li... > *Onderwerp:* Re: [Dbpedia-dutch] Conditional mapping > > Hi Gerard, > > Unfortunately the condition template is very simple and you cannot add > logical expressions (at least for now). > The problem you refer to, that xtp4000 property will supersede the > otherwise rule, is very template specific and, > if you place that rule then I guess you want it to execute it if it > succeeds and so you shouldn't care what check comes next. > > If you want something different, then maybe you could share the high > level condition condition you want to achieve and the template / mapping > you refer to. > > Best, > Dimitris > > > On Fri, Mar 1, 2013 at 11:10 AM, Gerard Kuys <Ger...@bi...>wrote: > >> Hi Dimitris, >> >> Or, as a variety of the two-condition-list option: >> >> {{Condition >> | (templateProperty = type >> | operator = equals >> | value = River) && >> | (templateProperty = name >> | operator = contains >> | value = "River") >> | mapping = >> {{TemplateMapping >> | mapToClass = River >> }} >> }} >> >> Would this &&-approach work? (never mind the soundness of the example) >> >> Regards, >> >> Gerard >> >> >> ------------------------------ >> *Van:* Dimitris Kontokostas [kon...@in...] >> >> *Verzonden:* vrijdag 1 maart 2013 8:37 >> *To:* Gerard Kuys >> *Cc:* dbp...@li... >> *Onderwerp:* Re: [Dbpedia-dutch] Conditional mapping >> >> Although it will not throw an error I don't think it will work as >> expected because otherwise will supersede your last statement. >> Try to place the last condition just before the otherwise and it should >> be fine >> >> Best, >> Dimitris >> >> >> On Thu, Feb 28, 2013 at 11:40 PM, Gerard Kuys <Ger...@bi... >> > wrote: >> >>> Thank you, Dimitris, this documentation really is enlightening. One >>> last question, however. In the example I include below, there is a >>> condition statement with a 'case' clause. As is natural, this ends with an >>> 'otherwise' clause. Will the program when having processed this 'otherwise' >>> clause leave the entire condition section, or can I add another condition, >>> one that is not dependent on the condition (as below: 'templateProperty = >>> tpx10') to be fulfilled for the case...otherwise series? >>> >>> I mean this: >>> >>> {{ConditionalMapping >>> | cases = >>> {{Condition >>> | templateProperty = tpx10 >>> | operator = contains >>> | value = 'ABC' >>> | mapping = {{TemplateMapping >>> | mapToClass = Class1 >>> }} >>> }} >>> >>> {{Condition >>> | templateProperty = tpx10 >>> | operator = contains >>> | value = 'DEF' >>> | mapping = {{TemplateMapping >>> | mapToClass = Class2 >>> }} >>> }} >>> >>> {{Condition >>> | operator = otherwise >>> | mapping = {{TemplateMapping >>> | mapToClass =Class3 >>> }} >>> }} >>> >>> {{Condition >>> | templateProperty = xtp4000 >>> | operator = isSet >>> | mapping = {{ConstantMapping >>> | ontologyProperty = opx300 | value = 'GHI' >>> }} >>> }} >>> >>> Would this work? >>> >>> Regards, >>> >>> Gerard >>> ------------------------------ >>> *Van:* Dimitris Kontokostas [kon...@in...] >>> *Verzonden:* donderdag 28 februari 2013 21:48 >>> *To:* Gerard Kuys >>> *Cc:* dbp...@li... >>> *Onderwerp:* Re: [Dbpedia-dutch] Conditional mapping >>> >>> Hi Gerard, >>> >>> Although so-and-so is kind of ambiguous, for field existence you can >>> use the '*isSet' operator >>> >>> Complete documentation can be found here >>> http://mappings.dbpedia.org/index.php/Template:Condition >>> http://mappings.dbpedia.org/index.php/Template:ConditionalMapping >>> >>> and examples here: >>> >>> http://mappings.dbpedia.org/index.php?title=Special%3ASearch&search=isset&go=Go >>> >>> http://mappings.dbpedia.org/index.php/Special:WhatLinksHere/Template:Condition >>> >>> * >>> *Best, >>> Dimitris >>> * >>> * >>> >>> * >>> >>> >>> On Thu, Feb 28, 2013 at 9:38 AM, Gerard Kuys <Ger...@bi... >>> > wrote: >>> >>>> Hi all, >>>> >>>> I looked in the document on the DBpedia mapping language, but didn't >>>> find what I looked for: >>>> >>>> How can I, in a conditional mapping, express that the condition only >>>> fires if for field so-and-so there is a (or no) value? >>>> >>>> Thank you for answering! >>>> >>>> Regards, >>>> >>>> Gerard Kuys >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Everyone hates slow websites. So do we. >>>> Make your web apps faster with AppDynamics >>>> Download AppDynamics Lite for free today: >>>> http://p.sf.net/sfu/appdyn_d2d_feb >>>> _______________________________________________ >>>> Dbpedia-dutch mailing list >>>> Dbp...@li... >>>> https://lists.sourceforge.net/lists/listinfo/dbpedia-dutch >>>> >>>> >>> >>> >>> -- >>> Dimitris Kontokostas >>> Department of Computer Science, University of Leipzig >>> Research Group: http://aksw.org >>> Homepage:http://aksw.org/DimitrisKontokostas >>> >> >> >> >> -- >> Dimitris Kontokostas >> Department of Computer Science, University of Leipzig >> Research Group: http://aksw.org >> Homepage:http://aksw.org/DimitrisKontokostas >> > > > > -- > Dimitris Kontokostas > Department of Computer Science, University of Leipzig > Research Group: http://aksw.org > Homepage:http://aksw.org/DimitrisKontokostas > -- Dimitris Kontokostas Department of Computer Science, University of Leipzig Research Group: http://aksw.org Homepage:http://aksw.org/DimitrisKontokostas |
From: Gerard K. <Ger...@bi...> - 2013-03-01 19:23:08
|
Hi Dimitris, On further reflection, wouldn't it be better if we had two condition lists instead of one? One dependent on the criteria 'tpx10' and one dependent on the criteria 'xtp4000'? If we unite different criteria in a single case list, in the end it will be very cumbersome, having to repeat everything that must be there also in the case one of the criteria is not met. Or will the last condition list with one criteria supersede the previous one with another criteria? Regards, Gerard ________________________________ Van: Dimitris Kontokostas [kon...@in...] Verzonden: vrijdag 1 maart 2013 8:37 To: Gerard Kuys Cc: dbp...@li... Onderwerp: Re: [Dbpedia-dutch] Conditional mapping Although it will not throw an error I don't think it will work as expected because otherwise will supersede your last statement. Try to place the last condition just before the otherwise and it should be fine Best, Dimitris On Thu, Feb 28, 2013 at 11:40 PM, Gerard Kuys <Ger...@bi...<mailto:Ger...@bi...>> wrote: Thank you, Dimitris, this documentation really is enlightening. One last question, however. In the example I include below, there is a condition statement with a 'case' clause. As is natural, this ends with an 'otherwise' clause. Will the program when having processed this 'otherwise' clause leave the entire condition section, or can I add another condition, one that is not dependent on the condition (as below: 'templateProperty = tpx10') to be fulfilled for the case...otherwise series? I mean this: {{ConditionalMapping | cases = {{Condition | templateProperty = tpx10 | operator = contains | value = 'ABC' | mapping = {{TemplateMapping | mapToClass = Class1 }} }} {{Condition | templateProperty = tpx10 | operator = contains | value = 'DEF' | mapping = {{TemplateMapping | mapToClass = Class2 }} }} {{Condition | operator = otherwise | mapping = {{TemplateMapping | mapToClass =Class3 }} }} {{Condition | templateProperty = xtp4000 | operator = isSet | mapping = {{ConstantMapping | ontologyProperty = opx300 | value = 'GHI' }} }} Would this work? Regards, Gerard ________________________________ Van: Dimitris Kontokostas [kon...@in...<mailto:kon...@in...>] Verzonden: donderdag 28 februari 2013 21:48 To: Gerard Kuys Cc: dbp...@li...<mailto:dbp...@li...> Onderwerp: Re: [Dbpedia-dutch] Conditional mapping Hi Gerard, Although so-and-so is kind of ambiguous, for field existence you can use the 'isSet' operator Complete documentation can be found here http://mappings.dbpedia.org/index.php/Template:Condition http://mappings.dbpedia.org/index.php/Template:ConditionalMapping and examples here: http://mappings.dbpedia.org/index.php?title=Special%3ASearch&search=isset&go=Go http://mappings.dbpedia.org/index.php/Special:WhatLinksHere/Template:Condition Best, Dimitris On Thu, Feb 28, 2013 at 9:38 AM, Gerard Kuys <Ger...@bi...<mailto:Ger...@bi...>> wrote: Hi all, I looked in the document on the DBpedia mapping language, but didn't find what I looked for: How can I, in a conditional mapping, express that the condition only fires if for field so-and-so there is a (or no) value? Thank you for answering! Regards, Gerard Kuys ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Dbpedia-dutch mailing list Dbp...@li...<mailto:Dbp...@li...> https://lists.sourceforge.net/lists/listinfo/dbpedia-dutch -- Dimitris Kontokostas Department of Computer Science, University of Leipzig Research Group: http://aksw.org Homepage:http://aksw.org/DimitrisKontokostas -- Dimitris Kontokostas Department of Computer Science, University of Leipzig Research Group: http://aksw.org Homepage:http://aksw.org/DimitrisKontokostas |
From: Dimitris K. <kon...@in...> - 2013-03-01 19:20:28
|
Hi Gerard, Unfortunately the condition template is very simple and you cannot add logical expressions (at least for now). The problem you refer to, that xtp4000 property will supersede the otherwise rule, is very template specific and, if you place that rule then I guess you want it to execute it if it succeeds and so you shouldn't care what check comes next. If you want something different, then maybe you could share the high level condition condition you want to achieve and the template / mapping you refer to. Best, Dimitris On Fri, Mar 1, 2013 at 11:10 AM, Gerard Kuys <Ger...@bi...>wrote: > Hi Dimitris, > > Or, as a variety of the two-condition-list option: > > {{Condition > | (templateProperty = type > | operator = equals > | value = River) && > | (templateProperty = name > | operator = contains > | value = "River") > | mapping = > {{TemplateMapping > | mapToClass = River > }} > }} > > Would this &&-approach work? (never mind the soundness of the example) > > Regards, > > Gerard > > > ------------------------------ > *Van:* Dimitris Kontokostas [kon...@in...] > > *Verzonden:* vrijdag 1 maart 2013 8:37 > *To:* Gerard Kuys > *Cc:* dbp...@li... > *Onderwerp:* Re: [Dbpedia-dutch] Conditional mapping > > Although it will not throw an error I don't think it will work as > expected because otherwise will supersede your last statement. > Try to place the last condition just before the otherwise and it should be > fine > > Best, > Dimitris > > > On Thu, Feb 28, 2013 at 11:40 PM, Gerard Kuys <Ger...@bi...>wrote: > >> Thank you, Dimitris, this documentation really is enlightening. One >> last question, however. In the example I include below, there is a >> condition statement with a 'case' clause. As is natural, this ends with an >> 'otherwise' clause. Will the program when having processed this 'otherwise' >> clause leave the entire condition section, or can I add another condition, >> one that is not dependent on the condition (as below: 'templateProperty = >> tpx10') to be fulfilled for the case...otherwise series? >> >> I mean this: >> >> {{ConditionalMapping >> | cases = >> {{Condition >> | templateProperty = tpx10 >> | operator = contains >> | value = 'ABC' >> | mapping = {{TemplateMapping >> | mapToClass = Class1 >> }} >> }} >> >> {{Condition >> | templateProperty = tpx10 >> | operator = contains >> | value = 'DEF' >> | mapping = {{TemplateMapping >> | mapToClass = Class2 >> }} >> }} >> >> {{Condition >> | operator = otherwise >> | mapping = {{TemplateMapping >> | mapToClass =Class3 >> }} >> }} >> >> {{Condition >> | templateProperty = xtp4000 >> | operator = isSet >> | mapping = {{ConstantMapping >> | ontologyProperty = opx300 | value = 'GHI' >> }} >> }} >> >> Would this work? >> >> Regards, >> >> Gerard >> ------------------------------ >> *Van:* Dimitris Kontokostas [kon...@in...] >> *Verzonden:* donderdag 28 februari 2013 21:48 >> *To:* Gerard Kuys >> *Cc:* dbp...@li... >> *Onderwerp:* Re: [Dbpedia-dutch] Conditional mapping >> >> Hi Gerard, >> >> Although so-and-so is kind of ambiguous, for field existence you can use >> the '*isSet' operator >> >> Complete documentation can be found here >> http://mappings.dbpedia.org/index.php/Template:Condition >> http://mappings.dbpedia.org/index.php/Template:ConditionalMapping >> >> and examples here: >> >> http://mappings.dbpedia.org/index.php?title=Special%3ASearch&search=isset&go=Go >> >> http://mappings.dbpedia.org/index.php/Special:WhatLinksHere/Template:Condition >> >> * >> *Best, >> Dimitris >> * >> * >> >> * >> >> >> On Thu, Feb 28, 2013 at 9:38 AM, Gerard Kuys <Ger...@bi...>wrote: >> >>> Hi all, >>> >>> I looked in the document on the DBpedia mapping language, but didn't >>> find what I looked for: >>> >>> How can I, in a conditional mapping, express that the condition only >>> fires if for field so-and-so there is a (or no) value? >>> >>> Thank you for answering! >>> >>> Regards, >>> >>> Gerard Kuys >>> >>> >>> ------------------------------------------------------------------------------ >>> Everyone hates slow websites. So do we. >>> Make your web apps faster with AppDynamics >>> Download AppDynamics Lite for free today: >>> http://p.sf.net/sfu/appdyn_d2d_feb >>> _______________________________________________ >>> Dbpedia-dutch mailing list >>> Dbp...@li... >>> https://lists.sourceforge.net/lists/listinfo/dbpedia-dutch >>> >>> >> >> >> -- >> Dimitris Kontokostas >> Department of Computer Science, University of Leipzig >> Research Group: http://aksw.org >> Homepage:http://aksw.org/DimitrisKontokostas >> > > > > -- > Dimitris Kontokostas > Department of Computer Science, University of Leipzig > Research Group: http://aksw.org > Homepage:http://aksw.org/DimitrisKontokostas > -- Dimitris Kontokostas Department of Computer Science, University of Leipzig Research Group: http://aksw.org Homepage:http://aksw.org/DimitrisKontokostas |
From: Gerard K. <Ger...@bi...> - 2013-03-01 18:53:10
|
Hi Dimitris, The problem is about Mills and the mapping of Infobox_Molen. However, I feel that this problem is far more general than just Mills. I want the mapping to do two things: 1. Type to the right Class. This worked quite well, except for the mapping to WindMotors (but this is, I think, because of an owl:sameAs relation to SustainableTechnologies, which is a totally different kind of problem. For the rest, my (and yours!) result list of Mill objects was approved by the Wikimedia specialist on Dutch mills, which is not the least of compliments). 2. If there is no monumentStatus property but indeed there is a codeNationalMonument, then we can safely assume that the monumentStatus property should be [[Rijksmonument]] for every mill that has a codeNationalMonument and currently a blank for the monumentStatus. I would like to do that in the mapping, but a CONSTRUCT statement might be a viable aternative as well. These are two completely different conditions with different criteria, so it is hard to combine them in the same list of conditional mappings, as you will agree. Regards, Gerard ________________________________ Van: Dimitris Kontokostas [kon...@in...] Verzonden: vrijdag 1 maart 2013 13:13 To: Gerard Kuys Cc: dbp...@li... Onderwerp: Re: [Dbpedia-dutch] Conditional mapping Hi Gerard, Unfortunately the condition template is very simple and you cannot add logical expressions (at least for now). The problem you refer to, that xtp4000 property will supersede the otherwise rule, is very template specific and, if you place that rule then I guess you want it to execute it if it succeeds and so you shouldn't care what check comes next. If you want something different, then maybe you could share the high level condition condition you want to achieve and the template / mapping you refer to. Best, Dimitris On Fri, Mar 1, 2013 at 11:10 AM, Gerard Kuys <Ger...@bi...<mailto:Ger...@bi...>> wrote: Hi Dimitris, Or, as a variety of the two-condition-list option: {{Condition | (templateProperty = type | operator = equals | value = River) && | (templateProperty = name | operator = contains | value = "River") | mapping = {{TemplateMapping | mapToClass = River }} }} Would this &&-approach work? (never mind the soundness of the example) Regards, Gerard ________________________________ Van: Dimitris Kontokostas [kon...@in...<mailto:kon...@in...>] Verzonden: vrijdag 1 maart 2013 8:37 To: Gerard Kuys Cc: dbp...@li...<mailto:dbp...@li...> Onderwerp: Re: [Dbpedia-dutch] Conditional mapping Although it will not throw an error I don't think it will work as expected because otherwise will supersede your last statement. Try to place the last condition just before the otherwise and it should be fine Best, Dimitris On Thu, Feb 28, 2013 at 11:40 PM, Gerard Kuys <Ger...@bi...<mailto:Ger...@bi...>> wrote: Thank you, Dimitris, this documentation really is enlightening. One last question, however. In the example I include below, there is a condition statement with a 'case' clause. As is natural, this ends with an 'otherwise' clause. Will the program when having processed this 'otherwise' clause leave the entire condition section, or can I add another condition, one that is not dependent on the condition (as below: 'templateProperty = tpx10') to be fulfilled for the case...otherwise series? I mean this: {{ConditionalMapping | cases = {{Condition | templateProperty = tpx10 | operator = contains | value = 'ABC' | mapping = {{TemplateMapping | mapToClass = Class1 }} }} {{Condition | templateProperty = tpx10 | operator = contains | value = 'DEF' | mapping = {{TemplateMapping | mapToClass = Class2 }} }} {{Condition | operator = otherwise | mapping = {{TemplateMapping | mapToClass =Class3 }} }} {{Condition | templateProperty = xtp4000 | operator = isSet | mapping = {{ConstantMapping | ontologyProperty = opx300 | value = 'GHI' }} }} Would this work? Regards, Gerard ________________________________ Van: Dimitris Kontokostas [kon...@in...<mailto:kon...@in...>] Verzonden: donderdag 28 februari 2013 21:48 To: Gerard Kuys Cc: dbp...@li...<mailto:dbp...@li...> Onderwerp: Re: [Dbpedia-dutch] Conditional mapping Hi Gerard, Although so-and-so is kind of ambiguous, for field existence you can use the 'isSet' operator Complete documentation can be found here http://mappings.dbpedia.org/index.php/Template:Condition http://mappings.dbpedia.org/index.php/Template:ConditionalMapping and examples here: http://mappings.dbpedia.org/index.php?title=Special%3ASearch&search=isset&go=Go http://mappings.dbpedia.org/index.php/Special:WhatLinksHere/Template:Condition Best, Dimitris On Thu, Feb 28, 2013 at 9:38 AM, Gerard Kuys <Ger...@bi...<mailto:Ger...@bi...>> wrote: Hi all, I looked in the document on the DBpedia mapping language, but didn't find what I looked for: How can I, in a conditional mapping, express that the condition only fires if for field so-and-so there is a (or no) value? Thank you for answering! Regards, Gerard Kuys ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Dbpedia-dutch mailing list Dbp...@li...<mailto:Dbp...@li...> https://lists.sourceforge.net/lists/listinfo/dbpedia-dutch -- Dimitris Kontokostas Department of Computer Science, University of Leipzig Research Group: http://aksw.org Homepage:http://aksw.org/DimitrisKontokostas -- Dimitris Kontokostas Department of Computer Science, University of Leipzig Research Group: http://aksw.org Homepage:http://aksw.org/DimitrisKontokostas -- Dimitris Kontokostas Department of Computer Science, University of Leipzig Research Group: http://aksw.org Homepage:http://aksw.org/DimitrisKontokostas |
From: Dimitris K. <kon...@in...> - 2013-03-01 07:46:35
|
Although it will not throw an error I don't think it will work as expected because otherwise will supersede your last statement. Try to place the last condition just before the otherwise and it should be fine Best, Dimitris On Thu, Feb 28, 2013 at 11:40 PM, Gerard Kuys <Ger...@bi...>wrote: > Thank you, Dimitris, this documentation really is enlightening. One last > question, however. In the example I include below, there is a condition > statement with a 'case' clause. As is natural, this ends with an > 'otherwise' clause. Will the program when having processed this 'otherwise' > clause leave the entire condition section, or can I add another condition, > one that is not dependent on the condition (as below: 'templateProperty = > tpx10') to be fulfilled for the case...otherwise series? > > I mean this: > > {{ConditionalMapping > | cases = > {{Condition > | templateProperty = tpx10 > | operator = contains > | value = 'ABC' > | mapping = {{TemplateMapping > | mapToClass = Class1 > }} > }} > > {{Condition > | templateProperty = tpx10 > | operator = contains > | value = 'DEF' > | mapping = {{TemplateMapping > | mapToClass = Class2 > }} > }} > > {{Condition > | operator = otherwise > | mapping = {{TemplateMapping > | mapToClass =Class3 > }} > }} > > {{Condition > | templateProperty = xtp4000 > | operator = isSet > | mapping = {{ConstantMapping > | ontologyProperty = opx300 | value = 'GHI' > }} > }} > > Would this work? > > Regards, > > Gerard > ------------------------------ > *Van:* Dimitris Kontokostas [kon...@in...] > *Verzonden:* donderdag 28 februari 2013 21:48 > *To:* Gerard Kuys > *Cc:* dbp...@li... > *Onderwerp:* Re: [Dbpedia-dutch] Conditional mapping > > Hi Gerard, > > Although so-and-so is kind of ambiguous, for field existence you can use > the '*isSet' operator > > Complete documentation can be found here > http://mappings.dbpedia.org/index.php/Template:Condition > http://mappings.dbpedia.org/index.php/Template:ConditionalMapping > > and examples here: > > http://mappings.dbpedia.org/index.php?title=Special%3ASearch&search=isset&go=Go > > http://mappings.dbpedia.org/index.php/Special:WhatLinksHere/Template:Condition > > * > *Best, > Dimitris > * > * > > * > > > On Thu, Feb 28, 2013 at 9:38 AM, Gerard Kuys <Ger...@bi...>wrote: > >> Hi all, >> >> I looked in the document on the DBpedia mapping language, but didn't find >> what I looked for: >> >> How can I, in a conditional mapping, express that the condition only >> fires if for field so-and-so there is a (or no) value? >> >> Thank you for answering! >> >> Regards, >> >> Gerard Kuys >> >> >> ------------------------------------------------------------------------------ >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics >> Download AppDynamics Lite for free today: >> http://p.sf.net/sfu/appdyn_d2d_feb >> _______________________________________________ >> Dbpedia-dutch mailing list >> Dbp...@li... >> https://lists.sourceforge.net/lists/listinfo/dbpedia-dutch >> >> > > > -- > Dimitris Kontokostas > Department of Computer Science, University of Leipzig > Research Group: http://aksw.org > Homepage:http://aksw.org/DimitrisKontokostas > -- Dimitris Kontokostas Department of Computer Science, University of Leipzig Research Group: http://aksw.org Homepage:http://aksw.org/DimitrisKontokostas |
From: Gerard K. <Ger...@bi...> - 2013-03-01 00:16:07
|
Thank you, Dimitris, this documentation really is enlightening. One last question, however. In the example I include below, there is a condition statement with a 'case' clause. As is natural, this ends with an 'otherwise' clause. Will the program when having processed this 'otherwise' clause leave the entire condition section, or can I add another condition, one that is not dependent on the condition (as below: 'templateProperty = tpx10') to be fulfilled for the case...otherwise series? I mean this: {{ConditionalMapping | cases = {{Condition | templateProperty = tpx10 | operator = contains | value = 'ABC' | mapping = {{TemplateMapping | mapToClass = Class1 }} }} {{Condition | templateProperty = tpx10 | operator = contains | value = 'DEF' | mapping = {{TemplateMapping | mapToClass = Class2 }} }} {{Condition | operator = otherwise | mapping = {{TemplateMapping | mapToClass =Class3 }} }} {{Condition | templateProperty = xtp4000 | operator = isSet | mapping = {{ConstantMapping | ontologyProperty = opx300 | value = 'GHI' }} }} Would this work? Regards, Gerard ________________________________ Van: Dimitris Kontokostas [kon...@in...] Verzonden: donderdag 28 februari 2013 21:48 To: Gerard Kuys Cc: dbp...@li... Onderwerp: Re: [Dbpedia-dutch] Conditional mapping Hi Gerard, Although so-and-so is kind of ambiguous, for field existence you can use the 'isSet' operator Complete documentation can be found here http://mappings.dbpedia.org/index.php/Template:Condition http://mappings.dbpedia.org/index.php/Template:ConditionalMapping and examples here: http://mappings.dbpedia.org/index.php?title=Special%3ASearch&search=isset&go=Go http://mappings.dbpedia.org/index.php/Special:WhatLinksHere/Template:Condition Best, Dimitris On Thu, Feb 28, 2013 at 9:38 AM, Gerard Kuys <Ger...@bi...<mailto:Ger...@bi...>> wrote: Hi all, I looked in the document on the DBpedia mapping language, but didn't find what I looked for: How can I, in a conditional mapping, express that the condition only fires if for field so-and-so there is a (or no) value? Thank you for answering! Regards, Gerard Kuys ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Dbpedia-dutch mailing list Dbp...@li...<mailto:Dbp...@li...> https://lists.sourceforge.net/lists/listinfo/dbpedia-dutch -- Dimitris Kontokostas Department of Computer Science, University of Leipzig Research Group: http://aksw.org Homepage:http://aksw.org/DimitrisKontokostas |
From: Dimitris K. <kon...@in...> - 2013-02-28 20:59:19
|
Hi Gerard, Although so-and-so is kind of ambiguous, for field existence you can use the '*isSet' operator Complete documentation can be found here http://mappings.dbpedia.org/index.php/Template:Condition http://mappings.dbpedia.org/index.php/Template:ConditionalMapping and examples here: http://mappings.dbpedia.org/index.php?title=Special%3ASearch&search=isset&go=Go http://mappings.dbpedia.org/index.php/Special:WhatLinksHere/Template:Condition * *Best, Dimitris * * * On Thu, Feb 28, 2013 at 9:38 AM, Gerard Kuys <Ger...@bi...>wrote: > Hi all, > > I looked in the document on the DBpedia mapping language, but didn't find > what I looked for: > > How can I, in a conditional mapping, express that the condition only fires > if for field so-and-so there is a (or no) value? > > Thank you for answering! > > Regards, > > Gerard Kuys > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_feb > _______________________________________________ > Dbpedia-dutch mailing list > Dbp...@li... > https://lists.sourceforge.net/lists/listinfo/dbpedia-dutch > > -- Dimitris Kontokostas Department of Computer Science, University of Leipzig Research Group: http://aksw.org Homepage:http://aksw.org/DimitrisKontokostas |
From: Gerard K. <Ger...@bi...> - 2013-02-28 07:39:50
|
Hi all, I looked in the document on the DBpedia mapping language, but didn't find what I looked for: How can I, in a conditional mapping, express that the condition only fires if for field so-and-so there is a (or no) value? Thank you for answering! Regards, Gerard Kuys |
From: Gerard K. <Ger...@bi...> - 2013-02-26 09:20:31
|
Hi all, It would really be helpful if we could use Relfinder to have a closer look at the relations existing between: * The writer Nicolaas Matsier (http://nl.dbpedia.org/page/Nicolaas_Matsier ) * The book Het achtenveertigste uur (http://live.nl.dbpedia.org/page/Het_achtenveertigste_uur) * Two subjects of the book. Attention: this is a dc:subject relation, whereas dcterms:subject denotes Categories! (Subjects: http://live.nl.dbpedia.org/page/Bestuursrecht_%28Nederland%29 and http://live.nl.dbpedia.org/page/Asielbeleid ) I would want to give it a thought, in how far relations could be inferred and in how far we will have to get them into the source articles themselves. And as an exercise in literature, I would like to explore how far we can get modelling characters - Infobox_personage, in the process of being mapped. Is someone willing (and has the time) to do this? Thanks in advance! Regards, Gerard |
From: Dimitris K. <ji...@gm...> - 2013-02-24 06:56:49
|
Hi Gerard, (I added the mailing list in cc) this is normal SPARQL behavior. Since more than one of your predicates (in fact all of them: object, adres, objnr) have more than one values, SPARQL returns a combination for all of them. here's a simple explanation [1] and a few similar cases, but not exactly the same [2], [3], [4] Maybe you should use the list items inside the resource to get them (e.g. [5]) in a query like this: SELECT * WHERE { ?s dbpedia-owl:listItemOf dbpedia-nl:Lijst_van_gemeentelijke_monumenten_in_Haaksbergen . ?s dbpedia-owl:address ?address . ?s dbpedia-owl:municipalityCode ?mCode . } [1] http://www.franz.com/agraph/support/documentation/4.7/sparql-tutorial.html#header3-35 [2] http://stackoverflow.com/questions/5135577/dbpedia-query-returns-some-musicals-more-than-once-despite-filters [3] http://answers.semanticweb.com/questions/3488/duplicate-columns-in-sparql-result [4] http://answers.semanticweb.com/questions/20090/how-to-filter-out-duplicate-results-in-sparql-select-due-to-multiple-rdftypes [5] http://nl.dbpedia.org/page/Lijst_van_gemeentelijke_monumenten_in_Haaksbergen__Boerderij__1 On Sat, Feb 23, 2013 at 10:46 AM, Gerard Kuys <Ger...@bi...>wrote: > Hi Dimitris, > > Although undeniably we are making progress with the querying of lists, we > come across new problems to solve every time. After my initial enthousiasm > about the fact that we finally could query objects coming from a Wikipedia, > I had a closer look at the results. > > Take 'Lijst van gemeentelijke monumenten in Haaksbergen' for example. > > When I entert the following query: > > PREFIX prop-nl: <http://nl.dbpedia.org/property/> > > SELECT ?monument ?itemAdres ?itemObjnr WHERE > > { > > < > http://nl.dbpedia.org/resource/Lijst_van_gemeentelijke_monumenten_in_Haaksbergen> > prop-nl:object ?monument . > < > http://nl.dbpedia.org/resource/Lijst_van_gemeentelijke_monumenten_in_Haaksbergen> > prop-nl:adres ?itemAdres . > < > http://nl.dbpedia.org/resource/Lijst_van_gemeentelijke_monumenten_in_Haaksbergen> > prop-nl:objnr ?itemObjnr . > > } > > the results I get do not represent the single objects in the list. In > fact, what is happing is a multiplication of each element with each other > element. There are not so many "Grenspaal" objects in the list, nor do > "Grenspalen" have that many addresses nor that many object IDs. I don't > know whether it is easy or difficult to fix this one (of course I hope it > will be easy), but this is a rather important issue. Do you agree? > > Kind regards, > > Gerard > -- Kontokostas Dimitris |
From: Dimitris K. <kon...@in...> - 2013-02-19 06:33:36
|
A new static release has been extracted based on the 20130205 Dutch Wikipedia dump.The new dataset has a total of 157M triples with 3.5M triples linking to other DBpedia language editions and 1M triples linking to the rest of the LOD Cloud. You can download the new dataset from here [1] or use out SPARQL Endpoint [2]. For detailed links to the LOD cloud you can also look at our updated datahub.io entry [3]. On behalf of the DBpedia in Dutch community Dimitris Kontokostas [1] http://nl.dbpedia.org/downloads/nlwiki/20130205/ [2] http://nl.dbpedia.org/sparql [3] http://datahub.io/dataset/dbpedia-nl -- Dimitris Kontokostas Department of Computer Science, University of Leipzig Research Group: http://aksw.org Homepage:http://aksw.org/DimitrisKontokostas |
From: Dimitris K. <ji...@gm...> - 2013-02-19 06:16:35
|
Hi enno, The settings in the config are what you provided me in August when I asked for some Dutch-specific Wikipedia configurations and probably needs to be updated. now what you send as an a Greek equivalent example is a completely different error. In your case you have two mappings (date & place) in one property and although the date is correctly extracted, part of the date is also extracted as a place (due to the place mapping). In the Greek example we have a single mapping (death date) in a single property and the date is not extracted at all, so this is just a Greek-date-tune problem To sum things up, the extraction framework is clever enough to extract a date when we tell it to get a date out of a string (date mapping) but not clever enough to understand and exclude a date when we instruct it to just get resources (links) out of a string (place mapping). That is why a date-template would help in this regard, the date mapping would handle it correctly, and it would remove the link that confused the place mapping. I hope it got clearer this time :) Best, Dimitris On Mon, Feb 18, 2013 at 7:32 PM, Enno Meijers <Enn...@bi...>wrote: > Hi Dimitris, > > I see what you saying about the templates. In most infoboxes where not > using templates to format the date like in the English version is done. > It's not clear to me if the settings in the config file has the same > effects when your not using templates. > > I had a look at Shakespeare in the Greek Wikipedia and DBpedia and I see > a simular problem with the date not properly being recogized: > > |ημερομηνία θανάτου = [[23 Απριλίου]] [[1616]] (52 ετών) > > > http://el.dbpedia.org/page/%CE%9F%CF%85%CE%AF%CE%BB%CE%BB%CE%B9%CE%B1%CE%BC_%CE%A3%CE%B1%CE%AF%CE%BE%CF%80%CE%B7%CF%81 > > Best, > Enno > > ------------------------------ > *Van:* Dimitris Kontokostas [ji...@gm...] > *Verzonden:* maandag 18 februari 2013 13:33 > > *To:* Enno Meijers > *Cc:* Gerard Kuys; Roland Cornelissen; dbp...@li... > *Onderwerp:* Re: mapping question > > Sorry, It seems that the nl configuration is not correct and some of > the templates do not exist > > Lets take an English Wikipedia example for this [1]: "birth date and age" > it has this page in Wikipedia [2] and is used in the following articles [3] > e.g. in [4] we write: |birth_date = {{birth date and > age|1947|04|01|df=y}} > and the framework maps year, month & date to argument order and correctly > extracts a date out of the above > I was suggesting something similar for Dutch but we need to update the > configuration to the correct templates. > > Now, in our case, the reason we get only > http://nl.dbpedia.org/resource/13_maart and not > http://nl.dbpedia.org/resource/1975 > is that the framework breaks every value according to some rules (e.g. > coma, line breaks, etc) and extracts 1 value from each > so we get : > > [[Utrecht (stad)|Utrecht]] => > http://nl.dbpedia.org/resource/Utrecht_(stad) > [[13 maart]] [[1975]] => http://nl.dbpedia.org/resource/13_maar > > Best, > Dimitris > > [1] > https://github.com/jimkont/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/config/dataparser/DateTimeParserConfig.scala#L57 > [2] http://en.wikipedia.org/wiki/Template:Birth_date_and_age > [3] > http://en.wikipedia.org/wiki/Special:WhatLinksHere/Template:Birth_date_and_age > [4] > http://en.wikipedia.org/w/index.php?title=Alain_Connes&action=edit&editintro=Template:BLP_editintro > > > On Mon, Feb 18, 2013 at 1:10 PM, Enno Meijers <Enn...@bi... > > wrote: > >> Hi Dimitris, >> >> This sheds a little more light on the problem, but I'm still confused. >> >> It looks light the real problem is the use of the resources mixed with >> dates, in the Dutch Wikipedia dates are often written as [[13 maart]] >> [[1975]]. >> This is probably done to support an easy way of grouping on dates or >> years. In the Dutch version there is a resource for every day of the year >> f.e. http://nl.wikipedia.org/wiki/13_maart >> >> The correct date extraction is of course by combining the [[dd-mm]] and >> [[yyyy]] resources, this seams to be working fine. But for birthPlace >> extraction [[dd-mm]] is not regonized as part of a date format. The year >> resources [[yyyy]] is not assigned to the birthPlace, so that must have >> been regonized as a date format. >> >> I think the line in the configuratiion file is correct: >> "geboren" -> Map ("year" -> "3", "month"-> "2", "day" -> "1") >> >> Do you mean we should set up mappings for "dd-mm" and "yyyy" parts >> seperately or are you thinking of another way to fix this? >> >> Best, >> Enno >> >> >> ------------------------------ >> *Van:* Dimitris Kontokostas [ji...@gm...] >> *Verzonden:* maandag 18 februari 2013 11:16 >> >> *To:* Enno Meijers >> *Cc:* Gerard Kuys; Roland Cornelissen; >> dbp...@li... >> *Onderwerp:* Re: mapping question >> >> Hi Enno, >> >> You are right, I didn't explain it in detail :) >> >> The problem here is that the birthPlace tries to find resources to add >> and when we include the link [[13 maart]] it is mistakenly takes it for a >> resource. >> What I suggested avoids this problem. >> * The birthDate correctly parses the date because the framework is >> configured to understand these templates and the article has better >> formatting >> * the birthPlace skips the date template because it is not a resource >> anymore >> >> I hope it is better now >> >> Best, >> Dimitris >> >> >> On Mon, Feb 18, 2013 at 12:03 PM, Enno Meijers < >> Enn...@bi...> wrote: >> >>> Hi Dimitris, >>> >>> I am not quite sure that your reply is a answer to my question. The >>> main problem is to prevent the extraction of: >>> >>> http://dbpedia.org/ontology/birthPlace = >>> http://nl.dbpedia.org/resource/13_maart >>> >>> when the data in the Infobox is: >>> >>> geboren =[[Utrecht (stad)|Utrecht]], [[13 maart]] [[1975]] >>> >>> the other extracted values are correct: >>> http://dbpedia.org/ontology/birthDate 1975-03-13 >>> http://dbpedia.org/ontology/birthPlace >>> http://nl.dbpedia.org/resource/Utrecht_(stad) >>> >>> If you answer helps to prevent this from happening than please >>> elaborate a little more. >>> >>> Best, >>> Enno >>> ------------------------------ >>> *Van:* Dimitris Kontokostas [ji...@gm...] >>> *Verzonden:* maandag 18 februari 2013 8:38 >>> *To:* Enno Meijers >>> *Cc:* Gerard Kuys; Roland Cornelissen; >>> dbp...@li... >>> *Onderwerp:* Re: mapping question >>> >>> Hi Enno, >>> >>> you are right, we should include the Dutch mailing list (included) >>> >>> For me the best approach is to use the special date templates >>> we already have these for Dutch [1] and we can always include more if >>> you find any. >>> These templates are usually better because they already include date >>> links the *Wikipadia style* and have more formatting options (e.g. for >>> people they display age) >>> >>> Dimitris >>> >>> [1] >>> https://github.com/jimkont/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/config/dataparser/DateTimeParserConfig.scala#L118 >>> >>> >>> On Fri, Feb 15, 2013 at 10:50 PM, Enno Meijers < >>> Enn...@bi...> wrote: >>> >>>> Hi Dimirtris, >>>> >>>> Sorry for bugging you, but I ran into the following problem: >>>> >>>> >>>> f.e. Infobox presentator in Wikipedia: >>>> geboren =[[Utrecht (stad)|Utrecht]], [[13 maart]] [[1975]] >>>> >>>> >>>> Mapping: >>>> {{PropertyMapping | templateProperty = geboren | ontologyProperty = >>>> birthDate }} >>>> {{PropertyMapping | templateProperty = geboren | ontologyProperty = >>>> birthPlace }} >>>> >>>> Results in: >>>> >>>> http://dbpedia.org/ontology/birthDate 1975-03-13 >>>> http://dbpedia.org/ontology/birthPlace >>>> http://nl.dbpedia.org/resource/Utrecht_(stad) >>>> http://dbpedia.org/ontology/birthPlace >>>> http://nl.dbpedia.org/resource/13_maart >>>> >>>> Is there a way to prevent the second result for birthPlace? >>>> >>>> For Infobox_auteur (writer) I used two properties in the Infobox one >>>> for the birthDate (geboortedatum) and another for the Birthplace >>>> (geboorteplaats). But this means editing by hand for all these cases. >>>> >>>> Do you have a solution? >>>> >>>> Best, >>>> Enno >>>> >>>> BTW: should I post questions like this on the (nl)dbpedia.org list? >>>> >>>> >>>> >>>> >>> >>> >>> -- >>> Kontokostas Dimitris >>> >> >> >> >> -- >> Kontokostas Dimitris >> > > > > -- > Kontokostas Dimitris > -- Kontokostas Dimitris |
From: Enno M. <Enn...@bi...> - 2013-02-18 17:32:59
|
Hi Dimitris, I see what you saying about the templates. In most infoboxes where not using templates to format the date like in the English version is done. It's not clear to me if the settings in the config file has the same effects when your not using templates. I had a look at Shakespeare in the Greek Wikipedia and DBpedia and I see a simular problem with the date not properly being recogized: |ημερομηνία θανάτου = [[23 Απριλίου]] [[1616]] (52 ετών) http://el.dbpedia.org/page/%CE%9F%CF%85%CE%AF%CE%BB%CE%BB%CE%B9%CE%B1%CE%BC_%CE%A3%CE%B1%CE%AF%CE%BE%CF%80%CE%B7%CF%81 Best, Enno ________________________________ Van: Dimitris Kontokostas [ji...@gm...] Verzonden: maandag 18 februari 2013 13:33 To: Enno Meijers Cc: Gerard Kuys; Roland Cornelissen; dbp...@li... Onderwerp: Re: mapping question Sorry, It seems that the nl configuration is not correct and some of the templates do not exist Lets take an English Wikipedia example for this [1]: "birth date and age" it has this page in Wikipedia [2] and is used in the following articles [3] e.g. in [4] we write: |birth_date = {{birth date and age|1947|04|01|df=y}} and the framework maps year, month & date to argument order and correctly extracts a date out of the above I was suggesting something similar for Dutch but we need to update the configuration to the correct templates. Now, in our case, the reason we get only http://nl.dbpedia.org/resource/13_maart and not http://nl.dbpedia.org/resource/1975 is that the framework breaks every value according to some rules (e.g. coma, line breaks, etc) and extracts 1 value from each so we get : [[Utrecht (stad)|Utrecht]] => http://nl.dbpedia.org/resource/Utrecht_(stad) [[13 maart]] [[1975]] => http://nl.dbpedia.org/resource/13_maar Best, Dimitris [1] https://github.com/jimkont/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/config/dataparser/DateTimeParserConfig.scala#L57 [2] http://en.wikipedia.org/wiki/Template:Birth_date_and_age [3] http://en.wikipedia.org/wiki/Special:WhatLinksHere/Template:Birth_date_and_age [4] http://en.wikipedia.org/w/index.php?title=Alain_Connes&action=edit&editintro=Template:BLP_editintro On Mon, Feb 18, 2013 at 1:10 PM, Enno Meijers <Enn...@bi...<mailto:Enn...@bi...>> wrote: Hi Dimitris, This sheds a little more light on the problem, but I'm still confused. It looks light the real problem is the use of the resources mixed with dates, in the Dutch Wikipedia dates are often written as [[13 maart]] [[1975]]. This is probably done to support an easy way of grouping on dates or years. In the Dutch version there is a resource for every day of the year f.e. http://nl.wikipedia.org/wiki/13_maart The correct date extraction is of course by combining the [[dd-mm]] and [[yyyy]] resources, this seams to be working fine. But for birthPlace extraction [[dd-mm]] is not regonized as part of a date format. The year resources [[yyyy]] is not assigned to the birthPlace, so that must have been regonized as a date format. I think the line in the configuratiion file is correct: "geboren" -> Map ("year" -> "3", "month"-> "2", "day" -> "1") Do you mean we should set up mappings for "dd-mm" and "yyyy" parts seperately or are you thinking of another way to fix this? Best, Enno ________________________________ Van: Dimitris Kontokostas [ji...@gm...<mailto:ji...@gm...>] Verzonden: maandag 18 februari 2013 11:16 To: Enno Meijers Cc: Gerard Kuys; Roland Cornelissen; dbp...@li...<mailto:dbp...@li...> Onderwerp: Re: mapping question Hi Enno, You are right, I didn't explain it in detail :) The problem here is that the birthPlace tries to find resources to add and when we include the link [[13 maart]] it is mistakenly takes it for a resource. What I suggested avoids this problem. * The birthDate correctly parses the date because the framework is configured to understand these templates and the article has better formatting * the birthPlace skips the date template because it is not a resource anymore I hope it is better now Best, Dimitris On Mon, Feb 18, 2013 at 12:03 PM, Enno Meijers <Enn...@bi...<mailto:Enn...@bi...>> wrote: Hi Dimitris, I am not quite sure that your reply is a answer to my question. The main problem is to prevent the extraction of: http://dbpedia.org/ontology/birthPlace = http://nl.dbpedia.org/resource/13_maart when the data in the Infobox is: geboren =[[Utrecht (stad)|Utrecht]], [[13 maart]] [[1975]] the other extracted values are correct: http://dbpedia.org/ontology/birthDate 1975-03-13 http://dbpedia.org/ontology/birthPlace http://nl.dbpedia.org/resource/Utrecht_(stad) If you answer helps to prevent this from happening than please elaborate a little more. Best, Enno ________________________________ Van: Dimitris Kontokostas [ji...@gm...<mailto:ji...@gm...>] Verzonden: maandag 18 februari 2013 8:38 To: Enno Meijers Cc: Gerard Kuys; Roland Cornelissen; dbp...@li...<mailto:dbp...@li...> Onderwerp: Re: mapping question Hi Enno, you are right, we should include the Dutch mailing list (included) For me the best approach is to use the special date templates we already have these for Dutch [1] and we can always include more if you find any. These templates are usually better because they already include date links the *Wikipadia style* and have more formatting options (e.g. for people they display age) Dimitris [1] https://github.com/jimkont/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/config/dataparser/DateTimeParserConfig.scala#L118 On Fri, Feb 15, 2013 at 10:50 PM, Enno Meijers <Enn...@bi...<mailto:Enn...@bi...>> wrote: Hi Dimirtris, Sorry for bugging you, but I ran into the following problem: f.e. Infobox presentator in Wikipedia: geboren =[[Utrecht (stad)|Utrecht]], [[13 maart]] [[1975]] Mapping: {{PropertyMapping | templateProperty = geboren | ontologyProperty = birthDate }} {{PropertyMapping | templateProperty = geboren | ontologyProperty = birthPlace }} Results in: http://dbpedia.org/ontology/birthDate 1975-03-13 http://dbpedia.org/ontology/birthPlace http://nl.dbpedia.org/resource/Utrecht_(stad) http://dbpedia.org/ontology/birthPlace http://nl.dbpedia.org/resource/13_maart Is there a way to prevent the second result for birthPlace? For Infobox_auteur (writer) I used two properties in the Infobox one for the birthDate (geboortedatum) and another for the Birthplace (geboorteplaats). But this means editing by hand for all these cases. Do you have a solution? Best, Enno BTW: should I post questions like this on the (nl)dbpedia.org<http://dbpedia.org> list? -- Kontokostas Dimitris -- Kontokostas Dimitris -- Kontokostas Dimitris |
From: Dimitris K. <ji...@gm...> - 2013-02-18 12:33:54
|
Sorry, It seems that the nl configuration is not correct and some of the templates do not exist Lets take an English Wikipedia example for this [1]: "birth date and age" it has this page in Wikipedia [2] and is used in the following articles [3] e.g. in [4] we write: |birth_date = {{birth date and age|1947|04|01|df=y}} and the framework maps year, month & date to argument order and correctly extracts a date out of the above I was suggesting something similar for Dutch but we need to update the configuration to the correct templates. Now, in our case, the reason we get only http://nl.dbpedia.org/resource/13_maart and not http://nl.dbpedia.org/resource/1975 is that the framework breaks every value according to some rules (e.g. coma, line breaks, etc) and extracts 1 value from each so we get : [[Utrecht (stad)|Utrecht]] => http://nl.dbpedia.org/resource/Utrecht_(stad) [[13 maart]] [[1975]] => http://nl.dbpedia.org/resource/13_maar Best, Dimitris [1] https://github.com/jimkont/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/config/dataparser/DateTimeParserConfig.scala#L57 [2] http://en.wikipedia.org/wiki/Template:Birth_date_and_age [3] http://en.wikipedia.org/wiki/Special:WhatLinksHere/Template:Birth_date_and_age [4] http://en.wikipedia.org/w/index.php?title=Alain_Connes&action=edit&editintro=Template:BLP_editintro On Mon, Feb 18, 2013 at 1:10 PM, Enno Meijers <Enn...@bi...>wrote: > Hi Dimitris, > > This sheds a little more light on the problem, but I'm still confused. > > It looks light the real problem is the use of the resources mixed with > dates, in the Dutch Wikipedia dates are often written as [[13 maart]] > [[1975]]. > This is probably done to support an easy way of grouping on dates or > years. In the Dutch version there is a resource for every day of the year > f.e. http://nl.wikipedia.org/wiki/13_maart > > The correct date extraction is of course by combining the [[dd-mm]] and > [[yyyy]] resources, this seams to be working fine. But for birthPlace > extraction [[dd-mm]] is not regonized as part of a date format. The year > resources [[yyyy]] is not assigned to the birthPlace, so that must have > been regonized as a date format. > > I think the line in the configuratiion file is correct: > "geboren" -> Map ("year" -> "3", "month"-> "2", "day" -> "1") > > Do you mean we should set up mappings for "dd-mm" and "yyyy" parts > seperately or are you thinking of another way to fix this? > > Best, > Enno > > > ------------------------------ > *Van:* Dimitris Kontokostas [ji...@gm...] > *Verzonden:* maandag 18 februari 2013 11:16 > > *To:* Enno Meijers > *Cc:* Gerard Kuys; Roland Cornelissen; dbp...@li... > *Onderwerp:* Re: mapping question > > Hi Enno, > > You are right, I didn't explain it in detail :) > > The problem here is that the birthPlace tries to find resources to add > and when we include the link [[13 maart]] it is mistakenly takes it for a > resource. > What I suggested avoids this problem. > * The birthDate correctly parses the date because the framework is > configured to understand these templates and the article has better > formatting > * the birthPlace skips the date template because it is not a resource > anymore > > I hope it is better now > > Best, > Dimitris > > > On Mon, Feb 18, 2013 at 12:03 PM, Enno Meijers < > Enn...@bi...> wrote: > >> Hi Dimitris, >> >> I am not quite sure that your reply is a answer to my question. The >> main problem is to prevent the extraction of: >> >> http://dbpedia.org/ontology/birthPlace = >> http://nl.dbpedia.org/resource/13_maart >> >> when the data in the Infobox is: >> >> geboren =[[Utrecht (stad)|Utrecht]], [[13 maart]] [[1975]] >> >> the other extracted values are correct: >> http://dbpedia.org/ontology/birthDate 1975-03-13 >> http://dbpedia.org/ontology/birthPlace >> http://nl.dbpedia.org/resource/Utrecht_(stad) >> >> If you answer helps to prevent this from happening than please >> elaborate a little more. >> >> Best, >> Enno >> ------------------------------ >> *Van:* Dimitris Kontokostas [ji...@gm...] >> *Verzonden:* maandag 18 februari 2013 8:38 >> *To:* Enno Meijers >> *Cc:* Gerard Kuys; Roland Cornelissen; >> dbp...@li... >> *Onderwerp:* Re: mapping question >> >> Hi Enno, >> >> you are right, we should include the Dutch mailing list (included) >> >> For me the best approach is to use the special date templates >> we already have these for Dutch [1] and we can always include more if >> you find any. >> These templates are usually better because they already include date >> links the *Wikipadia style* and have more formatting options (e.g. for >> people they display age) >> >> Dimitris >> >> [1] >> https://github.com/jimkont/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/config/dataparser/DateTimeParserConfig.scala#L118 >> >> >> On Fri, Feb 15, 2013 at 10:50 PM, Enno Meijers < >> Enn...@bi...> wrote: >> >>> Hi Dimirtris, >>> >>> Sorry for bugging you, but I ran into the following problem: >>> >>> >>> f.e. Infobox presentator in Wikipedia: >>> geboren =[[Utrecht (stad)|Utrecht]], [[13 maart]] [[1975]] >>> >>> >>> Mapping: >>> {{PropertyMapping | templateProperty = geboren | ontologyProperty = >>> birthDate }} >>> {{PropertyMapping | templateProperty = geboren | ontologyProperty = >>> birthPlace }} >>> >>> Results in: >>> >>> http://dbpedia.org/ontology/birthDate 1975-03-13 >>> http://dbpedia.org/ontology/birthPlace >>> http://nl.dbpedia.org/resource/Utrecht_(stad) >>> http://dbpedia.org/ontology/birthPlace >>> http://nl.dbpedia.org/resource/13_maart >>> >>> Is there a way to prevent the second result for birthPlace? >>> >>> For Infobox_auteur (writer) I used two properties in the Infobox one >>> for the birthDate (geboortedatum) and another for the Birthplace >>> (geboorteplaats). But this means editing by hand for all these cases. >>> >>> Do you have a solution? >>> >>> Best, >>> Enno >>> >>> BTW: should I post questions like this on the (nl)dbpedia.org list? >>> >>> >>> >>> >> >> >> -- >> Kontokostas Dimitris >> > > > > -- > Kontokostas Dimitris > -- Kontokostas Dimitris |
From: Enno M. <Enn...@bi...> - 2013-02-18 11:10:49
|
Hi Dimitris, This sheds a little more light on the problem, but I'm still confused. It looks light the real problem is the use of the resources mixed with dates, in the Dutch Wikipedia dates are often written as [[13 maart]] [[1975]]. This is probably done to support an easy way of grouping on dates or years. In the Dutch version there is a resource for every day of the year f.e. http://nl.wikipedia.org/wiki/13_maart The correct date extraction is of course by combining the [[dd-mm]] and [[yyyy]] resources, this seams to be working fine. But for birthPlace extraction [[dd-mm]] is not regonized as part of a date format. The year resources [[yyyy]] is not assigned to the birthPlace, so that must have been regonized as a date format. I think the line in the configuratiion file is correct: "geboren" -> Map ("year" -> "3", "month"-> "2", "day" -> "1") Do you mean we should set up mappings for "dd-mm" and "yyyy" parts seperately or are you thinking of another way to fix this? Best, Enno ________________________________ Van: Dimitris Kontokostas [ji...@gm...] Verzonden: maandag 18 februari 2013 11:16 To: Enno Meijers Cc: Gerard Kuys; Roland Cornelissen; dbp...@li... Onderwerp: Re: mapping question Hi Enno, You are right, I didn't explain it in detail :) The problem here is that the birthPlace tries to find resources to add and when we include the link [[13 maart]] it is mistakenly takes it for a resource. What I suggested avoids this problem. * The birthDate correctly parses the date because the framework is configured to understand these templates and the article has better formatting * the birthPlace skips the date template because it is not a resource anymore I hope it is better now Best, Dimitris On Mon, Feb 18, 2013 at 12:03 PM, Enno Meijers <Enn...@bi...<mailto:Enn...@bi...>> wrote: Hi Dimitris, I am not quite sure that your reply is a answer to my question. The main problem is to prevent the extraction of: http://dbpedia.org/ontology/birthPlace = http://nl.dbpedia.org/resource/13_maart when the data in the Infobox is: geboren =[[Utrecht (stad)|Utrecht]], [[13 maart]] [[1975]] the other extracted values are correct: http://dbpedia.org/ontology/birthDate 1975-03-13 http://dbpedia.org/ontology/birthPlace http://nl.dbpedia.org/resource/Utrecht_(stad) If you answer helps to prevent this from happening than please elaborate a little more. Best, Enno ________________________________ Van: Dimitris Kontokostas [ji...@gm...<mailto:ji...@gm...>] Verzonden: maandag 18 februari 2013 8:38 To: Enno Meijers Cc: Gerard Kuys; Roland Cornelissen; dbp...@li...<mailto:dbp...@li...> Onderwerp: Re: mapping question Hi Enno, you are right, we should include the Dutch mailing list (included) For me the best approach is to use the special date templates we already have these for Dutch [1] and we can always include more if you find any. These templates are usually better because they already include date links the *Wikipadia style* and have more formatting options (e.g. for people they display age) Dimitris [1] https://github.com/jimkont/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/config/dataparser/DateTimeParserConfig.scala#L118 On Fri, Feb 15, 2013 at 10:50 PM, Enno Meijers <Enn...@bi...<mailto:Enn...@bi...>> wrote: Hi Dimirtris, Sorry for bugging you, but I ran into the following problem: f.e. Infobox presentator in Wikipedia: geboren =[[Utrecht (stad)|Utrecht]], [[13 maart]] [[1975]] Mapping: {{PropertyMapping | templateProperty = geboren | ontologyProperty = birthDate }} {{PropertyMapping | templateProperty = geboren | ontologyProperty = birthPlace }} Results in: http://dbpedia.org/ontology/birthDate 1975-03-13 http://dbpedia.org/ontology/birthPlace http://nl.dbpedia.org/resource/Utrecht_(stad) http://dbpedia.org/ontology/birthPlace http://nl.dbpedia.org/resource/13_maart Is there a way to prevent the second result for birthPlace? For Infobox_auteur (writer) I used two properties in the Infobox one for the birthDate (geboortedatum) and another for the Birthplace (geboorteplaats). But this means editing by hand for all these cases. Do you have a solution? Best, Enno BTW: should I post questions like this on the (nl)dbpedia.org<http://dbpedia.org> list? -- Kontokostas Dimitris -- Kontokostas Dimitris |
From: Enno M. <Enn...@bi...> - 2013-02-18 10:23:15
|
Hi Dimitris, I am not quite sure that your reply is a answer to my question. The main problem is to prevent the extraction of: http://dbpedia.org/ontology/birthPlace = http://nl.dbpedia.org/resource/13_maart when the data in the Infobox is: geboren =[[Utrecht (stad)|Utrecht]], [[13 maart]] [[1975]] the other extracted values are correct: http://dbpedia.org/ontology/birthDate 1975-03-13 http://dbpedia.org/ontology/birthPlace http://nl.dbpedia.org/resource/Utrecht_(stad) If you answer helps to prevent this from happening than please elaborate a little more. Best, Enno ________________________________ Van: Dimitris Kontokostas [ji...@gm...] Verzonden: maandag 18 februari 2013 8:38 To: Enno Meijers Cc: Gerard Kuys; Roland Cornelissen; dbp...@li... Onderwerp: Re: mapping question Hi Enno, you are right, we should include the Dutch mailing list (included) For me the best approach is to use the special date templates we already have these for Dutch [1] and we can always include more if you find any. These templates are usually better because they already include date links the *Wikipadia style* and have more formatting options (e.g. for people they display age) Dimitris [1] https://github.com/jimkont/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/config/dataparser/DateTimeParserConfig.scala#L118 On Fri, Feb 15, 2013 at 10:50 PM, Enno Meijers <Enn...@bi...<mailto:Enn...@bi...>> wrote: Hi Dimirtris, Sorry for bugging you, but I ran into the following problem: f.e. Infobox presentator in Wikipedia: geboren =[[Utrecht (stad)|Utrecht]], [[13 maart]] [[1975]] Mapping: {{PropertyMapping | templateProperty = geboren | ontologyProperty = birthDate }} {{PropertyMapping | templateProperty = geboren | ontologyProperty = birthPlace }} Results in: http://dbpedia.org/ontology/birthDate 1975-03-13 http://dbpedia.org/ontology/birthPlace http://nl.dbpedia.org/resource/Utrecht_(stad) http://dbpedia.org/ontology/birthPlace http://nl.dbpedia.org/resource/13_maart Is there a way to prevent the second result for birthPlace? For Infobox_auteur (writer) I used two properties in the Infobox one for the birthDate (geboortedatum) and another for the Birthplace (geboorteplaats). But this means editing by hand for all these cases. Do you have a solution? Best, Enno BTW: should I post questions like this on the (nl)dbpedia.org<http://dbpedia.org> list? -- Kontokostas Dimitris |
From: Dimitris K. <ji...@gm...> - 2013-02-18 10:17:17
|
Hi Enno, You are right, I didn't explain it in detail :) The problem here is that the birthPlace tries to find resources to add and when we include the link [[13 maart]] it is mistakenly takes it for a resource. What I suggested avoids this problem. * The birthDate correctly parses the date because the framework is configured to understand these templates and the article has better formatting * the birthPlace skips the date template because it is not a resource anymore I hope it is better now Best, Dimitris On Mon, Feb 18, 2013 at 12:03 PM, Enno Meijers <Enn...@bi...>wrote: > Hi Dimitris, > > I am not quite sure that your reply is a answer to my question. The main > problem is to prevent the extraction of: > > http://dbpedia.org/ontology/birthPlace = > http://nl.dbpedia.org/resource/13_maart > > when the data in the Infobox is: > > geboren =[[Utrecht (stad)|Utrecht]], [[13 maart]] [[1975]] > > the other extracted values are correct: > http://dbpedia.org/ontology/birthDate 1975-03-13 > http://dbpedia.org/ontology/birthPlace > http://nl.dbpedia.org/resource/Utrecht_(stad) > > If you answer helps to prevent this from happening than please elaborate > a little more. > > Best, > Enno > ------------------------------ > *Van:* Dimitris Kontokostas [ji...@gm...] > *Verzonden:* maandag 18 februari 2013 8:38 > *To:* Enno Meijers > *Cc:* Gerard Kuys; Roland Cornelissen; dbp...@li... > *Onderwerp:* Re: mapping question > > Hi Enno, > > you are right, we should include the Dutch mailing list (included) > > For me the best approach is to use the special date templates > we already have these for Dutch [1] and we can always include more if you > find any. > These templates are usually better because they already include date > links the *Wikipadia style* and have more formatting options (e.g. for > people they display age) > > Dimitris > > [1] > https://github.com/jimkont/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/config/dataparser/DateTimeParserConfig.scala#L118 > > > On Fri, Feb 15, 2013 at 10:50 PM, Enno Meijers < > Enn...@bi...> wrote: > >> Hi Dimirtris, >> >> Sorry for bugging you, but I ran into the following problem: >> >> >> f.e. Infobox presentator in Wikipedia: >> geboren =[[Utrecht (stad)|Utrecht]], [[13 maart]] [[1975]] >> >> >> Mapping: >> {{PropertyMapping | templateProperty = geboren | ontologyProperty = >> birthDate }} >> {{PropertyMapping | templateProperty = geboren | ontologyProperty = >> birthPlace }} >> >> Results in: >> >> http://dbpedia.org/ontology/birthDate 1975-03-13 >> http://dbpedia.org/ontology/birthPlace >> http://nl.dbpedia.org/resource/Utrecht_(stad) >> http://dbpedia.org/ontology/birthPlace >> http://nl.dbpedia.org/resource/13_maart >> >> Is there a way to prevent the second result for birthPlace? >> >> For Infobox_auteur (writer) I used two properties in the Infobox one >> for the birthDate (geboortedatum) and another for the Birthplace >> (geboorteplaats). But this means editing by hand for all these cases. >> >> Do you have a solution? >> >> Best, >> Enno >> >> BTW: should I post questions like this on the (nl)dbpedia.org list? >> >> >> >> > > > -- > Kontokostas Dimitris > -- Kontokostas Dimitris |
From: Dimitris K. <ji...@gm...> - 2013-02-18 07:38:54
|
Hi Enno, you are right, we should include the Dutch mailing list (included) For me the best approach is to use the special date templates we already have these for Dutch [1] and we can always include more if you find any. These templates are usually better because they already include date links the *Wikipadia style* and have more formatting options (e.g. for people they display age) Dimitris [1] https://github.com/jimkont/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/config/dataparser/DateTimeParserConfig.scala#L118 On Fri, Feb 15, 2013 at 10:50 PM, Enno Meijers <Enn...@bi...>wrote: > Hi Dimirtris, > > Sorry for bugging you, but I ran into the following problem: > > > f.e. Infobox presentator in Wikipedia: > geboren =[[Utrecht (stad)|Utrecht]], [[13 maart]] [[1975]] > > > Mapping: > {{PropertyMapping | templateProperty = geboren | ontologyProperty = > birthDate }} > {{PropertyMapping | templateProperty = geboren | ontologyProperty = > birthPlace }} > > Results in: > > http://dbpedia.org/ontology/birthDate 1975-03-13 > http://dbpedia.org/ontology/birthPlace > http://nl.dbpedia.org/resource/Utrecht_(stad) > http://dbpedia.org/ontology/birthPlace > http://nl.dbpedia.org/resource/13_maart > > Is there a way to prevent the second result for birthPlace? > > For Infobox_auteur (writer) I used two properties in the Infobox one for > the birthDate (geboortedatum) and another for the Birthplace > (geboorteplaats). But this means editing by hand for all these cases. > > Do you have a solution? > > Best, > Enno > > BTW: should I post questions like this on the (nl)dbpedia.org list? > > > > -- Kontokostas Dimitris |
From: Roland C. <met...@gm...> - 2013-01-14 10:36:20
|
Hi folks, While writing this post the we have 99 mappings realised for the DBpedia Dutch! I believe we will pass hundred today. There are some nice stats for feedback on where we stand now: Some absolute figures: http://mappings.dbpedia.org/server/statistics/nl/ > 6% of all templates are mapped, but, > 60% of all template occurrences are already mapped. A comparison of mappings to other languages; http://mappings.dbpedia.org/sprint/ Keep up the good work! Thanks, Roland -- Signature Kabel&Co metamatter*| *Drs. Roland Cornelissen*| *Weersterweg 12*| *9832TE*| *Den Horn*| *T +31 (0)50 5515369*| *M +31 (0)6 14797518*| *www.metamatter.nl <http://www.metamatter.nl> |
From: Enno M. <Enn...@bi...> - 2012-09-29 14:03:03
|
Hi, In the HomePageExtractorConfig.scala there are definitions for the Dutch namespace. The following definitions should be used: val externalLinkSectionsMap = Map( .. "nl" -> "Externe links|Externe link", .. val officialMap = Map( .. "nl" -> "(officieel|officiële)", .. The settings for propertyNamesMap are correct: val propertyNamesMap = Map( .. "nl" -> Set("website", "homepage", "hoofdpagina", "webpagina", "web", "site"), .. Regards, Enno |