The PIA tool allows JSON-based import/export of information used within its processes. The format or schema or structure of this JSON is not documented, which prevents the information from being used elsewhere (if exported), or to be taken from elsewhere for use in PIA (if imported). To help users use their PIA-specified information in other tools (e.g. reporting, scripts) and to reuse existing information within PIA (e.g. import ROPA into PIA) - understanding the structure of the JSON is required. Reverse-engineering this is complicated because of language barriers (English --> French), requirement to understand how JSON data is used in code, and uncertainty as to whether identified solution is correct.
Other than use in import/export within PIA, the documented JSON format would also be beneficial to assess and assist in adding features to PIA, such as information fields, new taxonomies and knowledge bases, and connecting it to other tools/services (e.g. local databases).
The PIA tool allows JSON-based import/export of information used within its processes. The format or schema or structure of this JSON is not documented, which prevents the information from being used elsewhere (if exported), or to be taken from elsewhere for use in PIA (if imported). To help users use their PIA-specified information in other tools (e.g. reporting, scripts) and to reuse existing information within PIA (e.g. import ROPA into PIA) - understanding the structure of the JSON is required. Reverse-engineering this is complicated because of language barriers (English --> French), requirement to understand how JSON data is used in code, and uncertainty as to whether identified solution is correct.
Other than use in import/export within PIA, the documented JSON format would also be beneficial to assess and assist in adding features to PIA, such as information fields, new taxonomies and knowledge bases, and connecting it to other tools/services (e.g. local databases).