Hi Jona,
Thanks for the exhaustive explanation.
On 5/8/12 7:14 PM, Jona Christopher Sahnwaldt wrote:
Even worse - there is a link to [[Heavy metal]], but in the infobox
it's spelled Heavy Metal (with a capital M), so we don't find that
link. This behavior could be considered a bug. Wikipedia
Hi Marco,
This smells like another thread:
http://www.mail-archive.com/dbpedia-discussion@lists.sourceforge.net/msg02767.html
Would it be possible to emulate Wikipedia renderer engine behavior? It
is written in PHP, so it should be a piece of cake to implement it in
powerful Scala.
So... are
Would it be possible to emulate Wikipedia renderer engine behavior? It
is written in PHP, so it should be a piece of cake to implement it in
powerful Scala.
So... are you volunteering to try it out?
I think he just missed to add an appropriate emoticon at the end of
the sentence :-)
--
2012/5/10 Pablo Mendes pablomen...@gmail.com:
Hi Marco,
This smells like another thread:
http://www.mail-archive.com/dbpedia-discussion@lists.sourceforge.net/msg02767.html
This is not similar, In this thread I was asking about a couple of
bugs of misconfiguration of dbpedia html page renderer
2012/5/10 Jona Christopher Sahnwaldt j...@sahnwaldt.de:
I would guess that adding template expansion to DBpedia is a *major*
task. May take several months. It would also be a *huge* benefit. :-)
Sure it is, but here Marco Fossati was just asking about case
insensitive wikilink discovery in
Hi All,
The latest dbpedia_dav.vad version “1.3.65” built can be downloaded from:
http://opldownload.s3.amazonaws.com/uda/vad-packages/6.3/virtuoso/dbpedia_dav.vad
I have also updated the DBpedia Internationalisation wiki page
(http://wiki.dbpedia.org/Internationalization/Guide) with
Marco,
My pointer to the thread was with reference to the Sweble parser usage.
Rendering pages like the PHP of wikipedia seems to do means just using
their code or implementing template resolution. We've been doing the first,
in that thread we suggested doing the second.
Fixing this in the code
I know. :-)
On Thu, May 10, 2012 at 1:50 PM, Marco Fossati hell.j@gmail.com wrote:
On 5/10/12 12:24 PM, Jona Christopher Sahnwaldt wrote:
sorry for the exhausting explanation.
I meant exhaustive. :-)
--
Live
I just made that little change. I had looked at the code before, so it
was very simple. We now also get the triple for Heavy metal, but
that's it:
http://mappings.dbpedia.org/server/extraction/it/extract?title=Glenn+Danzig
Let's hope that this doesn't introduce too many extraction errors.
It's
2012/5/10 Jona Christopher Sahnwaldt j...@sahnwaldt.de:
I just made that little change. I had looked at the code before, so it
was very simple. We now also get the triple for Heavy metal, but
that's it:
http://mappings.dbpedia.org/server/extraction/it/extract?title=Glenn+Danzig
It seems a
I think what Marco meant was: the mapping says it's an object
property, so we should extract a URI, even if the property value is
just a string.
In the case of the musician infoboxes on it wiki, that would work, but
in many other cases, it wouldn't. For example:
http://en.wikipedia.org/wiki/Neocon
http://en.wikipedia.org/wiki/NeoCon
Nice example on why case insensitiveness is bad. :-)
Oh, I don't see a problem here. There would only be a problem if we
extracted a page that contained the string NeoCon in the infobox but
a link to [[Neocon]] in the
On Thursday 10 May 2012 21:06:30 Jona Christopher Sahnwaldt wrote:
I think what Marco meant was: the mapping says it's an object
property, so we should extract a URI, even if the property value is
just a string.
Right.
In the case of the musician infoboxes on it wiki, that would work, but
In the context of...
When there is a link, then the object property MUST be generated directly
FROM THE LINK PROVIDED BY THE USER.
If there isn't a link FOR AN OBJECT PROPERTY, then we should try to find
one in the page.
Jona said...
We could use a heuristic to
split the string into
14 matches
Mail list logo
