Mirror of the Rel4tion website/wiki source, view at <http://rel4tion.org>
Clone
HTTPS:
git clone https://vervis.peers.community/repos/yEzqv
SSH:
git clone USERNAME@vervis.peers.community:yEzqv
Branches
Tags
plans.mdwn
Purpose
Design conceptual implementation plans for the various app types listed in app-types). These plans will help me design an overall architecture.
Hacking Tools
Before I take care of the app types, I’d like to discuss hacking tools.
Behind many desktop applications stand lower level technologies which are sometimes not visible to the user. For example, many applications use XML files to store data, networking APIs, string conversion tools, document transformations and many other things. These technologies have their own sets of tools, e.g. XML parsing/writing/conversion programs. The same concept applies here.
While desktop apps are concerned with satisfying the user’s needs and examining high-level requirements, a library/tool/API designer needs to take care of the applications’ needs. A new language or file format will require scripts, tools and APIs for manipulating, parsing and converting files to and from other formats.
I will make two lists here:
- List of results the tools should be able to deliver, or may be able to deliver (i.e. ideas)
- List of tools / programs / scripts / functions
These are just ideas - some of them may not be worth a direct implementation and then the same result can be acheived through the high-level main architecture.
Results
fill
Tools
- Do changes to file/database using an operation language (like SPARQL update) or with CLI commands
- Get queries from file/database using a query language (like SPARQL) or with CLI commands
High Level
Here I’m going to make plans for app types.
- Data in Plain Text
fill
- Data Editor
fill
- Ontology in Plain Text
fill
- Ontology Editor
fill
- Content Reader
fill
- Content Editor
fill