fix additionalItems in jsf

Signed-off-by: Jan Kowalleck <[email protected]>

Author: jkowalleck

schema/jsf-0.82.schema.json

@@ -16,7 +16,6 @@
               "type": "array",
               "title": "Signature",
               "description": "Unique top level property for Multiple Signatures. (multisignature)",
-              "additionalItems": false,
               "items": {"$ref": "#/definitions/signer"}
             }
           }
@@ -28,7 +27,6 @@
               "type": "array",
               "title": "Signature",
               "description": "Unique top level property for Signature Chains. (signaturechain)",
-              "additionalItems": false,
               "items": {"$ref": "#/definitions/signer"}
             }
           }
@@ -94,7 +92,6 @@
           "type": "array",
           "title": "Certificate path",
           "description": "Optional. Sorted array of X.509 [RFC5280] certificates, where the first element must contain the signature certificate. The certificate path must be contiguous but is not required to be complete.",
-          "additionalItems": false,
           "items": {
             "type": "string"
           }
@@ -103,7 +100,6 @@
           "type": "array",
           "title": "Excludes",
           "description": "Optional. Array holding the names of one or more application level properties that must be excluded from the signature process. Note that the \"excludes\" property itself, must also be excluded from the signature process. Since both the \"excludes\" property and the associated data it points to are unsigned, a conforming JSF implementation must provide options for specifying which properties to accept.",
-          "additionalItems": false,
           "items": {
             "type": "string"
           }