Recent Releases of dekalog
dekalog - Fix of bad date formatting
Multiple fixes, notably the fixe of the incorrect date formatting
- JavaScript
Published by MaillPierre almost 4 years ago
dekalog - Kartographi working with cache
- Major internal rework of KartoGraphI to use query results stored in json files instead of querying the IndeGx SPARQL endpoint
- JavaScript
Published by MaillPierre about 4 years ago
dekalog - New rewriting, new tests, advances in KartoGraphI,
- The original asserted metadata is no longer stored in the index, due to internal compatibility problems and problems with the virtuoso endpoint
- The dataset, endpoint, metadata, graph lists, class and property partitions resources are now generated from the MD5 hash of their endpoint URL.
- Multiple bugs and fixes, notably, the unfindable description from WASABI is now found
- Large extension of the KartoGraphI website
- JavaScript
Published by MaillPierre over 4 years ago
dekalog - Bugfix for chained interactions
- Fixing a bug that failed the application of interactions triggering others
- JavaScript
Published by MaillPierre over 4 years ago
dekalog - Log4j upgrade
- Minor fixes
- Change of the version of Log4j because of the log4shell exploit
- JavaScript
Published by MaillPierre over 4 years ago
dekalog - Catalog generation
- Generation of a proper DCAT catalog
- Addition of numerous example queries to the root of the catalog
- Multiple bug and rule fixes
- JavaScript
Published by MaillPierre over 4 years ago
dekalog - Fixes for experimentation
- More bugfixes
- re-factoring for the index generation
- JavaScript
Published by MaillPierre over 4 years ago
dekalog - Catalog reading
- Multiple bugfixes
- SPARQLES tests to determine the SPARQL coverage of an endpoint have been implemented
- A new main class implement the reading of a file or an endpoint containing a DCAT catalog of data to extract the description of each of them
- Rules can use external sources, such as LOV, for their tests and actions
- JavaScript
Published by MaillPierre over 4 years ago
dekalog - Rule trigger on Success or Failure
- Rules can now trigger action in case of success or failure of their test. It is also possible to trigger other rules in this manner.
- Rules that use a federation server need to use a specific resource as an endpoint (kgi:federation) which will be replaced by the URL given to the generation executable
- Reorganisation of the files
- Start of the definition of rules to determine the coverage of the SPARQL features of an endpoint.
- JavaScript
Published by MaillPierre almost 5 years ago
dekalog - Another endpoint in a rule
- Usage of a secundary endpoint in rule possible. Made to interface with a local federation server (namely, a Corese server).
- Merging of the application and rules project, reorganisation of the files.
- JavaScript
Published by MaillPierre almost 5 years ago