**********************
Planning Files Schemas
**********************

The SOC is using JSON files at different levels of the planning process:

 - Observation Plan File (OPL): These files are used as inputs during the Observation Timeline Harmonisation of the
   Detailed Scenario Exercise to schedule the observations and determine the pointing designers.
 - Instrument Timeline Files (ITL): Used as inputs during the Instrument Timeline Harmonisation of the
   Detailed Scenario Exercise to provide power and data resources envelopes.
 - Activity Plan Files (APL): Used as inputs of the activities to schedule during Cruise Operations.
 - Timeline within Observation Definition File (ODF): An ITL snippet within an observation.


One of the advantages of using JSON files is that we can use a JSON schema to validate (partially at least) the syntax
of these files.

For this purpose, the SOC provides the following Schemas:

 - `JUICE Science Operations Activity Plan File Schema <https://juicesoc.esac.esa.int/data/schemas/jsoc-apl-schema.json>`_
 - `JUICE Science Operations Observation Plan File Schema <https://juicesoc.esac.esa.int/data/schemas/jsoc-opl-schema.json>`_
 - `JUICE Science Operations Instrument Timeline File Schema <https://juicesoc.esac.esa.int/data/schemas/jsoc-itl-schema.json>`_

To validate the APL, a plethora of JSON validators can be used, the only requirement is that they support the DRAFT 7
version of the schema. We are using the Python package `jsonschema  <https://github.com/python-jsonschema/jsonschema>`_)
and the API `checkjsonschema <https://github.com/python-jsonschema/check-jsonschema>`_), but you can use any of the
listed In the `JSON Schema site <https://json-schema.org/tools?query=&sortBy=name&sortOrder=ascending&groupBy=languages&licenses=&languages=&drafts=&toolingTypes=&environments=>`_.