Reference implementations are currently available for the Change, Requirements and Architecture Management specifications. See the&nbsp;[[Lyo/LyoRIO|Lyo reference implementation]] page for details. Currently planned enhancements are:

+

Reference implementations are currently available for the Change, Requirements, Architecture Management, Automation, and Tracked Resource Set specifications. See the&nbsp;[[Lyo/LyoRIO|Lyo reference implementation]] page for details. Currently planned enhancements are:

We would like to move to quarterly releases starting with 2.1. 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] Build a W3C LDP reference impl and SDK for LDP only

+

** Simple JAX-RS + Jena based reference server

+

** Reference apps to driver reference server (possibly Node)

+

** Build a OSLC V3 ref impl and/or SDK on it

+

* [HIGH] Test suite and assessment report consumability

+

** Deployable web app

+

** Increase MUST/SHOULD coverage

+

* [HIGH] - Re-factor test suites to use OSLC4J and drive them via resource shape and service provider resurces

+

* [MEDIUM] Automation enablements

+

** Hudson/Jenkins

+

** Test tools

+

** Chef/Puppet

+

* [MEDIIUM] - JavaScript client library

+

** Consumer navigation of provider (catalog->provider->resources)

+

** Helpers for dialogs (frame handlers, etc)

+

* [MEDIUM] Orion integration

+

** [RDF formats] People like to hand crank some RDF formats, can we do something simple to plug into to provide some simple syntax highlighting and validation

+

** [Node.js] Perhaps just a document of how to use Orion to do JS/Node dev with our impl. FYI https://github.com/scripted-editor/scripted

Introduction

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 lyo-dev@eclipse.org mailing list.

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:

Additional Proposed SDKs

Contributors are needed and welcome for all of the following:

Perl

Python

PHP

JavaScript

Upcoming Releases

Lyo 2.1 is planned for Q1 2014.

Lyo 2.2 is planned for Q2 2014.

We would like to move to quarterly releases starting with 2.1. 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] Build a W3C LDP reference impl and SDK for LDP only

Simple JAX-RS + Jena based reference server

Reference apps to driver reference server (possibly Node)

Build a OSLC V3 ref impl and/or SDK on it

[HIGH] Test suite and assessment report consumability

Deployable web app

Increase MUST/SHOULD coverage

[HIGH] - Re-factor test suites to use OSLC4J and drive them via resource shape and service provider resurces

[MEDIUM] Automation enablements

Hudson/Jenkins

Test tools

Chef/Puppet

[MEDIIUM] - JavaScript client library

Consumer navigation of provider (catalog->provider->resources)

Helpers for dialogs (frame handlers, etc)

[MEDIUM] Orion integration

[RDF formats] People like to hand crank some RDF formats, can we do something simple to plug into to provide some simple syntax highlighting and validation