Tracker Ontology Reference Manual: NMO Ontology Classes

## NMO Ontology Classes

### nmo:IMMessage

`Superclasses` : | nmo:Message,
`Subclasses` : | --
`In domain of` : | --
`In range of` : | --

### nmo:Email

Root node in a MIME Email

`Superclasses` : | nmo:Message,
`Subclasses` : | --
`In domain of` : | nmo:contentMimeType, nmo:responseType, nmo:status, nmo:isRecent, nmo:isFlagged, nmo:hasContent,
`In range of` : | --

### nmo:PermanentChannel

Well-known stable channel like an IRC room in a specific server. Predefined URL schema for the instances is recommended

`Superclasses` : | nmo:CommunicationChannel,
`Subclasses` : | --
`In domain of` : | --
`In range of` : | --

### nmo:Attachment

`Superclasses` : | nfo:Attachment, nmo:MimePart,
`Subclasses` : | --
`In domain of` : | --
`In range of` : | --

### nmo:MMSMessage

An MMS message is basically a Email with different envelop. It inherits also from SMS the folders and delivery status

`Superclasses` : | nmo:PhoneMessage,
`Subclasses` : | --
`In domain of` : | nmo:mmsHasContent,
`In range of` : | --

### nmo:MimePart

`Superclasses` : | nfo:EmbeddedFileDataObject,
`Subclasses` : | nmo:Attachment,
`In domain of` : | nmo:mimeHeader, nmo:contentDisposition, nmo:contentDescription, nmo:contentTransferEncoding, nmo:contentId, nmo:charSet,
`In range of` : | nmo:mmsHasContent, nmo:hasContent,

### nmo:VOIPCall

`Superclasses` : | nmo:Call,
`Subclasses` : | --
`In domain of` : | --
`In range of` : | --

### nmo:Call

Phone call. Voice communication with the user with somebody else.

`Superclasses` : | nmo:Message,
`Subclasses` : | nmo:VOIPCall,
`In domain of` : | nmo:duration,
`In range of` : | --

### Note:

This class notifies about changes

### nmo:MessageHeader

Pairs key=value to store arbitrary message header. Note that if a property exists already in the ontology for those headers it should be used. This is just a safe guard mechanism.

`Superclasses` : | rdfs:Resource,
`Subclasses` : | --
`In domain of` : | nmo:headerValue, nmo:headerName,
`In range of` : | nmo:messageHeader,

### nmo:Multipart

`Superclasses` : | nfo:DataContainer,
`Subclasses` : | --
`In domain of` : | nmo:partBoundary,
`In range of` : | --

### nmo:Message

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

`Superclasses` : | nfo:TextDocument,
`Subclasses` : | nmo:PhoneMessage, nmo:Call, nmo:IMMessage, nmo:Email,
`In domain of` : | nmo:mmsId, nmo:mustAnswerReportRead, nmo:reportReadStatus, nmo:sentWithReportRead, nmo:reportDelivery, nmo:deliveryStatus, nmo:hasAttachment, nmo:communicationChannel, nmo:conversation, nmo:cc, nmo:bcc, nmo:to, nmo:sender, nmo:replyTo, nmo:receivedDate, nmo:messageSubject, nmo:messageId, nmo:messageHeader, nmo:inReplyTo, nmo:references, nmo:htmlMessageContent, nmo:isEmergency, nmo:isSent, nmo:isRead, nmo:isDraft, nmo:isDeleted, nmo:isAnswered, nmo:from, nmo:recipient, nmo:sentDate,
`In range of` : | nmo:inReplyTo, nmo:references,

### Note:

This class notifies about changes

### nmo:MailAccount

`Superclasses` : | nie:InformationElement,
`Subclasses` : | --
`In domain of` : | nmo:signature, nmo:fromAddress, nmo:accountDisplayName, nmo:accountName,
`In range of` : | --

### nmo:TransientChannel

Channel created ad-hoc for the communication like a multi chat in some systems

`Superclasses` : | nmo:CommunicationChannel,
`Subclasses` : | --
`In domain of` : | --
`In range of` : | --

### nmo:Conversation

A conversation. An exchange of one or multiple messages within a time frame or about a specific topic.

`Superclasses` : | nie:InformationElement,
`Subclasses` : | --
`In domain of` : | --
`In range of` : | nmo:conversation,

### nmo:CommunicationChannel

A communication channel. The container for all messages between participants of a specific group or in a persistent channel.

`Superclasses` : | nie:InformationElement,
`Subclasses` : | nmo:TransientChannel, nmo:PermanentChannel,
`In domain of` : | nmo:hasParticipant, nmo:lastSuccessfulMessageDate, nmo:lastMessageDate,
`In range of` : | nmo:communicationChannel,

### nmo:PhoneMessageFolder

Folder for phone message (SMS and MMS). Not a subclass of nfo:Folder because it would confuse filesystem folders

`Superclasses` : | nie:InformationElement,
`Subclasses` : | --
`In domain of` : | nmo:containsPhoneMessage, nmo:containsPhoneMessageFolder, nmo:phoneMessageFolderId,
`In range of` : | nmo:containsPhoneMessageFolder,
`Predefined instances` : | nmo:predefined-phone-msg-folder-myfolder, nmo:predefined-phone-msg-folder-sent, nmo:predefined-phone-msg-folder-draft, nmo:predefined-phone-msg-folder-outbox, nmo:predefined-phone-msg-folder-inbox,

### nmo:MailboxDataObject

`Superclasses` : | nie:DataObject,
`Subclasses` : | --
`In domain of` : | --
`In range of` : | --

### nmo:SMSMessage

Plain SMS Message

`Superclasses` : | nmo:PhoneMessage,
`Subclasses` : | --
`In domain of` : | --
`In range of` : | --

### nmo:PhoneMessage

Superclass with shared properties between SMS and MMS.

`Superclasses` : | nmo:Message,
`Subclasses` : | nmo:MMSMessage, nmo:SMSMessage,
`In domain of` : | nmo:validityPeriod, nmo:phoneMessageId, nmo:encoding, nmo:fromVCard, nmo:toVCard,
`In range of` : | nmo:containsPhoneMessage,

### nmo:ReportReadStatus

Predefined set of read status instances

`Superclasses` : | rdfs:Resource,
`Subclasses` : | --
`In domain of` : | --
`In range of` : | nmo:reportReadStatus,
`Predefined instances` : | nmo:read-status-unknown, nmo:read-status-deleted, nmo:read-status-read,

### nmo:MailFolder

`Superclasses` : | nfo:Folder,
`Subclasses` : | --
`In domain of` : | nmo:serverUnreadCount, nmo:serverCount, nmo:folderName,
`In range of` : | --

### nmo:DeliveryStatus

Predefined set of delivery status instances

`Superclasses` : | rdfs:Resource,
`Subclasses` : | --
`In domain of` : | --
`In range of` : | nmo:deliveryStatus,
`Predefined instances` : | nmo:delivery-status-permanently-failed, nmo:delivery-status-temporarily-failed-offline, nmo:delivery-status-temporarily-failed, nmo:delivery-status-delivered, nmo:delivery-status-sent,