First impression on Review Board.

There is a website you may want to read when thinking about a project.

From Jekyll to Astro.

This project aims to reimagine how we work with libraries.

Integration of code reviews into development process can enhance code quality. Code reviews are integrated as part of the public tools and repositories, such as GitLab or GitHub. Yet often code review is limited to the scope of a change, like a pull request. This can be sufficient for day to day operation, but it is not suitable for external or complete reviews. Objective is to create an online tool that would address this short coming.

There are many ways how to define a data schema: JSON Schema, RDFS, or code. We also have plenty of visualisation techniques like UML or ER-Model. So it should be simple to take your schema and visualise it right? Well, I've tried and I was unable to find, as of 2023, any suitable online tool to get the job done. We can try to change this together.

The aim is to make data available in multiple representations as requested by the user.

Linked data is five start data format, with promises of semantics and interoperability. Yet viewing, the basic operation, is not living up to the promise. The objective is to improve this situation and try to address not only linked data but RDF in general.

One of the core principles of linked data is to employ vocabularies to describe data in a machine-readable way. By doing so, data producers can significantly enhance data usability and interoperability. Findable, Interoperable, Accessible, and Reusable, or FAIR in short, vocabularies are enablers of the aforementioned. However, many vocabularies are not published in an easy-to-consume way. As a result, data publishers often resort to the design of their new proprietary vocabulary. While feasible, this approach decreases the value we would get from reuse and hinders data interoperability. The objective of this project is to tackle those issues.

We all may need to give a presentation at some point in time. Many presenters rely on slides as a cornerstone of their presentations. Those slides are created in software like PowerPoint and Google Slides, ... If you, like me, feel that there should be a better tool, you may consider reading the rest of this post.

Honestly, I do not enjoy writing documentation. By documentation, I do not mean comments in source code. I am talking about external documentation, API specification, data model, user documentation, database schema documentation, etc...

Yet frankly, even more, tedious and labour-intensive than writing the documentation is keeping it up to date. The reason is there is no connection between to code to the documentation. As a result, we manually synchronize multiple documents.

Many formats represent hierarchical data. Yet there is no single tool for transformation between those formats, with strict output control.

Semantic web, semantic data - the common objective is to attach meaning to the data and increase interoperability. Tools like vocabularies, ontologies, and query languages, are employed to support the above-mentioned goals. Yet while all the tools aim to add meaning to data, none is the source of true meaning.

Source code is the source of truth. We can leverage it to improve software interoperability and introduce semantics.

Resource Description Framework (RDF) is a standard data model. As RDF becomes widespread, more and more data are available in one of the RDF data formats. Yet no Python library would allow for the processing of larger RDF data files.

Resource Description Framework (RDF) is a standard data model. As RDF becomes widespread, more and more data are available in one of the RDF data formats. Yet no Python library would allow for the processing of larger RDF data files.