support base64decode

[wandmagic]

User Story

when handling a base64 resource for profile or other imported document, i can't examine its contents without base-64-decoding it

Goals

base64 encoded resource support

Dependencies

base64-decode, inline doc() parsing of results

Acceptance Criteria

• All website and readme documentation affected by the changes in this issue have been updated.
• A Pull Request (PR) is submitted that fully addresses the goals of this User Story. This issue is referenced in the PR.
• The CI-CD build process runs without any reported errors on the PR. This can be confirmed by reviewing that all checks have passed in the PR.

Revisions

No response

[david-waltermire]

@wandmagic Are you asking for base64 decoding support in Metapath? I think this is the case, but the issue is not clear about this.

[wandmagic]

yes according to oscal spec, we allow resources to be base64 format. in order to introspect the resource and determine if the resource is formatted as expected and includes the required info, it would be nice to have a base64 decoding function. I think in the short term we should simply not support base64 resources until this is implemented in metaschema java.