Sergio,

I would go with STON, as advised by Norbert (I don't have experience with Soil). One of the nice things of STON is that you can use whatever DVCS you like to versionate your data. For example, we locally use Fossil, while most people prefer Git.��

STON is super versatile! As an example, I used it with Grafoscopio, my Pharo powered interactive outliner/documenter, to store notebooks with Markdown stored inside STON, as you can see in [1]. And now I flipped that idea and I'm using STON to embed notebooks metadata inside Markdeep. In this way anyone can read notebooks directly in the web, without specialized software. [1a] is just the same document in [1] but with this flipped format idea (if you,re even more curious, look at the source code of the page at [1a] and you�� will find that the STON representation of notebook cell/node medatada is pretty light and readable).

[1] https://mutabit.com/repos.fossil/indieweb/file?name=indieweb.ston&ci=tip
[1a] https://mutabit.com/repos.fossil/indieweb/doc/tip/indie-web--25zqu.md.html

This is just an example of how STON allowed us to port lessons��learned from Grafoscopio, made in 2016, to Lepiter, released in 2021, ensuring longevity of our community memory and data. Hopefully you will find STON pretty empowering in your own experiments.

Cheers,

Offray

On 18/01/24 9:37, Norbert Hartl wrote:


Am 18.01.2024 um 14:54 schrieb sergio ruiz <sergio.rrd@gmail.com>:

Using this Will my links remain viable using this method?

Meaning that an event has a theater. That theater is also in the OrderedCollection of Theaters.

If the name of he theater changed in the Theaters collection, will that name change occur in the event theater object?

After bringing these collections back in via STON, will all of these relationships remain intact?

If with relationship you mean that one object event has a reference to a theater object then yes. STON serializes the graph as objects and all references will be reestablished on materialization.

Norbert



On Jan 18, 2024, at 8:26���AM, Norbert Hartl <norbert@hartl.name> wrote:

If you have three classes with class side collections you can have a make e.g. a dictionary and put the collections from the class side into it like��

model := {
�� ��#theaters -> Theater instances.
�� ��#movies -> Movie instances.
�� ��#event -> Event instances.
} asDictionary.



----
peace,
sergio
photographer, journalist,��visionary

Public Key:��https://pgp.key-server.io/pks/lookup?op=get&search=0x69B08F58923AB3A2
#BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV
@sergio_101@mastodon.social