David Waltermire

@wendellpiez and @bradh I don't like the idea of changing the profile title. I believe it should be preserved as-is.

The current profile [resolution specification](https://github.com/usnistgov/OSCAL/blob/main/docs/content/concepts/processing/profile-resolution.html) is silent on what to use as the title. This will result is variability between implementations. For example, [`liboscal-java`](https://github.com/usnistgov/liboscal-java) and XSLT implementations uses the profile...

As follow-on work, we could normalize the description to be one or two sentences. The first sentence fragment might start with a verb that describes what the thing does. Such...

Need to extract RMF constraints into an external constraints file.

@bradh Would it be possible to version the document at the document level, but add a property at the control level that indicates which document version the control was last...

@wendellpiez Has this issue been fully addressed in PR #559?

This relates to mapping in profile resolution. #843 and #1115

Implemented a means to support this in [liboscal-java v1.0.4](https://github.com/usnistgov/liboscal-java/releases/tag/v1.0.4) through use of an [identifier mapper](https://github.com/usnistgov/liboscal-java/blob/main/src/main/java/gov/nist/secauto/oscal/lib/profile/resolver/IIdentifierMapper.java). This needs to be added to the Profile Resolution specification (see #1196).

@guyzyl Please make the Metaschema changes to support this and submit a PR.

You can use the `use-name` element in the assembly. Here is an [example](https://github.com/usnistgov/OSCAL/blob/75a3fc177a63c04d8719824cb88039c16bbd0d38/src/metaschema/oscal_ssp_metaschema.xml#L580).