Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Lyo/ProjectPlans

< Lyo
Revision as of 17:03, 31 October 2011 by Fiedler.mf.gmail.com (Talk | contribs) (Milestones)

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. These are categorized as MUST, SHOULD or MAY items based on how the project participants have ranked them. 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.

Lyo Components

OSLC Java SDKs

  • 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

  • Add reporting capabilities
  • Improve Change Management MUST and SHOULD requirement coverage
  • Improve Requirements and Change Management MUST coverage
  • Improved query tests
  • Improved Oauth tests
  • Tests driven by resource shape documents

Reference implementations for OSLC (RIOs)

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

  • Support for the Quality Management domain
  • Adoption of the OSLC Java SDK
  • Refactoring to allow for pluggable RDF and application server technologies


Additional Proposed SDKs

  • .NET (C# or other)
  • Perl
  • Python
  • PHP
  • JavaScript

Milestones

Currently planned milestones are:

  • M1 (Q4 2011) - theme is test suite enhancements
  * Reporting
  * Improved CM MUST and SHOULD requirement coverage
  * Improved QM and RM MUST coverage
  * Soliciting contributions for other domains
  • M2 (Q1 2011) - theme is initial Java SDK and refactored reference implementations
  * Initial Java provider and client SDK
  * Example reference implementations based on the SDK
  * Additional test suite enhancements to support apps written with the SDK
  • M3/Beta (Q2 2011)
  * Full Java provider and client SDKs
  * Reference implementation completely refactored to take advantage of SDK 
  * Reference implementation can use pluggable RDF/application server providers
  * Documentation
  • Release candidates and 1.0 (Q3 2011)
  * Stretch items based on community participation
     * non-Java language SDKs
     * Additional reference implementation and test suite enhancements
  * Release shutdown work

Back to the top