Skip to main content
Jump to: navigation, search


< Lyo


This page contains the project plans for the Eclipse Lyo project. The first part of the plan describes the various components of Lyo and the currently planned enhancements to functionality. This plan is subject to changes based on community participation and the importance of proposed functionality to the community - we encourage anyone interested to participate. The planning process will be as open as possible and this plan will be updated as it changes. Please provide feedback on the mailing list.

Lyo Components


  • Documentation
  • Constant strings for OSLC namespaces and providers
  • POJO model for OSLC resources
  • RDF parser and serializer
  • JSON parser and serializer
  • OSLC query parser
  • HTTP client library
  • Basic, Form, OAuth support

Test suite for OSLC

The test suite for OSLC is currently available on the Lyo project. See the Lyo test suite page for details. Currently planned enhancements are

  • OSLC 3.0 Support
    • Attachments
    • Delegated Dialogs
    • Discovery
    • Resource Preview
  • Support for 2-legged OAuth [DONE]
  • Add coverage for TRS specification [DONE]
  • Tests driven by resource shape documents [DONE]

Reference implementations for OSLC (RIOs)

Reference implementations are currently available for the Change, Requirements, Architecture Management, Automation, and Tracked Resource Set specifications. See the Lyo reference implementation page for details. Currently planned enhancements are:

  • OSLC 3.0 reference implementation
    • LDP Basic Containers
    • Discovery
    • Dialogs
    • Resource Preview
    • Attachments
  • Hosting the reference implementations

Additional Proposed SDKs

Contributors are needed and welcome for all of the following:

  • JavaScript / Node.js
  • Perl
  • Python
  • PHP

Upcoming Releases

  • Lyo 3.0, release TBD. OSLC 3.0 support planned! Waiting for OASIS Committee specifications.

Release content will come from the prioritized backlog, stakeholder feedback, and community contributions. Contributions are always welcome! Even small bug fixes help.

Lyo Backlog

Backlog items with rough prioritizations:

  • [HIGH] Update dependencies and remove technical debt
  • [MEDIUM] Refactor repositories and projects to better separate concerns
  • [HIGH] Updated to the OSLC4J Java client
  • [HIGH] OSLC 3.0
    • Reference implementation
    • Test suite
    • OSLC4J SDK support
  • [HIGH] Build a W3C LDP reference impl [DONE]
    • Simple JAX-RS + Jena based reference server
    • Node.js reference implementation
  • [MEDIUM] Automation enablements
    • Hudson/Jenkins
    • Test tools
    • Chef/Puppet
  • [MEDIUM] - JavaScript libraries
    • Client
    • Server (Node.js)
  • [LOW] Perl enhancements, merge libs
  • [LOW] Python examples

Lyo OSLC4J 2.1.2 (service release)

This is a services release on OSLC4J 2.1.0 to address the following issues:

  • Clarify the provenance of 2.1.1 since since release 2.1.0 was not tagged in the Git repositories and 2.1.1 was built off 3.0.0-SNAPSHOT, not 2.1.0
  • The java client can’t be built because the net.oauth.core:oauth-httpclient4:jar:20090617 dependency is no longer available
  • Add support for TLSv1.2

2.1.2 will include cherry-picked changes from 3.0.0-SNAPSHOT for:

  • Bug 440206 - ResponseInfo's totalCount should by typed
  • Bug 442517 - Create UnparseableLiteral type to handle incorrectly typed literals in extended properties
  • Bug 460377 - OSLC4J SDK does not build under Java 8 doe to doclint errors. DocLint should be disabled in the pom.xml files for JavaDoc generation configuration
  • Bug 430390 - Missing call to resolve path parameters in method-path annotation for CreationFactory
  • Bug 462995 - Warning building
  • Bug 472227 - Compiler warnings in org.eclipse.lyo.oslc4j.provider.jena
  • Bug 472637 - Migrate Lyo to Java 8 (JimR Antlr version 3.5.2 fix) probably a duplicate of Bug 463324
  • Bug 463324 - org.eclipse.lyo.core.query - Build failure with Java 8,
  • bug 510779 - The OSLC4J release version 2.1.1 has the wrong release ID

Specific Java client bugs will also be included:

  • Bug 503995 - Jazz auth login does not work with Jazz Authenticator Server and OIDC in CLM 6.x
  • Bug 499848 - The client libraries can not be built: net.oauth.core:oauth-httpclient4:jar:20090617 dependency can not be retrieved
  • Bug 511492 - Add TSLv1.2 support back to the OSLC4J Java client

Lyo 3.0 (In progress)


  • LDP 1.0 Reference Implementation
  • OSLC 3.0

Previous Releases

  • Lyo 2.1 (February 2014)
  • Lyo 2.0 (October 2013)
  • Lyo 1.1 (February 2013)
  • Lyo 1.0 (October 2012)

Lyo 2.1


  • Hudon/Jenkins OSLC Automation Provider
  • Test Suite Consumability

Lyo 2.0


  • Support for Tracked Resource Set specification
    • TRS SDK
    • TRS Test Suite
    • TRS Reference Implementation
    • TRS Sample with Bugzilla
  • LDP Reference Implementation
    • Server support for latest W3C draft
    • Pluggable triple store implementation with Jena TDB provided for reference
    • Sample data (net worth and bug tracking examples)
  • Continuous Integration
    • Automated Hudson builds after any change
    • Snapshot artifacts published to Maven repository after each build

Lyo 1.1


  • Enhancing OSLC4J
    • OSLC Query library
    • OSLC consumer library
    • Other minor enhancements (RDF collection support, etc) and bug fixes
  • Test suite enhancements
    • RM suite improvements
    • Automation suite
  • OAuth libraries
  • Additional samples
    • client library sample usage
    • automation reference implementation

Lyo 1.0

  • M1 (Q4 2011) - theme is test suite enhancements
* Compliance Reporting
   * Bug 365198 - Would like to add the compliance toolkit to the TestSuite
   * Bug 365201 - Seeking a place to post OSLC compliance baseline reports
   * Bug 365206 - Post the OSLC Test Suite and Compliance toolkit instructions documentation
   * Bug 365302 - Post the "OSLC TestSuite and Compliance Test" demo/walkthrough video     
* Improved CM MUST and SHOULD requirement coverage
   * Bug 365618 - Complete CM MUST test cases
   * Goal: 100% CM MUST
   * Analyze CM SHOULD coverage
* Improved QM and RM MUST coverage
   * Bug 365622 - QM and RM core spec coverage by the test suite 
* Suite bug fixes and enhancements
   * Bug 363478 - Add test suite configuration for Bugzilla adapter 
   * Bug 357387 - Investigate uplift of TestSuites to Apache HttpClient 4.1.x 
   * Bug 365422 - Add RDF model validation to the OSLC JUnits. 
   * Already resolved improvements  
  • M2 (Q1 2012) - theme is initial Java SDK and refactored reference implementations
* Initial Java provider and client SDK
   * Initial contribution of OSLC4J
   * Initial documentation to help developer's get started with OSLC4J
* Example reference implementations based on the SDK
   * CM reference implementation based on OSLC4J
* Test suite improvements
  * Refactor test suite to enable additional domain tests more easily 
  * Test suite configurations for OSLC4J CM provider
* Improved QM and RM MUST coverage
   * Bug 365622 - QM and RM core spec coverage by the test suite 
* Provide a community webcast on Lyo content
  • M3/Beta (Q2 2012) - theme is feature completeness
* Full Java provider and client SDKs
* Re-vamped OSLC Workshop based on OSLC4J, including documentation
* Reference implementation can use pluggable RDF/application server providers
  * Stub service provider for use as an OSLC starter application
* Documentation
  * OSLC4J API reference guide
  * OSLC4J Tutorial and Getting started guide.
* Additional test suite enhancements to support apps written with the SDK
   * Bug 360175 - Validate ATOM responses 
   * Bug 360176 - Test for link labels 
   * Bug 360180 - Improve tests around partial get/put 
* Improve QM domain spec MUST coverage
   * Goal (dependent on community): 75%
* Test suite enhancements and bug fixes
  * Bug 360184 - Use OSLC throughout the test suite
  * Bug 360183 - Define test suite cases in the form of scenarios 
  • Release candidates and 1.0 (Q3 2012) - theme is release readiness
  * Some reference implementation refactored to take advantage of SDK
     * QM reference implementation based on OSLC4J
     * AM reference implementation based on OSLC4J 
  * Test suite enhancements
     * Improve CM, QM, RM core and domain SHOULD and MAY coverage
     * Improve RM domain spec MUST coverage
  * Stretch items based on community participation
     * non-Java language SDKs (could be in earlier milestones based on participation)
        * C#/.NET
        * Scripting languages (Python, Perl, Ruby)
        * JavaScript client library
     * Additional reference implementation and test suite enhancements
  * Release shutdown work

Release Review Documentation

Back to the top