nmo:Message: Tracker Ontology Reference Manual

## nmo:Message nmo:Message |

## Description

A message. Could be an email, instant messanging message, SMS message etc.

This class emits notifications about changes, and can be tracked through the `GraphUpdated` DBus signal.

## Class hierarchy

        rdfs:Resource
        ╰── nie:InformationElement
            ╰── nfo:Document
                ╰── nfo:TextDocument
                    ╰── nmo:Message
                        ├── nmo:Email
                        ├── nmo:IMMessage
                        ├── nmo:Call
                        ├── nmo:PhoneMessage
                        ╰── mfo:FeedMessage

## Full-text-indexed properties

nmo:Message has the following full-text-indexed properties:

- nmo:messageSubject

## Properties

### The `“nmo:mmsId”` property

    “nmo:mmsId”          xsd:string

Unique identifier of an MMS message. It comes from the server

Number of possible elements per resource (Cardinality): 1

### The `“nmo:mustAnswerReportRead”` property

    “nmo:mustAnswerReportRead”          xsd:boolean

The message came with the report-read flag enabled, and somebody must be send the answer back. Once the report is sent, this property goes to False.

Number of possible elements per resource (Cardinality): 1

### The `“nmo:reportReadStatus”` property

    “nmo:reportReadStatus”          nmo:ReportReadStatus

If the message was sent with report read enable, this property stores the status of that message: if the recipient has read it, delete it, or we are still waiting for an answer

Number of possible elements per resource (Cardinality): 1

### The `“nmo:sentWithReportRead”` property

    “nmo:sentWithReportRead”          xsd:boolean

The message has been send with a flag indicating that we want to receive a confirmation when the recipient reads it

Number of possible elements per resource (Cardinality): 1

### The `“nmo:reportDelivery”` property

    “nmo:reportDelivery”          xsd:boolean

Report delivery has been requested for the message

Number of possible elements per resource (Cardinality): 1

### The `“nmo:deliveryStatus”` property

    “nmo:deliveryStatus”          nmo:DeliveryStatus

Number of possible elements per resource (Cardinality): 1

### The `“nmo:hasAttachment”` property

    “nmo:hasAttachment”          nfo:Attachment

Number of possible elements per resource (Cardinality): Unlimited

### The `“nmo:communicationChannel”` property

    “nmo:communicationChannel”          nmo:CommunicationChannel

Connects this message to a communication channel. Every message must only be in a single channel.

Number of possible elements per resource (Cardinality): Unlimited

### The `“nmo:conversation”` property

    “nmo:conversation”          nmo:Conversation

Connects this message to a conversation. Every message must only be part of a single conversation.

Number of possible elements per resource (Cardinality): 1

### The `“nmo:cc”` property

    “nmo:cc”          nco:Contact

Number of possible elements per resource (Cardinality): Unlimited

### The `“nmo:bcc”` property

    “nmo:bcc”          nco:Contact

Number of possible elements per resource (Cardinality): Unlimited

### The `“nmo:to”` property

    “nmo:to”          nco:Contact

Number of possible elements per resource (Cardinality): Unlimited

### The `“nmo:sender”` property

    “nmo:sender”          nco:Contact

Number of possible elements per resource (Cardinality): 1

This property supersedes the following properties from this or parent classes:

- `“nmo:recipient”` from the `nmo:Message` class

### The `“nmo:replyTo”` property

    “nmo:replyTo”          nco:Contact

Number of possible elements per resource (Cardinality): 1

### The `“nmo:receivedDate”` property

    “nmo:receivedDate”          xsd:dateTime

Number of possible elements per resource (Cardinality): 1

### The `“nmo:messageSubject”` property

    “nmo:messageSubject”          xsd:string

Number of possible elements per resource (Cardinality): 1

This property is full-text-indexed, and can be looked up through `fts:match`.

### The `“nmo:messageId”` property

    “nmo:messageId”          xsd:string

Number of possible elements per resource (Cardinality): 1

### The `“nmo:messageHeader”` property

    “nmo:messageHeader”          nmo:MessageHeader

Number of possible elements per resource (Cardinality): Unlimited

### The `“nmo:inReplyTo”` property

    “nmo:inReplyTo”          nmo:Message

Number of possible elements per resource (Cardinality): Unlimited

This property supersedes the following properties from this or parent classes:

- `“nmo:references”` from the `nmo:Message` class

### The `“nmo:references”` property

    “nmo:references”          nmo:Message

Number of possible elements per resource (Cardinality): Unlimited

### The `“nmo:htmlMessageContent”` property

    “nmo:htmlMessageContent”          xsd:string

Number of possible elements per resource (Cardinality): 1

### The `“nmo:isEmergency”` property

    “nmo:isEmergency”          xsd:boolean

Special message from the network, probably coming via Cell broadcasting with emergency information

Number of possible elements per resource (Cardinality): 1

### The `“nmo:isSent”` property

    “nmo:isSent”          xsd:boolean

Number of possible elements per resource (Cardinality): 1

### The `“nmo:isRead”` property

    “nmo:isRead”          xsd:boolean

The messsage has been readed. The user has opened the message or has marked it directly as readed

Number of possible elements per resource (Cardinality): 1

### The `“nmo:isDraft”` property

    “nmo:isDraft”          xsd:boolean

The user hasn't finished editing the message and might want to continue later

Number of possible elements per resource (Cardinality): 1

### The `“nmo:isDeleted”` property

    “nmo:isDeleted”          xsd:boolean

True when the user has removed the Email in the UI but still exists in the DB. Usually a purge or confirmation from the user will actually remove the data.

Number of possible elements per resource (Cardinality): 1

### The `“nmo:isAnswered”` property

    “nmo:isAnswered”          xsd:boolean

True when the user has sent a replay to this message

Number of possible elements per resource (Cardinality): 1

### The `“nmo:from”` property

    “nmo:from”          nco:Contact

The sender of the message.

Number of possible elements per resource (Cardinality): 1

### The `“nmo:recipient”` property

    “nmo:recipient”          nco:Contact

Number of possible elements per resource (Cardinality): Unlimited

### The `“nmo:sentDate”` property

    “nmo:sentDate”          xsd:dateTime

Date when this message was sent.

Number of possible elements per resource (Cardinality): 1

## See also

The upstream documentation for the NMO ontology.