For a few basic things, the DBpedia green screens pack in a higher density
of data per square inch meaning you can scan them with eyes rather than
with your fingers.
Also the DBpedia green screens tell you what the predicates and object URIs
are so you have a leg up on writing SPARQL queries.
Your interface might be more fashionable, but I don't see that it is
concretely better (or that much worse) than what DBpedia already has.
---
As for what to do about WikiData, here are two ideas:
(1) use special-case handling for common resource and identifier types;
for instance, Wikidata has wide coverage and is important. Similarly,
ISBN numbers can be pointed at OpenLibrary, ITIS numbers at itis.gov,
etc. Usually it is not hard to turn an identifier into a human-readable
URI. This is not an "infinite" tasks because you will find the targets
have an exceptional events distribution distribution so 20% of the work
gets you 80% of the impact. (Also, if you want to "add value" or "mash
up" data you've got to do *some* work)
(2) be bold, claim namespace, and make a dereferencable endpoint from
Wikidata that converts the JSON data published by WD. If it catches on,
you might pressure the Wikidata to do what they should have done a long
time ago.
Another viewpoint is to ask "how can I add value?" For instance, when I
was thinking about the green screens, I saw
http://dbpedia.org/page/Albert_Einstein
and noted that
:Einstein_Family :childOf{2} :Einstein_Family
which is a quality problem from many viewpoints:
(1) common sense about instances
(2) RDFS inferring the wrong conclusion (:Einstein_Family a :Person)
(3) A naive traversal algorithm that tries to construct a family tree by
"following it's nose" could get stuck an infinite loop. For that matter,
try starting at the root to construct the "tree of life" and see what you
get.
A value adding interface could try to hide data glitches (it looks good
because FUBAR facts are removed) or alternately try to focus attention on
them (good for people who want to improve DBpedia or fix it up after the
fact.)
On Fri, Feb 6, 2015 at 2:12 PM, Martynas Jusevičius <marty...@graphity.org>
wrote:
> Kingsley,
>
> with all due respect, what are you talking about? What visualization?
> Did you look at the example?
>
> It is a generic Linked Data browser interface, which also can be used
> to publish Linked Data datasets such as DBPedia. All it uses to render
> the page is the RDF result it retrieves from the source.
>
> As to "why?" -- because it is much more user-friendly? Is that not a
> goal for DBPedia?
>
> Let me hear about non-obvious capabilities that are required, and see
> if we can meet them. We're offering to contribute open-source code.
>
>
> Martynas
>
> On Fri, Feb 6, 2015 at 8:00 PM, Kingsley Idehen <kide...@openlinksw.com>
> wrote:
> > On 2/6/15 11:46 AM, Martynas Jusevičius wrote:
> >>
> >> Hey all,
> >>
> >> as some of you might know, our company has been developing Graphity -
> >> an open-source Linked Data client, which provides browser
> >> functionality and more.
> >>
> >> Here's an instance of it running on Linked Data Hub, rendering DBPedia
> >> resource of Tim Berners-Lee:
> >>
> >>
> http://linkeddatahub.com/?uri=http%3A%2F%2Fdbpedia.org%2Fresource%2FTim_Berners-Lee
> >>
> >> You can compare it with the current interface:
> >> http://dbpedia.org/page/Tim_Berners-Lee
> >>
> >> I think it is safe to say that user-friendliness is on another level.
> >
> >
> >> Also check out the SPARQL endpoint which contains an interactive query
> >> editor.
> >>
> >> I would like the DBPedia community to consider making Graphity the
> >> default Linked Data interface.
> >
> >
> > Why? You are adding a visualization to the mix. The tool in question is
> > already listed on the applications collection[1] page currently
> maintained
> > for the project.
> >
> > Please remember, Linked Open Data is all about loosely-coupling the
> > following:
> >
> > 1. Object (Entity) Identity
> > 2. Object (Entity) Description Location -- basically the Name->Address
> > indirection that's crucial to any Identity based system
> > 3. Notation used to construct Object (Entity) Descriptions
> > 4. Wire-Protocol used to serialize Object (Entity) Descriptionsover a
> > network
> > 5. Data Access Tools for interrogating, manipulating, and visualizing
> Object
> > (Entity) Descriptions.
> >
> > DBpedia publishes 5-Star Linked Open Data. You, like many others, have
> built
> > a nice data visualization tool. Great job! But that isn't a mutually
> > exclusive endeavor relative to DBpedia (the data space), it's a nice
> > addition to the mix :)
> >
> > Do we need an upgrade of the default green pages? Of course! Getting that
> > rolled out is something that's been looping for a while because the
> > capabilities required are a little more challenging than is obvious.
> >
> > Maybe, at some point, we could have a competition for the community to
> vote
> > on re., new default interface. The beauty of said competition is that
> > outlining the expectations provides a nice route to actually discussing
> > Linked Open Data visualization matters, clearly etc..
> >
> >
> >> After that, we could take things much
> >> further: enable editing mode, add custom layout modes etc.
> >>
> >> Please let me know what you think. The source code can be found here:
> >> https://github.com/Graphity/linked-data-hub
> >> https://github.com/Graphity/graphity-client
> >>
> >>
> >> Best regards,
> >>
> >> Martynas
> >> graphityhq.com
> >>
> >>
> > Links:
> >
> > [1] http://wiki.dbpedia.org/Applications -- DBpedia Applications .
> >
> > --
> > Regards,
> >
> > Kingsley Idehen
> > Founder & CEO
> > OpenLink Software
> > Company Web:http://www.openlinksw.com
> > Personal Weblog 1:http://kidehen.blogspot.com
> > Personal Weblog 2:http://www.openlinksw.com/blog/~kidehen
> > Twitter Profile:https://twitter.com/kidehen
> > Google+ Profile:https://plus.google.com/+KingsleyIdehen/about
> > LinkedIn Profile:http://www.linkedin.com/in/kidehen
> > Personal WebID:http://kingsley.idehen.net/dataspace/person/kidehen#this
> >
> >
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming. The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is
> your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Dbpedia-discussion mailing list
> Dbpedia-discussion@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
>
--
Paul Houle
Expert on Freebase, DBpedia, Hadoop and RDF
(607) 539 6254 paul.houle on Skype ontolo...@gmail.com
http://legalentityidentifier.info/lei/lookup
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Dbpedia-discussion mailing list
Dbpedia-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
