A RIDDL repository is an abstraction for anything that can retain information(e.g. messages for retrieval at a later time. This might be a relational database, NoSQL database, data lake, API, or something not yet invented. There is no specific technology implied other than the retention and retrieval of information. You should think of repositories more like a message-oriented version of the Java Repository Pattern than any particular kind ofdatabase.
Value parameters
authors
The author(s) who wrote this repository specification.
brief
A brief description of this repository
description
A detailed description of this repository
handlers
The handler for specifying how messages should be handled by the repository
id
The unique identifier for this Repository
includes
Included files
loc
Location in the source of the Repository
options
Options that can be used by the translators
terms
Definitions of terms about this repository
types
The types, typically messages, that the Repository uses
Compute the completeness of this definition. Vital definitions should have options, terms, and authors but includes are optional. Incompleteness is signalled by child definitions that are empty.
Compute the 'maturity' of a definition. Maturity is a score with no maximum but with scoring rules that target 100 points per definition. Maturity is broken down this way:
has a description - up to 50 points depending on # of non empty lines
has a brief description - 5 points
has options specified - 5 points
has terms defined -
has an author in or above the definition - 5 points \-