While a part is not required to have an id, it is often desirable for an identifier to be provided, which allows the part to be referenced elsewhere in OSCAL document instances. For this reason, it is RECOMMENDED to provide a part identifier.
id
value. When referencing an externally defined control
, the Control Identifier Reference
must be used in the context of the external / imported OSCAL instance (e.g., uri-reference).id
value. When referencing an externally defined control
, the Control Identifier Reference
must be used in the context of the external / imported OSCAL instance (e.g., uri-reference).Role
from the imported OSCAL instance must be referenced in the context of the containing resource (e.g., import, import-component-definition, import-profile, import-ssp or import-ap). This ID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.party
can be used to reference the data item locally or globally (e.g., from an importing OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.party
(person
or organization
) that this subject is associated with. The UUID of the party
in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance).
+
+ party
(person
or organization
) that this subject is associated with. The UUID of the party
in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance).
location
defined in the metadata
section of this or another OSCAL instance. The UUID of the location
in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance).
+
+ location
defined in the metadata
section of this or another OSCAL instance. The UUID of the location
in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance).
location
defined in the metadata
section of this or another OSCAL instance. The UUID of the location
in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance).
+
+ location
defined in the metadata
section of this or another OSCAL instance. The UUID of the location
in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance).
party
defined in metadata
. The UUID of the party
in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance).
+
+ party
defined in metadata
. The UUID of the party
in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance).
roles
served by the user.roles
served by the user.role
performed.role
performed by a party
.