Distinct objects for predicate rdfs:comment in graph nmo sorted by frequency with mapping to SKOS

ResourceCountSKOS mapping
"A Contact that is to receive a bcc of the email. A Bcc (blind carbon copy) is a copy of an email message sent to a recipient whose email address does not appear in the message."1
"A Contact that is to receive a cc of the email. A cc (carbon copy) is a copy of an email message whose recipient appears on the recipient list, so that all other recipients are aware of it."1
"A MIME entity, as defined in RFC2045, Section 2.4."1
"A common superproperty for all properties that link a message with its recipients. Please don't use this property directly."1
"A flag that states the fact that a MailboxDataObject has been read."1
"A mailbox - container for MailboxDataObjects."1
"A message sent with Instant Messaging software."1
"A message. Could be an email, instant messanging message, SMS message etc."1
"A superproperty for all "additional" recipients of a message."1
"An address where the reply should be sent."1
"An arbitrary message header."1
"An email."1
"An entity encountered in a mailbox. Most common interpretations for such an entity include Message or Folder"1
"An identifier of a message. This property has been inspired by the message-id property defined in RFC 2822, Sec. 3.6.4. It should be used for all kinds of identifiers used by various messaging applications to connect multiple messages into conversations. For email messageids, values are according to RFC2822/sec 3.6.4 and the literal value in RDF must include the brackets."1
"Date when this message was received."1
"Date when this message was sent."1
"HTML representation of the body of the message. For multipart messages, all parts are concatenated into the value of this property. Attachments, whose mimeTypes are different from text/plain or message/rfc822 are considered separate DataObjects and are therefore not included in the value of this property."1
"Key used to store the MIME type of the content of an object when it is different from the object's main MIME type. This value can be used, for example, to model an e-mail message whose mime type is"message/rfc822", but whose content has type "text/html". If not specified, the MIME type of the content defaults to the value specified by the 'mimeType' property."1
"Links a message with files that were sent as attachments."1
"Links the message with an arbitrary message header."1
"Name of the message header."1
"Plain text representation of the body of the message. For multipart messages, all parts are concatenated into the value of this property. Attachments, whose mimeTypes are different from text/plain or message/rfc822 are considered separate DataObjects and are therefore not included in the value of this property."1
"Signifies that a message is a reply to another message. This feature is commonly used to link messages into conversations. Note that it is more specific than nmo:references. See RFC 2822 sec. 3.6.4"1
"Signifies that a message references another message. This property is a generic one. See RFC 2822 Sec. 3.6.4"1
"The person or agent submitting the message to the network, if other from the one given with the nmo:from property. Defined in RFC 822 sec. 4.4.2"1
"The primary intended recipient of a message."1
"The primary intended recipient of an email."1
"The sender of the message"1
"The subject of a message"1
"Value of the message header."1
"deprecated in favor of nmo:emailBcc"1
"deprecated in favor of nmo:emailCc"1
"deprecated in favor of nmo:emailTo"1
"deprecated in favor of nmo:messageFrom"1
"deprecated in favor of nmo:messageRecipient"1
"deprecated in favor of nmo:messageReplyTo"1
"deprecated in favor of nmo:messageSender"1
"deprecated in favor of nmo:secondaryMessageRecipient"1
"deprecated in favor of primaryMessageRecipient"1