Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Sources data model #11
Some elements I missed to include in this SCS:
I'll add these later on.
It might also be interesting to notice that the events properties that are related to signatures might be inconsistent with the naming in other parts of the specs. Basically, we're waiting on #7 (i.e. figuring out whether relying on Matrix's cryptographic features to sign our events is possible) to be complete before harmonising this whole part of the specs and adding some technical details and advices on signature generation.
left a comment
I propose we add a LocalisedString object, that maps language code to string text, to use for some source fields like name & description, and eventually other fields or other events' fields.
We also need to add a section about source fields that can be overridden by sub-source fields (namely
Also I haven't seen anything about the network.informo.source event being signed by the source user. My first idea was to sign the event using one of the source's previous keys (or any key if it's the first source event), but it requires fetching the entire state event history in order to check if a source event is correctly signed.
From what I remember from our discussions about this, we concluded that the