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.)

Contents


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

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, Michael Fiedler
Status
Planning
Timeline
License
Platform
Language
Java

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

MyProfile REST API

Summary
Identity platform based on WebID. Project details here.
Website
https://auth.my-profile.eu/
Contact
Andrei Sambra
Status
Early development
Timeline
Q3 of 2013
License
MIT
Platform
Web
Language
PHP

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
?

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

Linked Media Framework (Client and Server)

Summary
The Linked Media Framework (aka LMF) is an easy-to-setup server application that bundles core Semantic Web technologies to offer some advanced services.
Website
http://lmf.googlecode.com
Contact
lmf@salzburgresearch.at
Status
Full release (to be rebranded as Apache Marmotta (incubating))
Timeline
LDP Resources already almost implemented, LDP Containers still not
License
Open Source (Apache 2)
Platform
JavaEE
Language
Java (Server); Java, PHP and Javascript (Client)

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
:?
Retrieved from "http://www.w3.org/wiki/LDP_Implementations"
Personal tools