Creating standard REST APIs to connect data
Use OSLC to connect your data and achieve the digital thread across domains, applications, and organizations
Transition from a world of incompatible systems into a world of connected data
There were many hypertext systems. Those systems had no compatibility to one another. They also used different protocols to access and connect the documents. This made so that documents in System Type 1 could not link to documents in System Type 2.
HTML became the standard for documents in the web. Alongside with a standard protocol (HTTP) which determined how to access and connect documents. Now documents could link to others independently of where they were stored.
Difference between Web of documents, as we use today, and Web of data, as enabled by OSLC
The web uses documents, standardized to .html, to define web pages.
Documents in the web use URLs as identifiers
(URL represented by )
The web uses data, standardized to .RDF, to define data in the web.
Data in the web use URLs as identifiers
(URL represented by )
Clients can request documents from Servers via a common protocol, HTTP
Clients can request data from Servers via a common protocol, HTTP.
Documents from different sources can link to one another by referencing the other document's URL
Data from different sources can link to one another by referencing the other data's URL
Clients can use mashup applications to interact with documents in the web (Search, Visualize, Analize, etc)
Google Search, Mozilla Firefox, Google Analytics
Here's how OSLC can empower you
Free yourself from vendor dependancy. Your data in your hands
Reuse existing OSLC REST APIs supported by major vendor and for especific application or data formats
Integrate your own or existing open sources applications to visualize, search, analyze and edit your data, and more!
Integrate databases from different sources
Integrate systems with different technologies and standards
Link your data using widely adopted web stardards
Visualize your data the way you need. Graphs, Tables, Trees, you name it
Analyze your connected data for insights never before possible
Take action with information and insight never possible before
The OSLC Core Specification is a Hypermedia API standard currently mainly adopted in software and systems engineering domains, but with the potential to provide value to any domain with data integration challenges. The OSLC Core specifications expands on the W3C LDP capabilities, to define the essential and common technical elements of OSLC domain specifications and offers guidance on common concerns for creating, updating, retrieving, and linking to lifecycle resources.
OSLC domain-specific specifications define the equivalent of schemas in RDF for enabling data interoperability. They consist of RDF vocabularies and OSLC resource shapes. RDF vocabularies are used to describe standardized resource types and properties. OSLC resource shapes are used to define constraints such as multiplicity constraints on properties of specific resource types.
And many more!