LibMISB/LibMISB Introduction/ Functionalities supported: Difference between revisions

From RidgeRun Developer Wiki
No edit summary
No edit summary
Line 22: Line 22:
Sets the Formatter object to convert between format and metadata object. In other words, the user chooses which file format to use for both encoding and decoding actions.
Sets the Formatter object to convert between format and metadata object. In other words, the user chooses which file format to use for both encoding and decoding actions.


===== Heading text =====
* Composition input format: For the input file to be encoded, it must follow the following structure (an example will be shown using the JSON format).
<syntaxhighlight lang=bash>
{
  "key": "<MISB KEY>",
  "items": [
    {
      "tag": "<TAG NUMBER >",
      "value": "<TAG VALUE >"
    }
  ]
}
</syntaxhighlight>
 
Note: some tags are mandatories depending on the standard.
 


==== Encode ====
==== Encode ====


==== Decode ====
==== Decode ====

Revision as of 06:35, 20 June 2022




Previous: LibMISB_Introduction/What_does_the_library_do Index  





General

The functionalities of the library, regardless of the standard used, are as follows

SetDebuggerLevel

Sets the level at which messages will be recorded. The modes, ordered from least to most verbose, are as follows:

  1. MISB_NONE
  2. MISB_ERROR
  3. MISB_WARN
  4. MISB_INFO
  5. MISB_DEBUG

SetFormatter

Sets the Formatter object to convert between format and metadata object. In other words, the user chooses which file format to use for both encoding and decoding actions.

  • Composition input format: For the input file to be encoded, it must follow the following structure (an example will be shown using the JSON format).
{ 
  "key": "<MISB KEY>",
  "items": [
    {
      "tag": "<TAG NUMBER >",
      "value": "<TAG VALUE >"
    }
  ]
}

Note: some tags are mandatories depending on the standard.


Encode

Decode