JSON cards and text encodings

When utilizing a native JSON schema in an input card, the automatic determination of text encoding for input data takes place during map execution.

When an output card uses a native JSON schema, the text encoding of card output is determined during map definition. The allowed text encodings for output data are UTF-8, UTF-16LE, UTF-16BE, UTF-32LE, and UTF-32BE.

Previously, the text encoding for the output of a native JSON output card was designated through a rule specified on a text item component termed “encoding.” The component's path was denoted as encoding:<card name>. For instance, the rule might be ‘=NONE,’ resulting in the use of UTF-8. Alternatively, the rule could be ‘=”UTF-16LE”’ signifying the utilization of UTF-16LE.

The encoding item component has been eliminated from native JSON schemas. Currently, the text encoding for an output card is determined by selecting a UTF encoding for the Data Language card property. This property exclusively pertains to output cards employing a native JSON schema that lacks the encoding item type. In the absence of a selection, UTF-8 is defaulted for the output card. Existing maps and schemas utilizing the encoding item type remain valid.