<commit_before>Headers
=======
The following headers are supported in version |version| of the message specification. Headers may be added to or removed from the specification over time. Backwards compatibility is achievable through the version header. The message processor uses the version header to determine whether a given message should be processed using older message specifications.

================= ============================================================================================================================================================================================================================================= ================================================================================================================================================================================================================================================================================================================================================
Header Name       Description                                                                                                                                                                                                                                   Required?
================= ============================================================================================================================================================================================================================================= ================================================================================================================================================================================================================================================================================================================================================
``producertoken`` Unique token generated by the destination system used to identify and authorize a given OMF producer. Consult the Qi or PI Connector Relay documentation for further information.                                                             Yes.
``version``       Version of the PI System message specification. Used by the message processor to determine how to process the remaining headers and body.                                                                                                     No. Each target system will define a default messaging version. If a message omits the version header, it is assumed to comply with the target system's default message version. If the message contains headers belonging to an older specification, the version should be included to ensure that the message will be processed appropriately.
``messagetype``   One of: values, streams, or types. See :doc:`Message_Types`.                                                                                                                                                                                  Yes.
``messageformat`` Describes the data serialization format employed in the message body. Currently restricted to ``json``.                                                                                                                                       Yes.
``action``        One of: ``create``, ``update``, or ``delete``. Describes the action to be performed using the data in the message body.                                                                                                                       No. If not specified, ``create`` is assumed.
``compression``   The compression algorithm used to compress the message body. Currently restricted to ``gzip``.                                                                                                                                                No. If not specified, message body is assumed to be uncompressed.
``part``          If a message is too large for a given wire protocol or message queue, it may be broken into multiple parts. This header must be of the form x/y, where y is the total number of parts, and x is the individual sub-message's sequence number. No.
``msgid``         A unique identifier associating a sub-message with the other sub-messages required to assemble a complete message. Each sub-message must use the same ``msgid`` in order for the message to be properly re-assembled.                         Only when the ``part`` header is specified.
================= ============================================================================================================================================================================================================================================= ================================================================================================================================================================================================================================================================================================================================================<commit_msg>removed msgid and part headers. converted headers table to paragraphs for better readability<commit_after>Headers
=======
The following headers are supported in version |version| of the message specification. Headers may be added to or removed from the specification over time. Backwards compatibility is achievable through the version header. The message processor uses the version header to determine whether a given message should be processed using older message specifications.

Required Headers
----------------

``producertoken``

A unique token generated by the destination system used to identify and authorize a given OMF producer. Consult the Qi or PI Connector Relay documentation for further information.

``messagetype``

Describes the type of message contained in the message body. One of: values, streams, or types. See :doc:`Message_Types`.

``messageformat``

Describes the data serialization format employed in the message body. Currently limited to ``json``.

Optional Headers
----------------

``version``

Specifies the version of the OSIsoft Message Format used in the message. Used by the message processor to determine how to process the remaining headers and body. If omitted, it is assumed to comply with the target system's default message version. If the message contains headers belonging to an older specification, the version should be included to ensure that the message will be processed appropriately.

``action``

One of: ``create``, ``update``, or ``delete``. Describes the action to be performed using the data in the message body. If not specified, ``create`` is assumed.

``compression``

The compression algorithm used to compress the message body. Currently limited to ``gzip``. If not specified, message body is assumed to be uncompressed.

{'fraction_non_alphanumeric': 0.2995140627300839, 'fraction_numerical': 0.0, 'mean_word_length': 2.9534342258440045, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 45, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4776209', 'n_tokens_mistral': 1027, 'n_tokens_neox': 898, 'n_words': 575}