📜 Release LexFCS Specification v0.3

General
1

Version 0.3 of the LexFCS specification has been released. It can be considered stable with regards to the data model, the FCS Data Views and Endpoint Description. A few additions to the specification are still planned and being tested in Text+ but those changes are optional and therefore backwards compatible. Centres planning to implement their own LexFCS endpoints are welcome to do so and should not have to fear breaking changes.

What does LexFCS v0.3 contain?

The LexFCS v0.3 specification can be considered semi-final. A few additions are planned but the framework to support lexical resources in the FCS is more or less finished.

The LexFCS specification describes the
(a) data model, which is basically an entry with different information fields like lemma, pos, etymology, sentiment, synonym, ref, …, the corresponding
(b) Lex Data View, to serialize results, and
(c) LexCQL query language, and
(d) the extensions to the Endpoint Description, to describe “supported Lex Fields”, i.e. which information fields a lexical resource supports for querying and what is returned.

Resources about LexFCS

Software support?

The CLARIN Java SRU/FCS libraries have been updated to support LexFCS v0.3.

For FCS Endpoints the dependencies are:

For FCS Clients those are:

The FCS SRU Aggregator and FCS Endpoint Valiator have also been updated to support LexFCS.

More FCS resources are listed in the Awesome FCS list.

See LexFCS in action

LexFCS was proposed and developed in Text+ / Germany. There are already a few FCS Endpoints implementing LexFCS and offering lexical resources. The majority of resources is still in German (for now).

LexFCS Demo with custom frontend (see forum post) and great visualization of the new Lex Data View: Text+ FCS Vuetify Playground

LexFCS Aggregator: https://fcs.text-plus.org/ and https://alpha-fcs.text-plus.org/

Future plans

The FCS SRU Aggregator (aka CLARIN ContentSearch) is currently being refactored to improve the code base (better reusability) and new frontend (demo, code). Support for LexFCS will then be built-in for the Lex Data View and offer a new LexCQL query builder.