logos-messaging/specs
1
0
Fork 0
mirror of https://github.com/logos-messaging/specs.git synced 2026-05-24 05:49:37 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update background context

Browse Source
This commit is contained in:
Jazz Turner-Baggs 2026-05-22 15:47:52 -07:00
parent 4d9de1d746
commit a78e10ca1b
No known key found for this signature in database
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
standards/application/chat-framework.md
View File

@ -16,13 +16,12 @@ This specification defines a modular communication protocol framework for descri
Chat protocols specifications can be long and dense documents. To fully describe a chat protocol there are many layers and operations which are required to be documented. This includes payloads, message transport, encryption as well as user level features such as account registration, typing indicators, content formatting. Chat protocols specifications can be long and dense documents. To fully describe a chat protocol there are many layers and operations which are required to be documented. This includes payloads, message transport, encryption as well as user level features such as account registration, typing indicators, content formatting.
With the vast amount of information required to maintain compatibility between applications - protocol documentation is either comprehensive which leads to large monolithic specifications or lacking the required details for interop between implementors. With the vast amount of information required to maintain compatibility between applications - protocol documentation is either comprehensive which leads to large monolithic specifications or lacking the required details for interop between implementors. A suitable solution would provide both the specificity while also remaining lean and focused.
# Theory / Semantics # Theory / Semantics
This specification defines an abstract framework for building a chat protocol. Its purpose is to name the components, and define modular boundaries between components to promote reuse. The end result is that a chat protocol implementation can be described by listing its approach to 5 problem areas. This specification defines an abstract framework for building a chat protocol. Its purpose is to name the components, and define modular boundaries between components to promote reuse. The end result is that a chat protocol implementation can be described by listing its approach to 5 problem areas.
The chat protocol is decomposed into 3 distinct phases. The chat protocol is decomposed into 3 distinct phases.
- **Discovery:** How does a Sender learn of other clients. - **Discovery:** How does a Sender learn of other clients.
@ -35,6 +34,7 @@ and transport details are divided into:
- **Framing Strategy:** How are payloads encoded. - **Framing Strategy:** How are payloads encoded.
Defining these 5 parameters allows for chat protocol implementations to be fully defined, which allows clients from different applications to exchange messages. Defining these 5 parameters allows for chat protocol implementations to be fully defined, which allows clients from different applications to exchange messages.
While also dividing documents by their focus area.
## Abstract Transport ## Abstract Transport