Proposals
The ComMA language allows the specification of the provided and required interfaces of a software component. Each interface is described by means of (1) a signature, i.e., the set of commands, signals and notifications that are offered by a server, (2) a protocol state machine which describes the allowed sequences of interaction events between clients and server, (3) timing constraints on the occurrence of the events, and (4) data constraints on the values communicated. For a component, constraints can be added on the relations between its interfaces.
A language server implementation based on the Language Server Protocol for the Jakarta EE programming model. This LSP4Jakarta (Language Server for Jakarta EE) will provide core language support capabilities (such as code complete, diagnostics, quick fixes) to enable developers to easily and quickly develop cloud-native applications using the Jakarta EE APIs.
The Eclipse client for the Language Server for Jakarta EE will surface the capabilities provided by the language server to developers using the Eclipse (desktop) IDE.
Machine learning (ML)-based functions – especially methods that continue the learning process online – cannot be approved by current methods and standards (e.g. ISO 26262). One approach to address this issue is to introduce an online verification module, that constantly checks and guarantees the function of interest to stay within safe bounds. That way, safety guarantees can be provided for an ML-based function.
The tool will be developed using web technologies in a way that allows to easily integrate and embed it into other web applications. The tool will cover the following features:
- Creating a new Thing Description (Template) from scratch
- Rendering a Thing Description (Template)
- Editing the Thing Description (Template)
- Validating the Thing Description (Template)
- Exporting the Thing Description (Template) from the visual representation into JSON-LD
The Eclipse Digital Cockpit provides an Edge Runtime focused on industrial automation. It stands somewhere between a simple Edge Runtime, an "Android for the machine" and a lightweight "Application Server" where services and Apps can be deployed to.
Besides the Edge Runtime there are multiple backends like an App Store (under development) or a Telemetry Backend which takes telemetry values that Apps or Services from the Cockpit send out.
Most importants services for common concerns are
Define an MQTT Topic Namespace
The intent of the Sparkplug specification is to define and document a Topic Namespace that is well thought out and optimized for the SCADA/IIoT solution sector.
Define an MQTT Payload
The intent of the Sparkplug specification is to strive to define payload encoding architectures that remain true to the original, lightweight, bandwidth efficient, low latency features of MQTT while adding modern encoding schemes targeting the SCADA/IIoT solution sector.
Eclipse WaSP implements Jakarta Pages, a technology that helps software developers create dynamically generated web pages based on HTML, XML, or other document types.
A language server implementation based on the Language Server Protocol for Eclipse MicroProfile programming model. This Language Server for Eclipse MicroProfile (LSP4MP) will provide core language support capabilities (such as code complete, diagnostics, quick fixes) to enable developers to easily and quickly develop cloud-native applications using MicroProfile APIs.
The Eclipse Arrowhead project consists of systems and services that are needed for anyone to design, implement and deploy Arrowhead-compliant System of Systems. The generic concept of the Arrowhead Framework is based on the concept of Service Oriented Architectures, and aims at enabling all of its users to work in a common and unified approach – leading towards high levels of interoperability.