While looking for an alternative to JSON and YAML, I found Rec. It seems a good alternative to create a text oriented database, easy to edit, share and export. Here an example with two publications from README.md`:
%rec: Publication
%mandatory: Date Title Urls
Date: 2023-09-27
Title: A monitoring tool for linear-time 𝜇HML
Abstract: We present detectEr, a monitoring tool that targets software
+ applications written for Erlang/OTP. The tool runtime checks
+ specifications expressed in a safety fragment of the linear-time
+ modal 𝜇-calculus called MAX HML D , used to describe properties
+ about the current system execution. Our technical development is
+ founded on previous theoretical results that are lifted to a
+ first-order setting, where systems produce executions containing
+ events that carry data. We overview the main features of detectEr,
+ showing how properties can be flexibly written and synthesised as
+ executable Erlang monitors that can be instrumented with the running
+ system.
DOI: https://doi.org/10.1016/j.scico.2023.103031
Urls: http://staff.um.edu.mt/afra1/papers/linearDetectErSCP2024.pdf
Authors: Luca Aceto
Authors: Antonis Achilleos
Authors: Duncan Paul Attard
Authors: Léo Exibard
Authors: Adrian Francalanza
Authors: Anna Ingólfsdóttir
Keywords: Runtime verification
Keywords: Linear-time properties
Keywords: Monitor synthesis
Keywords: detectEr
Keywords: MAXHML
Date: 2023-05-31
Title: Effective integration of low-cost digital manufacturing systems: a reference architecture driven approach
Urls: https://www.tandfonline.com/doi/full/10.1080/0951192X.2024.2314785
DOI: https://doi.org/10.1080/0951192X.2024.2314785
Keywords: System integration
Keywords: low-cost
Keywords: digital manufacturing
Keywords: reference architecture
Why using Rec instead of JSON or YAML? (1) a full implementation already exist to define constraints and edit rec files (2) the format is flexible (3) it will probably help people to add more content in this list because of the open format (4) we can easily export it into mnesia or an ets table (5) a simple subset of Rec format can easily be implemented.
While looking for an alternative to JSON and YAML, I found Rec. It seems a good alternative to create a text oriented database, easy to edit, share and export. Here an example with two publications from README.md`:
Why using Rec instead of JSON or YAML? (1) a full implementation already exist to define constraints and edit rec files (2) the format is flexible (3) it will probably help people to add more content in this list because of the open format (4) we can easily export it into mnesia or an ets table (5) a simple subset of Rec format can easily be implemented.