Playing around with possible output schemas

Author: ml-evs

schemas/base.yaml

@@ -133,6 +133,30 @@ classes:
                     multiple output `FileTypes`. Defaults to the `FileType->id` for
                     each supported output file type.
 
+    OutputSchema:
+        description: >-
+            A human-readable specification of the schema that the output of an `Extractor`.
+        attributes:
+            supported_filetypes:
+                range: SupportedFileType
+                multivalued: true
+                required: false
+                description: >-
+                  The file types that this schema can be used for; defaults to all if not provided.
+            schema:
+                required: true
+                description: >-
+                    A human-readable schema definition, with a reference to a machine-actionable
+                    schema definition if available.
+                attributes:
+                    description:
+                        description: >-
+                            A human-readable description of the schema and its usage.
+                    href:
+                         description: >-
+                             A URL or URI for a machine-actionable schema definition.
+
+
     Usage:
         description: >-
             A machine-actionable specification of a set of usage instructions of the

schemas/extractor.yaml

@@ -59,6 +59,16 @@ classes:
                     These should match `FileTypes` present in the registry. They can
                     be specified on extractor execution using the templates described
                     in the `Extractor->Usage->command` slot, [see the `Usage` class](Usage.md).
+            supported_output_schemas:
+                multivalued: true
+                required: false
+                range: OutputSchema
+                description: >-
+                    A description of the schema that a extractor output can follow; this may be
+                    scoped per file type, or a global schema that works for all file types.
+                    This should refer to any machine-actionable schema definition, for example,
+                    JSONSchema, XMLSchema, or it may refer to a self-describing format such as 
+                    JSON-LD or RDF.
             source_repository:
                 description: >-
                     A URL or URI for a source code repository associated with this