Aaron Lippold

So after talking with @cwolf I think we should wrap this in another object called either, - `supporting_data` - `supplepmental_data` So that we have a more generalized approach and it...

So we would have: ``` attestation: { stuff... supporting_data: { cci: [string], ref: https://www.... img: https://link... } } ```

This would be an optional - but highly suggested in HDF style - field that would allow us to maintain cross-data support between eMass and HDF data and allow users...

Looks like this may be the process: https://developer.apple.com/developer-id/

Perhaps also add the ability to use the `-C` `color` flag to color the output if desired

I think we added this to Heimdall with the Generic CSV export. When we convert inspec_tools to javascript this should become part of the cli I think. Is cli support...

In talking with @camdenmoors we agreed that the primary method on these should be `utils` rather than under the `attest` area. The function name of either `apply` or `write` is...

Does this help with the multi-part thing? https://docs.nestjs.com/techniques/file-upload and does it makes sense this is the integration point?

Unless I am missing something - the nextjs folks have the push capability worked out

Is this closed by mitre/inspec_tools#246