# Protocol Core ## Entity ID * Room alias: `#:` * Username: `@@` * User ID with MSISDN (Mobile Station International Subscriber Directory Number): `%:` * User ID with Email: `^_at_:` * Message ID: `&:` * Room ID: `!@` * Single server-part: `` **Server-part (hostname)** - `IPv4 / [IPv6] / dns-domain:`. **Username/Room alias/RoomID** - MUST NOT be empty, and MUST contain only the characters `a-z`, `0-9`, `.`, `_`, `=`, `-`, and `/`. RoomID SHOULD be UUID identifier. ## BaseMessage BaseMessage is a basic message model, basis of the whole protocol. It is used for a very easy protocol extension process. BaseMessage scheme: ``` id (string) - identifier of message (used to track the request-response chain) type (string) - type of message (used to determine which extension this message belongs to) from (EntityID) - from which entity this message is send to (EntityID) - message recipient ok (boolean) - operation success indicator (used to determine if errors was happened when processing request) payload (Map) - message payload (used to store extra information in message, list of permissible fields in the payload are depends on "type" field) ``` ## Errors Mechanism of error processing included into protocol. Adds into type name `:error` postfix. **Payload**: * `errCode: int` - error code (defined in extensions. Error code which defined in the specific extension MUST NOT overlap with other error codes) * `errText: String` - explanation of error in human-readable view * `errPayload: Map` - advanced error information (fields defined in extensions) **Example**: *Request*: ```json { "id": "abcd", "type": "incorrectMessageType", "from": "@juliet@cadmium.im", "to": "cadmium.im", "payload": { "test": "test" } } ``` *Response*: ```json { "id": "abcd", "type": "incorrectMessageType:error", "from": "cadmium.im", "to": "@juliet@cadmium.im", "payload": { "errCode": 0, "errText": "Incorrect type of message (type isn't implemented in the server)", "errPayload": {} } } ```