Debugging XProc Pipelines Using Outdated Paths

[aj-stein-nist]

Describe the bug

As a NIST OSCAL developer, in order to locally test complex XSLT transformation scenarios with XProc pipelines, I would like the team to review the pipelines for import file (stylesheet and otherwise) to ensure they have been updated to reflect the new repository structure.

Who is the bug affecting?

OSCAL developers using Metaschema for (OSCAL data format) schema generation, content converters, validation, and content processing utilities via the XSLT M4 toolchain.

What is affected by this bug?

Properly running local development XProc pipelines accordingly to debug and incrementally development changes to Metaschema needed for OSCAL development with Metaschema.

From doing some code spelunking, these are some minor misses from a major cleanup and overhaul that occurred for #172.

When does this occur?

Consistently.

How do we replicate the issue?

{What are the steps to reproduce the behavior?

1. Check out a current version of the develop branch of this Metaschema repo.
2. Attempt to use local development and testing transforms, such as test-xml-conversions.xpl.
3. Note incorrect relative path imports that will cause exceptions when executing the XProc pipeline, such as those examples below:

https://github.com/usnistgov/metaschema/blob/develop/toolchains/xslt-M4/testing/test-xml-conversions.xpl#L78

https://github.com/usnistgov/metaschema/blob/develop/toolchains/xslt-M4/testing/test-xml-conversions.xpl#L162

Expected behavior (i.e. solution)

Relative paths are current, and XProc pipelines as currently specified execute without issue.

Other Comments

{Add any other context about the problem here.}

[aj-stein-nist]

I am provisionally going to pull this into sprint and quickly work to merge into develop as I did not want to include this work into #235 (where it was originally found from ongoing development) unless expressly requested to do by Dave and Wendell during review. Rather, I will work to quickly fix these, get merged into develop, then rebase that branch.