My Vision for an Enhanced Linked Data Architecture – PART 1

In my previous post, I discussed the movement towards Semantic Web Technology (SWT)-based information sharing via Linked Data Concepts. Within that posting, I also made a prediction that evolving Linked Data open standards, specifications, and solutions are now creating, and will in the future create, continued disruption across the entire Information Interoperability / Information Sharing space. In this post, I will identify some of what I believe to be the current stumbling blocks to full adoption of Linked Data integration concepts and patterns in today’s Information Interoperability / Information Sharing space. I will also begin to discuss some of these stumbling blocks via additional components (the Enhanced parts) of my proposed Enhanced Linked Data Architecture and its current incarnation as the Enhanced Linkeddata Architecture for Persistent Sharing Environments (ELAPSE)™.

One stumbling block to full adoption of these concepts is the lack of an event-based and “Real-time” Push Notification ability that is already built-in to available RDF [i.e. Triple Store or Graph Database (Graph DB)] Stores and LinkedData Framework solutions. A number of popular RDF Store solutions do support the concept of “Events,” although not many of them. Events, in this context, are a basic notification of any changes made in the RDF Store – a typical, basic “Real-time” Push Notification ability can be customized to meet the needs of the business domain.  I attempt to address this deficiency in my proposed Enhanced Linked Data Architecture by including components that support the concept of “Real-time” Push Notification style of Internet-based immediate communication, where the request for a given transaction is initiated by the publisher of that transaction/notification not by the receiver. This capability is implemented via a Hypertext Transfer Protocol (HTTP) Webhook/Service Hook Web Application Programming Interface (API) – i.e. simple HTTP(S)-based webserver-to-webserver, service-oriented communication mechanism initiated on an event/transaction basis. WebHooks are typically invoked via an API using simple mechanisms for sending Push Notification “trigger events” between APIs using HTTP POST callbacks.

An additional stumbling blocks to full adoption of these concepts is the perception and real lack of “Triple-level” security across most RDF Stores and Linkeddata Stack Framework solutions. Like moving to the “cloud” itself (i.e. cloud computing; or, “the cloud”), this can become a major issue–be it real or not–and a serious stumbling block to full adoption of Linked Data integration concepts and patterns in today’s Information Interoperability / Information Sharing space.

My next post will begin to discuss security labeling/classification and how “Triple-level” security concerns associated with today’s RDF Stores and Linkeddata Stack Framework solutions could be addressed via this Enhanced Linked Data Architecture.

=david.l.woolfenden

2 thoughts on “My Vision for an Enhanced Linked Data Architecture – PART 1”

Leave a Reply

Your email address will not be published. Required fields are marked *