L.O.B.S.T.E.R.

AND IF the file content is invalid JSON,
THEN the tool shall exit with a non-zero return code.

OTHERWISE the input data
SHALL be written in the LOBSTER interchange format

to the file given in the command line option "out",
IF that option is given AND is not an empty string;

OTHERWISE to STDOUT.

IF the operating system fails to fully serialize the output to a file,
THEN the tool shall print an error message to STDERR and exit with a non-zero return code.

IF [[Input_File]]
AND IF the file extension is not "json" (case-insensitive),
THEN the tool shall print a warning.

IF a list element given through the configuration file under "inputs" is not a file nor a directory,
THEN the tool shall exit with a non-zero return code.

Note: This could happen if a path does not exist.

In addition to [[Parse_Input_File]],
IF the command line option "name-attribute" is given and not an empty string,
AND the input items contains that key
THEN the tool SHALL use the value of that key as tag in the serialized LOBSTER item.

OTHERWISE (if they key does not exist)
the tool SHALL print an error message.

OTHERWISE ("name-attribute" is not given or not an empty string), the tool
SHALL create a synthetic tag name based on the path of the JSON input file and an item counter.

Notes:
- "Synthetic" means that, the name does not need to be related to the data.
- The item counter does not need to be unique across input files,
but it shall be unique at least for each input file separately.
- No further specification is made about how to combine the path and the item counter.