Michaela Iorga

@davaya - David, than you for creating the issue that describes your proposed Information Model representation of OSCAL. Looking forward to your proof of concept code. The [feature-information-model](https://github.com/usnistgov/OSCAL/tree/feature-information-model) branch was...

@Laughter79 - Exam[pleas belong to [oscal-content](https://github.com/usnistgov/oscal-content) repository. This repository is for OSCAL schemas. Please move your issue in [oscal-content](https://github.com/usnistgov/oscal-content) repository so it can be linked to future submissions of examples....

Unfortunately, oscal-cli v 1.0.1 was sunset. Currently, per latest change in NIST policy and due to reduce resources, our team no longer releases the tool. The team provided guidance for...

Thank you for the pointer. For the community members’ clear understanding of the facts, it is important to herein note that the [metaschema-framework]( https://github.com/metaschema-framework) repository is neither NIST-owned nor it...

@Telos-sa - OSCAL schema never had an `inventory-item/implemented-components/asset-id` please check with all released versions. Please provide the `oscal-cli` version . I am guessing you are using the `oscal-cli` released/used by...

> I am using oscal-cli version v1.0.3 from https://github.com/usnistgov/oscal-cli. > > > The error log is suggesting that inventory-items>implemented-components requires a **prop** with **name="asset-id"**. There is no implemented-components>asset-id element. >...

If no additional information is needed under this issue, I recommend we close it.

> What is the user story for this constraint? This section already requires a component-uuid, so is it requiring the id of the asset as well? In most cases the...

@dependabot rebase

I perceived this issue as enhancement to facilitate the information representation and not a coding or inconsistency bug. The use of the `oscal-cli` version created not from the OSCAL models...