anchor.diff:  
   + Response 200 (application/json)
       + Attributes (Chunk)
  -
  -
  -
  -
  +        + output_chunk_id: `a3a3a1c6-826f-5fc0-8dee-9d015e1fff30` (string) - the output chunk ID association
  +
  +
  +## Data Chunk Output [/processors/{id}/runs/{runID}/data/output/{chunkID}]
  +
  +Retrieves the output of the given output data chunk. This is either raw data or a filesystem reference
  +
  ++ Parameters
  +    + id (string) - The processor ID
  +    + runID (string) - The run ID
  +    + chunkID (string) - The output chunk ID to retrieve
  +
  +### Get specific chunk [GET]
  ++ Response 200 (application/json)
  +    + Attributes (Chunk)
  +        + data (Data)
   
   # Data Structures
   
  
positive.code:     + Attributes (Error)
  
  ## Data [/processors/{id}/runs/{runID}/data]
  The endpoint for manipulating data sources/streams/chunks for the processor
  
  You can either add:
  
negative.code: # Group Processors
  All of the processor API is designed here.
  
  
  Because the Wiz Manager could likely schedule multiple Pipelines or Tasks in the same Pipeline that use the same Processor Task on one physical/logical Processor, the Processor MUST support partitioning all of its logic including Configuration and State by a Manager-scope globally unique **Run ID**
  
  ## Processors Collection [/processors]
  This provides information about all the available processors registered at a given endpoint.
  
  Metadata: this is information about how the processor identifies itself to the Manager
  
  ### Retrieve All Processors [GET]
  + Relation: self
  + Response 200 (application/json)
  