Elektrine lite

← Feed

@ocratato@discuss.systems

Post #2153649

2026-05-02 02:56 UTC

The Next Phase of SASSY This morning I was contemplating what to do next on the SASSY project. The infrastructure is now mostly in place, so its time to move up a level. The make or break part of the project is getting the data out of the knowledge base. Its all a bit pointless without that capability. In order to get stuff out, it must first go in. Hence the next level will be support for data entry. There appears to be three classes of data entry: The first is the classical style for any database application, where the schema is used to design the program. This is for those schemas that are provided as a part of the distributed system. The second class is for project specific schemas. In this scenario the developers are creating and updating the schemas as they discover aspects of the project's domain. The data entry programs need to dynamically follow the evolving schemas. The third class is for a pure discovery task. This will be something like a mind mapping program where a graph of ideas and concepts is constructed during the initial investigations for the proposed system. 1/n #SASSY

Replies (1)

  • @ocratato@discuss.systems 2026-05-02 03:55

    The Next Phase of SASSY (2) The core task of the data entry system is to create a data entry form from an RDF schema. I have created a simple instance of this, but it is quite limited in both its abilities and its style. Something more flexible would be nice. I am thinking that an Entry Form Language would be a useful middle ground between the schemas and whatever it is that implements the data entry system. This would be an RDF schema that defined the elements of entry forms. Specific forms would be created from a combination of schema data and style information. As a proof of concept I will have a look at Qt's QML. It is a language for defining user interfaces, and appears to have both static and dynamic capabilities. It can therefore support both the classical data entry task as well as something that evolves with the user's new schemas. 2/n #SASSY

    Open ##2585525