Enhanced linkeddata architecture for persistent sharing environments elapse - v1.1

Both ELAPSE® and AFIELD® Logos are registered Trademarks of eVectis Technologies LLC
eVectis Technologies LLC Confidential –Internal Use Only
Enhanced Linkeddata Architecture for Persistent Sharing Environment-ELAPSE™(to slip or pass by)
Information Sharing Architecture direction that supports…
A Future-oriented Information Exchange of Local Data
-AFIELD™(Off the usual or desired track. Away from one's home or usual environment)

Linkeddata Fundamentals
1.
Overview of the Semantic Web (AKA “Web of data”)
The Semantic Web is a vision of how the existing infrastructure of the World Wide Web can be extended in such a way that machines can interpret the meaning of data involved in protocol interactions.
•
RDF
–
The goal of a universal approach to machine-oriented interpretation of data in the Semantic Web is facilitated through the use of a data representation standard called the Resource Description Framework (RDF). RDF captures meaning as a set of triples similar to the subject, verb, and object components of an elementary sentence in a natural language.
•
Linkeddata
–
Linkeddata relies on RDF to provide a general framework for interpreting data connections as logical statements and adds value through this additional dimension of machine understanding.
•
SPARQL query language
–
SPARQL provides the means to accessing a collection of named RDF graphs (where each graph is associated with a URI) called an RDF dataset and a language for querying across an RDF dataset.
Enhanced Linkeddata Architecture

The Enhanced parts…..
1.
“Real-time” Push Notification
–
a 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.
2.
WebHooks/Service Hook API over HTTP or HTTP-CoAP
–
A simple HTTP(S) based webserver-to-webserver, service-oriented communication and Representational State Transfer (REST) mechanism initiated on an event/transaction basis. Typically invoked via an Application Programming Interface (API) using simple mechanisms for sending Push Notification “trigger events” between APIs using HTTP POST callbacks. Using Constrained Application Protocol (CoAP), a lightweight variant of HTTP that a provides a subset of REST common with HTTP, that has been optimized for M2M applications, when needed.
3.
MQTT lightweight publish/subscribe messaging protocol
–
The Message Queue Telemetry Transport (MQTT) protocol is based on the principle of publishing messages and subscribing to topics, or "pub/sub". Multiple clients connect to a broker and subscribe to topics that they are interested in. MQTT is widely adopted in mobile environments due to the low power consumption, simplicity of API, and small bandwidth used. Clients and servers are available in various languages including C, Python, Erlang, C#, Java etc.
Enhanced Linkeddata Architecture

A Future-oriented Information Exchange of Local Data (AFIELD)
Enhanced Linkeddata Architecture for Pennsylvania's Sharing Environment (ELAPSE)

LEJIS Web Interface (LWI)

Human
Incident Notifications
JNET continues to provide secure infrastructure support……
System Incident
Notifications
Legacy LEJIS information exchange support

RDF Graph Linkeddata “cloud” of incident
“Big Data”
(Clustered using Hadoop & ready
for Amazon Elastic MapReduce)
1200+ Local LE RMSs & county CAD systems
Human
System Incident
Notifications

“Big Data”
(Clustered using Hadoop & ready for Amazon Elastic MapReduce)
1200+ Local LE RMSs & county CAD
Human
System Incident
Notifications
Incident information search & access is performed via Linkeddata concepts
(Authentication via OAuth/WebID- TLS/NetID-TLS protocols)

“Big Data”
and
REST/WebHooks or MQTT protocol based push notifications
Human
System Incident
Notifications
Incident Notifications made as result of “Real-time” Push Notification of PD/CAD incident events via HTTP(s) and WebHooks APIs or MQTT protocol
(Authentication via OAuth)

“Big Data”
and
REST/WebHooks or MQTT protocol based push notifications
Key characteristics:
1.JNET/LEJIS does not store PD/911 incident data, incident data remains in the PDs and is “exposed” as a RDFGraph Linkeddata “cloud” for incident information searching via SPARQL
2.SecureHTTP(s) based information exchange from LE RMSs and county CAD systems to JNET/LEJIS via REST WebHooks or MQTT protocol based APIs for Real- time Push Notifications)
3.RMS/CAD/LWI incident Information is securely(OAuth/WebID-TLS/NetID-TLS protocols) searched & accessed via Semantic Web concepts including Linkeddata, RDF and SPARQL queries
4.Support for legacy LEJIS information exchange isprovided until no longer needed
5.Email, SMS & M2M push notification can be securely sent from LEJIS core (possibly leveraging PA Alert)
6.Advanced Message Queuing Protocol (AMQP) support, where needed, (if additional requirements for message orientation, queuing, routing (including point-to-point and publish-and-subscribe), reliability and security are required) from Core to Incident Notification subscribers.
AFIELD driven Local Law Enforcement Sharing allows PDs and 911 centers to maintain control over their own incident information while still fully participating in ELAPSE provided services
2
3
1
Human
1
System Incident
Notifications
4
5
Incident Notifications made as result of “Real-time” Push Notification of PD/CAD incident events via HTTP(s) and WebHooks APIs or MQTT protocol
(Authentication via OAuth)
6

What is different about Linkeddata?
Linkeddata addresses how to convey information, the association between the data itself and the metadata that gives it meaning , by changing the way that we interact with the data, especially via computer programs, in particular:
–
every data resource, is given a unique identity (known as a URI);
–
that unique identity is based on HTTP, the widely-used network protocol used by web browsers to fetch web pages for display;
–
properties of data resources, such as their type, scale, units, provenance, last updated time, etc, are represented using the Resource Description Framework (RDF) in which values are connected together in networks of named links, called properties;
–
the names of the properties, resource types, classification codes, etc, are also given web identifier URIs. This means that they too can be fetched (technically the term we use is resolved) using HTTP. The information returned when resolving, say, an RDF property help give a clear semantic meaning to the data.

What is different about Linkeddata? (cont)
It's this practice of connecting resources together using named, meaningful links that gives Linkeddata both its name and its power. Once the reference data has been created, the possibilities to extend and refine it with additional data sources are unlimited.
The query language SPARQLis a powerful and general-purpose tool for accessing RDF data, but having to learn SPARQL is an extra burden for developers. Electing instead to use an API approach, in which a collection of HTTP-accessible end- points provide a programming interface that web developers can make use of more easily. In particular using the Linked Data API (LDA) to provide a programming interface to the data. The LDA uses well-established conventions for accessing the details of individual data resources, and/or a collection of resources.
Blueprints 2.0..including Gremlin & Rexster –Evolving mechanisms to provide a common set of interfaces that allow developers to plug-and-play their graph database backend collections. These open-source based products are analogous to the JDBC, but for graph databases.

W3C Linked Data Profile Working Group
The principal technologies of the Semantic Web fit into a set of layered specifications. The current components are:
–
the Resource Description Framework (RDF) Core Model,
–
the RDF Schema language,
–
the Web Ontology language (OWL), and
–
the Simple Knowledge Organization System (SKOS).
Building on these core components is a standardized query language, SPARQL(pronounced "sparkle"), enabling querying of decentralized collections of RDF data.
The POWDERrecommendations provide technologies to find resource descriptions for specific resources on the Web; descriptions which can be “joined” to other RDF data.
The GRDDLand RDFarecommendations aim at creating bridges between the RDF model and various XML formats, like XHTML.
RDFa also plays an important role as a format to add Structured Data to HTML, i.e., as a means to help using Linked Data in Web Applications.
The goal of the R2RMLlanguage is to provide standard language to map relational data and relational database schemas to RDF and OWL.
Finally, the goal of the newly proposed Linked Data Profile Working Group is to provide a “entry level” layer to manage Linked Data file using RESTful, HTTP based API.

Enhanced linkeddata architecture for persistent sharing environments elapse - v1.1

More Related Content

Similar to Enhanced linkeddata architecture for persistent sharing environments elapse - v1.1 (20)

Recently uploaded (20)

Enhanced linkeddata architecture for persistent sharing environments elapse - v1.1