LDP Implementations

From W3C Wiki
Jump to: navigation, search

This is community-maintained page listing planned and existing implementations of the Linked Data Platform (LDP). If you are associated with such an implementation (planned or complete), please make sure it is correctly listed on this page.

Disclaimer: The contents of this page have not necessarily been reviewed by the LDP Working Group. Things listed on this page might not actually be LDP implementations. (But please do try to keep it limited to things which aim to be full or partial LDP implementations.)

ALM iStack (Client and Server, Software Lifecycle)

Summary
ALM-iStack main goal is to create a open source ALM, integrating existing open source inciatives using OLSC and LDP specifications.
Website
https://sites.google.com/a/centeropenmiddleware.com/alm-istack/
Contact
Raúl García-Castro, Miguel Esteban-Gutiérrez, Nandana Mihindukulasooriya
Status
In progress
Timeline
During 2013
License
Apache 2
Platform
Java EE 6
Language
Java

Apache Marmotta (Client and Server)

Summary
Apache Marmotta is an Open Platform for Linked Data..
Website
http://marmotta.apache.org
Contact
dev@marmotta.apache.org
Status
Full release
Timeline
work-in-progress alignment of the current implementation with the current version of the specification.
License
Open Source (Apache 2)
Platform
JavaEE
Language
Java (Server); Java, PHP and Javascript (Client)

Callimachus (Client and Server)

Summary
Callimachus (kəlĭm'əkəs) is a framework for data-driven applications based on Linked Data principles. Callimachus allows Web authors to quickly and easily create semantically-enabled Web applications.
Website
http://callimachusproject.org
Contact
David Wood
Status
Full release
Timeline
Ongoing; tracking the LDP specification
License
Open Source (Apache 2)
Platform
Java 1.6.0 (Linux/Mac/Windows), prefers browsers with HTML5 features
Language
Java

Carbon LDP (Server)

Summary
Carbon LDP is an enterprise-class solution platform that helps artists and engineers create and extend web applications with ease. Information can be modeled and managed without creating database schema or modifying those of existing apps. Carbon significantly reduces the need for complex SQL queries and compiled deployments when building sophisticated systems. Existing enterprise apps can be extended and better integrated. New apps can be created to be future-proof, with all the benefits of Linked Data and the RDF data model. Data is managed through a simple JSON/REST API that can be leveraged using HTML and JavaScript. Development on Carbon is tracking as close to the LDP specification as possible - evolving as the spec evolves to achieve the highest level of compliance possible.
Website
http://carbonldp.com
Contact
Cody Burleson of Base22
Status
In progress. HTTP PATCH, JSON-LD, authentication, and access control are still up in our development plan.
Timeline
Q3 2014
License
Commercial (specific details to be determined)
Platform
Java 1.6.0 (Linux/Mac/Windows). We're building and testing on Tomcat as well as IBM WebSphere Application Server. Datasets are currently stored in IBM DB2 (NoSQL Graph Store), though we hope to be supporting more repositories by the time we're 'Generally Available'.
Language
Platform developers can extend the platform itself using Java/J2EE. Application developers can leverage the JSON/REST API, platform end-point services, and a wealth of jQuery plugins and UI widgets.

Eclipse Lyo (Client and Server, Software Lifecycle)

Summary
Eclipse Lyo provides a Java SDK to help adopt Linked Lifecycle Data and OSLC (Open Services for Lifecycle Collaboration) compliant tools.
Website
http://eclipse.org/lyo
Contact
Steve Speicher, Samuel Padgett, Michael Fiedler
Status
In progress
Planning
TBD
Timeline
3Q2013
License
EPL 1.0
Platform
JEE (Tomcat, Derby, etc)
Language
Java

RWW.IO

Summary
Read/write Linked Data platform for applications and their data. Also supports WebAccessControl and WebID. Details here.
Website
https://rww.io
Contact
Andrei Sambra
Status
LDPC:
BasicContainer
GET, POST, PUT, DELETE, HEAD, OPTIONS
Full paging through Link headers
Prefer header
Accept-Post header
LDPR:
GET, POST, PUT, DELETE, HEAD, OPTIONS
If-Match and ETag
Pending:
PATCH
DirectContainer and IndirectContainer
Ordering/sorting
Timeline
-
License
MIT
Platform
Linux, Windows, etc. (anything that can run PHP)
Language
PHP

node_ldp (Server)

Summary
Implementation of the Linked Data Platform for Node.
Website
https://github.com/AKSW/node_ldp
Contact
AKSW, Contributors
Status
started 01/2013, some issues open
Timeline
put, post, delete, container, ... implemented, webid, pingback, other features in roadmap
License
??
Platform
node.js
Language
JavaScript

OpenLink Data Spaces (Hosted Service; LDP Client & Server)

Summary
OpenLink Data Spaces (ODS) is an industry standards-compliant data space platform that includes a broad collection of distributed collaborative applications covering blogs, wikis, shared bookmarks, file management, calendaring, email, photo galleries, discussion forums, polls, and more. :Every item of data within an ODS instance is denoted by a URL, enabling any HTTP-compatible client to obtain a negotiated representation of the description of any ODS data item.
Website
http://ods.openlinksw.com
Contact
Ted Thibodeau or http://www.openlinksw.com/contact
Status
Full release
Timeline
Full compatibility with LDP-WG output awaits that output...
License
Open Source
Platform
client-side - Browser-based via Javascript.
server-side - Currently Virtuoso-specific. Back-end agnosticism coming soon.
Language
Javascript

OpenLink Virtuoso (Data Server; LDP Client & Server)

Summary
OpenLink Virtuoso is a hybrid data store and application server, which can generally act as a client for the same data models, access mechanisms, and interaction protocols as it serves. These include (but are not limited to) SPARQL, RDF and other graph model data, SQL, RDBMS data, HTTP, LDAP, SMTP, IMAP4, POP3, ODBC, JDBC, OLE DB, ADO.NET, and others.
Website
http://virtuoso.openlinksw.com/
Contact
Ted Thibodeau or http://www.openlinksw.com/contact
Status
Full release
Timeline
Full compatibility with LDP-WG output awaits that output...
License
Open Source and Commercial
Platform
AIX, HP-UX, Linux, Mac OS X, Solaris, Windows, other Unix-like
Language
C/C++ (extensible with Java, C/C++, PHP, Perl, Python, Ruby, and others)

rdflib.js (Client Library)

Summary
?
Website
https://github.com/linkeddata/rdflib.js
Contact
?
Status
?
Timeline
?
License
?
Platform
?
Language
?

rdf.sh (Client)

Summary
A multi tool for doing Semantic Web jobs on the command line, incl. LDP client jobs
Website
https://github.com/seebi/rdf.sh
Contact
Sebastian Tramp
Status
v0.6
Timeline
get, delete, put, ...
License
Open Source (GPL2+)
Platform
Command Line
Language
bash

RWW Play Server

Summary
Server written in Scala implementing LDP, WebID, and WebAccessControl
Website
https://github.com/read-write-web/rww-play
Contact
Henry Story
Status
early development
Timeline
End of November implement working version of current spec
License
Apache 2.0
Platform
Play2.0 framework using Banana-RDF
Language
Scala

Tabulator (Client)

Summary
The Tabulator project is a generic data browser and editor. Using outline and table modes, it provides a way to browse RDF data on the web.
Website
http://www.w3.org/2005/ajar/tab
Contact
Tim Berners-Lee <timbl@w3.org>
Status
complete functionality, but not in sync with LDP spec (as of 2 Nov 2012)
Timeline
Initially released 2005. LDP conformance expected before or during CR.
License
?
Platform
Browser (Firefox only?)
Language
JavaScript

TopBraid Live (Client and Server)

Summary
TopBraid Live ('TBL') is an enterprise SOA-capable Semantic Web application platform. TBL is optimized for delivering dynamic SWT (Semantic Web Technologies) -driven applications that realize the Linked Data Platform.
Website
http://topquadrant.com/products/TB_Live.html
Contact
Ralph Hodgson, W3C wiki profile at http://www.w3.org/wiki/User:Rhodgson
Status
First version was released in 2008, currently shipping release 4.2.
Timeline
Full LDP conformance expected before or during CR. POST and GET available now.
License
Open Source and TopQuadrant Licensing
Platform
Java
Language
Java (Server); Java, Javascript (Client), SWA (SPARQL Web Applications - http://topquadrant.com/swp/#SWPAppComp )/ SWP (SPARQL Web Pages - http://topquadrant.com/swp/ ) and SPIN (http://www.w3.org/Submission/spin-overview/ ).

APPENDIX: Instructions for modifying this page

Please help keep this page up to date. Ideally, entries include the following information, when applicable:

  • Implementation name (in entry header)
  • Client, Server, Both, Something Else (in entry header)
  • Summary blurb
  • Link to project/implementation Website. (Ideally this page should include DOAP information and be the doap:homepage of that project.]
  • Contact information
  • Status
  • Timeline (when release/conformance expected)
  • Software license
  • Platform (eg Unix, Android, Browser)
  • Programming Language(s) used in implementation
  • Other notes, features, qualifications


The following template may be helpful:

== Template (Client? Server?) ==

;Summary
:?
;Website
:?
;Contact
:?
;Status
:?
;Timeline
:?
;License
:?
;Platform
:?
;Language
:?