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

• master

Tags

model.mdwn

Purpose

Design the Model component of the Repository-Model-Application architecture.

Content

In order to design memory management, signals, etc. I need to decide the responsibilities of Model.

Responsibilities:

• Load data from file/database
• Track changes and update model
• Save model to file/database
• Update file/database with changes
• Do queries on in-memory data?

Memory/Signal options:

• Object created using ctor
• Object created using Object::create ()
• Object created using model.create_object ()

Question: How to model and store requirements? E.g. objects of given class must have a given property with a given default value and given cardinality constraints. Properties in general can have cardinality constraints.

1. Are they part of the semantic model?
2. Are they part of the database?
3. Do they require separate files/syntax?

The answers depend on my plans for constraint types, which should be made at ./language/expression-model/4-model/info.