OSLC Open Project is pleased to announce that the OSLC Systems Modeling Language Version 2.0 Project Specification Draft 01 has been published.

OSLC Open Project thanks the community of implementers, developers and users who have brought the work successfully to this milestone and welcomes feedback on this Project Specification Draft.

OASIS is pleased to announce that the OSLC Configuration Management Version 1.0 has been published after reaching the OASIS Standard status.

OASIS congratulates the members of the OSLC Open Project and the community of implementers, developers and users who have brought the work successfully to this milestone.

OASIS is pleased to announce that the OSLC PROMCODE Version 1.0 has been published after reaching the OASIS Standard status.

OASIS congratulates the members of the OSLC Open Project and the community of implementers, developers and users who have brought the work successfully to this milestone.

OASIS is pleased to announce that the Call for Consent has closed and, effective 26 May 2021, OSLC Change Management Version 3.0 is an OASIS Standard according to the Call for Consent procedure. Project Administration will now undertake the final tasks of preparing and loading the standard.

Change Management Version 3.0 was one of the first approved Project Specifications to come out of the new OASIS Open Project Program and its first OASIS Standard. The Project Governing Board will be acting on additional deliverables over the next few months.

OASIS is pleased to announce that OSLC Core v3.0, OSLC Query v3.0, OSLC Requirements Management v2.1, and OSLC Change Management v3.0 are now approved \OASIS Project Specifications. These join the previously announced OSLC Quality Management v2.1 as the first approved Project Specifications from the Open Projects program.

OSLC Core defines the overall approach to Open Services for Lifecycle Collaboration that extend and complement the W3C Linked Data Platform.

OSLC Query provides a mechanism for a client to search for RDF resources.

The OSLCFest took place on May 18-20, 2020. There were a total of 20 presentations on OSLC, including 8 presentations by tool vendors. The recording of the talks of the OSLCFest 2020 (http://www.oslcfest.org/) can be found on YouTube: Day1: https://www.youtube.com/watch?v=FxMAyHqEay8 Day2: https://www.youtube.com/watch?v=tz35ecvqLlQ Day3: https://youtu.be/t1AJg8HAEn4

We finally have some great news to share! After starting the OSLC Open Project in May 2019 and having a long summer with various people being off for vacations, we have prepared the first specification for publication, updated the templates and fixed major outstanding issues. The OSLC OP Project Governing Board has approved the publication of the Change Management 2.1 PSD (Project Specification Draft) 03.

This specification defines the OSLC Change Management domain, a RESTful web services interface for the management of product change requests, activities, tasks and relationships between those and related resources such as requirements, test cases, or architectural resources. To support these scenarios, this specification defines a set of HTTP-based RESTful interfaces in terms of HTTP methods: GET, POST, PUT and DELETE, HTTP response codes, content type handling and resource formats. The table of all specs has been updated to point to the newly published draft, which is available in the OASIS repository for OSLC specs: OSLC CM 2.1 PSD 03.

We are pleased to announce a big step forward for OSLC!

The most exciting thing that we heard throughout the OSLCfest 2018 conference was that people were eager to contribute and were asking for a simpler, more streamlined way to provide contributions and make their voices heard. After exploring several alternatives, the OSLC Steering Committee decided to shift ongoing work from the OASIS Technical Committees to a new OSLC Open Project under the recently-announced OASIS Open Project program.

Short summary

Migration to Github is complete; Lyo now supports JSON-LD and Turtle; Lyo Designer generates OpenAPI/Swagger docs and adds modelling support for SHACL shapes. Lyo 2.4 is expected to be the last 2.x release. We also make a switch to a better changelog convention.

✨ Added

• JSON-LD support has been added to Lyo Core. Thanks to Ricardo Javier Herrera Ledesma from Koneksys for his effort!
• Lyo Designer now allows modelling SHACL shapes. Code generation of SHACL shapes has not been implemented yet. If this is something you need, get in touch! Thanks to Yash Khatri from SCANIA for this contribution.
• Lyo Designer now allows to generate OpenAPI/Swagger documentation for your OSLC Server; see the details below. Thanks to Jad El-khoury and SCANIA for this contribution.
• Turtle support is now turned on by default in Lyo Designer for the generated code.
• Support for OSLC Query has been added to Lyo Store. Thanks to Jad El-khoury and SCANIA for this contribution.
• OpenJDK 11 has been added to the test matrix for most repos. JDK 11 is not yet supported officially, however.
• A lyo repository has been added to manage all cross-cutting issues that span multiple repos.
• Kotlin is now used for unit tests in Lyo Core.

Swagger Docs

Dear Lyo users,

It is my pleasure to announce on behalf of the project team that Lyo 2.3.0 has been released! 🚀

The release artefacts are available on Maven and the Eclipse plugins are available from Lyo P2 repository.

Notable changes:

• 🔥 switch the SDK to use Jena 3.0
• 🔧 many improvements to Lyo Designer and code generator, including vocabulary modelling view, Turtle support out of the box and switch to user-friendly Bootstrap templates.
• ✨ new library for validation against constraints defined either as SHACL or OSLC Resource Shapes https://github.com/eclipse/lyo-validation

2.3.0 release page on Eclipse.

We are delighted to announce today the Lyo 2.2.0 release! The artefacts are available immediately from the Eclipse maven repository, the Lyo Toolchain Designer is available for download from the Lyo P2 update site.

Main features of the 2.2.0 release are:

✨ Lyo Toolchain Designer plugin

The Lyo Toolchain Designer plugin is now officially released as part of the Lyo project. Toolchain Designer allows you to graphically model a complete OSLC toolchain (including interactions between OSLC servers and clients), as well as a single server and/or client. From such models, the Lyo Code Generator can then automatically generate an almost complete OSLC4J-compliant Java web project. To model and generate your first toolchain, follow the Lyo Designer tutorial.

Eclipse Lyo 2.1.2 is the first release since 2013 done by the new release team and fixes many issues in Lyo Core & Lyo Client.

Please participate in this survey, the results will help to initiate the ALM-PLM Interoperability Workflow Forum from the ProSTEP iViP Association

The OSLC steering committee is gathering feedback from the community to help shape the future vision and mission for OSLC.

The OASIS OSLC Core 3.0 Specifications represent the continued evolution of OSLC through collaborating organizations to provide the standards, APIs and tools that support integrated product, system and application lifecycle management.

OpenPDM OSLC Adapter enables PLM systems to connect to the OSLC world. It offers OSLC standard services, especially for those PLM systems which don’t offer native ones.

Tasktop announced the latest versions of its Tasktop Sync and Tasktop Data products, which add strategic new tools to its integration network and provide a vastly superior user experience.

The September 2015 elections for the OASIS OSLC Steering Committee have concluded.

The Open Services Communication User Group held its kickoff call on August 13. The team is positioned to highlight integration successes and communicate the benefits of OSLC.

If you're interested in working with other leaders in this space and helping influence the direction and expansion of OSLC, consider becoming a member of OASIS OSLC Steering Committee.

The updated site is live.

Coming in a couple weeks is IBM's new InterConnect conference which brings together past IBM events (Innovate, Pulse, Impact) into one.