Xtext simplifies the creation of DSLs. This is particularly true for syntax and basic aspects of semantics such as scoping and validation in general. An important part of validation are static type systems. In computer science, formal type systems are a well-known concept and they are defined using operational semantics. Eclipse Xsemantics aims at minimizing the gap between the formalization of a language and the actual implementation in Xtext. It is thought to be used by people who are at least somewhat familiar with formal type systems and operational semantics: it aims at providing a syntax which resembles how deduction rules are written in a formal setting.
The scope of Eclipse Xsemantics is to provide a DSL for writing rules for languages implemented in Xtext, particularly the static semantics (type system), the dynamic semantics (operational semantics) and relation rules (subtyping), and it provides a generator to create a Java implementation based on these rules to be used in Xtext validations.
Eclipse Xsemantics is a DSL (implemented in Xtext itself) for writing type systems, reduction rules, interpreters and general relation rules for languages implemented in Xtext. A system definition in Xsemantics is a set of judgment rules which have a conclusion and a set of premises. Xsemantics then generates Java code that can be used in your Xtext-based language for scoping and validation.
Eclipse Xsemantics is based on Eclipse Xtext (and Xbase in particular). It is to be used for Xtext-based languages and, as such, it is dependent on, and provides support for, this Eclipse project. Other Eclipse projects using Xtext may use Xsemantics to model the type system of their DSL. This is already true for Eclipse N4JS which heavily relies on Xsemantics.
Hosting Xsemantics at Eclipse dramatically simplifies using it in other Eclipse projects such as N4JS.
A build process similar to other Eclipse projects is already in use, so it should be possible to quickly set up an Eclipse project with a nightly build once approval has been granted and the initial contribution has gone through the due diligence process.
The current version is already stable (the first version has been created in 2012) and has been in production mode (as part of other projects, e.g., Eclipse N4JS) for years. Fixing bugs and adding minor improvements is ongoing work, of course. Adding new features highly depends on the needs of projects using Xsemantics. Simplifying cooperation with existing (or new) projects within Eclipse or related to Eclipse/Xtext is one of the goals of bringing Xsemantics to Eclipse.