Skip to content

Allow local definition of "asset-type" prop values #1797

@Rene2mt

Description

@Rene2mt

User Story

As an OSCAL developer, I need to be able to locally define "asset-type" values (for components and/or inventory items) that currently are not defined in core OSCAL.

Goals

Systems can be comprised of a variety of physical and/or virtual components (e.g., gateway devices, load balancers, object storage, cloud-based services, etc.) that cannot be categorized by the current defined list of asset types (see documentation).

The goals of this issue are as follows:

  • Allow ability to locally define values for "asset-type". This should apply on
  • Make the <prop name='asset-type' value='...'/> prop optional on components. Certain components (e.g. "this-system", leveraged systems, documentation, etc.) may not require an "asset-type".

Dependencies

No response

Acceptance Criteria

  • All OSCAL website and readme documentation affected by the changes in this issue have been updated. Changes to the OSCAL website can be made in the docs/content directory of your branch.
  • 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.

(For reviewers: The wiki has guidance on code review and overall issue review for completeness.)

Revisions

No response

Metadata

Metadata

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions