All,

One of the fundamental misconceptions about Linked Data is the assumption that Web-scale publication is a complex process, utterly beyond the capabilities of end-users that are already capable of creating, editing, and saving a document to a local or network drive.

I've written a detailed post [1] showcasing how anyone can publish Linked Data via a Turtle document using Web resource storage and sharing services provided by the likes of: DropBox, Amazon S3, Box.net, Microsoft SkyDrive, Google Drive, and our own ODS-Briefcase (aka. ODrive).

This guide shows how the following items simply never need to show up at the front door of Linked Data deployment narratives targeting decision makers, end-users, and systems integrators (plumbers who mesh or mash components together):

1. content negotiation
2. httpRange-14 and 303 redirection
3. web server administration.

In a nutshell, Linked Data publishing is much easier than HTML publishing while also delivering superior benefits re., ability to find relevant data, information, and knowledge, with ever increasing precision and serendipity.

Links:

1. http://bit.ly/LNIeLj -- Simple Linked Data Deployment via Turtle Docs & Storage Services .

--

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




Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to