//
you're reading...
Announcement, Linked Data

Can NoSQL help us in processing Linked Data?

This is an announcement and call for feedback. Over the past couple of days I’ve compiled a short review article where I look into NoSQL solutions and to what extent they can be used to process Linked Data.

I’d like to extend and refine this article, but this only works if you share your experiences and let me know what I’m missing out and where I’m maybe totally wrong?

If you just want to read it, use the following link: NoSQL solutions for Linked Data processing (read-only Web page).

If you want to provide feedback or rectify stuff I wrote, use: NoSQL solutions for Linked Data processing (Google Docs with discussion enabled).

Thanks, and enjoy reading as well as commenting on the article!

UPDATE: I’m sorry but it seems that the commenting/discussion feature is only available for people that I explicitly add to the document granting ‘Edit’ rights. I want to apologize to everyone who tried commenting and failed in the GDocs – please let me know via Twitter or mail if you want to be added so that you can share your thoughts. Thanks for your understanding.

About these ads

About mhausenblas

Chief Data Engineer EMEA @MapR #bigdata #hadoop #apachedrill

Discussion

5 thoughts on “Can NoSQL help us in processing Linked Data?

  1. A quick comment on this: for those of us using NoSQL very extensively (Mongo, Riak and Couch in my case) providing properly prefixed JSON-LD snapshots of LATC data would be infinetly useful.

    Skimming one of the articles mentioned (http://blog.datagraph.org/2010/04/rdf-nosql-diff) I also find it fascinating how there’s an attempt to reframe some of the key advantages promoted in the current NoSQL move (e.g. lax/ad-hoc schemas, lack of a fixed query language to adhere to) are reframed are disadvantages: people aren’t using NoSQL despite these factors, but because of them. Most of the prime examples of NoSQL usage go into a very different direction from the strongly structured and modeled approach inherent in Linked Data.

    This is not done out of stupidity or ignorance but because it works well in practice. I have had various conversations with linked data proponents which discard such approaches as plainly stupid and insufficient. If that’s going to be RDFs answer to NoSQL, it is further distancing itself from the emerging best practices establishing themselves in web app development.

    Posted by Friedrich Lindenberg | 2011-05-02, 23:27
    • Friedrich,

      I understand and appreciate your position. Just one thing I don’t really get: why is a lack of a fixed (standardised) query language an advantage? Can you expand on this one please?

      Cheers,
      Michael

      Posted by mhausenblas | 2011-05-03, 08:08
  2. Sentence #2:
    s/extend/extent/

    Discussion on the document does not appear to be enabled.

    Posted by KevBurnsJr | 2011-05-03, 01:16

Trackbacks/Pingbacks

  1. Pingback: Storing and querying RDF data with Redis | seevl.net - 2013-01-15

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Archives

Follow

Get every new post delivered to your Inbox.

Join 2,150 other followers

%d bloggers like this: