All,Here is a rehash of a post I made last week about DBpedia attribution in line with the fundamental goals and principles of Linked Open Data.
** Attribution Guidelines Start ***There are some very important things that are sometimes a little unclear about Linked Data and DBpedia. I would characterize them as follows:
1. Best Practices 2. Actual Principles. Best Practices:Attribute your Linked Data sources in your Linked Data consumers. You can achieve this in a number of ways, in descending preference order:
1. Make the DBpedia data source URIs visible to user agents that are capable of processing HTTP response headers (using "Link:") and/or <link/> entries in <head/> section of (X)HTML documents -- here you have the ability to point to one or all the URIs referenced in a document, just as one would when attributing sources in a paper
2. Use DBpedia URIs for @href values In (X)HTML document3. Explicitly acknowledge DBpedia as a data source -- this is the least preferred option because its loose and veers way from fundamental Linked Data principles.
Actual Principles:Linked Data is all about creating a virtuous cycle that ultimately increases the density of the burgeoning Web of Linked Data or Data Web. Every producer or consumer is ultimately in a symbiotic as opposed to parasitic relationship. Thus, all Linked Data consumers have to keep the chain of links going by creating resources and interfaces that enable others user agents discover and follow (using the follow-your-nose pattern) Linked Data URIs e.g., those produced by DBpedia and other Data Spaces in the LOD cloud. This is what Linked Data is fundamentally about.
Put differently, its the same principle behind the document Web, when you publish an HTML file, the virtue lies in linking to something else on the Web. That act is the fundamental essence of the Web. Linked Data just adds granularity to this most powerful principle.
Thanks for this post, as what I've outlined is something isn't always expressly clear re. DBpedia or the rest of the LOD cloud. All we seek, fundamentally, is a symbiotic ecosystem that virtuously makes Web denser and ultimately more useful.
Here are examples of what I mean, using DBpedia resources as an example: 1. http://dbpedia.org/resource/DBpedia -- URI that denotes a DBpedia entity2. http://dbpedia.org/page/DBpedia -- URI/URL that denotes a document that describes a DBpedia entity
3. http://bit.ly/OipZA3 -- URI Debugger showcasing the approaches I listed re. making URIs available to other user agents via "Link:" (response headers) and/or <link/> (html doc header section)
4. http://dbpedia.org/describe/?url=http://dbpedia.org/resource/DBpedia -- an alternative URI/URL that denotes a document that describes a DBpedia entity
5. http://bit.ly/OwNOzP -- URI Debugger showcasing approaches listed above re. making URIs available to other user agents .
Thanks for this post, this is an important matter that isn't always clear to others that build Linked Data consumer applications.
** End *** -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca handle: @kidehen Google+ Profile: https://plus.google.com/112399767740508618350/about LinkedIn Profile: http://www.linkedin.com/in/kidehen
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html
_______________________________________________ Dbpedia-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
