From 96b9ef51706e4355d7edf04e9f4d1b6654b01353 Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Fri, 21 May 2021 19:19:15 -0400 Subject: [PATCH 01/34] description updates --- json/schema/oscal_assessment-plan_schema.json | 6 +- .../oscal_assessment-results_schema.json | 6 +- json/schema/oscal_poam_schema.json | 8 +- .../oscal_assessment-common_metaschema.xml | 6 +- .../oscal_assessment-plan_metaschema.xml | 2 +- src/metaschema/oscal_component_metaschema.xml | 8 +- ...oscal_implementation-common_metaschema.xml | 10 +- src/metaschema/oscal_poam_metaschema.xml | 2 +- src/metaschema/oscal_ssp_metaschema.xml | 2 +- .../oscal_complete_json-to-xml-converter.xsl | 10 + .../oscal_profile_json-to-xml-converter.xsl | 10 + xml/schema/oscal_assessment-plan_schema.xsd | 214 +++++---- .../oscal_assessment-results_schema.xsd | 238 +++++----- xml/schema/oscal_catalog_schema.xsd | 70 ++- xml/schema/oscal_complete_schema.xsd | 416 +++++++++--------- xml/schema/oscal_component_schema.xsd | 126 +++--- xml/schema/oscal_poam_schema.xsd | 226 +++++----- xml/schema/oscal_profile_schema.xsd | 90 ++-- xml/schema/oscal_ssp_schema.xsd | 168 ++++--- 19 files changed, 825 insertions(+), 793 deletions(-) diff --git a/json/schema/oscal_assessment-plan_schema.json b/json/schema/oscal_assessment-plan_schema.json index 1ef46eadc4..3abc6ddc68 100644 --- a/json/schema/oscal_assessment-plan_schema.json +++ b/json/schema/oscal_assessment-plan_schema.json @@ -931,7 +931,7 @@ "properties" : { "uuid" : { "title" : "Task Universally Unique Identifier", - "description" : "Uniquely identifies this assessment task.", + "description" : "Uniquely identifies this assessment task. This identifier's uniqueness is document scoped and is intended to be consistent for the same task across minor revisions of the document.", "type" : "string", "pattern" : "^[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-4[0-9A-Fa-f]{3}-[89ABab][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12}$" }, "type" : @@ -1253,7 +1253,7 @@ "properties" : { "uuid" : { "title" : "Assessment Subject Placeholder Universally Unique Identifier", - "description" : "Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task.", + "description" : "Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task. This identifier's uniqueness is document scoped and is intended to be consistent for the same assessment subject across minor revisions of the document.", "type" : "string", "pattern" : "^[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-4[0-9A-Fa-f]{3}-[89ABab][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12}$" }, "description" : @@ -1426,7 +1426,7 @@ "properties" : { "uuid" : { "title" : "Assessment Platform Universally Unique Identifier", - "description" : "Uniquely identifies this assessment Platform.", + "description" : "Uniquely identifies this assessment Platform. This UUID may be referenced elsewhere in an OSCAL document when refering to this information. Once assigned, a UUID should be consistantly used for a given observation across revisions.", "type" : "string", "pattern" : "^[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-4[0-9A-Fa-f]{3}-[89ABab][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12}$" }, "title" : diff --git a/json/schema/oscal_assessment-results_schema.json b/json/schema/oscal_assessment-results_schema.json index 2f1ca48100..441b02fcce 100644 --- a/json/schema/oscal_assessment-results_schema.json +++ b/json/schema/oscal_assessment-results_schema.json @@ -1176,7 +1176,7 @@ "properties" : { "uuid" : { "title" : "Task Universally Unique Identifier", - "description" : "Uniquely identifies this assessment task.", + "description" : "Uniquely identifies this assessment task. This identifier's uniqueness is document scoped and is intended to be consistent for the same task across minor revisions of the document.", "type" : "string", "pattern" : "^[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-4[0-9A-Fa-f]{3}-[89ABab][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12}$" }, "type" : @@ -1498,7 +1498,7 @@ "properties" : { "uuid" : { "title" : "Assessment Subject Placeholder Universally Unique Identifier", - "description" : "Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task.", + "description" : "Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task. This identifier's uniqueness is document scoped and is intended to be consistent for the same assessment subject across minor revisions of the document.", "type" : "string", "pattern" : "^[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-4[0-9A-Fa-f]{3}-[89ABab][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12}$" }, "description" : @@ -1671,7 +1671,7 @@ "properties" : { "uuid" : { "title" : "Assessment Platform Universally Unique Identifier", - "description" : "Uniquely identifies this assessment Platform.", + "description" : "Uniquely identifies this assessment Platform. This UUID may be referenced elsewhere in an OSCAL document when refering to this information. Once assigned, a UUID should be consistantly used for a given observation across revisions.", "type" : "string", "pattern" : "^[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-4[0-9A-Fa-f]{3}-[89ABab][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12}$" }, "title" : diff --git a/json/schema/oscal_poam_schema.json b/json/schema/oscal_poam_schema.json index c49faaa6ec..da2860ee60 100644 --- a/json/schema/oscal_poam_schema.json +++ b/json/schema/oscal_poam_schema.json @@ -1080,7 +1080,7 @@ "properties" : { "component-uuid" : { "title" : "Component Universally Unique Identifier Reference", - "description" : "A reference to a component that is implemented as part of an inventory item.", + "description" : "A reference to a component that is implemented as part of an inventory item. This identifier's uniqueness is document scoped and is intended to be consistent for the same component across minor revisions of the document.", "type" : "string", "pattern" : "^[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-4[0-9A-Fa-f]{3}-[89ABab][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12}$" }, "props" : @@ -1142,7 +1142,7 @@ "properties" : { "identifier-type" : { "title" : "Identification System Type", - "description" : "Identifies the identification system from which the provided identifier was assigned.", + "description" : "Identifies the identification system from which the provided identifier was assigned. This is a globally unique identifier and should be consistently used for a given system across revisions of the document.", "type" : "string", "format" : "uri" }, "id" : @@ -1512,7 +1512,7 @@ "properties" : { "uuid" : { "title" : "Task Universally Unique Identifier", - "description" : "Uniquely identifies this assessment task.", + "description" : "Uniquely identifies this assessment task. This identifier's uniqueness is document scoped and is intended to be consistent for the same task across minor revisions of the document.", "type" : "string", "pattern" : "^[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-4[0-9A-Fa-f]{3}-[89ABab][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12}$" }, "type" : @@ -1834,7 +1834,7 @@ "properties" : { "uuid" : { "title" : "Assessment Subject Placeholder Universally Unique Identifier", - "description" : "Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task.", + "description" : "Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task. This identifier's uniqueness is document scoped and is intended to be consistent for the same assessment subject across minor revisions of the document.", "type" : "string", "pattern" : "^[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-4[0-9A-Fa-f]{3}-[89ABab][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12}$" }, "description" : diff --git a/src/metaschema/oscal_assessment-common_metaschema.xml b/src/metaschema/oscal_assessment-common_metaschema.xml index ed3b1d4d1f..4b8652295e 100644 --- a/src/metaschema/oscal_assessment-common_metaschema.xml +++ b/src/metaschema/oscal_assessment-common_metaschema.xml @@ -204,7 +204,7 @@ Represents a scheduled event or milestone, which may be associated with a series of assessment actions. Task Universally Unique Identifier - Uniquely identifies this assessment task. + Uniquely identifies this assessment task. This identifier's uniqueness is document scoped and is intended to be consistent for the same task across minor revisions of the document. Task Type @@ -495,7 +495,7 @@ Used when the assessment subjects will be determined as part of one or more other assessment activities. These assessment subjects will be recorded in the assessment results in the assessment log. Assessment Subject Placeholder Universally Unique Identifier - Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task. + Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task. This identifier's uniqueness is document scoped and is intended to be consistent for the same assessment subject across minor revisions of the document. @@ -653,7 +653,7 @@ Assessment Platform Universally Unique Identifier - Uniquely identifies this assessment Platform. + Uniquely identifies this assessment Platform. This UUID may be referenced elsewhere in an OSCAL document when refering to this information. Once assigned, a UUID should be consistantly used for a given observation across revisions. diff --git a/src/metaschema/oscal_assessment-plan_metaschema.xml b/src/metaschema/oscal_assessment-plan_metaschema.xml index 9bef67975c..0bb788c77f 100644 --- a/src/metaschema/oscal_assessment-plan_metaschema.xml +++ b/src/metaschema/oscal_assessment-plan_metaschema.xml @@ -20,7 +20,7 @@ assessment-plan Assessment Plan Universally Unique Identifier - Uniquely identifies this assessment plan. This UUID must be changed each time the content of the plan changes. + Uniquely identifies this assessment plan. This identifier's uniqueness is document scoped and must be changed each time the content of the plan changes. diff --git a/src/metaschema/oscal_component_metaschema.xml b/src/metaschema/oscal_component_metaschema.xml index 7a9fe80aec..0fb1cbebb2 100644 --- a/src/metaschema/oscal_component_metaschema.xml +++ b/src/metaschema/oscal_component_metaschema.xml @@ -79,7 +79,7 @@ A defined component that can be part of an implemented system. Component Identifier - The unique identifier for the component. + The unique identifier for the component. This identifier's uniqueness is document scoped and is intended to be consistent for the same component across minor revisions of the document. type @@ -249,7 +249,7 @@ A grouping of other components and/or capabilities. Capability Identifier - A unique identifier for a capability. + A unique identifier for a capability. This identifier's uniqueness is document scoped and is intended to be consistent for the same capability across minor revisions of the document. Capability Name @@ -304,7 +304,7 @@ Defines how the component or capability supports a set of controls. Control Implementation Set Identifier - A unique identifier for the set of implemented controls. + A unique identifier for the set of implemented controls. This identifier's uniqueness is document scoped and is intended to be consistent for the same control implementation set across minor revisions of the document. @@ -346,7 +346,7 @@ Describes how the containing component or capability implements an individual control. Control Implementation Identifier - A unique identifier for a specific control implementation. + A unique identifier for a specific control implementation. This identifier's uniqueness is document scoped and is intended to be consistent for the same control implementation across minor revisions of the document. diff --git a/src/metaschema/oscal_implementation-common_metaschema.xml b/src/metaschema/oscal_implementation-common_metaschema.xml index 6829307fef..a1df3904bc 100644 --- a/src/metaschema/oscal_implementation-common_metaschema.xml +++ b/src/metaschema/oscal_implementation-common_metaschema.xml @@ -30,7 +30,7 @@ A defined component that can be part of an implemented system. Component Identifier - The unique identifier for the component. + The unique identifier for the component. This identifier's uniqueness is document scoped and is intended to be consistent for the same component across minor revisions of the document. @@ -337,7 +337,7 @@ A type of user that interacts with the system based on an associated role. User Universally Unique Identifier - The unique identifier for the user class. + The unique identifier for the user class. This identifier's uniqueness is document scoped and is intended to be consistent for the same user universally unique idenfier across minor revisions of the document. @@ -452,7 +452,7 @@ Component Universally Unique Identifier Reference - A reference to a component that is implemented as part of an inventory item. + A reference to a component that is implemented as part of an inventory item. This identifier's uniqueness is document scoped and is intended to be consistent for the same component across minor revisions of the document. @@ -657,7 +657,7 @@ id Identification System Type - Identifies the identification system from which the provided identifier was assigned. + Identifies the identification system from which the provided identifier was assigned. This is a globally unique identifier and should be consistently used for a given system across revisions of the document. The identifier was assigned by FedRAMP. @@ -671,7 +671,7 @@ Parameter ID - A reference to a parameter within a control, who's catalog has been imported into the current implementation context. + A reference to a parameter within a control, who's catalog has been imported into the current implementation context. This identifier's uniqueness is document scoped and is intended to be consistent for the same param across minor revisions of the document. System ISSO diff --git a/src/metaschema/oscal_poam_metaschema.xml b/src/metaschema/oscal_poam_metaschema.xml index bce14bc6be..e7dcd54218 100644 --- a/src/metaschema/oscal_poam_metaschema.xml +++ b/src/metaschema/oscal_poam_metaschema.xml @@ -23,7 +23,7 @@ plan-of-action-and-milestones POA&M Universally Unique Identifier - Uniquely identifies this POA&M. This UUID must be changed each time the content of the POA&M changes. + Uniquely identifies this POA&M. This UUID may be referenced elsewhere in an OSCAL document when refering to this information. This UUID must be changed each time the content of the POA&M changes. diff --git a/src/metaschema/oscal_ssp_metaschema.xml b/src/metaschema/oscal_ssp_metaschema.xml index 295356ec2e..2025dd9a3e 100644 --- a/src/metaschema/oscal_ssp_metaschema.xml +++ b/src/metaschema/oscal_ssp_metaschema.xml @@ -815,7 +815,7 @@ Defines how the referenced component implements a set of controls. Component Universally Unique Identifier Reference - A reference to the component that is implementing a given control or control statement. + A reference to the component that is implementing a given control or control statement. A UUID should be consistantly used for a given resource across revisions of the document. By-Component Universally Unique Identifier diff --git a/xml/convert/oscal_complete_json-to-xml-converter.xsl b/xml/convert/oscal_complete_json-to-xml-converter.xsl index dfa76898cd..082db9cc21 100644 --- a/xml/convert/oscal_complete_json-to-xml-converter.xsl +++ b/xml/convert/oscal_complete_json-to-xml-converter.xsl @@ -369,6 +369,7 @@ + @@ -382,6 +383,15 @@ + + + + + + flat + + + diff --git a/xml/convert/oscal_profile_json-to-xml-converter.xsl b/xml/convert/oscal_profile_json-to-xml-converter.xsl index fae2fffb5e..21a6befc28 100644 --- a/xml/convert/oscal_profile_json-to-xml-converter.xsl +++ b/xml/convert/oscal_profile_json-to-xml-converter.xsl @@ -223,6 +223,7 @@ + @@ -236,6 +237,15 @@ + + + + + + flat + + + diff --git a/xml/schema/oscal_assessment-plan_schema.xsd b/xml/schema/oscal_assessment-plan_schema.xsd index 5111f5e28a..dc747e531e 100644 --- a/xml/schema/oscal_assessment-plan_schema.xsd +++ b/xml/schema/oscal_assessment-plan_schema.xsd @@ -130,10 +130,10 @@ Assessment Plan Universally Unique Identifier - Uniquely identifies this assessment plan. This UUID must be changed each time the content of the plan changes. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment plan in this or other OSCAL instances. The locally defined UUID of the assessment plan can be used to reference the data item locally or globally (e.g., in an imported 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. - Assessment Plan Universally Unique Identifier: Uniquely identifies this assessment plan. This UUID must be changed each time the content of the plan changes. + Assessment Plan Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment plan in this or other OSCAL instances. The locally defined UUID of the assessment plan can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -377,10 +377,10 @@ Location Universally Unique Identifier - A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. - Location Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + Location Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. @@ -388,10 +388,10 @@ Location Reference - References a location defined in metadata. + A machine-oriented identifier reference to a 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 Reference: References a location defined in metadata. + Location Reference: A machine-oriented identifier reference to a 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). @@ -488,10 +488,10 @@ Organizational Affiliation - Identifies that the party object is a member of the organization associated with the provided UUID. + A machine-oriented identifier reference to another 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). - Organizational Affiliation: Identifies that the party object is a member of the organization associated with the provided UUID. + Organizational Affiliation: A machine-oriented identifier reference to another 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). @@ -516,10 +516,10 @@ Party Universally Unique Identifier - A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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 Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. + Party Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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. @@ -537,10 +537,10 @@ Party Reference - References a party defined in metadata. + A machine-oriented identifier reference to another 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 Reference: References a party defined in metadata. + Party Reference: A machine-oriented identifier reference to another 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). @@ -624,11 +624,9 @@ - Role Identifier - A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. - - Role Identifier: A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. @@ -636,10 +634,10 @@ Role Identifier Reference - A reference to the roles served by the user. + A human-oriented identifier reference to roles served by the user. - Role Identifier Reference: A reference to the roles served by the user. + Role Identifier Reference: A human-oriented identifier reference to roles served by the user. @@ -833,10 +831,10 @@ Resource Universally Unique Identifier - A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Resource Universally Unique Identifier: A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Resource Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -883,10 +881,10 @@ Property Universally Unique Identifier - A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Property Universally Unique Identifier: A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + Property Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -1019,10 +1017,10 @@ Responsible Role - The role that the party is responsible for. + A human-oriented identifier reference to roles served by the user. - Responsible Role: The role that the party is responsible for. + Responsible Role: A human-oriented identifier reference to roles served by the user. @@ -1068,10 +1066,10 @@ Responsible Role ID - The role that is responsible for the business function. + A human-oriented identifier reference to roles responsible for the business function. - Responsible Role ID: The role that is responsible for the business function. + Responsible Role ID: A human-oriented identifier reference to roles responsible for the business function. @@ -1284,10 +1282,10 @@ Document Identifier - A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. - Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. @@ -1398,10 +1396,10 @@ Control Identifier Reference - A reference to a control with a corresponding id value. + A human-oriented identifier reference to a control with a corresponding 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). - Control Identifier Reference: A reference to a control with a corresponding id value. + Control Identifier Reference: A human-oriented identifier reference to a control with a corresponding 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). @@ -1462,10 +1460,10 @@ Assessment Method Universally Unique Identifier - Uniquely identifies this defined assessment method. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given assessment method across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment method elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment method can be used to reference the data item locally or globally (e.g., in an imported 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. - Assessment Method Universally Unique Identifier: Uniquely identifies this defined assessment method. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given assessment method across revisions of the document. + Assessment Method Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment method elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment method can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -1594,10 +1592,10 @@ Step Universally Unique Identifier - Uniquely identifies a step. This UUID may be referenced elsewhere in an OSCAL document when referring to this step. A UUID should be consistently used for a given test step across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this step elsewhere in this or other OSCAL instances. The locally defined UUID of the step (in a series of steps) can be used to reference the data item locally or globally (e.g., in an imported 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. - Step Universally Unique Identifier: Uniquely identifies a step. This UUID may be referenced elsewhere in an OSCAL document when referring to this step. A UUID should be consistently used for a given test step across revisions of the document. + Step Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this step elsewhere in this or other OSCAL instances. The locally defined UUID of the step (in a series of steps) can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -1630,10 +1628,10 @@ Assessment Activity Universally Unique Identifier - Uniquely identifies this assessment activity. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given included activity across revisions of the document. + A machine-oriented, globally unique> identifier with cross-instance scope that can be used to reference this assessment activity elsewhere in this or other OSCAL instances. The locally defined UUID of the activity can be used to reference the data item locally or globally (e.g., in an imported 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. - Assessment Activity Universally Unique Identifier: Uniquely identifies this assessment activity. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given included activity across revisions of the document. + Assessment Activity Universally Unique Identifier: A machine-oriented, globally unique> identifier with cross-instance scope that can be used to reference this assessment activity elsewhere in this or other OSCAL instances. The locally defined UUID of the activity can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -1818,10 +1816,10 @@ Task Universally Unique Identifier Reference - References a unique task by UUID. + A machine-oriented identifier reference to a unique task. - Task Universally Unique Identifier Reference: References a unique task by UUID. + Task Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique task. @@ -1877,10 +1875,10 @@ Activity Universally Unique Identifier Reference - References an activity defined in the list of activities. + A machine-oriented identifier reference to an activity defined in the list of activities. - Activity Universally Unique Identifier Reference: References an activity defined in the list of activities. + Activity Universally Unique Identifier Reference: A machine-oriented identifier reference to an activity defined in the list of activities. @@ -1913,10 +1911,10 @@ Task Universally Unique Identifier - Uniquely identifies this assessment task. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this task elsewhere in this or other OSCAL instances. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. - Task Universally Unique Identifier: Uniquely identifies this assessment task. + Task Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this task elsewhere in this or other OSCAL instances. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -2158,10 +2156,10 @@ Control Identifier Reference - A reference to a control with a corresponding id value. + A human-oriented identifier reference to a control with a corresponding 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). - Control Identifier Reference: A reference to a control with a corresponding id value. + Control Identifier Reference: A human-oriented identifier reference to a control with a corresponding 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). @@ -2224,10 +2222,10 @@ Task Universally Unique Identifier - Uniquely identifies an assessment activity to be performed as part of the event. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference (in this or other OSCAL instances) an assessment activity to be performed as part of the event. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. - Task Universally Unique Identifier: Uniquely identifies an assessment activity to be performed as part of the event. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. + Task Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference (in this or other OSCAL instances) an assessment activity to be performed as part of the event. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -2260,10 +2258,10 @@ Assessment Subject Placeholder Universally Unique Identifier - Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task. + A machine-oriented, globally unique identifier for a set of assessment subjects that will be identified by a task or an activity that is part of a task. The locally defined UUID of the assessment subject placeholder can be used to reference the data item locally or globally (e.g., in an imported 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. - Assessment Subject Placeholder Universally Unique Identifier: Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task. + Assessment Subject Placeholder Universally Unique Identifier: A machine-oriented, globally unique identifier for a set of assessment subjects that will be identified by a task or an activity that is part of a task. The locally defined UUID of the assessment subject placeholder can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -2387,10 +2385,10 @@ Subject Universally Unique Identifier Reference - A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. + A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. - Subject Universally Unique Identifier Reference: A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. + Subject Universally Unique Identifier Reference: A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. @@ -2408,10 +2406,10 @@ Identifies the Subject - A pointer to a resource based on its universally unique identifier (UUID). Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. + A human-oriented identifier reference to a resource. Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. - Identifies the Subject: A pointer to a resource based on its universally unique identifier (UUID). Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. + Identifies the Subject: A human-oriented identifier reference to a resource. Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. @@ -2457,10 +2455,10 @@ Subject Universally Unique Identifier Reference - A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. + A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. - Subject Universally Unique Identifier Reference: A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. + Subject Universally Unique Identifier Reference: A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. @@ -2565,10 +2563,10 @@ Component Universally Unique Identifier Reference - A reference to a component that is implemented as part of an inventory item. + A machine-oriented identifier reference to a component that is implemented as part of an inventory item. - Component Universally Unique Identifier Reference: A reference to a component that is implemented as part of an inventory item. + Component Universally Unique Identifier Reference: A machine-oriented identifier reference to a component that is implemented as part of an inventory item. @@ -2593,10 +2591,10 @@ Assessment Platform Universally Unique Identifier - Uniquely identifies this assessment Platform. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment platform elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment platform can be used to reference the data item locally or globally (e.g., in an imported 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. - Assessment Platform Universally Unique Identifier: Uniquely identifies this assessment Platform. + Assessment Platform Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment platform elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment platform can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -2734,10 +2732,10 @@ Finding Target Identifier Reference - Identifies the specific target qualified by the type. + A machine-oriented identifier reference for a specific target qualified by the type. - Finding Target Identifier Reference: Identifies the specific target qualified by the type. + Finding Target Identifier Reference: A machine-oriented identifier reference for a specific target qualified by the type. @@ -2931,10 +2929,10 @@ Observation Universally Unique Identifier - Uniquely identifies this observation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given observation across revisions. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. The locally defined UUID of the observation can be used to reference the data item locally or globally (e.g., in an imorted 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. - Observation Universally Unique Identifier: Uniquely identifies this observation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given observation across revisions. + Observation Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. The locally defined UUID of the observation can be used to reference the data item locally or globally (e.g., in an imorted 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. @@ -2991,10 +2989,10 @@ Actor Universally Unique Identifier Reference - A pointer to the tool or person based on the associated type. + A machine-oriented identifier reference to the tool or person based on the associated type. - Actor Universally Unique Identifier Reference: A pointer to the tool or person based on the associated type. + Actor Universally Unique Identifier Reference: A machine-oriented identifier reference to the tool or person based on the associated type. @@ -3054,10 +3052,10 @@ Assessment Subject Placeholder Universally Unique Identifier Reference - References a unique assessment subject placeholder defined by this task. + A machine-oriented identifier reference to a unique assessment subject placeholder defined by this task. - Assessment Subject Placeholder Universally Unique Identifier Reference: References a unique assessment subject placeholder defined by this task. + Assessment Subject Placeholder Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique assessment subject placeholder defined by this task. @@ -3082,10 +3080,10 @@ Task Universally Unique Identifier Reference - References a unique task by UUID. + A machine-oriented identifier reference to a unique task. - Task Universally Unique Identifier Reference: References a unique task by UUID. + Task Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique task. @@ -3254,20 +3252,20 @@ Mitigating Factor Universally Unique Identifier - Uniquely identifies this mitigating factor. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given mitigating factor across revisions. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mitigating factor elsewhere in this or other OSCAL instances. The locally defined UUID of the mitigating factor can be used to reference the data item locally or globally (e.g., in an imported 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. - Mitigating Factor Universally Unique Identifier: Uniquely identifies this mitigating factor. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given mitigating factor across revisions. + Mitigating Factor Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mitigating factor elsewhere in this or other OSCAL instances. The locally defined UUID of the mitigating factor can be used to reference the data item locally or globally (e.g., in an imported 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. Implementation UUID - Points to an implementation statement in the SSP. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this implementation statement elsewhere in this or other OSCAL instancess. The locally defined UUID of the implementation statement can be used to reference the data item locally or globally (e.g., in an imported 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. - Implementation UUID: Points to an implementation statement in the SSP. + Implementation UUID: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this implementation statement elsewhere in this or other OSCAL instancess. The locally defined UUID of the implementation statement can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -3426,10 +3424,10 @@ Response Universally Unique Identifier Reference - References a unique risk response by UUID. + A machine-oriented identifier reference to a unique risk response. - Response Universally Unique Identifier Reference: References a unique risk response by UUID. + Response Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique risk response. @@ -3454,10 +3452,10 @@ Risk Log Entry Universally Unique Identifier - Uniquely identifies a risk log entry. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk log entry elsewhere in this or other OSCAL instances. The locally defined UUID of the risk log entry can be used to reference the data item locally or globally (e.g., in an imported 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. - Risk Log Entry Universally Unique Identifier: Uniquely identifies a risk log entry. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. + Risk Log Entry Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk log entry elsewhere in this or other OSCAL instances. The locally defined UUID of the risk log entry can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -3479,10 +3477,10 @@ Observation Universally Unique Identifier Reference - References an observation defined in the list of observations. + A machine-oriented identifier reference to an observation defined in the list of observations. - Observation Universally Unique Identifier Reference: References an observation defined in the list of observations. + Observation Universally Unique Identifier Reference: A machine-oriented identifier reference to an observation defined in the list of observations. @@ -3492,10 +3490,10 @@ Risk Universally Unique Identifier - Uniquely identifies this risk. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given risk across revisions. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk elsewhere in this or other OSCAL instances. The locally defined UUID of the risk can be used to reference the data item locally or globally (e.g., in an imported 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. - Risk Universally Unique Identifier: Uniquely identifies this risk. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given risk across revisions. + Risk Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk elsewhere in this or other OSCAL instances. The locally defined UUID of the risk can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -3512,10 +3510,10 @@ Party UUID Reference - A pointer to the party who is making the log entry. + A machine-oriented identifier reference to the party who is making the log entry. - Party UUID Reference: A pointer to the party who is making the log entry. + Party UUID Reference: A machine-oriented identifier reference to the party who is making the log entry. @@ -3756,10 +3754,10 @@ Required Universally Unique Identifier - Uniquely identifies this required asset. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given required asset across revisions. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this required asset elsewhere in this or other OSCAL instances. The locally defined UUID of the asset can be used to reference the data item locally or globally (e.g., in an imported 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. - Required Universally Unique Identifier: Uniquely identifies this required asset. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given required asset across revisions. + Required Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this required asset elsewhere in this or other OSCAL instances. The locally defined UUID of the asset can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -3788,10 +3786,10 @@ Remediation Universally Unique Identifier - Uniquely identifies this remediation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given remediation across revisions. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this remediation elsewhere in this or other OSCAL instances. The locally defined UUID of the risk response can be used to reference the data item locally or globally (e.g., in an imported 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. - Remediation Universally Unique Identifier: Uniquely identifies this remediation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given remediation across revisions. + Remediation Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this remediation elsewhere in this or other OSCAL instances. The locally defined UUID of the risk response can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -3850,10 +3848,10 @@ Part Identifier - A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this part elsewhere in this or other OSCAL instances. The locally defined UUID of the part can be used to reference the data item locally or globally (e.g., in an ported 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. - Part Identifier: A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. + Part Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this part elsewhere in this or other OSCAL instances. The locally defined UUID of the part can be used to reference the data item locally or globally (e.g., in an ported 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. @@ -3932,10 +3930,10 @@ Part Identifier - A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Part Identifier: A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. + Part Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -4055,10 +4053,10 @@ Parameter Identifier - A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Parameter Identifier: A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. + Parameter Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -4344,10 +4342,10 @@ Component Identifier - The unique identifier for the component. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. - Component Identifier: The unique identifier for the component. + Component Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -4395,10 +4393,10 @@ Service Protocol Information Universally Unique Identifier - A globally unique identifier that can be used to reference this service protocol entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported 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. - Service Protocol Information Universally Unique Identifier: A globally unique identifier that can be used to reference this service protocol entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Service Protocol Information Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -4578,10 +4576,10 @@ User Universally Unique Identifier - The unique identifier for the user class. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported 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. - User Universally Unique Identifier: The unique identifier for the user class. + User Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -4722,10 +4720,10 @@ Component Universally Unique Identifier Reference - A reference to a component that is implemented as part of an inventory item. + A machine-oriented identifier reference to a component that is implemented as part of an inventory item. - Component Universally Unique Identifier Reference: A reference to a component that is implemented as part of an inventory item. + Component Universally Unique Identifier Reference: A machine-oriented identifier reference to a component that is implemented as part of an inventory item. @@ -4750,10 +4748,10 @@ Inventory Item Universally Unique Identifier - A globally unique identifier that can be used to reference this inventory item entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported 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. - Inventory Item Universally Unique Identifier: A globally unique identifier that can be used to reference this inventory item entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Inventory Item Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -4800,10 +4798,10 @@ Parameter ID - A reference to a parameter within a control, who's catalog has been imported into the current implementation context. + A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context. - Parameter ID: A reference to a parameter within a control, who's catalog has been imported into the current implementation context. + Parameter ID: A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context. @@ -4811,10 +4809,10 @@ System Identification - A unique identifier for the system described by this system security plan. + A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. - System Identification: A unique identifier for the system described by this system security plan. + System Identification: A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. @@ -4822,10 +4820,10 @@ Identification System Type - Identifies the identification system from which the provided identifier was assigned. + Identifies the identification system from which the provided identifier was assigned. - Identification System Type: Identifies the identification system from which the provided identifier was assigned. + Identification System Type: Identifies the identification system from which the provided identifier was assigned. diff --git a/xml/schema/oscal_assessment-results_schema.xsd b/xml/schema/oscal_assessment-results_schema.xsd index ae7c5aaffa..a5b8d7878f 100644 --- a/xml/schema/oscal_assessment-results_schema.xsd +++ b/xml/schema/oscal_assessment-results_schema.xsd @@ -88,10 +88,10 @@ Assessment Results Universally Unique Identifier - Uniquely identifies this assessment results file. This UUID must be changed each time the content of the results changes. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment results instance in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported 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. - Assessment Results Universally Unique Identifier: Uniquely identifies this assessment results file. This UUID must be changed each time the content of the results changes. + Assessment Results Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment results instance in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -343,10 +343,10 @@ Assessment Log Entry Universally Unique Identifier - Uniquely identifies an assessment event. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference an assessment event in this or other OSCAL instances. The locally defined UUID of the assessment log entry can be used to reference the data item locally or globally (e.g., in an imported 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. - Assessment Log Entry Universally Unique Identifier: Uniquely identifies an assessment event. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. + Assessment Log Entry Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference an assessment event in this or other OSCAL instances. The locally defined UUID of the assessment log entry can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -386,10 +386,10 @@ Results Universally Unique Identifier - Uniquely identifies this set of results. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given set of results across revisions. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this set of results in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported 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. - Results Universally Unique Identifier: Uniquely identifies this set of results. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given set of results across revisions. + Results Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this set of results in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -454,10 +454,10 @@ Implementation Statement UUID - Identifies the implementation statement in the SSP to which this finding is related. + A machine-oriented identifier reference to the implementation statement in the SSP to which this finding is related. - Implementation Statement UUID: Identifies the implementation statement in the SSP to which this finding is related. + Implementation Statement UUID: A machine-oriented identifier reference to the implementation statement in the SSP to which this finding is related. @@ -476,10 +476,10 @@ Observation Universally Unique Identifier Reference - References an observation defined in the list of observations. + A machine-oriented identifier reference to an observation defined in the list of observations. - Observation Universally Unique Identifier Reference: References an observation defined in the list of observations. + Observation Universally Unique Identifier Reference: A machine-oriented identifier reference to an observation defined in the list of observations. @@ -498,10 +498,10 @@ Risk Universally Unique Identifier Reference - References an risk defined in the list of risks. + A machine-oriented identifier reference to a risk defined in the list of risks. - Risk Universally Unique Identifier Reference: References an risk defined in the list of risks. + Risk Universally Unique Identifier Reference: A machine-oriented identifier reference to a risk defined in the list of risks. @@ -526,10 +526,10 @@ Finding Universally Unique Identifier - Uniquely identifies this finding. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given finding across revisions. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this finding in this or other OSCAL instances. The locally defined UUID of the finding can be used to reference the data item locally or globally (e.g., in an imported 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. - Finding Universally Unique Identifier: Uniquely identifies this finding. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given finding across revisions. + Finding Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this finding in this or other OSCAL instances. The locally defined UUID of the finding can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -810,10 +810,10 @@ Location Universally Unique Identifier - A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. - Location Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + Location Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. @@ -821,10 +821,10 @@ Location Reference - References a location defined in metadata. + A machine-oriented identifier reference to a 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 Reference: References a location defined in metadata. + Location Reference: A machine-oriented identifier reference to a 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). @@ -921,10 +921,10 @@ Organizational Affiliation - Identifies that the party object is a member of the organization associated with the provided UUID. + A machine-oriented identifier reference to another 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). - Organizational Affiliation: Identifies that the party object is a member of the organization associated with the provided UUID. + Organizational Affiliation: A machine-oriented identifier reference to another 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). @@ -949,10 +949,10 @@ Party Universally Unique Identifier - A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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 Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. + Party Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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. @@ -970,10 +970,10 @@ Party Reference - References a party defined in metadata. + A machine-oriented identifier reference to another 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 Reference: References a party defined in metadata. + Party Reference: A machine-oriented identifier reference to another 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). @@ -1057,11 +1057,9 @@ - Role Identifier - A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. - - Role Identifier: A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. @@ -1069,10 +1067,10 @@ Role Identifier Reference - A reference to the roles served by the user. + A human-oriented identifier reference to roles served by the user. - Role Identifier Reference: A reference to the roles served by the user. + Role Identifier Reference: A human-oriented identifier reference to roles served by the user. @@ -1266,10 +1264,10 @@ Resource Universally Unique Identifier - A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Resource Universally Unique Identifier: A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Resource Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -1316,10 +1314,10 @@ Property Universally Unique Identifier - A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Property Universally Unique Identifier: A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + Property Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -1452,10 +1450,10 @@ Responsible Role - The role that the party is responsible for. + A human-oriented identifier reference to roles served by the user. - Responsible Role: The role that the party is responsible for. + Responsible Role: A human-oriented identifier reference to roles served by the user. @@ -1501,10 +1499,10 @@ Responsible Role ID - The role that is responsible for the business function. + A human-oriented identifier reference to roles responsible for the business function. - Responsible Role ID: The role that is responsible for the business function. + Responsible Role ID: A human-oriented identifier reference to roles responsible for the business function. @@ -1717,10 +1715,10 @@ Document Identifier - A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. - Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. @@ -1831,10 +1829,10 @@ Control Identifier Reference - A reference to a control with a corresponding id value. + A human-oriented identifier reference to a control with a corresponding 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). - Control Identifier Reference: A reference to a control with a corresponding id value. + Control Identifier Reference: A human-oriented identifier reference to a control with a corresponding 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). @@ -1895,10 +1893,10 @@ Assessment Method Universally Unique Identifier - Uniquely identifies this defined assessment method. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given assessment method across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment method elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment method can be used to reference the data item locally or globally (e.g., in an imported 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. - Assessment Method Universally Unique Identifier: Uniquely identifies this defined assessment method. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given assessment method across revisions of the document. + Assessment Method Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment method elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment method can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -2027,10 +2025,10 @@ Step Universally Unique Identifier - Uniquely identifies a step. This UUID may be referenced elsewhere in an OSCAL document when referring to this step. A UUID should be consistently used for a given test step across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this step elsewhere in this or other OSCAL instances. The locally defined UUID of the step (in a series of steps) can be used to reference the data item locally or globally (e.g., in an imported 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. - Step Universally Unique Identifier: Uniquely identifies a step. This UUID may be referenced elsewhere in an OSCAL document when referring to this step. A UUID should be consistently used for a given test step across revisions of the document. + Step Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this step elsewhere in this or other OSCAL instances. The locally defined UUID of the step (in a series of steps) can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -2063,10 +2061,10 @@ Assessment Activity Universally Unique Identifier - Uniquely identifies this assessment activity. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given included activity across revisions of the document. + A machine-oriented, globally unique> identifier with cross-instance scope that can be used to reference this assessment activity elsewhere in this or other OSCAL instances. The locally defined UUID of the activity can be used to reference the data item locally or globally (e.g., in an imported 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. - Assessment Activity Universally Unique Identifier: Uniquely identifies this assessment activity. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given included activity across revisions of the document. + Assessment Activity Universally Unique Identifier: A machine-oriented, globally unique> identifier with cross-instance scope that can be used to reference this assessment activity elsewhere in this or other OSCAL instances. The locally defined UUID of the activity can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -2251,10 +2249,10 @@ Task Universally Unique Identifier Reference - References a unique task by UUID. + A machine-oriented identifier reference to a unique task. - Task Universally Unique Identifier Reference: References a unique task by UUID. + Task Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique task. @@ -2310,10 +2308,10 @@ Activity Universally Unique Identifier Reference - References an activity defined in the list of activities. + A machine-oriented identifier reference to an activity defined in the list of activities. - Activity Universally Unique Identifier Reference: References an activity defined in the list of activities. + Activity Universally Unique Identifier Reference: A machine-oriented identifier reference to an activity defined in the list of activities. @@ -2346,10 +2344,10 @@ Task Universally Unique Identifier - Uniquely identifies this assessment task. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this task elsewhere in this or other OSCAL instances. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. - Task Universally Unique Identifier: Uniquely identifies this assessment task. + Task Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this task elsewhere in this or other OSCAL instances. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -2591,10 +2589,10 @@ Control Identifier Reference - A reference to a control with a corresponding id value. + A human-oriented identifier reference to a control with a corresponding 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). - Control Identifier Reference: A reference to a control with a corresponding id value. + Control Identifier Reference: A human-oriented identifier reference to a control with a corresponding 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). @@ -2657,10 +2655,10 @@ Task Universally Unique Identifier - Uniquely identifies an assessment activity to be performed as part of the event. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference (in this or other OSCAL instances) an assessment activity to be performed as part of the event. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. - Task Universally Unique Identifier: Uniquely identifies an assessment activity to be performed as part of the event. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. + Task Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference (in this or other OSCAL instances) an assessment activity to be performed as part of the event. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -2693,10 +2691,10 @@ Assessment Subject Placeholder Universally Unique Identifier - Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task. + A machine-oriented, globally unique identifier for a set of assessment subjects that will be identified by a task or an activity that is part of a task. The locally defined UUID of the assessment subject placeholder can be used to reference the data item locally or globally (e.g., in an imported 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. - Assessment Subject Placeholder Universally Unique Identifier: Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task. + Assessment Subject Placeholder Universally Unique Identifier: A machine-oriented, globally unique identifier for a set of assessment subjects that will be identified by a task or an activity that is part of a task. The locally defined UUID of the assessment subject placeholder can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -2820,10 +2818,10 @@ Subject Universally Unique Identifier Reference - A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. + A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. - Subject Universally Unique Identifier Reference: A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. + Subject Universally Unique Identifier Reference: A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. @@ -2841,10 +2839,10 @@ Identifies the Subject - A pointer to a resource based on its universally unique identifier (UUID). Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. + A human-oriented identifier reference to a resource. Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. - Identifies the Subject: A pointer to a resource based on its universally unique identifier (UUID). Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. + Identifies the Subject: A human-oriented identifier reference to a resource. Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. @@ -2890,10 +2888,10 @@ Subject Universally Unique Identifier Reference - A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. + A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. - Subject Universally Unique Identifier Reference: A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. + Subject Universally Unique Identifier Reference: A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. @@ -2998,10 +2996,10 @@ Component Universally Unique Identifier Reference - A reference to a component that is implemented as part of an inventory item. + A machine-oriented identifier reference to a component that is implemented as part of an inventory item. - Component Universally Unique Identifier Reference: A reference to a component that is implemented as part of an inventory item. + Component Universally Unique Identifier Reference: A machine-oriented identifier reference to a component that is implemented as part of an inventory item. @@ -3026,10 +3024,10 @@ Assessment Platform Universally Unique Identifier - Uniquely identifies this assessment Platform. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment platform elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment platform can be used to reference the data item locally or globally (e.g., in an imported 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. - Assessment Platform Universally Unique Identifier: Uniquely identifies this assessment Platform. + Assessment Platform Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment platform elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment platform can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -3167,10 +3165,10 @@ Finding Target Identifier Reference - Identifies the specific target qualified by the type. + A machine-oriented identifier reference for a specific target qualified by the type. - Finding Target Identifier Reference: Identifies the specific target qualified by the type. + Finding Target Identifier Reference: A machine-oriented identifier reference for a specific target qualified by the type. @@ -3364,10 +3362,10 @@ Observation Universally Unique Identifier - Uniquely identifies this observation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given observation across revisions. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. The locally defined UUID of the observation can be used to reference the data item locally or globally (e.g., in an imorted 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. - Observation Universally Unique Identifier: Uniquely identifies this observation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given observation across revisions. + Observation Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. The locally defined UUID of the observation can be used to reference the data item locally or globally (e.g., in an imorted 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. @@ -3424,10 +3422,10 @@ Actor Universally Unique Identifier Reference - A pointer to the tool or person based on the associated type. + A machine-oriented identifier reference to the tool or person based on the associated type. - Actor Universally Unique Identifier Reference: A pointer to the tool or person based on the associated type. + Actor Universally Unique Identifier Reference: A machine-oriented identifier reference to the tool or person based on the associated type. @@ -3487,10 +3485,10 @@ Assessment Subject Placeholder Universally Unique Identifier Reference - References a unique assessment subject placeholder defined by this task. + A machine-oriented identifier reference to a unique assessment subject placeholder defined by this task. - Assessment Subject Placeholder Universally Unique Identifier Reference: References a unique assessment subject placeholder defined by this task. + Assessment Subject Placeholder Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique assessment subject placeholder defined by this task. @@ -3515,10 +3513,10 @@ Task Universally Unique Identifier Reference - References a unique task by UUID. + A machine-oriented identifier reference to a unique task. - Task Universally Unique Identifier Reference: References a unique task by UUID. + Task Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique task. @@ -3687,20 +3685,20 @@ Mitigating Factor Universally Unique Identifier - Uniquely identifies this mitigating factor. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given mitigating factor across revisions. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mitigating factor elsewhere in this or other OSCAL instances. The locally defined UUID of the mitigating factor can be used to reference the data item locally or globally (e.g., in an imported 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. - Mitigating Factor Universally Unique Identifier: Uniquely identifies this mitigating factor. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given mitigating factor across revisions. + Mitigating Factor Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mitigating factor elsewhere in this or other OSCAL instances. The locally defined UUID of the mitigating factor can be used to reference the data item locally or globally (e.g., in an imported 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. Implementation UUID - Points to an implementation statement in the SSP. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this implementation statement elsewhere in this or other OSCAL instancess. The locally defined UUID of the implementation statement can be used to reference the data item locally or globally (e.g., in an imported 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. - Implementation UUID: Points to an implementation statement in the SSP. + Implementation UUID: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this implementation statement elsewhere in this or other OSCAL instancess. The locally defined UUID of the implementation statement can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -3859,10 +3857,10 @@ Response Universally Unique Identifier Reference - References a unique risk response by UUID. + A machine-oriented identifier reference to a unique risk response. - Response Universally Unique Identifier Reference: References a unique risk response by UUID. + Response Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique risk response. @@ -3887,10 +3885,10 @@ Risk Log Entry Universally Unique Identifier - Uniquely identifies a risk log entry. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk log entry elsewhere in this or other OSCAL instances. The locally defined UUID of the risk log entry can be used to reference the data item locally or globally (e.g., in an imported 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. - Risk Log Entry Universally Unique Identifier: Uniquely identifies a risk log entry. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. + Risk Log Entry Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk log entry elsewhere in this or other OSCAL instances. The locally defined UUID of the risk log entry can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -3912,10 +3910,10 @@ Observation Universally Unique Identifier Reference - References an observation defined in the list of observations. + A machine-oriented identifier reference to an observation defined in the list of observations. - Observation Universally Unique Identifier Reference: References an observation defined in the list of observations. + Observation Universally Unique Identifier Reference: A machine-oriented identifier reference to an observation defined in the list of observations. @@ -3925,10 +3923,10 @@ Risk Universally Unique Identifier - Uniquely identifies this risk. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given risk across revisions. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk elsewhere in this or other OSCAL instances. The locally defined UUID of the risk can be used to reference the data item locally or globally (e.g., in an imported 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. - Risk Universally Unique Identifier: Uniquely identifies this risk. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given risk across revisions. + Risk Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk elsewhere in this or other OSCAL instances. The locally defined UUID of the risk can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -3945,10 +3943,10 @@ Party UUID Reference - A pointer to the party who is making the log entry. + A machine-oriented identifier reference to the party who is making the log entry. - Party UUID Reference: A pointer to the party who is making the log entry. + Party UUID Reference: A machine-oriented identifier reference to the party who is making the log entry. @@ -4189,10 +4187,10 @@ Required Universally Unique Identifier - Uniquely identifies this required asset. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given required asset across revisions. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this required asset elsewhere in this or other OSCAL instances. The locally defined UUID of the asset can be used to reference the data item locally or globally (e.g., in an imported 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. - Required Universally Unique Identifier: Uniquely identifies this required asset. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given required asset across revisions. + Required Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this required asset elsewhere in this or other OSCAL instances. The locally defined UUID of the asset can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -4221,10 +4219,10 @@ Remediation Universally Unique Identifier - Uniquely identifies this remediation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given remediation across revisions. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this remediation elsewhere in this or other OSCAL instances. The locally defined UUID of the risk response can be used to reference the data item locally or globally (e.g., in an imported 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. - Remediation Universally Unique Identifier: Uniquely identifies this remediation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given remediation across revisions. + Remediation Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this remediation elsewhere in this or other OSCAL instances. The locally defined UUID of the risk response can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -4283,10 +4281,10 @@ Part Identifier - A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this part elsewhere in this or other OSCAL instances. The locally defined UUID of the part can be used to reference the data item locally or globally (e.g., in an ported 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. - Part Identifier: A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. + Part Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this part elsewhere in this or other OSCAL instances. The locally defined UUID of the part can be used to reference the data item locally or globally (e.g., in an ported 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. @@ -4365,10 +4363,10 @@ Part Identifier - A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Part Identifier: A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. + Part Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -4488,10 +4486,10 @@ Parameter Identifier - A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Parameter Identifier: A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. + Parameter Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -4777,10 +4775,10 @@ Component Identifier - The unique identifier for the component. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. - Component Identifier: The unique identifier for the component. + Component Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -4828,10 +4826,10 @@ Service Protocol Information Universally Unique Identifier - A globally unique identifier that can be used to reference this service protocol entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported 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. - Service Protocol Information Universally Unique Identifier: A globally unique identifier that can be used to reference this service protocol entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Service Protocol Information Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -5011,10 +5009,10 @@ User Universally Unique Identifier - The unique identifier for the user class. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported 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. - User Universally Unique Identifier: The unique identifier for the user class. + User Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -5155,10 +5153,10 @@ Component Universally Unique Identifier Reference - A reference to a component that is implemented as part of an inventory item. + A machine-oriented identifier reference to a component that is implemented as part of an inventory item. - Component Universally Unique Identifier Reference: A reference to a component that is implemented as part of an inventory item. + Component Universally Unique Identifier Reference: A machine-oriented identifier reference to a component that is implemented as part of an inventory item. @@ -5183,10 +5181,10 @@ Inventory Item Universally Unique Identifier - A globally unique identifier that can be used to reference this inventory item entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported 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. - Inventory Item Universally Unique Identifier: A globally unique identifier that can be used to reference this inventory item entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Inventory Item Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -5233,10 +5231,10 @@ Parameter ID - A reference to a parameter within a control, who's catalog has been imported into the current implementation context. + A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context. - Parameter ID: A reference to a parameter within a control, who's catalog has been imported into the current implementation context. + Parameter ID: A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context. @@ -5244,10 +5242,10 @@ System Identification - A unique identifier for the system described by this system security plan. + A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. - System Identification: A unique identifier for the system described by this system security plan. + System Identification: A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. @@ -5255,10 +5253,10 @@ Identification System Type - Identifies the identification system from which the provided identifier was assigned. + Identifies the identification system from which the provided identifier was assigned. - Identification System Type: Identifies the identification system from which the provided identifier was assigned. + Identification System Type: Identifies the identification system from which the provided identifier was assigned. diff --git a/xml/schema/oscal_catalog_schema.xsd b/xml/schema/oscal_catalog_schema.xsd index 59b30e494b..a1e4bc9714 100644 --- a/xml/schema/oscal_catalog_schema.xsd +++ b/xml/schema/oscal_catalog_schema.xsd @@ -53,10 +53,10 @@ Catalog Universally Unique Identifier - A globally unique identifier for this catalog instance. This UUID should be changed when this document is revised. + A globally unique identifier with cross-instance scope for this catalog instance. This UUID should be changed when this document is revised. - Catalog Universally Unique Identifier: A globally unique identifier for this catalog instance. This UUID should be changed when this document is revised. + Catalog Universally Unique Identifier: A globally unique identifier with cross-instance scope for this catalog instance. This UUID should be changed when this document is revised. @@ -116,10 +116,10 @@ Group Identifier - A unique identifier for a specific group instance that can be used to reference the group within this and in other OSCAL documents. This identifier's uniqueness is document scoped and is intended to be consistent for the same group across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in in this and other OSCAL instances (e.g., profiles). This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. - Group Identifier: A unique identifier for a specific group instance that can be used to reference the group within this and in other OSCAL documents. This identifier's uniqueness is document scoped and is intended to be consistent for the same group across minor revisions of the document. + Group Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in in this and other OSCAL instances (e.g., profiles). This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. @@ -183,10 +183,10 @@ Control Identifier - A unique identifier for a specific control instance that can be used to reference the control in other OSCAL documents. This identifier's uniqueness is document scoped and is intended to be consistent for the same control across minor revisions of the document. + A human-oriented, locally unique identifier with instance scope that can be used to reference this control elsewhere in this and other OSCAL instances (e.g., profiles). This id should be assigned per-subject, which means it should be consistently used to identify the same control across revisions of the document. - Control Identifier: A unique identifier for a specific control instance that can be used to reference the control in other OSCAL documents. This identifier's uniqueness is document scoped and is intended to be consistent for the same control across minor revisions of the document. + Control Identifier: A human-oriented, locally unique identifier with instance scope that can be used to reference this control elsewhere in this and other OSCAL instances (e.g., profiles). This id should be assigned per-subject, which means it should be consistently used to identify the same control across revisions of the document. @@ -245,10 +245,10 @@ Part Identifier - A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Part Identifier: A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. + Part Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -368,10 +368,10 @@ Parameter Identifier - A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Parameter Identifier: A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. + Parameter Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -767,10 +767,10 @@ Location Universally Unique Identifier - A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. - Location Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + Location Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. @@ -778,10 +778,10 @@ Location Reference - References a location defined in metadata. + A machine-oriented identifier reference to a 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 Reference: References a location defined in metadata. + Location Reference: A machine-oriented identifier reference to a 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). @@ -878,10 +878,10 @@ Organizational Affiliation - Identifies that the party object is a member of the organization associated with the provided UUID. + A machine-oriented identifier reference to another 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). - Organizational Affiliation: Identifies that the party object is a member of the organization associated with the provided UUID. + Organizational Affiliation: A machine-oriented identifier reference to another 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). @@ -906,10 +906,10 @@ Party Universally Unique Identifier - A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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 Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. + Party Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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. @@ -927,10 +927,10 @@ Party Reference - References a party defined in metadata. + A machine-oriented identifier reference to another 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 Reference: References a party defined in metadata. + Party Reference: A machine-oriented identifier reference to another 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). @@ -1014,11 +1014,9 @@ - Role Identifier - A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. - - Role Identifier: A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. @@ -1026,10 +1024,10 @@ Role Identifier Reference - A reference to the roles served by the user. + A human-oriented identifier reference to roles served by the user. - Role Identifier Reference: A reference to the roles served by the user. + Role Identifier Reference: A human-oriented identifier reference to roles served by the user. @@ -1223,10 +1221,10 @@ Resource Universally Unique Identifier - A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Resource Universally Unique Identifier: A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Resource Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -1273,10 +1271,10 @@ Property Universally Unique Identifier - A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Property Universally Unique Identifier: A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + Property Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -1409,10 +1407,10 @@ Responsible Role - The role that the party is responsible for. + A human-oriented identifier reference to roles served by the user. - Responsible Role: The role that the party is responsible for. + Responsible Role: A human-oriented identifier reference to roles served by the user. @@ -1458,10 +1456,10 @@ Responsible Role ID - The role that is responsible for the business function. + A human-oriented identifier reference to roles responsible for the business function. - Responsible Role ID: The role that is responsible for the business function. + Responsible Role ID: A human-oriented identifier reference to roles responsible for the business function. @@ -1674,10 +1672,10 @@ Document Identifier - A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. - Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. diff --git a/xml/schema/oscal_complete_schema.xsd b/xml/schema/oscal_complete_schema.xsd index 64ce1cffb3..a616dffa3c 100644 --- a/xml/schema/oscal_complete_schema.xsd +++ b/xml/schema/oscal_complete_schema.xsd @@ -59,10 +59,10 @@ Catalog Universally Unique Identifier - A globally unique identifier for this catalog instance. This UUID should be changed when this document is revised. + A globally unique identifier with cross-instance scope for this catalog instance. This UUID should be changed when this document is revised. - Catalog Universally Unique Identifier: A globally unique identifier for this catalog instance. This UUID should be changed when this document is revised. + Catalog Universally Unique Identifier: A globally unique identifier with cross-instance scope for this catalog instance. This UUID should be changed when this document is revised. @@ -122,10 +122,10 @@ Group Identifier - A unique identifier for a specific group instance that can be used to reference the group within this and in other OSCAL documents. This identifier's uniqueness is document scoped and is intended to be consistent for the same group across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in in this and other OSCAL instances (e.g., profiles). This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. - Group Identifier: A unique identifier for a specific group instance that can be used to reference the group within this and in other OSCAL documents. This identifier's uniqueness is document scoped and is intended to be consistent for the same group across minor revisions of the document. + Group Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in in this and other OSCAL instances (e.g., profiles). This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. @@ -189,10 +189,10 @@ Control Identifier - A unique identifier for a specific control instance that can be used to reference the control in other OSCAL documents. This identifier's uniqueness is document scoped and is intended to be consistent for the same control across minor revisions of the document. + A human-oriented, locally unique identifier with instance scope that can be used to reference this control elsewhere in this and other OSCAL instances (e.g., profiles). This id should be assigned per-subject, which means it should be consistently used to identify the same control across revisions of the document. - Control Identifier: A unique identifier for a specific control instance that can be used to reference the control in other OSCAL documents. This identifier's uniqueness is document scoped and is intended to be consistent for the same control across minor revisions of the document. + Control Identifier: A human-oriented, locally unique identifier with instance scope that can be used to reference this control elsewhere in this and other OSCAL instances (e.g., profiles). This id should be assigned per-subject, which means it should be consistently used to identify the same control across revisions of the document. @@ -251,10 +251,10 @@ Part Identifier - A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Part Identifier: A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. + Part Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -374,10 +374,10 @@ Parameter Identifier - A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Parameter Identifier: A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. + Parameter Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -773,10 +773,10 @@ Location Universally Unique Identifier - A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. - Location Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + Location Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. @@ -784,10 +784,10 @@ Location Reference - References a location defined in metadata. + A machine-oriented identifier reference to a 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 Reference: References a location defined in metadata. + Location Reference: A machine-oriented identifier reference to a 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). @@ -884,10 +884,10 @@ Organizational Affiliation - Identifies that the party object is a member of the organization associated with the provided UUID. + A machine-oriented identifier reference to another 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). - Organizational Affiliation: Identifies that the party object is a member of the organization associated with the provided UUID. + Organizational Affiliation: A machine-oriented identifier reference to another 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). @@ -912,10 +912,10 @@ Party Universally Unique Identifier - A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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 Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. + Party Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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. @@ -933,10 +933,10 @@ Party Reference - References a party defined in metadata. + A machine-oriented identifier reference to another 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 Reference: References a party defined in metadata. + Party Reference: A machine-oriented identifier reference to another 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). @@ -1020,11 +1020,9 @@ - Role Identifier - A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. - - Role Identifier: A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. @@ -1032,10 +1030,10 @@ Role Identifier Reference - A reference to the roles served by the user. + A human-oriented identifier reference to roles served by the user. - Role Identifier Reference: A reference to the roles served by the user. + Role Identifier Reference: A human-oriented identifier reference to roles served by the user. @@ -1229,10 +1227,10 @@ Resource Universally Unique Identifier - A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Resource Universally Unique Identifier: A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Resource Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -1279,10 +1277,10 @@ Property Universally Unique Identifier - A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Property Universally Unique Identifier: A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + Property Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -1415,10 +1413,10 @@ Responsible Role - The role that the party is responsible for. + A human-oriented identifier reference to roles served by the user. - Responsible Role: The role that the party is responsible for. + Responsible Role: A human-oriented identifier reference to roles served by the user. @@ -1464,10 +1462,10 @@ Responsible Role ID - The role that is responsible for the business function. + A human-oriented identifier reference to roles responsible for the business function. - Responsible Role ID: The role that is responsible for the business function. + Responsible Role ID: A human-oriented identifier reference to roles responsible for the business function. @@ -1680,10 +1678,10 @@ Document Identifier - A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. - Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. @@ -1735,11 +1733,11 @@ - Catalog Universally Unique Identifier - A globally unique identifier for this profile instance. This UUID should be changed when this document is revised. + Profile Universally Unique Identifier + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this profile elsewhere in this or other OSCAL instances. The locally defined UUID of the profile can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance).This identifier should be assigned per-subject, which means it should be consistently used to identify the same profile across revisions of the document. - Catalog Universally Unique Identifier: A globally unique identifier for this profile instance. This UUID should be changed when this document is revised. + Profile Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this profile elsewhere in this or other OSCAL instances. The locally defined UUID of the profile can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance).This identifier should be assigned per-subject, which means it should be consistently used to identify the same profile across revisions of the document. @@ -1798,6 +1796,10 @@ type="oscal-complete:oscal-profile-as-is-FIELD" minOccurs="0" maxOccurs="1"/> + + + + + Flat + A Flat element indicates that the controls should be structured in a completely flat list. It does not contain any elements or attributes. + + + Flat: A Flat element indicates that the controls should be structured in a completely flat list. It does not contain any elements or attributes. + + @@ -1912,10 +1924,10 @@ Group Identifier - A unique identifier for a specific group instance that can be used to reference the group within this and in other OSCAL documents. This identifier's uniqueness is document scoped and is intended to be consistent for the same group across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. - Group Identifier: A unique identifier for a specific group instance that can be used to reference the group within this and in other OSCAL documents. This identifier's uniqueness is document scoped and is intended to be consistent for the same group across minor revisions of the document. + Group Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. @@ -2011,10 +2023,10 @@ Parameter ID - Indicates the value of the 'id' flag on a target parameter; i.e. which parameter to set + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Parameter ID: Indicates the value of the 'id' flag on a target parameter; i.e. which parameter to set + Parameter ID: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -2171,10 +2183,10 @@ Control Identifier Reference - A reference to a control with a corresponding id value. + A human-oriented identifier reference to a control with a corresponding 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). - Control Identifier Reference: A reference to a control with a corresponding id value. + Control Identifier Reference: A human-oriented identifier reference to a control with a corresponding 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). @@ -2339,10 +2351,10 @@ Component Definition Universally Unique Identifier - A globally unique identifier for this component definition instance. This UUID should be changed when this document is revised. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component definition elsewhere in this or other OSCAL instances. The locally defined UUID of the component definition can be used to reference the data item locally or globally (e.g., in an imported 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. - Component Definition Universally Unique Identifier: A globally unique identifier for this component definition instance. This UUID should be changed when this document is revised. + Component Definition Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component definition elsewhere in this or other OSCAL instances. The locally defined UUID of the component definition can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -2461,10 +2473,10 @@ Component Identifier - The unique identifier for the component. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. - Component Identifier: The unique identifier for the component. + Component Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -2539,10 +2551,10 @@ Capability Identifier - A unique identifier for a capability. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this capability elsewhere in this or other OSCAL instances. The locally defined UUID of the capability can be used to reference the data item locally or globally (e.g., in an imported 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. - Capability Identifier: A unique identifier for a capability. + Capability Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this capability elsewhere in this or other OSCAL instances. The locally defined UUID of the capability can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -2586,10 +2598,10 @@ Component Reference - A reference to a component by its identifier + A machine-oriented identifier reference to a component. - Component Reference: A reference to a component by its identifier + Component Reference: A machine-oriented identifier reference to a component. @@ -2639,10 +2651,10 @@ Control Implementation Set Identifier - A unique identifier for the set of implemented controls. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference a set of implemented controls elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation set can be used to reference the data item locally or globally (e.g., in an imported 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. - Control Implementation Set Identifier: A unique identifier for the set of implemented controls. + Control Implementation Set Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference a set of implemented controls elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation set can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -2721,20 +2733,20 @@ Control Implementation Identifier - A unique identifier for a specific control implementation. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference a specific control implementation elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. - Control Implementation Identifier: A unique identifier for a specific control implementation. + Control Implementation Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference a specific control implementation elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. Control Identifier Reference - A reference to a control with a corresponding id value. + A human-oriented identifier reference to a control with a corresponding 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). - Control Identifier Reference: A reference to a control with a corresponding id value. + Control Identifier Reference: A human-oriented identifier reference to a control with a corresponding 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). @@ -2795,20 +2807,20 @@ Control Statement Reference - A reference to a control statement by its identifier + A human-oriented identifier reference to a control statement. - Control Statement Reference: A reference to a control statement by its identifier + Control Statement Reference: A human-oriented identifier reference to a control statement. Control Statement Reference Universally Unique Identifier - A globally unique identifier that can be used to reference this control statement entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. The UUID of the control statement in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance). - Control Statement Reference Universally Unique Identifier: A globally unique identifier that can be used to reference this control statement entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Control Statement Reference Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. The UUID of the control statement in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance). @@ -2942,10 +2954,10 @@ Component Identifier - The unique identifier for the component. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. - Component Identifier: The unique identifier for the component. + Component Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -2993,10 +3005,10 @@ Service Protocol Information Universally Unique Identifier - A globally unique identifier that can be used to reference this service protocol entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported 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. - Service Protocol Information Universally Unique Identifier: A globally unique identifier that can be used to reference this service protocol entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Service Protocol Information Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -3176,10 +3188,10 @@ User Universally Unique Identifier - The unique identifier for the user class. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported 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. - User Universally Unique Identifier: The unique identifier for the user class. + User Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -3320,10 +3332,10 @@ Component Universally Unique Identifier Reference - A reference to a component that is implemented as part of an inventory item. + A machine-oriented identifier reference to a component that is implemented as part of an inventory item. - Component Universally Unique Identifier Reference: A reference to a component that is implemented as part of an inventory item. + Component Universally Unique Identifier Reference: A machine-oriented identifier reference to a component that is implemented as part of an inventory item. @@ -3348,10 +3360,10 @@ Inventory Item Universally Unique Identifier - A globally unique identifier that can be used to reference this inventory item entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported 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. - Inventory Item Universally Unique Identifier: A globally unique identifier that can be used to reference this inventory item entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Inventory Item Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -3398,10 +3410,10 @@ Parameter ID - A reference to a parameter within a control, who's catalog has been imported into the current implementation context. + A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context. - Parameter ID: A reference to a parameter within a control, who's catalog has been imported into the current implementation context. + Parameter ID: A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context. @@ -3409,10 +3421,10 @@ System Identification - A unique identifier for the system described by this system security plan. + A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. - System Identification: A unique identifier for the system described by this system security plan. + System Identification: A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. @@ -3420,10 +3432,10 @@ Identification System Type - Identifies the identification system from which the provided identifier was assigned. + Identifies the identification system from which the provided identifier was assigned. - Identification System Type: Identifies the identification system from which the provided identifier was assigned. + Identification System Type: Identifies the identification system from which the provided identifier was assigned. @@ -3470,10 +3482,10 @@ System Security Plan Universally Unique Identifier - A globally unique identifier for this catalog instance. This UUID should be changed when this document is revised. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this system security plan (SSP) elsewhere in this or other OSCAL instances. The locally defined UUID of the SSP can be used to reference the data item locally or globally (e.g., in an imported 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. - System Security Plan Universally Unique Identifier: A globally unique identifier for this catalog instance. This UUID should be changed when this document is revised. + System Security Plan Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this system security plan (SSP) elsewhere in this or other OSCAL instances. The locally defined UUID of the SSP can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -3714,10 +3726,10 @@ Information Type Systematized Identifier - An identifier qualified by the given identification system used, such as NIST SP 800-60. + A human-oriented, globally unique identifier qualified by the given identification system used, such as NIST SP 800-60. This identifier has cross-instance scope and can be used to reference this system elsewhere in this or other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Information Type Systematized Identifier: An identifier qualified by the given identification system used, such as NIST SP 800-60. + Information Type Systematized Identifier: A human-oriented, globally unique identifier qualified by the given identification system used, such as NIST SP 800-60. This identifier has cross-instance scope and can be used to reference this system elsewhere in this or other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -3883,10 +3895,10 @@ Information Type Universally Unique Identifier - A globally unique identifier that can be used to reference this information type entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this information type elsewhere in this or other OSCAL instances. The locally defined UUID of the information type can be used to reference the data item locally or globally (e.g., in an imported 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. - Information Type Universally Unique Identifier: A globally unique identifier that can be used to reference this information type entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Information Type Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this information type elsewhere in this or other OSCAL instances. The locally defined UUID of the information type can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -4151,10 +4163,10 @@ Diagram ID - The identifier for this diagram. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this diagram elsewhere in this or other OSCAL instances. The locally defined UUID of the diagram can be used to reference the data item locally or globally (e.g., in an imported 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. - Diagram ID: The identifier for this diagram. + Diagram ID: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this diagram elsewhere in this or other OSCAL instances. The locally defined UUID of the diagram can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -4323,10 +4335,10 @@ party-uuid field - A reference to the party that manages the leveraged system. + A machine-oriented identifier reference to the party that manages the leveraged system. - party-uuid field: A reference to the party that manages the leveraged system. + party-uuid field: A machine-oriented identifier reference to the party that manages the leveraged system. @@ -4355,10 +4367,10 @@ Leveraged Authorization Universally Unique Identifier - A globally unique identifier that can be used to reference this leveraged authorization entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope and can be used to reference this leveraged authorization elsewhere in this or other OSCAL instances. The locally defined UUID of the leveraged authorization can be used to reference the data item locally or globally (e.g., in an imported 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. - Leveraged Authorization Universally Unique Identifier: A globally unique identifier that can be used to reference this leveraged authorization entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Leveraged Authorization Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope and can be used to reference this leveraged authorization elsewhere in this or other OSCAL instances. The locally defined UUID of the leveraged authorization can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -4481,20 +4493,20 @@ Control Requirement Universally Unique Identifier - A globally unique identifier that can be used to reference this control requirement entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control requirement elsewhere in this or other OSCAL instances. The locally defined UUID of the control requirement can be used to reference the data item locally or globally (e.g., in an imported 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. - Control Requirement Universally Unique Identifier: A globally unique identifier that can be used to reference this control requirement entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Control Requirement Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control requirement elsewhere in this or other OSCAL instances. The locally defined UUID of the control requirement can be used to reference the data item locally or globally (e.g., in an imported 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. Control Identifier Reference - A reference to a control with a corresponding id value. + A human-oriented identifier reference to a control with a corresponding 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). - Control Identifier Reference: A reference to a control with a corresponding id value. + Control Identifier Reference: A human-oriented identifier reference to a control with a corresponding 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). @@ -4544,20 +4556,20 @@ Control Statement Reference - A reference to a control statement by its identifier + A human-oriented identifier reference to a control statement. - Control Statement Reference: A reference to a control statement by its identifier + Control Statement Reference: A human-oriented identifier reference to a control statement. Control Statement Reference Universally Unique Identifier - A globally unique identifier that can be used to reference this control statement entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. The UUID of the control statement in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance). - Control Statement Reference Universally Unique Identifier: A globally unique identifier that can be used to reference this control statement entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Control Statement Reference Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. The UUID of the control statement in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance). @@ -4694,10 +4706,10 @@ Provided Universally Unique Identifier - A globally unique identifier that can be used to reference this provided entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this provided entry elsewhere in this or other OSCAL instances. The locally defined UUID of the provided entry can be used to reference the data item locally or globally (e.g., in an imported 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. - Provided Universally Unique Identifier: A globally unique identifier that can be used to reference this provided entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Provided Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this provided entry elsewhere in this or other OSCAL instances. The locally defined UUID of the provided entry can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -4760,20 +4772,20 @@ Responsibility Universally Unique Identifier - A globally unique identifier that can be used to reference this responsibility entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this responsibility elsewhere in this or other OSCAL instances. The locally defined UUID of the responsibility can be used to reference the data item locally or globally (e.g., in an imported 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. - Responsibility Universally Unique Identifier: A globally unique identifier that can be used to reference this responsibility entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Responsibility Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this responsibility elsewhere in this or other OSCAL instances. The locally defined UUID of the responsibility can be used to reference the data item locally or globally (e.g., in an imported 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. Provided UUID - Identifies a 'provided' assembly associated with this assembly. + A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system. - Provided UUID: Identifies a 'provided' assembly associated with this assembly. + Provided UUID: A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system. @@ -4839,20 +4851,20 @@ Inherited Universally Unique Identifier - A globally unique identifier that can be used to reference this inherited entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inherited entry elsewhere in this or other OSCAL instances. The locally defined UUID of the inherited control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. - Inherited Universally Unique Identifier: A globally unique identifier that can be used to reference this inherited entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Inherited Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inherited entry elsewhere in this or other OSCAL instances. The locally defined UUID of the inherited control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. Provided UUID - Identifies a 'provided' assembly associated with this assembly. + A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system. - Provided UUID: Identifies a 'provided' assembly associated with this assembly. + Provided UUID: A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system. @@ -4915,20 +4927,20 @@ Satisfied Universally Unique Identifier - A globally unique identifier that can be used to reference this satisfied entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this satisfied control implementation entry elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. - Satisfied Universally Unique Identifier: A globally unique identifier that can be used to reference this satisfied entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Satisfied Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this satisfied control implementation entry elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. - Provided UUID - Identifies a 'provided' assembly associated with this assembly. + Responsibility UUID + A machine-oriented identifier reference to a control implementation that satisfies a responsibility imposed by a leveraged system. - Provided UUID: Identifies a 'provided' assembly associated with this assembly. + Responsibility UUID: A machine-oriented identifier reference to a control implementation that satisfies a responsibility imposed by a leveraged system. @@ -4957,20 +4969,20 @@ Component Universally Unique Identifier Reference - A reference to the component that is implementing a given control or control statement. + A machine-oriented identifier reference to the component that is implemeting a given control. - Component Universally Unique Identifier Reference: A reference to the component that is implementing a given control or control statement. + Component Universally Unique Identifier Reference: A machine-oriented identifier reference to the component that is implemeting a given control. By-Component Universally Unique Identifier - A globally unique identifier that can be used to reference this by-component entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this by-component entry elsewhere in this or other OSCAL instances. The locally defined UUID of the by-component entry can be used to reference the data item locally or globally (e.g., in an imported 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. - By-Component Universally Unique Identifier: A globally unique identifier that can be used to reference this by-component entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + By-Component Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this by-component entry elsewhere in this or other OSCAL instances. The locally defined UUID of the by-component entry can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -5086,10 +5098,10 @@ Assessment Plan Universally Unique Identifier - Uniquely identifies this assessment plan. This UUID must be changed each time the content of the plan changes. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment plan in this or other OSCAL instances. The locally defined UUID of the assessment plan can be used to reference the data item locally or globally (e.g., in an imported 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. - Assessment Plan Universally Unique Identifier: Uniquely identifies this assessment plan. This UUID must be changed each time the content of the plan changes. + Assessment Plan Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment plan in this or other OSCAL instances. The locally defined UUID of the assessment plan can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -5187,10 +5199,10 @@ Control Identifier Reference - A reference to a control with a corresponding id value. + A human-oriented identifier reference to a control with a corresponding 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). - Control Identifier Reference: A reference to a control with a corresponding id value. + Control Identifier Reference: A human-oriented identifier reference to a control with a corresponding 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). @@ -5251,10 +5263,10 @@ Assessment Method Universally Unique Identifier - Uniquely identifies this defined assessment method. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given assessment method across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment method elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment method can be used to reference the data item locally or globally (e.g., in an imported 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. - Assessment Method Universally Unique Identifier: Uniquely identifies this defined assessment method. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given assessment method across revisions of the document. + Assessment Method Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment method elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment method can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -5383,10 +5395,10 @@ Step Universally Unique Identifier - Uniquely identifies a step. This UUID may be referenced elsewhere in an OSCAL document when referring to this step. A UUID should be consistently used for a given test step across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this step elsewhere in this or other OSCAL instances. The locally defined UUID of the step (in a series of steps) can be used to reference the data item locally or globally (e.g., in an imported 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. - Step Universally Unique Identifier: Uniquely identifies a step. This UUID may be referenced elsewhere in an OSCAL document when referring to this step. A UUID should be consistently used for a given test step across revisions of the document. + Step Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this step elsewhere in this or other OSCAL instances. The locally defined UUID of the step (in a series of steps) can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -5419,10 +5431,10 @@ Assessment Activity Universally Unique Identifier - Uniquely identifies this assessment activity. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given included activity across revisions of the document. + A machine-oriented, globally unique> identifier with cross-instance scope that can be used to reference this assessment activity elsewhere in this or other OSCAL instances. The locally defined UUID of the activity can be used to reference the data item locally or globally (e.g., in an imported 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. - Assessment Activity Universally Unique Identifier: Uniquely identifies this assessment activity. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given included activity across revisions of the document. + Assessment Activity Universally Unique Identifier: A machine-oriented, globally unique> identifier with cross-instance scope that can be used to reference this assessment activity elsewhere in this or other OSCAL instances. The locally defined UUID of the activity can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -5613,10 +5625,10 @@ Task Universally Unique Identifier Reference - References a unique task by UUID. + A machine-oriented identifier reference to a unique task. - Task Universally Unique Identifier Reference: References a unique task by UUID. + Task Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique task. @@ -5672,10 +5684,10 @@ Activity Universally Unique Identifier Reference - References an activity defined in the list of activities. + A machine-oriented identifier reference to an activity defined in the list of activities. - Activity Universally Unique Identifier Reference: References an activity defined in the list of activities. + Activity Universally Unique Identifier Reference: A machine-oriented identifier reference to an activity defined in the list of activities. @@ -5708,10 +5720,10 @@ Task Universally Unique Identifier - Uniquely identifies this assessment task. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this task elsewhere in this or other OSCAL instances. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. - Task Universally Unique Identifier: Uniquely identifies this assessment task. + Task Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this task elsewhere in this or other OSCAL instances. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -5953,10 +5965,10 @@ Control Identifier Reference - A reference to a control with a corresponding id value. + A human-oriented identifier reference to a control with a corresponding 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). - Control Identifier Reference: A reference to a control with a corresponding id value. + Control Identifier Reference: A human-oriented identifier reference to a control with a corresponding 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). @@ -6019,10 +6031,10 @@ Task Universally Unique Identifier - Uniquely identifies an assessment activity to be performed as part of the event. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference (in this or other OSCAL instances) an assessment activity to be performed as part of the event. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. - Task Universally Unique Identifier: Uniquely identifies an assessment activity to be performed as part of the event. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. + Task Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference (in this or other OSCAL instances) an assessment activity to be performed as part of the event. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -6055,10 +6067,10 @@ Assessment Subject Placeholder Universally Unique Identifier - Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task. + A machine-oriented, globally unique identifier for a set of assessment subjects that will be identified by a task or an activity that is part of a task. The locally defined UUID of the assessment subject placeholder can be used to reference the data item locally or globally (e.g., in an imported 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. - Assessment Subject Placeholder Universally Unique Identifier: Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task. + Assessment Subject Placeholder Universally Unique Identifier: A machine-oriented, globally unique identifier for a set of assessment subjects that will be identified by a task or an activity that is part of a task. The locally defined UUID of the assessment subject placeholder can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -6182,10 +6194,10 @@ Subject Universally Unique Identifier Reference - A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. + A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. - Subject Universally Unique Identifier Reference: A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. + Subject Universally Unique Identifier Reference: A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. @@ -6203,10 +6215,10 @@ Identifies the Subject - A pointer to a resource based on its universally unique identifier (UUID). Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. + A human-oriented identifier reference to a resource. Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. - Identifies the Subject: A pointer to a resource based on its universally unique identifier (UUID). Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. + Identifies the Subject: A human-oriented identifier reference to a resource. Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. @@ -6252,10 +6264,10 @@ Subject Universally Unique Identifier Reference - A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. + A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. - Subject Universally Unique Identifier Reference: A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. + Subject Universally Unique Identifier Reference: A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. @@ -6360,10 +6372,10 @@ Component Universally Unique Identifier Reference - A reference to a component that is implemented as part of an inventory item. + A machine-oriented identifier reference to a component that is implemented as part of an inventory item. - Component Universally Unique Identifier Reference: A reference to a component that is implemented as part of an inventory item. + Component Universally Unique Identifier Reference: A machine-oriented identifier reference to a component that is implemented as part of an inventory item. @@ -6388,10 +6400,10 @@ Assessment Platform Universally Unique Identifier - Uniquely identifies this assessment Platform. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment platform elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment platform can be used to reference the data item locally or globally (e.g., in an imported 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. - Assessment Platform Universally Unique Identifier: Uniquely identifies this assessment Platform. + Assessment Platform Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment platform elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment platform can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -6529,10 +6541,10 @@ Finding Target Identifier Reference - Identifies the specific target qualified by the type. + A machine-oriented identifier reference for a specific target qualified by the type. - Finding Target Identifier Reference: Identifies the specific target qualified by the type. + Finding Target Identifier Reference: A machine-oriented identifier reference for a specific target qualified by the type. @@ -6726,10 +6738,10 @@ Observation Universally Unique Identifier - Uniquely identifies this observation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given observation across revisions. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. The locally defined UUID of the observation can be used to reference the data item locally or globally (e.g., in an imorted 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. - Observation Universally Unique Identifier: Uniquely identifies this observation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given observation across revisions. + Observation Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. The locally defined UUID of the observation can be used to reference the data item locally or globally (e.g., in an imorted 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. @@ -6786,10 +6798,10 @@ Actor Universally Unique Identifier Reference - A pointer to the tool or person based on the associated type. + A machine-oriented identifier reference to the tool or person based on the associated type. - Actor Universally Unique Identifier Reference: A pointer to the tool or person based on the associated type. + Actor Universally Unique Identifier Reference: A machine-oriented identifier reference to the tool or person based on the associated type. @@ -6851,10 +6863,10 @@ Assessment Subject Placeholder Universally Unique Identifier Reference - References a unique assessment subject placeholder defined by this task. + A machine-oriented identifier reference to a unique assessment subject placeholder defined by this task. - Assessment Subject Placeholder Universally Unique Identifier Reference: References a unique assessment subject placeholder defined by this task. + Assessment Subject Placeholder Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique assessment subject placeholder defined by this task. @@ -6879,10 +6891,10 @@ Task Universally Unique Identifier Reference - References a unique task by UUID. + A machine-oriented identifier reference to a unique task. - Task Universally Unique Identifier Reference: References a unique task by UUID. + Task Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique task. @@ -7051,20 +7063,20 @@ Mitigating Factor Universally Unique Identifier - Uniquely identifies this mitigating factor. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given mitigating factor across revisions. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mitigating factor elsewhere in this or other OSCAL instances. The locally defined UUID of the mitigating factor can be used to reference the data item locally or globally (e.g., in an imported 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. - Mitigating Factor Universally Unique Identifier: Uniquely identifies this mitigating factor. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given mitigating factor across revisions. + Mitigating Factor Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mitigating factor elsewhere in this or other OSCAL instances. The locally defined UUID of the mitigating factor can be used to reference the data item locally or globally (e.g., in an imported 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. Implementation UUID - Points to an implementation statement in the SSP. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this implementation statement elsewhere in this or other OSCAL instancess. The locally defined UUID of the implementation statement can be used to reference the data item locally or globally (e.g., in an imported 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. - Implementation UUID: Points to an implementation statement in the SSP. + Implementation UUID: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this implementation statement elsewhere in this or other OSCAL instancess. The locally defined UUID of the implementation statement can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -7223,10 +7235,10 @@ Response Universally Unique Identifier Reference - References a unique risk response by UUID. + A machine-oriented identifier reference to a unique risk response. - Response Universally Unique Identifier Reference: References a unique risk response by UUID. + Response Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique risk response. @@ -7251,10 +7263,10 @@ Risk Log Entry Universally Unique Identifier - Uniquely identifies a risk log entry. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk log entry elsewhere in this or other OSCAL instances. The locally defined UUID of the risk log entry can be used to reference the data item locally or globally (e.g., in an imported 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. - Risk Log Entry Universally Unique Identifier: Uniquely identifies a risk log entry. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. + Risk Log Entry Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk log entry elsewhere in this or other OSCAL instances. The locally defined UUID of the risk log entry can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -7276,10 +7288,10 @@ Observation Universally Unique Identifier Reference - References an observation defined in the list of observations. + A machine-oriented identifier reference to an observation defined in the list of observations. - Observation Universally Unique Identifier Reference: References an observation defined in the list of observations. + Observation Universally Unique Identifier Reference: A machine-oriented identifier reference to an observation defined in the list of observations. @@ -7289,10 +7301,10 @@ Risk Universally Unique Identifier - Uniquely identifies this risk. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given risk across revisions. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk elsewhere in this or other OSCAL instances. The locally defined UUID of the risk can be used to reference the data item locally or globally (e.g., in an imported 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. - Risk Universally Unique Identifier: Uniquely identifies this risk. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given risk across revisions. + Risk Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk elsewhere in this or other OSCAL instances. The locally defined UUID of the risk can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -7309,10 +7321,10 @@ Party UUID Reference - A pointer to the party who is making the log entry. + A machine-oriented identifier reference to the party who is making the log entry. - Party UUID Reference: A pointer to the party who is making the log entry. + Party UUID Reference: A machine-oriented identifier reference to the party who is making the log entry. @@ -7553,10 +7565,10 @@ Required Universally Unique Identifier - Uniquely identifies this required asset. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given required asset across revisions. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this required asset elsewhere in this or other OSCAL instances. The locally defined UUID of the asset can be used to reference the data item locally or globally (e.g., in an imported 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. - Required Universally Unique Identifier: Uniquely identifies this required asset. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given required asset across revisions. + Required Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this required asset elsewhere in this or other OSCAL instances. The locally defined UUID of the asset can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -7585,10 +7597,10 @@ Remediation Universally Unique Identifier - Uniquely identifies this remediation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given remediation across revisions. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this remediation elsewhere in this or other OSCAL instances. The locally defined UUID of the risk response can be used to reference the data item locally or globally (e.g., in an imported 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. - Remediation Universally Unique Identifier: Uniquely identifies this remediation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given remediation across revisions. + Remediation Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this remediation elsewhere in this or other OSCAL instances. The locally defined UUID of the risk response can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -7647,10 +7659,10 @@ Part Identifier - A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this part elsewhere in this or other OSCAL instances. The locally defined UUID of the part can be used to reference the data item locally or globally (e.g., in an ported 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. - Part Identifier: A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. + Part Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this part elsewhere in this or other OSCAL instances. The locally defined UUID of the part can be used to reference the data item locally or globally (e.g., in an ported 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. @@ -7754,10 +7766,10 @@ Assessment Results Universally Unique Identifier - Uniquely identifies this assessment results file. This UUID must be changed each time the content of the results changes. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment results instance in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported 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. - Assessment Results Universally Unique Identifier: Uniquely identifies this assessment results file. This UUID must be changed each time the content of the results changes. + Assessment Results Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment results instance in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -8009,10 +8021,10 @@ Assessment Log Entry Universally Unique Identifier - Uniquely identifies an assessment event. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference an assessment event in this or other OSCAL instances. The locally defined UUID of the assessment log entry can be used to reference the data item locally or globally (e.g., in an imported 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. - Assessment Log Entry Universally Unique Identifier: Uniquely identifies an assessment event. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. + Assessment Log Entry Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference an assessment event in this or other OSCAL instances. The locally defined UUID of the assessment log entry can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -8052,10 +8064,10 @@ Results Universally Unique Identifier - Uniquely identifies this set of results. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given set of results across revisions. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this set of results in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported 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. - Results Universally Unique Identifier: Uniquely identifies this set of results. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given set of results across revisions. + Results Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this set of results in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -8120,10 +8132,10 @@ Implementation Statement UUID - Identifies the implementation statement in the SSP to which this finding is related. + A machine-oriented identifier reference to the implementation statement in the SSP to which this finding is related. - Implementation Statement UUID: Identifies the implementation statement in the SSP to which this finding is related. + Implementation Statement UUID: A machine-oriented identifier reference to the implementation statement in the SSP to which this finding is related. @@ -8142,10 +8154,10 @@ Observation Universally Unique Identifier Reference - References an observation defined in the list of observations. + A machine-oriented identifier reference to an observation defined in the list of observations. - Observation Universally Unique Identifier Reference: References an observation defined in the list of observations. + Observation Universally Unique Identifier Reference: A machine-oriented identifier reference to an observation defined in the list of observations. @@ -8164,10 +8176,10 @@ Risk Universally Unique Identifier Reference - References an risk defined in the list of risks. + A machine-oriented identifier reference to a risk defined in the list of risks. - Risk Universally Unique Identifier Reference: References an risk defined in the list of risks. + Risk Universally Unique Identifier Reference: A machine-oriented identifier reference to a risk defined in the list of risks. @@ -8192,10 +8204,10 @@ Finding Universally Unique Identifier - Uniquely identifies this finding. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given finding across revisions. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this finding in this or other OSCAL instances. The locally defined UUID of the finding can be used to reference the data item locally or globally (e.g., in an imported 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. - Finding Universally Unique Identifier: Uniquely identifies this finding. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given finding across revisions. + Finding Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this finding in this or other OSCAL instances. The locally defined UUID of the finding can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -8285,10 +8297,10 @@ POA&M Universally Unique Identifier - Uniquely identifies this POA&M. This UUID must be changed each time the content of the POA&M changes. + A machine-oriented, globally unique identifier with instancescope that can be used to reference this POA&M instance in this 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. - POA&M Universally Unique Identifier: Uniquely identifies this POA&M. This UUID must be changed each time the content of the POA&M changes. + POA&M Universally Unique Identifier: A machine-oriented, globally unique identifier with instancescope that can be used to reference this POA&M instance in this 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. @@ -8407,10 +8419,10 @@ Observation Universally Unique Identifier Reference - References an observation defined in the list of observations. + A machine-oriented identifier reference to an observation defined in the list of observations. - Observation Universally Unique Identifier Reference: References an observation defined in the list of observations. + Observation Universally Unique Identifier Reference: A machine-oriented identifier reference to an observation defined in the list of observations. @@ -8429,10 +8441,10 @@ Risk Universally Unique Identifier Reference - References an risk defined in the list of risks. + A machine-oriented identifier reference to a risk defined in the list of risks. - Risk Universally Unique Identifier Reference: References an risk defined in the list of risks. + Risk Universally Unique Identifier Reference: A machine-oriented identifier reference to a risk defined in the list of risks. @@ -8457,10 +8469,10 @@ POA&M Item Universally Unique Identifier - Uniquely identifies the POA&M entry. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given POA&M item across revisions of the document. + A machine-oriented, globally unique identifier with instance scope that can be used to reference this POA&M item entry in this 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. - POA&M Item Universally Unique Identifier: Uniquely identifies the POA&M entry. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given POA&M item across revisions of the document. + POA&M Item Universally Unique Identifier: A machine-oriented, globally unique identifier with instance scope that can be used to reference this POA&M item entry in this 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. diff --git a/xml/schema/oscal_component_schema.xsd b/xml/schema/oscal_component_schema.xsd index 23eda146ed..2b62d39331 100644 --- a/xml/schema/oscal_component_schema.xsd +++ b/xml/schema/oscal_component_schema.xsd @@ -56,10 +56,10 @@ Component Definition Universally Unique Identifier - A globally unique identifier for this component definition instance. This UUID should be changed when this document is revised. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component definition elsewhere in this or other OSCAL instances. The locally defined UUID of the component definition can be used to reference the data item locally or globally (e.g., in an imported 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. - Component Definition Universally Unique Identifier: A globally unique identifier for this component definition instance. This UUID should be changed when this document is revised. + Component Definition Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component definition elsewhere in this or other OSCAL instances. The locally defined UUID of the component definition can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -180,10 +180,10 @@ Component Identifier - The unique identifier for the component. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. - Component Identifier: The unique identifier for the component. + Component Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -258,10 +258,10 @@ Capability Identifier - A unique identifier for a capability. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this capability elsewhere in this or other OSCAL instances. The locally defined UUID of the capability can be used to reference the data item locally or globally (e.g., in an imported 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. - Capability Identifier: A unique identifier for a capability. + Capability Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this capability elsewhere in this or other OSCAL instances. The locally defined UUID of the capability can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -307,10 +307,10 @@ Component Reference - A reference to a component by its identifier + A machine-oriented identifier reference to a component. - Component Reference: A reference to a component by its identifier + Component Reference: A machine-oriented identifier reference to a component. @@ -360,10 +360,10 @@ Control Implementation Set Identifier - A unique identifier for the set of implemented controls. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference a set of implemented controls elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation set can be used to reference the data item locally or globally (e.g., in an imported 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. - Control Implementation Set Identifier: A unique identifier for the set of implemented controls. + Control Implementation Set Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference a set of implemented controls elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation set can be used to reference the data item locally or globally (e.g., in an imported 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. Control Implementation Identifier - A unique identifier for a specific control implementation. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference a specific control implementation elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. - Control Implementation Identifier: A unique identifier for a specific control implementation. + Control Implementation Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference a specific control implementation elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. Control Identifier Reference - A reference to a control with a corresponding id value. + A human-oriented identifier reference to a control with a corresponding 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). - Control Identifier Reference: A reference to a control with a corresponding id value. + Control Identifier Reference: A human-oriented identifier reference to a control with a corresponding 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). @@ -522,20 +522,20 @@ Control Statement Reference - A reference to a control statement by its identifier + A human-oriented identifier reference to a control statement. - Control Statement Reference: A reference to a control statement by its identifier + Control Statement Reference: A human-oriented identifier reference to a control statement. Control Statement Reference Universally Unique Identifier - A globally unique identifier that can be used to reference this control statement entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. The UUID of the control statement in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance). - Control Statement Reference Universally Unique Identifier: A globally unique identifier that can be used to reference this control statement entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Control Statement Reference Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. The UUID of the control statement in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance). @@ -669,10 +669,10 @@ Component Identifier - The unique identifier for the component. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. - Component Identifier: The unique identifier for the component. + Component Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -720,10 +720,10 @@ Service Protocol Information Universally Unique Identifier - A globally unique identifier that can be used to reference this service protocol entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported 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. - Service Protocol Information Universally Unique Identifier: A globally unique identifier that can be used to reference this service protocol entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Service Protocol Information Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -903,10 +903,10 @@ User Universally Unique Identifier - The unique identifier for the user class. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported 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. - User Universally Unique Identifier: The unique identifier for the user class. + User Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -1049,10 +1049,10 @@ Component Universally Unique Identifier Reference - A reference to a component that is implemented as part of an inventory item. + A machine-oriented identifier reference to a component that is implemented as part of an inventory item. - Component Universally Unique Identifier Reference: A reference to a component that is implemented as part of an inventory item. + Component Universally Unique Identifier Reference: A machine-oriented identifier reference to a component that is implemented as part of an inventory item. @@ -1077,10 +1077,10 @@ Inventory Item Universally Unique Identifier - A globally unique identifier that can be used to reference this inventory item entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported 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. - Inventory Item Universally Unique Identifier: A globally unique identifier that can be used to reference this inventory item entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Inventory Item Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -1129,10 +1129,10 @@ Parameter ID - A reference to a parameter within a control, who's catalog has been imported into the current implementation context. + A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context. - Parameter ID: A reference to a parameter within a control, who's catalog has been imported into the current implementation context. + Parameter ID: A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context. @@ -1140,10 +1140,10 @@ System Identification - A unique identifier for the system described by this system security plan. + A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. - System Identification: A unique identifier for the system described by this system security plan. + System Identification: A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. @@ -1151,10 +1151,10 @@ Identification System Type - Identifies the identification system from which the provided identifier was assigned. + Identifies the identification system from which the provided identifier was assigned. - Identification System Type: Identifies the identification system from which the provided identifier was assigned. + Identification System Type: Identifies the identification system from which the provided identifier was assigned. @@ -1400,10 +1400,10 @@ Location Universally Unique Identifier - A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. - Location Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + Location Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. @@ -1411,10 +1411,10 @@ Location Reference - References a location defined in metadata. + A machine-oriented identifier reference to a 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 Reference: References a location defined in metadata. + Location Reference: A machine-oriented identifier reference to a 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). @@ -1511,10 +1511,10 @@ Organizational Affiliation - Identifies that the party object is a member of the organization associated with the provided UUID. + A machine-oriented identifier reference to another 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). - Organizational Affiliation: Identifies that the party object is a member of the organization associated with the provided UUID. + Organizational Affiliation: A machine-oriented identifier reference to another 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). @@ -1539,10 +1539,10 @@ Party Universally Unique Identifier - A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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 Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. + Party Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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. @@ -1560,10 +1560,10 @@ Party Reference - References a party defined in metadata. + A machine-oriented identifier reference to another 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 Reference: References a party defined in metadata. + Party Reference: A machine-oriented identifier reference to another 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). @@ -1647,11 +1647,9 @@ - Role Identifier - A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. - - Role Identifier: A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. @@ -1659,10 +1657,10 @@ Role Identifier Reference - A reference to the roles served by the user. + A human-oriented identifier reference to roles served by the user. - Role Identifier Reference: A reference to the roles served by the user. + Role Identifier Reference: A human-oriented identifier reference to roles served by the user. @@ -1858,10 +1856,10 @@ Resource Universally Unique Identifier - A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Resource Universally Unique Identifier: A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Resource Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -1908,10 +1906,10 @@ Property Universally Unique Identifier - A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Property Universally Unique Identifier: A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + Property Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -2050,10 +2048,10 @@ Responsible Role - The role that the party is responsible for. + A human-oriented identifier reference to roles served by the user. - Responsible Role: The role that the party is responsible for. + Responsible Role: A human-oriented identifier reference to roles served by the user. @@ -2101,10 +2099,10 @@ Responsible Role ID - The role that is responsible for the business function. + A human-oriented identifier reference to roles responsible for the business function. - Responsible Role ID: The role that is responsible for the business function. + Responsible Role ID: A human-oriented identifier reference to roles responsible for the business function. @@ -2319,10 +2317,10 @@ Document Identifier - A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. - Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. @@ -2384,10 +2382,10 @@ Part Identifier - A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Part Identifier: A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. + Part Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -2507,10 +2505,10 @@ Parameter Identifier - A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Parameter Identifier: A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. + Parameter Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. diff --git a/xml/schema/oscal_poam_schema.xsd b/xml/schema/oscal_poam_schema.xsd index 018e4330a1..a9dc350968 100644 --- a/xml/schema/oscal_poam_schema.xsd +++ b/xml/schema/oscal_poam_schema.xsd @@ -67,10 +67,10 @@ POA&M Universally Unique Identifier - Uniquely identifies this POA&M. This UUID must be changed each time the content of the POA&M changes. + A machine-oriented, globally unique identifier with instancescope that can be used to reference this POA&M instance in this 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. - POA&M Universally Unique Identifier: Uniquely identifies this POA&M. This UUID must be changed each time the content of the POA&M changes. + POA&M Universally Unique Identifier: A machine-oriented, globally unique identifier with instancescope that can be used to reference this POA&M instance in this 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. @@ -189,10 +189,10 @@ Observation Universally Unique Identifier Reference - References an observation defined in the list of observations. + A machine-oriented identifier reference to an observation defined in the list of observations. - Observation Universally Unique Identifier Reference: References an observation defined in the list of observations. + Observation Universally Unique Identifier Reference: A machine-oriented identifier reference to an observation defined in the list of observations. @@ -211,10 +211,10 @@ Risk Universally Unique Identifier Reference - References an risk defined in the list of risks. + A machine-oriented identifier reference to a risk defined in the list of risks. - Risk Universally Unique Identifier Reference: References an risk defined in the list of risks. + Risk Universally Unique Identifier Reference: A machine-oriented identifier reference to a risk defined in the list of risks. @@ -239,10 +239,10 @@ POA&M Item Universally Unique Identifier - Uniquely identifies the POA&M entry. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given POA&M item across revisions of the document. + A machine-oriented, globally unique identifier with instance scope that can be used to reference this POA&M item entry in this 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. - POA&M Item Universally Unique Identifier: Uniquely identifies the POA&M entry. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given POA&M item across revisions of the document. + POA&M Item Universally Unique Identifier: A machine-oriented, globally unique identifier with instance scope that can be used to reference this POA&M item entry in this 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. @@ -486,10 +486,10 @@ Location Universally Unique Identifier - A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. - Location Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + Location Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. @@ -497,10 +497,10 @@ Location Reference - References a location defined in metadata. + A machine-oriented identifier reference to a 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 Reference: References a location defined in metadata. + Location Reference: A machine-oriented identifier reference to a 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). @@ -597,10 +597,10 @@ Organizational Affiliation - Identifies that the party object is a member of the organization associated with the provided UUID. + A machine-oriented identifier reference to another 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). - Organizational Affiliation: Identifies that the party object is a member of the organization associated with the provided UUID. + Organizational Affiliation: A machine-oriented identifier reference to another 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). @@ -625,10 +625,10 @@ Party Universally Unique Identifier - A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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 Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. + Party Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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. @@ -646,10 +646,10 @@ Party Reference - References a party defined in metadata. + A machine-oriented identifier reference to another 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 Reference: References a party defined in metadata. + Party Reference: A machine-oriented identifier reference to another 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). @@ -733,11 +733,9 @@ - Role Identifier - A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. - - Role Identifier: A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. @@ -745,10 +743,10 @@ Role Identifier Reference - A reference to the roles served by the user. + A human-oriented identifier reference to roles served by the user. - Role Identifier Reference: A reference to the roles served by the user. + Role Identifier Reference: A human-oriented identifier reference to roles served by the user. @@ -942,10 +940,10 @@ Resource Universally Unique Identifier - A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Resource Universally Unique Identifier: A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Resource Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -992,10 +990,10 @@ Property Universally Unique Identifier - A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Property Universally Unique Identifier: A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + Property Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -1128,10 +1126,10 @@ Responsible Role - The role that the party is responsible for. + A human-oriented identifier reference to roles served by the user. - Responsible Role: The role that the party is responsible for. + Responsible Role: A human-oriented identifier reference to roles served by the user. @@ -1177,10 +1175,10 @@ Responsible Role ID - The role that is responsible for the business function. + A human-oriented identifier reference to roles responsible for the business function. - Responsible Role ID: The role that is responsible for the business function. + Responsible Role ID: A human-oriented identifier reference to roles responsible for the business function. @@ -1393,10 +1391,10 @@ Document Identifier - A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. - Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. @@ -1543,10 +1541,10 @@ Component Identifier - The unique identifier for the component. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. - Component Identifier: The unique identifier for the component. + Component Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -1594,10 +1592,10 @@ Service Protocol Information Universally Unique Identifier - A globally unique identifier that can be used to reference this service protocol entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported 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. - Service Protocol Information Universally Unique Identifier: A globally unique identifier that can be used to reference this service protocol entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Service Protocol Information Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -1777,10 +1775,10 @@ User Universally Unique Identifier - The unique identifier for the user class. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported 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. - User Universally Unique Identifier: The unique identifier for the user class. + User Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -1921,10 +1919,10 @@ Component Universally Unique Identifier Reference - A reference to a component that is implemented as part of an inventory item. + A machine-oriented identifier reference to a component that is implemented as part of an inventory item. - Component Universally Unique Identifier Reference: A reference to a component that is implemented as part of an inventory item. + Component Universally Unique Identifier Reference: A machine-oriented identifier reference to a component that is implemented as part of an inventory item. @@ -1949,10 +1947,10 @@ Inventory Item Universally Unique Identifier - A globally unique identifier that can be used to reference this inventory item entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported 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. - Inventory Item Universally Unique Identifier: A globally unique identifier that can be used to reference this inventory item entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Inventory Item Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -1999,10 +1997,10 @@ Parameter ID - A reference to a parameter within a control, who's catalog has been imported into the current implementation context. + A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context. - Parameter ID: A reference to a parameter within a control, who's catalog has been imported into the current implementation context. + Parameter ID: A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context. @@ -2010,10 +2008,10 @@ System Identification - A unique identifier for the system described by this system security plan. + A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. - System Identification: A unique identifier for the system described by this system security plan. + System Identification: A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. @@ -2021,10 +2019,10 @@ Identification System Type - Identifies the identification system from which the provided identifier was assigned. + Identifies the identification system from which the provided identifier was assigned. - Identification System Type: Identifies the identification system from which the provided identifier was assigned. + Identification System Type: Identifies the identification system from which the provided identifier was assigned. @@ -2075,10 +2073,10 @@ Part Identifier - A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Part Identifier: A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. + Part Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -2198,10 +2196,10 @@ Parameter Identifier - A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Parameter Identifier: A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. + Parameter Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -2451,10 +2449,10 @@ Control Identifier Reference - A reference to a control with a corresponding id value. + A human-oriented identifier reference to a control with a corresponding 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). - Control Identifier Reference: A reference to a control with a corresponding id value. + Control Identifier Reference: A human-oriented identifier reference to a control with a corresponding 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). @@ -2515,10 +2513,10 @@ Assessment Method Universally Unique Identifier - Uniquely identifies this defined assessment method. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given assessment method across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment method elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment method can be used to reference the data item locally or globally (e.g., in an imported 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. - Assessment Method Universally Unique Identifier: Uniquely identifies this defined assessment method. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given assessment method across revisions of the document. + Assessment Method Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment method elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment method can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -2647,10 +2645,10 @@ Step Universally Unique Identifier - Uniquely identifies a step. This UUID may be referenced elsewhere in an OSCAL document when referring to this step. A UUID should be consistently used for a given test step across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this step elsewhere in this or other OSCAL instances. The locally defined UUID of the step (in a series of steps) can be used to reference the data item locally or globally (e.g., in an imported 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. - Step Universally Unique Identifier: Uniquely identifies a step. This UUID may be referenced elsewhere in an OSCAL document when referring to this step. A UUID should be consistently used for a given test step across revisions of the document. + Step Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this step elsewhere in this or other OSCAL instances. The locally defined UUID of the step (in a series of steps) can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -2683,10 +2681,10 @@ Assessment Activity Universally Unique Identifier - Uniquely identifies this assessment activity. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given included activity across revisions of the document. + A machine-oriented, globally unique> identifier with cross-instance scope that can be used to reference this assessment activity elsewhere in this or other OSCAL instances. The locally defined UUID of the activity can be used to reference the data item locally or globally (e.g., in an imported 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. - Assessment Activity Universally Unique Identifier: Uniquely identifies this assessment activity. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given included activity across revisions of the document. + Assessment Activity Universally Unique Identifier: A machine-oriented, globally unique> identifier with cross-instance scope that can be used to reference this assessment activity elsewhere in this or other OSCAL instances. The locally defined UUID of the activity can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -2873,10 +2871,10 @@ Task Universally Unique Identifier Reference - References a unique task by UUID. + A machine-oriented identifier reference to a unique task. - Task Universally Unique Identifier Reference: References a unique task by UUID. + Task Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique task. @@ -2932,10 +2930,10 @@ Activity Universally Unique Identifier Reference - References an activity defined in the list of activities. + A machine-oriented identifier reference to an activity defined in the list of activities. - Activity Universally Unique Identifier Reference: References an activity defined in the list of activities. + Activity Universally Unique Identifier Reference: A machine-oriented identifier reference to an activity defined in the list of activities. @@ -2968,10 +2966,10 @@ Task Universally Unique Identifier - Uniquely identifies this assessment task. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this task elsewhere in this or other OSCAL instances. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. - Task Universally Unique Identifier: Uniquely identifies this assessment task. + Task Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this task elsewhere in this or other OSCAL instances. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -3213,10 +3211,10 @@ Control Identifier Reference - A reference to a control with a corresponding id value. + A human-oriented identifier reference to a control with a corresponding 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). - Control Identifier Reference: A reference to a control with a corresponding id value. + Control Identifier Reference: A human-oriented identifier reference to a control with a corresponding 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). @@ -3279,10 +3277,10 @@ Task Universally Unique Identifier - Uniquely identifies an assessment activity to be performed as part of the event. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference (in this or other OSCAL instances) an assessment activity to be performed as part of the event. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. - Task Universally Unique Identifier: Uniquely identifies an assessment activity to be performed as part of the event. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. + Task Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference (in this or other OSCAL instances) an assessment activity to be performed as part of the event. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -3315,10 +3313,10 @@ Assessment Subject Placeholder Universally Unique Identifier - Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task. + A machine-oriented, globally unique identifier for a set of assessment subjects that will be identified by a task or an activity that is part of a task. The locally defined UUID of the assessment subject placeholder can be used to reference the data item locally or globally (e.g., in an imported 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. - Assessment Subject Placeholder Universally Unique Identifier: Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task. + Assessment Subject Placeholder Universally Unique Identifier: A machine-oriented, globally unique identifier for a set of assessment subjects that will be identified by a task or an activity that is part of a task. The locally defined UUID of the assessment subject placeholder can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -3442,10 +3440,10 @@ Subject Universally Unique Identifier Reference - A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. + A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. - Subject Universally Unique Identifier Reference: A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. + Subject Universally Unique Identifier Reference: A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. @@ -3463,10 +3461,10 @@ Identifies the Subject - A pointer to a resource based on its universally unique identifier (UUID). Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. + A human-oriented identifier reference to a resource. Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. - Identifies the Subject: A pointer to a resource based on its universally unique identifier (UUID). Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. + Identifies the Subject: A human-oriented identifier reference to a resource. Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. @@ -3512,10 +3510,10 @@ Subject Universally Unique Identifier Reference - A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. + A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. - Subject Universally Unique Identifier Reference: A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. + Subject Universally Unique Identifier Reference: A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. @@ -3620,10 +3618,10 @@ Component Universally Unique Identifier Reference - A reference to a component that is implemented as part of an inventory item. + A machine-oriented identifier reference to a component that is implemented as part of an inventory item. - Component Universally Unique Identifier Reference: A reference to a component that is implemented as part of an inventory item. + Component Universally Unique Identifier Reference: A machine-oriented identifier reference to a component that is implemented as part of an inventory item. @@ -3648,10 +3646,10 @@ Assessment Platform Universally Unique Identifier - Uniquely identifies this assessment Platform. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment platform elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment platform can be used to reference the data item locally or globally (e.g., in an imported 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. - Assessment Platform Universally Unique Identifier: Uniquely identifies this assessment Platform. + Assessment Platform Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment platform elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment platform can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -3789,10 +3787,10 @@ Finding Target Identifier Reference - Identifies the specific target qualified by the type. + A machine-oriented identifier reference for a specific target qualified by the type. - Finding Target Identifier Reference: Identifies the specific target qualified by the type. + Finding Target Identifier Reference: A machine-oriented identifier reference for a specific target qualified by the type. @@ -3986,10 +3984,10 @@ Observation Universally Unique Identifier - Uniquely identifies this observation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given observation across revisions. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. The locally defined UUID of the observation can be used to reference the data item locally or globally (e.g., in an imorted 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. - Observation Universally Unique Identifier: Uniquely identifies this observation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given observation across revisions. + Observation Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. The locally defined UUID of the observation can be used to reference the data item locally or globally (e.g., in an imorted 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. @@ -4046,10 +4044,10 @@ Actor Universally Unique Identifier Reference - A pointer to the tool or person based on the associated type. + A machine-oriented identifier reference to the tool or person based on the associated type. - Actor Universally Unique Identifier Reference: A pointer to the tool or person based on the associated type. + Actor Universally Unique Identifier Reference: A machine-oriented identifier reference to the tool or person based on the associated type. @@ -4111,10 +4109,10 @@ Assessment Subject Placeholder Universally Unique Identifier Reference - References a unique assessment subject placeholder defined by this task. + A machine-oriented identifier reference to a unique assessment subject placeholder defined by this task. - Assessment Subject Placeholder Universally Unique Identifier Reference: References a unique assessment subject placeholder defined by this task. + Assessment Subject Placeholder Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique assessment subject placeholder defined by this task. @@ -4139,10 +4137,10 @@ Task Universally Unique Identifier Reference - References a unique task by UUID. + A machine-oriented identifier reference to a unique task. - Task Universally Unique Identifier Reference: References a unique task by UUID. + Task Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique task. @@ -4311,20 +4309,20 @@ Mitigating Factor Universally Unique Identifier - Uniquely identifies this mitigating factor. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given mitigating factor across revisions. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mitigating factor elsewhere in this or other OSCAL instances. The locally defined UUID of the mitigating factor can be used to reference the data item locally or globally (e.g., in an imported 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. - Mitigating Factor Universally Unique Identifier: Uniquely identifies this mitigating factor. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given mitigating factor across revisions. + Mitigating Factor Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mitigating factor elsewhere in this or other OSCAL instances. The locally defined UUID of the mitigating factor can be used to reference the data item locally or globally (e.g., in an imported 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. Implementation UUID - Points to an implementation statement in the SSP. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this implementation statement elsewhere in this or other OSCAL instancess. The locally defined UUID of the implementation statement can be used to reference the data item locally or globally (e.g., in an imported 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. - Implementation UUID: Points to an implementation statement in the SSP. + Implementation UUID: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this implementation statement elsewhere in this or other OSCAL instancess. The locally defined UUID of the implementation statement can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -4483,10 +4481,10 @@ Response Universally Unique Identifier Reference - References a unique risk response by UUID. + A machine-oriented identifier reference to a unique risk response. - Response Universally Unique Identifier Reference: References a unique risk response by UUID. + Response Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique risk response. @@ -4511,10 +4509,10 @@ Risk Log Entry Universally Unique Identifier - Uniquely identifies a risk log entry. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk log entry elsewhere in this or other OSCAL instances. The locally defined UUID of the risk log entry can be used to reference the data item locally or globally (e.g., in an imported 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. - Risk Log Entry Universally Unique Identifier: Uniquely identifies a risk log entry. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. + Risk Log Entry Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk log entry elsewhere in this or other OSCAL instances. The locally defined UUID of the risk log entry can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -4536,10 +4534,10 @@ Observation Universally Unique Identifier Reference - References an observation defined in the list of observations. + A machine-oriented identifier reference to an observation defined in the list of observations. - Observation Universally Unique Identifier Reference: References an observation defined in the list of observations. + Observation Universally Unique Identifier Reference: A machine-oriented identifier reference to an observation defined in the list of observations. @@ -4549,10 +4547,10 @@ Risk Universally Unique Identifier - Uniquely identifies this risk. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given risk across revisions. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk elsewhere in this or other OSCAL instances. The locally defined UUID of the risk can be used to reference the data item locally or globally (e.g., in an imported 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. - Risk Universally Unique Identifier: Uniquely identifies this risk. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given risk across revisions. + Risk Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk elsewhere in this or other OSCAL instances. The locally defined UUID of the risk can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -4569,10 +4567,10 @@ Party UUID Reference - A pointer to the party who is making the log entry. + A machine-oriented identifier reference to the party who is making the log entry. - Party UUID Reference: A pointer to the party who is making the log entry. + Party UUID Reference: A machine-oriented identifier reference to the party who is making the log entry. @@ -4813,10 +4811,10 @@ Required Universally Unique Identifier - Uniquely identifies this required asset. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given required asset across revisions. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this required asset elsewhere in this or other OSCAL instances. The locally defined UUID of the asset can be used to reference the data item locally or globally (e.g., in an imported 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. - Required Universally Unique Identifier: Uniquely identifies this required asset. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given required asset across revisions. + Required Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this required asset elsewhere in this or other OSCAL instances. The locally defined UUID of the asset can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -4845,10 +4843,10 @@ Remediation Universally Unique Identifier - Uniquely identifies this remediation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given remediation across revisions. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this remediation elsewhere in this or other OSCAL instances. The locally defined UUID of the risk response can be used to reference the data item locally or globally (e.g., in an imported 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. - Remediation Universally Unique Identifier: Uniquely identifies this remediation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given remediation across revisions. + Remediation Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this remediation elsewhere in this or other OSCAL instances. The locally defined UUID of the risk response can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -4907,10 +4905,10 @@ Part Identifier - A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this part elsewhere in this or other OSCAL instances. The locally defined UUID of the part can be used to reference the data item locally or globally (e.g., in an ported 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. - Part Identifier: A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. + Part Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this part elsewhere in this or other OSCAL instances. The locally defined UUID of the part can be used to reference the data item locally or globally (e.g., in an ported 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. diff --git a/xml/schema/oscal_profile_schema.xsd b/xml/schema/oscal_profile_schema.xsd index 92aa271a02..60a84655db 100644 --- a/xml/schema/oscal_profile_schema.xsd +++ b/xml/schema/oscal_profile_schema.xsd @@ -52,11 +52,11 @@ - Catalog Universally Unique Identifier - A globally unique identifier for this profile instance. This UUID should be changed when this document is revised. + Profile Universally Unique Identifier + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this profile elsewhere in this or other OSCAL instances. The locally defined UUID of the profile can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance).This identifier should be assigned per-subject, which means it should be consistently used to identify the same profile across revisions of the document. - Catalog Universally Unique Identifier: A globally unique identifier for this profile instance. This UUID should be changed when this document is revised. + Profile Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this profile elsewhere in this or other OSCAL instances. The locally defined UUID of the profile can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance).This identifier should be assigned per-subject, which means it should be consistently used to identify the same profile across revisions of the document. @@ -115,6 +115,10 @@ type="oscal-profile:oscal-profile-as-is-FIELD" minOccurs="0" maxOccurs="1"/> + + + + + Flat + A Flat element indicates that the controls should be structured in a completely flat list. It does not contain any elements or attributes. + + + Flat: A Flat element indicates that the controls should be structured in a completely flat list. It does not contain any elements or attributes. + + @@ -229,10 +243,10 @@ Group Identifier - A unique identifier for a specific group instance that can be used to reference the group within this and in other OSCAL documents. This identifier's uniqueness is document scoped and is intended to be consistent for the same group across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. - Group Identifier: A unique identifier for a specific group instance that can be used to reference the group within this and in other OSCAL documents. This identifier's uniqueness is document scoped and is intended to be consistent for the same group across minor revisions of the document. + Group Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. @@ -328,10 +342,10 @@ Parameter ID - Indicates the value of the 'id' flag on a target parameter; i.e. which parameter to set + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Parameter ID: Indicates the value of the 'id' flag on a target parameter; i.e. which parameter to set + Parameter ID: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -488,10 +502,10 @@ Control Identifier Reference - A reference to a control with a corresponding id value. + A human-oriented identifier reference to a control with a corresponding 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). - Control Identifier Reference: A reference to a control with a corresponding id value. + Control Identifier Reference: A human-oriented identifier reference to a control with a corresponding 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). @@ -859,10 +873,10 @@ Location Universally Unique Identifier - A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. - Location Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + Location Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. @@ -870,10 +884,10 @@ Location Reference - References a location defined in metadata. + A machine-oriented identifier reference to a 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 Reference: References a location defined in metadata. + Location Reference: A machine-oriented identifier reference to a 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). @@ -970,10 +984,10 @@ Organizational Affiliation - Identifies that the party object is a member of the organization associated with the provided UUID. + A machine-oriented identifier reference to another 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). - Organizational Affiliation: Identifies that the party object is a member of the organization associated with the provided UUID. + Organizational Affiliation: A machine-oriented identifier reference to another 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). @@ -998,10 +1012,10 @@ Party Universally Unique Identifier - A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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 Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. + Party Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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. @@ -1019,10 +1033,10 @@ Party Reference - References a party defined in metadata. + A machine-oriented identifier reference to another 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 Reference: References a party defined in metadata. + Party Reference: A machine-oriented identifier reference to another 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). @@ -1106,11 +1120,9 @@ - Role Identifier - A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. - - Role Identifier: A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. @@ -1118,10 +1130,10 @@ Role Identifier Reference - A reference to the roles served by the user. + A human-oriented identifier reference to roles served by the user. - Role Identifier Reference: A reference to the roles served by the user. + Role Identifier Reference: A human-oriented identifier reference to roles served by the user. @@ -1315,10 +1327,10 @@ Resource Universally Unique Identifier - A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Resource Universally Unique Identifier: A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Resource Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -1365,10 +1377,10 @@ Property Universally Unique Identifier - A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Property Universally Unique Identifier: A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + Property Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -1501,10 +1513,10 @@ Responsible Role - The role that the party is responsible for. + A human-oriented identifier reference to roles served by the user. - Responsible Role: The role that the party is responsible for. + Responsible Role: A human-oriented identifier reference to roles served by the user. @@ -1550,10 +1562,10 @@ Responsible Role ID - The role that is responsible for the business function. + A human-oriented identifier reference to roles responsible for the business function. - Responsible Role ID: The role that is responsible for the business function. + Responsible Role ID: A human-oriented identifier reference to roles responsible for the business function. @@ -1766,10 +1778,10 @@ Document Identifier - A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. - Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. @@ -1831,10 +1843,10 @@ Part Identifier - A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Part Identifier: A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. + Part Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -1954,10 +1966,10 @@ Parameter Identifier - A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Parameter Identifier: A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. + Parameter Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. diff --git a/xml/schema/oscal_ssp_schema.xsd b/xml/schema/oscal_ssp_schema.xsd index 659502cc3d..435545066a 100644 --- a/xml/schema/oscal_ssp_schema.xsd +++ b/xml/schema/oscal_ssp_schema.xsd @@ -59,10 +59,10 @@ System Security Plan Universally Unique Identifier - A globally unique identifier for this catalog instance. This UUID should be changed when this document is revised. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this system security plan (SSP) elsewhere in this or other OSCAL instances. The locally defined UUID of the SSP can be used to reference the data item locally or globally (e.g., in an imported 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. - System Security Plan Universally Unique Identifier: A globally unique identifier for this catalog instance. This UUID should be changed when this document is revised. + System Security Plan Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this system security plan (SSP) elsewhere in this or other OSCAL instances. The locally defined UUID of the SSP can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -303,10 +303,10 @@ Information Type Systematized Identifier - An identifier qualified by the given identification system used, such as NIST SP 800-60. + A human-oriented, globally unique identifier qualified by the given identification system used, such as NIST SP 800-60. This identifier has cross-instance scope and can be used to reference this system elsewhere in this or other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Information Type Systematized Identifier: An identifier qualified by the given identification system used, such as NIST SP 800-60. + Information Type Systematized Identifier: A human-oriented, globally unique identifier qualified by the given identification system used, such as NIST SP 800-60. This identifier has cross-instance scope and can be used to reference this system elsewhere in this or other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -472,10 +472,10 @@ Information Type Universally Unique Identifier - A globally unique identifier that can be used to reference this information type entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this information type elsewhere in this or other OSCAL instances. The locally defined UUID of the information type can be used to reference the data item locally or globally (e.g., in an imported 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. - Information Type Universally Unique Identifier: A globally unique identifier that can be used to reference this information type entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Information Type Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this information type elsewhere in this or other OSCAL instances. The locally defined UUID of the information type can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -740,10 +740,10 @@ Diagram ID - The identifier for this diagram. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this diagram elsewhere in this or other OSCAL instances. The locally defined UUID of the diagram can be used to reference the data item locally or globally (e.g., in an imported 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. - Diagram ID: The identifier for this diagram. + Diagram ID: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this diagram elsewhere in this or other OSCAL instances. The locally defined UUID of the diagram can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -912,10 +912,10 @@ party-uuid field - A reference to the party that manages the leveraged system. + A machine-oriented identifier reference to the party that manages the leveraged system. - party-uuid field: A reference to the party that manages the leveraged system. + party-uuid field: A machine-oriented identifier reference to the party that manages the leveraged system. @@ -944,10 +944,10 @@ Leveraged Authorization Universally Unique Identifier - A globally unique identifier that can be used to reference this leveraged authorization entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope and can be used to reference this leveraged authorization elsewhere in this or other OSCAL instances. The locally defined UUID of the leveraged authorization can be used to reference the data item locally or globally (e.g., in an imported 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. - Leveraged Authorization Universally Unique Identifier: A globally unique identifier that can be used to reference this leveraged authorization entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Leveraged Authorization Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope and can be used to reference this leveraged authorization elsewhere in this or other OSCAL instances. The locally defined UUID of the leveraged authorization can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -1070,20 +1070,20 @@ Control Requirement Universally Unique Identifier - A globally unique identifier that can be used to reference this control requirement entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control requirement elsewhere in this or other OSCAL instances. The locally defined UUID of the control requirement can be used to reference the data item locally or globally (e.g., in an imported 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. - Control Requirement Universally Unique Identifier: A globally unique identifier that can be used to reference this control requirement entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Control Requirement Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control requirement elsewhere in this or other OSCAL instances. The locally defined UUID of the control requirement can be used to reference the data item locally or globally (e.g., in an imported 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. Control Identifier Reference - A reference to a control with a corresponding id value. + A human-oriented identifier reference to a control with a corresponding 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). - Control Identifier Reference: A reference to a control with a corresponding id value. + Control Identifier Reference: A human-oriented identifier reference to a control with a corresponding 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). @@ -1133,20 +1133,20 @@ Control Statement Reference - A reference to a control statement by its identifier + A human-oriented identifier reference to a control statement. - Control Statement Reference: A reference to a control statement by its identifier + Control Statement Reference: A human-oriented identifier reference to a control statement. Control Statement Reference Universally Unique Identifier - A globally unique identifier that can be used to reference this control statement entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. The UUID of the control statement in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance). - Control Statement Reference Universally Unique Identifier: A globally unique identifier that can be used to reference this control statement entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Control Statement Reference Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. The UUID of the control statement in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance). @@ -1283,10 +1283,10 @@ Provided Universally Unique Identifier - A globally unique identifier that can be used to reference this provided entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this provided entry elsewhere in this or other OSCAL instances. The locally defined UUID of the provided entry can be used to reference the data item locally or globally (e.g., in an imported 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. - Provided Universally Unique Identifier: A globally unique identifier that can be used to reference this provided entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Provided Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this provided entry elsewhere in this or other OSCAL instances. The locally defined UUID of the provided entry can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -1349,20 +1349,20 @@ Responsibility Universally Unique Identifier - A globally unique identifier that can be used to reference this responsibility entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this responsibility elsewhere in this or other OSCAL instances. The locally defined UUID of the responsibility can be used to reference the data item locally or globally (e.g., in an imported 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. - Responsibility Universally Unique Identifier: A globally unique identifier that can be used to reference this responsibility entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Responsibility Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this responsibility elsewhere in this or other OSCAL instances. The locally defined UUID of the responsibility can be used to reference the data item locally or globally (e.g., in an imported 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. Provided UUID - Identifies a 'provided' assembly associated with this assembly. + A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system. - Provided UUID: Identifies a 'provided' assembly associated with this assembly. + Provided UUID: A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system. @@ -1428,20 +1428,20 @@ Inherited Universally Unique Identifier - A globally unique identifier that can be used to reference this inherited entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inherited entry elsewhere in this or other OSCAL instances. The locally defined UUID of the inherited control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. - Inherited Universally Unique Identifier: A globally unique identifier that can be used to reference this inherited entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Inherited Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inherited entry elsewhere in this or other OSCAL instances. The locally defined UUID of the inherited control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. Provided UUID - Identifies a 'provided' assembly associated with this assembly. + A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system. - Provided UUID: Identifies a 'provided' assembly associated with this assembly. + Provided UUID: A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system. @@ -1504,20 +1504,20 @@ Satisfied Universally Unique Identifier - A globally unique identifier that can be used to reference this satisfied entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this satisfied control implementation entry elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. - Satisfied Universally Unique Identifier: A globally unique identifier that can be used to reference this satisfied entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Satisfied Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this satisfied control implementation entry elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. - Provided UUID - Identifies a 'provided' assembly associated with this assembly. + Responsibility UUID + A machine-oriented identifier reference to a control implementation that satisfies a responsibility imposed by a leveraged system. - Provided UUID: Identifies a 'provided' assembly associated with this assembly. + Responsibility UUID: A machine-oriented identifier reference to a control implementation that satisfies a responsibility imposed by a leveraged system. @@ -1546,20 +1546,20 @@ Component Universally Unique Identifier Reference - A reference to the component that is implementing a given control or control statement. + A machine-oriented identifier reference to the component that is implemeting a given control. - Component Universally Unique Identifier Reference: A reference to the component that is implementing a given control or control statement. + Component Universally Unique Identifier Reference: A machine-oriented identifier reference to the component that is implemeting a given control. By-Component Universally Unique Identifier - A globally unique identifier that can be used to reference this by-component entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this by-component entry elsewhere in this or other OSCAL instances. The locally defined UUID of the by-component entry can be used to reference the data item locally or globally (e.g., in an imported 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. - By-Component Universally Unique Identifier: A globally unique identifier that can be used to reference this by-component entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + By-Component Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this by-component entry elsewhere in this or other OSCAL instances. The locally defined UUID of the by-component entry can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -1803,10 +1803,10 @@ Location Universally Unique Identifier - A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. - Location Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + Location Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. @@ -1814,10 +1814,10 @@ Location Reference - References a location defined in metadata. + A machine-oriented identifier reference to a 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 Reference: References a location defined in metadata. + Location Reference: A machine-oriented identifier reference to a 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). @@ -1914,10 +1914,10 @@ Organizational Affiliation - Identifies that the party object is a member of the organization associated with the provided UUID. + A machine-oriented identifier reference to another 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). - Organizational Affiliation: Identifies that the party object is a member of the organization associated with the provided UUID. + Organizational Affiliation: A machine-oriented identifier reference to another 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). @@ -1942,10 +1942,10 @@ Party Universally Unique Identifier - A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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 Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. + Party Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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. @@ -1963,10 +1963,10 @@ Party Reference - References a party defined in metadata. + A machine-oriented identifier reference to another 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 Reference: References a party defined in metadata. + Party Reference: A machine-oriented identifier reference to another 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). @@ -2050,11 +2050,9 @@ - Role Identifier - A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. - - Role Identifier: A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. @@ -2062,10 +2060,10 @@ Role Identifier Reference - A reference to the roles served by the user. + A human-oriented identifier reference to roles served by the user. - Role Identifier Reference: A reference to the roles served by the user. + Role Identifier Reference: A human-oriented identifier reference to roles served by the user. @@ -2259,10 +2257,10 @@ Resource Universally Unique Identifier - A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Resource Universally Unique Identifier: A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Resource Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -2309,10 +2307,10 @@ Property Universally Unique Identifier - A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Property Universally Unique Identifier: A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + Property Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -2445,10 +2443,10 @@ Responsible Role - The role that the party is responsible for. + A human-oriented identifier reference to roles served by the user. - Responsible Role: The role that the party is responsible for. + Responsible Role: A human-oriented identifier reference to roles served by the user. @@ -2494,10 +2492,10 @@ Responsible Role ID - The role that is responsible for the business function. + A human-oriented identifier reference to roles responsible for the business function. - Responsible Role ID: The role that is responsible for the business function. + Responsible Role ID: A human-oriented identifier reference to roles responsible for the business function. @@ -2710,10 +2708,10 @@ Document Identifier - A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. - Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. @@ -2860,10 +2858,10 @@ Component Identifier - The unique identifier for the component. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. - Component Identifier: The unique identifier for the component. + Component Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -2911,10 +2909,10 @@ Service Protocol Information Universally Unique Identifier - A globally unique identifier that can be used to reference this service protocol entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported 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. - Service Protocol Information Universally Unique Identifier: A globally unique identifier that can be used to reference this service protocol entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Service Protocol Information Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -3094,10 +3092,10 @@ User Universally Unique Identifier - The unique identifier for the user class. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported 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. - User Universally Unique Identifier: The unique identifier for the user class. + User Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -3238,10 +3236,10 @@ Component Universally Unique Identifier Reference - A reference to a component that is implemented as part of an inventory item. + A machine-oriented identifier reference to a component that is implemented as part of an inventory item. - Component Universally Unique Identifier Reference: A reference to a component that is implemented as part of an inventory item. + Component Universally Unique Identifier Reference: A machine-oriented identifier reference to a component that is implemented as part of an inventory item. @@ -3266,10 +3264,10 @@ Inventory Item Universally Unique Identifier - A globally unique identifier that can be used to reference this inventory item entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported 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. - Inventory Item Universally Unique Identifier: A globally unique identifier that can be used to reference this inventory item entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + Inventory Item Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -3316,10 +3314,10 @@ Parameter ID - A reference to a parameter within a control, who's catalog has been imported into the current implementation context. + A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context. - Parameter ID: A reference to a parameter within a control, who's catalog has been imported into the current implementation context. + Parameter ID: A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context. @@ -3327,10 +3325,10 @@ System Identification - A unique identifier for the system described by this system security plan. + A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. - System Identification: A unique identifier for the system described by this system security plan. + System Identification: A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. @@ -3338,10 +3336,10 @@ Identification System Type - Identifies the identification system from which the provided identifier was assigned. + Identifies the identification system from which the provided identifier was assigned. - Identification System Type: Identifies the identification system from which the provided identifier was assigned. + Identification System Type: Identifies the identification system from which the provided identifier was assigned. @@ -3392,10 +3390,10 @@ Part Identifier - A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Part Identifier: A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. + Part Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -3515,10 +3513,10 @@ Parameter Identifier - A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - Parameter Identifier: A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. + Parameter Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. From b1101e2195f4314d1ae55c38c49b27c4f5e525d9 Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Fri, 25 Jun 2021 17:55:25 -0400 Subject: [PATCH 02/34] updated unique identified descriptions --- json/schema/oscal_assessment-plan_schema.json | 6 +- .../oscal_assessment-results_schema.json | 6 +- json/schema/oscal_poam_schema.json | 8 +- .../oscal_complete_json-to-xml-converter.xsl | 10 - .../oscal_profile_json-to-xml-converter.xsl | 10 - xml/schema/oscal_assessment-plan_schema.xsd | 214 ++++----- .../oscal_assessment-results_schema.xsd | 238 +++++----- xml/schema/oscal_catalog_schema.xsd | 70 +-- xml/schema/oscal_complete_schema.xsd | 416 +++++++++--------- xml/schema/oscal_component_schema.xsd | 126 +++--- xml/schema/oscal_poam_schema.xsd | 226 +++++----- xml/schema/oscal_profile_schema.xsd | 90 ++-- xml/schema/oscal_ssp_schema.xsd | 168 +++---- 13 files changed, 778 insertions(+), 810 deletions(-) diff --git a/json/schema/oscal_assessment-plan_schema.json b/json/schema/oscal_assessment-plan_schema.json index 3abc6ddc68..1ef46eadc4 100644 --- a/json/schema/oscal_assessment-plan_schema.json +++ b/json/schema/oscal_assessment-plan_schema.json @@ -931,7 +931,7 @@ "properties" : { "uuid" : { "title" : "Task Universally Unique Identifier", - "description" : "Uniquely identifies this assessment task. This identifier's uniqueness is document scoped and is intended to be consistent for the same task across minor revisions of the document.", + "description" : "Uniquely identifies this assessment task.", "type" : "string", "pattern" : "^[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-4[0-9A-Fa-f]{3}-[89ABab][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12}$" }, "type" : @@ -1253,7 +1253,7 @@ "properties" : { "uuid" : { "title" : "Assessment Subject Placeholder Universally Unique Identifier", - "description" : "Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task. This identifier's uniqueness is document scoped and is intended to be consistent for the same assessment subject across minor revisions of the document.", + "description" : "Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task.", "type" : "string", "pattern" : "^[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-4[0-9A-Fa-f]{3}-[89ABab][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12}$" }, "description" : @@ -1426,7 +1426,7 @@ "properties" : { "uuid" : { "title" : "Assessment Platform Universally Unique Identifier", - "description" : "Uniquely identifies this assessment Platform. This UUID may be referenced elsewhere in an OSCAL document when refering to this information. Once assigned, a UUID should be consistantly used for a given observation across revisions.", + "description" : "Uniquely identifies this assessment Platform.", "type" : "string", "pattern" : "^[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-4[0-9A-Fa-f]{3}-[89ABab][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12}$" }, "title" : diff --git a/json/schema/oscal_assessment-results_schema.json b/json/schema/oscal_assessment-results_schema.json index 441b02fcce..2f1ca48100 100644 --- a/json/schema/oscal_assessment-results_schema.json +++ b/json/schema/oscal_assessment-results_schema.json @@ -1176,7 +1176,7 @@ "properties" : { "uuid" : { "title" : "Task Universally Unique Identifier", - "description" : "Uniquely identifies this assessment task. This identifier's uniqueness is document scoped and is intended to be consistent for the same task across minor revisions of the document.", + "description" : "Uniquely identifies this assessment task.", "type" : "string", "pattern" : "^[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-4[0-9A-Fa-f]{3}-[89ABab][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12}$" }, "type" : @@ -1498,7 +1498,7 @@ "properties" : { "uuid" : { "title" : "Assessment Subject Placeholder Universally Unique Identifier", - "description" : "Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task. This identifier's uniqueness is document scoped and is intended to be consistent for the same assessment subject across minor revisions of the document.", + "description" : "Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task.", "type" : "string", "pattern" : "^[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-4[0-9A-Fa-f]{3}-[89ABab][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12}$" }, "description" : @@ -1671,7 +1671,7 @@ "properties" : { "uuid" : { "title" : "Assessment Platform Universally Unique Identifier", - "description" : "Uniquely identifies this assessment Platform. This UUID may be referenced elsewhere in an OSCAL document when refering to this information. Once assigned, a UUID should be consistantly used for a given observation across revisions.", + "description" : "Uniquely identifies this assessment Platform.", "type" : "string", "pattern" : "^[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-4[0-9A-Fa-f]{3}-[89ABab][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12}$" }, "title" : diff --git a/json/schema/oscal_poam_schema.json b/json/schema/oscal_poam_schema.json index da2860ee60..c49faaa6ec 100644 --- a/json/schema/oscal_poam_schema.json +++ b/json/schema/oscal_poam_schema.json @@ -1080,7 +1080,7 @@ "properties" : { "component-uuid" : { "title" : "Component Universally Unique Identifier Reference", - "description" : "A reference to a component that is implemented as part of an inventory item. This identifier's uniqueness is document scoped and is intended to be consistent for the same component across minor revisions of the document.", + "description" : "A reference to a component that is implemented as part of an inventory item.", "type" : "string", "pattern" : "^[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-4[0-9A-Fa-f]{3}-[89ABab][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12}$" }, "props" : @@ -1142,7 +1142,7 @@ "properties" : { "identifier-type" : { "title" : "Identification System Type", - "description" : "Identifies the identification system from which the provided identifier was assigned. This is a globally unique identifier and should be consistently used for a given system across revisions of the document.", + "description" : "Identifies the identification system from which the provided identifier was assigned.", "type" : "string", "format" : "uri" }, "id" : @@ -1512,7 +1512,7 @@ "properties" : { "uuid" : { "title" : "Task Universally Unique Identifier", - "description" : "Uniquely identifies this assessment task. This identifier's uniqueness is document scoped and is intended to be consistent for the same task across minor revisions of the document.", + "description" : "Uniquely identifies this assessment task.", "type" : "string", "pattern" : "^[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-4[0-9A-Fa-f]{3}-[89ABab][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12}$" }, "type" : @@ -1834,7 +1834,7 @@ "properties" : { "uuid" : { "title" : "Assessment Subject Placeholder Universally Unique Identifier", - "description" : "Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task. This identifier's uniqueness is document scoped and is intended to be consistent for the same assessment subject across minor revisions of the document.", + "description" : "Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task.", "type" : "string", "pattern" : "^[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-4[0-9A-Fa-f]{3}-[89ABab][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12}$" }, "description" : diff --git a/xml/convert/oscal_complete_json-to-xml-converter.xsl b/xml/convert/oscal_complete_json-to-xml-converter.xsl index 082db9cc21..dfa76898cd 100644 --- a/xml/convert/oscal_complete_json-to-xml-converter.xsl +++ b/xml/convert/oscal_complete_json-to-xml-converter.xsl @@ -369,7 +369,6 @@ - @@ -383,15 +382,6 @@ - - - - - - flat - - - diff --git a/xml/convert/oscal_profile_json-to-xml-converter.xsl b/xml/convert/oscal_profile_json-to-xml-converter.xsl index 21a6befc28..fae2fffb5e 100644 --- a/xml/convert/oscal_profile_json-to-xml-converter.xsl +++ b/xml/convert/oscal_profile_json-to-xml-converter.xsl @@ -223,7 +223,6 @@ - @@ -237,15 +236,6 @@ - - - - - - flat - - - diff --git a/xml/schema/oscal_assessment-plan_schema.xsd b/xml/schema/oscal_assessment-plan_schema.xsd index dc747e531e..5111f5e28a 100644 --- a/xml/schema/oscal_assessment-plan_schema.xsd +++ b/xml/schema/oscal_assessment-plan_schema.xsd @@ -130,10 +130,10 @@ Assessment Plan Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment plan in this or other OSCAL instances. The locally defined UUID of the assessment plan can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this assessment plan. This UUID must be changed each time the content of the plan changes. - Assessment Plan Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment plan in this or other OSCAL instances. The locally defined UUID of the assessment plan can be used to reference the data item locally or globally (e.g., in an imported 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. + Assessment Plan Universally Unique Identifier: Uniquely identifies this assessment plan. This UUID must be changed each time the content of the plan changes. @@ -377,10 +377,10 @@ Location Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. + A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. - Location Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. + Location Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. @@ -388,10 +388,10 @@ Location Reference - A machine-oriented identifier reference to a 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). + References a location defined in metadata. - Location Reference: A machine-oriented identifier reference to a 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 Reference: References a location defined in metadata. @@ -488,10 +488,10 @@ Organizational Affiliation - A machine-oriented identifier reference to another 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). + Identifies that the party object is a member of the organization associated with the provided UUID. - Organizational Affiliation: A machine-oriented identifier reference to another 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). + Organizational Affiliation: Identifies that the party object is a member of the organization associated with the provided UUID. @@ -516,10 +516,10 @@ Party Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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. + A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. - Party Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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 Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. @@ -537,10 +537,10 @@ Party Reference - A machine-oriented identifier reference to another 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). + References a party defined in metadata. - Party Reference: A machine-oriented identifier reference to another 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 Reference: References a party defined in metadata. @@ -624,9 +624,11 @@ - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. + Role Identifier + A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. + + Role Identifier: A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. @@ -634,10 +636,10 @@ Role Identifier Reference - A human-oriented identifier reference to roles served by the user. + A reference to the roles served by the user. - Role Identifier Reference: A human-oriented identifier reference to roles served by the user. + Role Identifier Reference: A reference to the roles served by the user. @@ -831,10 +833,10 @@ Resource Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Resource Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Resource Universally Unique Identifier: A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -881,10 +883,10 @@ Property Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. - Property Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Property Universally Unique Identifier: A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. @@ -1017,10 +1019,10 @@ Responsible Role - A human-oriented identifier reference to roles served by the user. + The role that the party is responsible for. - Responsible Role: A human-oriented identifier reference to roles served by the user. + Responsible Role: The role that the party is responsible for. @@ -1066,10 +1068,10 @@ Responsible Role ID - A human-oriented identifier reference to roles responsible for the business function. + The role that is responsible for the business function. - Responsible Role ID: A human-oriented identifier reference to roles responsible for the business function. + Responsible Role ID: The role that is responsible for the business function. @@ -1282,10 +1284,10 @@ Document Identifier - A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. - Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. @@ -1396,10 +1398,10 @@ Control Identifier Reference - A human-oriented identifier reference to a control with a corresponding 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). + A reference to a control with a corresponding id value. - Control Identifier Reference: A human-oriented identifier reference to a control with a corresponding 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). + Control Identifier Reference: A reference to a control with a corresponding id value. @@ -1460,10 +1462,10 @@ Assessment Method Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment method elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment method can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this defined assessment method. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given assessment method across revisions of the document. - Assessment Method Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment method elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment method can be used to reference the data item locally or globally (e.g., in an imported 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. + Assessment Method Universally Unique Identifier: Uniquely identifies this defined assessment method. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given assessment method across revisions of the document. @@ -1592,10 +1594,10 @@ Step Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this step elsewhere in this or other OSCAL instances. The locally defined UUID of the step (in a series of steps) can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies a step. This UUID may be referenced elsewhere in an OSCAL document when referring to this step. A UUID should be consistently used for a given test step across revisions of the document. - Step Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this step elsewhere in this or other OSCAL instances. The locally defined UUID of the step (in a series of steps) can be used to reference the data item locally or globally (e.g., in an imported 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. + Step Universally Unique Identifier: Uniquely identifies a step. This UUID may be referenced elsewhere in an OSCAL document when referring to this step. A UUID should be consistently used for a given test step across revisions of the document. @@ -1628,10 +1630,10 @@ Assessment Activity Universally Unique Identifier - A machine-oriented, globally unique> identifier with cross-instance scope that can be used to reference this assessment activity elsewhere in this or other OSCAL instances. The locally defined UUID of the activity can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this assessment activity. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given included activity across revisions of the document. - Assessment Activity Universally Unique Identifier: A machine-oriented, globally unique> identifier with cross-instance scope that can be used to reference this assessment activity elsewhere in this or other OSCAL instances. The locally defined UUID of the activity can be used to reference the data item locally or globally (e.g., in an imported 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. + Assessment Activity Universally Unique Identifier: Uniquely identifies this assessment activity. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given included activity across revisions of the document. @@ -1816,10 +1818,10 @@ Task Universally Unique Identifier Reference - A machine-oriented identifier reference to a unique task. + References a unique task by UUID. - Task Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique task. + Task Universally Unique Identifier Reference: References a unique task by UUID. @@ -1875,10 +1877,10 @@ Activity Universally Unique Identifier Reference - A machine-oriented identifier reference to an activity defined in the list of activities. + References an activity defined in the list of activities. - Activity Universally Unique Identifier Reference: A machine-oriented identifier reference to an activity defined in the list of activities. + Activity Universally Unique Identifier Reference: References an activity defined in the list of activities. @@ -1911,10 +1913,10 @@ Task Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this task elsewhere in this or other OSCAL instances. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this assessment task. - Task Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this task elsewhere in this or other OSCAL instances. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. + Task Universally Unique Identifier: Uniquely identifies this assessment task. @@ -2156,10 +2158,10 @@ Control Identifier Reference - A human-oriented identifier reference to a control with a corresponding 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). + A reference to a control with a corresponding id value. - Control Identifier Reference: A human-oriented identifier reference to a control with a corresponding 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). + Control Identifier Reference: A reference to a control with a corresponding id value. @@ -2222,10 +2224,10 @@ Task Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference (in this or other OSCAL instances) an assessment activity to be performed as part of the event. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies an assessment activity to be performed as part of the event. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. - Task Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference (in this or other OSCAL instances) an assessment activity to be performed as part of the event. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. + Task Universally Unique Identifier: Uniquely identifies an assessment activity to be performed as part of the event. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. @@ -2258,10 +2260,10 @@ Assessment Subject Placeholder Universally Unique Identifier - A machine-oriented, globally unique identifier for a set of assessment subjects that will be identified by a task or an activity that is part of a task. The locally defined UUID of the assessment subject placeholder can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task. - Assessment Subject Placeholder Universally Unique Identifier: A machine-oriented, globally unique identifier for a set of assessment subjects that will be identified by a task or an activity that is part of a task. The locally defined UUID of the assessment subject placeholder can be used to reference the data item locally or globally (e.g., in an imported 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. + Assessment Subject Placeholder Universally Unique Identifier: Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task. @@ -2385,10 +2387,10 @@ Subject Universally Unique Identifier Reference - A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. + A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. - Subject Universally Unique Identifier Reference: A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. + Subject Universally Unique Identifier Reference: A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. @@ -2406,10 +2408,10 @@ Identifies the Subject - A human-oriented identifier reference to a resource. Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. + A pointer to a resource based on its universally unique identifier (UUID). Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. - Identifies the Subject: A human-oriented identifier reference to a resource. Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. + Identifies the Subject: A pointer to a resource based on its universally unique identifier (UUID). Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. @@ -2455,10 +2457,10 @@ Subject Universally Unique Identifier Reference - A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. + A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. - Subject Universally Unique Identifier Reference: A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. + Subject Universally Unique Identifier Reference: A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. @@ -2563,10 +2565,10 @@ Component Universally Unique Identifier Reference - A machine-oriented identifier reference to a component that is implemented as part of an inventory item. + A reference to a component that is implemented as part of an inventory item. - Component Universally Unique Identifier Reference: A machine-oriented identifier reference to a component that is implemented as part of an inventory item. + Component Universally Unique Identifier Reference: A reference to a component that is implemented as part of an inventory item. @@ -2591,10 +2593,10 @@ Assessment Platform Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment platform elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment platform can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this assessment Platform. - Assessment Platform Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment platform elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment platform can be used to reference the data item locally or globally (e.g., in an imported 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. + Assessment Platform Universally Unique Identifier: Uniquely identifies this assessment Platform. @@ -2732,10 +2734,10 @@ Finding Target Identifier Reference - A machine-oriented identifier reference for a specific target qualified by the type. + Identifies the specific target qualified by the type. - Finding Target Identifier Reference: A machine-oriented identifier reference for a specific target qualified by the type. + Finding Target Identifier Reference: Identifies the specific target qualified by the type. @@ -2929,10 +2931,10 @@ Observation Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. The locally defined UUID of the observation can be used to reference the data item locally or globally (e.g., in an imorted 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. + Uniquely identifies this observation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given observation across revisions. - Observation Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. The locally defined UUID of the observation can be used to reference the data item locally or globally (e.g., in an imorted 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. + Observation Universally Unique Identifier: Uniquely identifies this observation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given observation across revisions. @@ -2989,10 +2991,10 @@ Actor Universally Unique Identifier Reference - A machine-oriented identifier reference to the tool or person based on the associated type. + A pointer to the tool or person based on the associated type. - Actor Universally Unique Identifier Reference: A machine-oriented identifier reference to the tool or person based on the associated type. + Actor Universally Unique Identifier Reference: A pointer to the tool or person based on the associated type. @@ -3052,10 +3054,10 @@ Assessment Subject Placeholder Universally Unique Identifier Reference - A machine-oriented identifier reference to a unique assessment subject placeholder defined by this task. + References a unique assessment subject placeholder defined by this task. - Assessment Subject Placeholder Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique assessment subject placeholder defined by this task. + Assessment Subject Placeholder Universally Unique Identifier Reference: References a unique assessment subject placeholder defined by this task. @@ -3080,10 +3082,10 @@ Task Universally Unique Identifier Reference - A machine-oriented identifier reference to a unique task. + References a unique task by UUID. - Task Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique task. + Task Universally Unique Identifier Reference: References a unique task by UUID. @@ -3252,20 +3254,20 @@ Mitigating Factor Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mitigating factor elsewhere in this or other OSCAL instances. The locally defined UUID of the mitigating factor can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this mitigating factor. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given mitigating factor across revisions. - Mitigating Factor Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mitigating factor elsewhere in this or other OSCAL instances. The locally defined UUID of the mitigating factor can be used to reference the data item locally or globally (e.g., in an imported 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. + Mitigating Factor Universally Unique Identifier: Uniquely identifies this mitigating factor. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given mitigating factor across revisions. Implementation UUID - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this implementation statement elsewhere in this or other OSCAL instancess. The locally defined UUID of the implementation statement can be used to reference the data item locally or globally (e.g., in an imported 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. + Points to an implementation statement in the SSP. - Implementation UUID: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this implementation statement elsewhere in this or other OSCAL instancess. The locally defined UUID of the implementation statement can be used to reference the data item locally or globally (e.g., in an imported 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. + Implementation UUID: Points to an implementation statement in the SSP. @@ -3424,10 +3426,10 @@ Response Universally Unique Identifier Reference - A machine-oriented identifier reference to a unique risk response. + References a unique risk response by UUID. - Response Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique risk response. + Response Universally Unique Identifier Reference: References a unique risk response by UUID. @@ -3452,10 +3454,10 @@ Risk Log Entry Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk log entry elsewhere in this or other OSCAL instances. The locally defined UUID of the risk log entry can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies a risk log entry. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. - Risk Log Entry Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk log entry elsewhere in this or other OSCAL instances. The locally defined UUID of the risk log entry can be used to reference the data item locally or globally (e.g., in an imported 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. + Risk Log Entry Universally Unique Identifier: Uniquely identifies a risk log entry. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. @@ -3477,10 +3479,10 @@ Observation Universally Unique Identifier Reference - A machine-oriented identifier reference to an observation defined in the list of observations. + References an observation defined in the list of observations. - Observation Universally Unique Identifier Reference: A machine-oriented identifier reference to an observation defined in the list of observations. + Observation Universally Unique Identifier Reference: References an observation defined in the list of observations. @@ -3490,10 +3492,10 @@ Risk Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk elsewhere in this or other OSCAL instances. The locally defined UUID of the risk can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this risk. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given risk across revisions. - Risk Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk elsewhere in this or other OSCAL instances. The locally defined UUID of the risk can be used to reference the data item locally or globally (e.g., in an imported 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. + Risk Universally Unique Identifier: Uniquely identifies this risk. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given risk across revisions. @@ -3510,10 +3512,10 @@ Party UUID Reference - A machine-oriented identifier reference to the party who is making the log entry. + A pointer to the party who is making the log entry. - Party UUID Reference: A machine-oriented identifier reference to the party who is making the log entry. + Party UUID Reference: A pointer to the party who is making the log entry. @@ -3754,10 +3756,10 @@ Required Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this required asset elsewhere in this or other OSCAL instances. The locally defined UUID of the asset can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this required asset. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given required asset across revisions. - Required Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this required asset elsewhere in this or other OSCAL instances. The locally defined UUID of the asset can be used to reference the data item locally or globally (e.g., in an imported 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. + Required Universally Unique Identifier: Uniquely identifies this required asset. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given required asset across revisions. @@ -3786,10 +3788,10 @@ Remediation Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this remediation elsewhere in this or other OSCAL instances. The locally defined UUID of the risk response can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this remediation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given remediation across revisions. - Remediation Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this remediation elsewhere in this or other OSCAL instances. The locally defined UUID of the risk response can be used to reference the data item locally or globally (e.g., in an imported 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. + Remediation Universally Unique Identifier: Uniquely identifies this remediation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given remediation across revisions. @@ -3848,10 +3850,10 @@ Part Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this part elsewhere in this or other OSCAL instances. The locally defined UUID of the part can be used to reference the data item locally or globally (e.g., in an ported 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. + A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. - Part Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this part elsewhere in this or other OSCAL instances. The locally defined UUID of the part can be used to reference the data item locally or globally (e.g., in an ported 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. + Part Identifier: A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. @@ -3930,10 +3932,10 @@ Part Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. - Part Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Part Identifier: A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. @@ -4053,10 +4055,10 @@ Parameter Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. - Parameter Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Parameter Identifier: A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. @@ -4342,10 +4344,10 @@ Component Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. + The unique identifier for the component. - Component Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. + Component Identifier: The unique identifier for the component. @@ -4393,10 +4395,10 @@ Service Protocol Information Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier that can be used to reference this service protocol entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Service Protocol Information Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported 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. + Service Protocol Information Universally Unique Identifier: A globally unique identifier that can be used to reference this service protocol entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -4576,10 +4578,10 @@ User Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported 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. + The unique identifier for the user class. - User Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported 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. + User Universally Unique Identifier: The unique identifier for the user class. @@ -4720,10 +4722,10 @@ Component Universally Unique Identifier Reference - A machine-oriented identifier reference to a component that is implemented as part of an inventory item. + A reference to a component that is implemented as part of an inventory item. - Component Universally Unique Identifier Reference: A machine-oriented identifier reference to a component that is implemented as part of an inventory item. + Component Universally Unique Identifier Reference: A reference to a component that is implemented as part of an inventory item. @@ -4748,10 +4750,10 @@ Inventory Item Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier that can be used to reference this inventory item entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Inventory Item Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported 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. + Inventory Item Universally Unique Identifier: A globally unique identifier that can be used to reference this inventory item entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -4798,10 +4800,10 @@ Parameter ID - A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context. + A reference to a parameter within a control, who's catalog has been imported into the current implementation context. - Parameter ID: A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context. + Parameter ID: A reference to a parameter within a control, who's catalog has been imported into the current implementation context. @@ -4809,10 +4811,10 @@ System Identification - A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. + A unique identifier for the system described by this system security plan. - System Identification: A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. + System Identification: A unique identifier for the system described by this system security plan. @@ -4820,10 +4822,10 @@ Identification System Type - Identifies the identification system from which the provided identifier was assigned. + Identifies the identification system from which the provided identifier was assigned. - Identification System Type: Identifies the identification system from which the provided identifier was assigned. + Identification System Type: Identifies the identification system from which the provided identifier was assigned. diff --git a/xml/schema/oscal_assessment-results_schema.xsd b/xml/schema/oscal_assessment-results_schema.xsd index a5b8d7878f..ae7c5aaffa 100644 --- a/xml/schema/oscal_assessment-results_schema.xsd +++ b/xml/schema/oscal_assessment-results_schema.xsd @@ -88,10 +88,10 @@ Assessment Results Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment results instance in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this assessment results file. This UUID must be changed each time the content of the results changes. - Assessment Results Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment results instance in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported 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. + Assessment Results Universally Unique Identifier: Uniquely identifies this assessment results file. This UUID must be changed each time the content of the results changes. @@ -343,10 +343,10 @@ Assessment Log Entry Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference an assessment event in this or other OSCAL instances. The locally defined UUID of the assessment log entry can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies an assessment event. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. - Assessment Log Entry Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference an assessment event in this or other OSCAL instances. The locally defined UUID of the assessment log entry can be used to reference the data item locally or globally (e.g., in an imported 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. + Assessment Log Entry Universally Unique Identifier: Uniquely identifies an assessment event. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. @@ -386,10 +386,10 @@ Results Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this set of results in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this set of results. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given set of results across revisions. - Results Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this set of results in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported 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. + Results Universally Unique Identifier: Uniquely identifies this set of results. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given set of results across revisions. @@ -454,10 +454,10 @@ Implementation Statement UUID - A machine-oriented identifier reference to the implementation statement in the SSP to which this finding is related. + Identifies the implementation statement in the SSP to which this finding is related. - Implementation Statement UUID: A machine-oriented identifier reference to the implementation statement in the SSP to which this finding is related. + Implementation Statement UUID: Identifies the implementation statement in the SSP to which this finding is related. @@ -476,10 +476,10 @@ Observation Universally Unique Identifier Reference - A machine-oriented identifier reference to an observation defined in the list of observations. + References an observation defined in the list of observations. - Observation Universally Unique Identifier Reference: A machine-oriented identifier reference to an observation defined in the list of observations. + Observation Universally Unique Identifier Reference: References an observation defined in the list of observations. @@ -498,10 +498,10 @@ Risk Universally Unique Identifier Reference - A machine-oriented identifier reference to a risk defined in the list of risks. + References an risk defined in the list of risks. - Risk Universally Unique Identifier Reference: A machine-oriented identifier reference to a risk defined in the list of risks. + Risk Universally Unique Identifier Reference: References an risk defined in the list of risks. @@ -526,10 +526,10 @@ Finding Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this finding in this or other OSCAL instances. The locally defined UUID of the finding can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this finding. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given finding across revisions. - Finding Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this finding in this or other OSCAL instances. The locally defined UUID of the finding can be used to reference the data item locally or globally (e.g., in an imported 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. + Finding Universally Unique Identifier: Uniquely identifies this finding. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given finding across revisions. @@ -810,10 +810,10 @@ Location Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. + A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. - Location Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. + Location Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. @@ -821,10 +821,10 @@ Location Reference - A machine-oriented identifier reference to a 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). + References a location defined in metadata. - Location Reference: A machine-oriented identifier reference to a 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 Reference: References a location defined in metadata. @@ -921,10 +921,10 @@ Organizational Affiliation - A machine-oriented identifier reference to another 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). + Identifies that the party object is a member of the organization associated with the provided UUID. - Organizational Affiliation: A machine-oriented identifier reference to another 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). + Organizational Affiliation: Identifies that the party object is a member of the organization associated with the provided UUID. @@ -949,10 +949,10 @@ Party Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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. + A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. - Party Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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 Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. @@ -970,10 +970,10 @@ Party Reference - A machine-oriented identifier reference to another 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). + References a party defined in metadata. - Party Reference: A machine-oriented identifier reference to another 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 Reference: References a party defined in metadata. @@ -1057,9 +1057,11 @@ - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. + Role Identifier + A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. + + Role Identifier: A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. @@ -1067,10 +1069,10 @@ Role Identifier Reference - A human-oriented identifier reference to roles served by the user. + A reference to the roles served by the user. - Role Identifier Reference: A human-oriented identifier reference to roles served by the user. + Role Identifier Reference: A reference to the roles served by the user. @@ -1264,10 +1266,10 @@ Resource Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Resource Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Resource Universally Unique Identifier: A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -1314,10 +1316,10 @@ Property Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. - Property Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Property Universally Unique Identifier: A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. @@ -1450,10 +1452,10 @@ Responsible Role - A human-oriented identifier reference to roles served by the user. + The role that the party is responsible for. - Responsible Role: A human-oriented identifier reference to roles served by the user. + Responsible Role: The role that the party is responsible for. @@ -1499,10 +1501,10 @@ Responsible Role ID - A human-oriented identifier reference to roles responsible for the business function. + The role that is responsible for the business function. - Responsible Role ID: A human-oriented identifier reference to roles responsible for the business function. + Responsible Role ID: The role that is responsible for the business function. @@ -1715,10 +1717,10 @@ Document Identifier - A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. - Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. @@ -1829,10 +1831,10 @@ Control Identifier Reference - A human-oriented identifier reference to a control with a corresponding 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). + A reference to a control with a corresponding id value. - Control Identifier Reference: A human-oriented identifier reference to a control with a corresponding 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). + Control Identifier Reference: A reference to a control with a corresponding id value. @@ -1893,10 +1895,10 @@ Assessment Method Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment method elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment method can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this defined assessment method. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given assessment method across revisions of the document. - Assessment Method Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment method elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment method can be used to reference the data item locally or globally (e.g., in an imported 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. + Assessment Method Universally Unique Identifier: Uniquely identifies this defined assessment method. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given assessment method across revisions of the document. @@ -2025,10 +2027,10 @@ Step Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this step elsewhere in this or other OSCAL instances. The locally defined UUID of the step (in a series of steps) can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies a step. This UUID may be referenced elsewhere in an OSCAL document when referring to this step. A UUID should be consistently used for a given test step across revisions of the document. - Step Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this step elsewhere in this or other OSCAL instances. The locally defined UUID of the step (in a series of steps) can be used to reference the data item locally or globally (e.g., in an imported 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. + Step Universally Unique Identifier: Uniquely identifies a step. This UUID may be referenced elsewhere in an OSCAL document when referring to this step. A UUID should be consistently used for a given test step across revisions of the document. @@ -2061,10 +2063,10 @@ Assessment Activity Universally Unique Identifier - A machine-oriented, globally unique> identifier with cross-instance scope that can be used to reference this assessment activity elsewhere in this or other OSCAL instances. The locally defined UUID of the activity can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this assessment activity. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given included activity across revisions of the document. - Assessment Activity Universally Unique Identifier: A machine-oriented, globally unique> identifier with cross-instance scope that can be used to reference this assessment activity elsewhere in this or other OSCAL instances. The locally defined UUID of the activity can be used to reference the data item locally or globally (e.g., in an imported 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. + Assessment Activity Universally Unique Identifier: Uniquely identifies this assessment activity. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given included activity across revisions of the document. @@ -2249,10 +2251,10 @@ Task Universally Unique Identifier Reference - A machine-oriented identifier reference to a unique task. + References a unique task by UUID. - Task Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique task. + Task Universally Unique Identifier Reference: References a unique task by UUID. @@ -2308,10 +2310,10 @@ Activity Universally Unique Identifier Reference - A machine-oriented identifier reference to an activity defined in the list of activities. + References an activity defined in the list of activities. - Activity Universally Unique Identifier Reference: A machine-oriented identifier reference to an activity defined in the list of activities. + Activity Universally Unique Identifier Reference: References an activity defined in the list of activities. @@ -2344,10 +2346,10 @@ Task Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this task elsewhere in this or other OSCAL instances. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this assessment task. - Task Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this task elsewhere in this or other OSCAL instances. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. + Task Universally Unique Identifier: Uniquely identifies this assessment task. @@ -2589,10 +2591,10 @@ Control Identifier Reference - A human-oriented identifier reference to a control with a corresponding 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). + A reference to a control with a corresponding id value. - Control Identifier Reference: A human-oriented identifier reference to a control with a corresponding 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). + Control Identifier Reference: A reference to a control with a corresponding id value. @@ -2655,10 +2657,10 @@ Task Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference (in this or other OSCAL instances) an assessment activity to be performed as part of the event. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies an assessment activity to be performed as part of the event. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. - Task Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference (in this or other OSCAL instances) an assessment activity to be performed as part of the event. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. + Task Universally Unique Identifier: Uniquely identifies an assessment activity to be performed as part of the event. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. @@ -2691,10 +2693,10 @@ Assessment Subject Placeholder Universally Unique Identifier - A machine-oriented, globally unique identifier for a set of assessment subjects that will be identified by a task or an activity that is part of a task. The locally defined UUID of the assessment subject placeholder can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task. - Assessment Subject Placeholder Universally Unique Identifier: A machine-oriented, globally unique identifier for a set of assessment subjects that will be identified by a task or an activity that is part of a task. The locally defined UUID of the assessment subject placeholder can be used to reference the data item locally or globally (e.g., in an imported 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. + Assessment Subject Placeholder Universally Unique Identifier: Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task. @@ -2818,10 +2820,10 @@ Subject Universally Unique Identifier Reference - A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. + A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. - Subject Universally Unique Identifier Reference: A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. + Subject Universally Unique Identifier Reference: A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. @@ -2839,10 +2841,10 @@ Identifies the Subject - A human-oriented identifier reference to a resource. Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. + A pointer to a resource based on its universally unique identifier (UUID). Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. - Identifies the Subject: A human-oriented identifier reference to a resource. Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. + Identifies the Subject: A pointer to a resource based on its universally unique identifier (UUID). Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. @@ -2888,10 +2890,10 @@ Subject Universally Unique Identifier Reference - A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. + A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. - Subject Universally Unique Identifier Reference: A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. + Subject Universally Unique Identifier Reference: A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. @@ -2996,10 +2998,10 @@ Component Universally Unique Identifier Reference - A machine-oriented identifier reference to a component that is implemented as part of an inventory item. + A reference to a component that is implemented as part of an inventory item. - Component Universally Unique Identifier Reference: A machine-oriented identifier reference to a component that is implemented as part of an inventory item. + Component Universally Unique Identifier Reference: A reference to a component that is implemented as part of an inventory item. @@ -3024,10 +3026,10 @@ Assessment Platform Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment platform elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment platform can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this assessment Platform. - Assessment Platform Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment platform elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment platform can be used to reference the data item locally or globally (e.g., in an imported 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. + Assessment Platform Universally Unique Identifier: Uniquely identifies this assessment Platform. @@ -3165,10 +3167,10 @@ Finding Target Identifier Reference - A machine-oriented identifier reference for a specific target qualified by the type. + Identifies the specific target qualified by the type. - Finding Target Identifier Reference: A machine-oriented identifier reference for a specific target qualified by the type. + Finding Target Identifier Reference: Identifies the specific target qualified by the type. @@ -3362,10 +3364,10 @@ Observation Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. The locally defined UUID of the observation can be used to reference the data item locally or globally (e.g., in an imorted 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. + Uniquely identifies this observation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given observation across revisions. - Observation Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. The locally defined UUID of the observation can be used to reference the data item locally or globally (e.g., in an imorted 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. + Observation Universally Unique Identifier: Uniquely identifies this observation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given observation across revisions. @@ -3422,10 +3424,10 @@ Actor Universally Unique Identifier Reference - A machine-oriented identifier reference to the tool or person based on the associated type. + A pointer to the tool or person based on the associated type. - Actor Universally Unique Identifier Reference: A machine-oriented identifier reference to the tool or person based on the associated type. + Actor Universally Unique Identifier Reference: A pointer to the tool or person based on the associated type. @@ -3485,10 +3487,10 @@ Assessment Subject Placeholder Universally Unique Identifier Reference - A machine-oriented identifier reference to a unique assessment subject placeholder defined by this task. + References a unique assessment subject placeholder defined by this task. - Assessment Subject Placeholder Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique assessment subject placeholder defined by this task. + Assessment Subject Placeholder Universally Unique Identifier Reference: References a unique assessment subject placeholder defined by this task. @@ -3513,10 +3515,10 @@ Task Universally Unique Identifier Reference - A machine-oriented identifier reference to a unique task. + References a unique task by UUID. - Task Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique task. + Task Universally Unique Identifier Reference: References a unique task by UUID. @@ -3685,20 +3687,20 @@ Mitigating Factor Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mitigating factor elsewhere in this or other OSCAL instances. The locally defined UUID of the mitigating factor can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this mitigating factor. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given mitigating factor across revisions. - Mitigating Factor Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mitigating factor elsewhere in this or other OSCAL instances. The locally defined UUID of the mitigating factor can be used to reference the data item locally or globally (e.g., in an imported 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. + Mitigating Factor Universally Unique Identifier: Uniquely identifies this mitigating factor. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given mitigating factor across revisions. Implementation UUID - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this implementation statement elsewhere in this or other OSCAL instancess. The locally defined UUID of the implementation statement can be used to reference the data item locally or globally (e.g., in an imported 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. + Points to an implementation statement in the SSP. - Implementation UUID: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this implementation statement elsewhere in this or other OSCAL instancess. The locally defined UUID of the implementation statement can be used to reference the data item locally or globally (e.g., in an imported 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. + Implementation UUID: Points to an implementation statement in the SSP. @@ -3857,10 +3859,10 @@ Response Universally Unique Identifier Reference - A machine-oriented identifier reference to a unique risk response. + References a unique risk response by UUID. - Response Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique risk response. + Response Universally Unique Identifier Reference: References a unique risk response by UUID. @@ -3885,10 +3887,10 @@ Risk Log Entry Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk log entry elsewhere in this or other OSCAL instances. The locally defined UUID of the risk log entry can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies a risk log entry. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. - Risk Log Entry Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk log entry elsewhere in this or other OSCAL instances. The locally defined UUID of the risk log entry can be used to reference the data item locally or globally (e.g., in an imported 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. + Risk Log Entry Universally Unique Identifier: Uniquely identifies a risk log entry. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. @@ -3910,10 +3912,10 @@ Observation Universally Unique Identifier Reference - A machine-oriented identifier reference to an observation defined in the list of observations. + References an observation defined in the list of observations. - Observation Universally Unique Identifier Reference: A machine-oriented identifier reference to an observation defined in the list of observations. + Observation Universally Unique Identifier Reference: References an observation defined in the list of observations. @@ -3923,10 +3925,10 @@ Risk Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk elsewhere in this or other OSCAL instances. The locally defined UUID of the risk can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this risk. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given risk across revisions. - Risk Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk elsewhere in this or other OSCAL instances. The locally defined UUID of the risk can be used to reference the data item locally or globally (e.g., in an imported 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. + Risk Universally Unique Identifier: Uniquely identifies this risk. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given risk across revisions. @@ -3943,10 +3945,10 @@ Party UUID Reference - A machine-oriented identifier reference to the party who is making the log entry. + A pointer to the party who is making the log entry. - Party UUID Reference: A machine-oriented identifier reference to the party who is making the log entry. + Party UUID Reference: A pointer to the party who is making the log entry. @@ -4187,10 +4189,10 @@ Required Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this required asset elsewhere in this or other OSCAL instances. The locally defined UUID of the asset can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this required asset. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given required asset across revisions. - Required Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this required asset elsewhere in this or other OSCAL instances. The locally defined UUID of the asset can be used to reference the data item locally or globally (e.g., in an imported 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. + Required Universally Unique Identifier: Uniquely identifies this required asset. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given required asset across revisions. @@ -4219,10 +4221,10 @@ Remediation Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this remediation elsewhere in this or other OSCAL instances. The locally defined UUID of the risk response can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this remediation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given remediation across revisions. - Remediation Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this remediation elsewhere in this or other OSCAL instances. The locally defined UUID of the risk response can be used to reference the data item locally or globally (e.g., in an imported 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. + Remediation Universally Unique Identifier: Uniquely identifies this remediation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given remediation across revisions. @@ -4281,10 +4283,10 @@ Part Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this part elsewhere in this or other OSCAL instances. The locally defined UUID of the part can be used to reference the data item locally or globally (e.g., in an ported 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. + A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. - Part Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this part elsewhere in this or other OSCAL instances. The locally defined UUID of the part can be used to reference the data item locally or globally (e.g., in an ported 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. + Part Identifier: A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. @@ -4363,10 +4365,10 @@ Part Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. - Part Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Part Identifier: A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. @@ -4486,10 +4488,10 @@ Parameter Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. - Parameter Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Parameter Identifier: A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. @@ -4775,10 +4777,10 @@ Component Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. + The unique identifier for the component. - Component Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. + Component Identifier: The unique identifier for the component. @@ -4826,10 +4828,10 @@ Service Protocol Information Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier that can be used to reference this service protocol entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Service Protocol Information Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported 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. + Service Protocol Information Universally Unique Identifier: A globally unique identifier that can be used to reference this service protocol entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -5009,10 +5011,10 @@ User Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported 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. + The unique identifier for the user class. - User Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported 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. + User Universally Unique Identifier: The unique identifier for the user class. @@ -5153,10 +5155,10 @@ Component Universally Unique Identifier Reference - A machine-oriented identifier reference to a component that is implemented as part of an inventory item. + A reference to a component that is implemented as part of an inventory item. - Component Universally Unique Identifier Reference: A machine-oriented identifier reference to a component that is implemented as part of an inventory item. + Component Universally Unique Identifier Reference: A reference to a component that is implemented as part of an inventory item. @@ -5181,10 +5183,10 @@ Inventory Item Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier that can be used to reference this inventory item entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Inventory Item Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported 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. + Inventory Item Universally Unique Identifier: A globally unique identifier that can be used to reference this inventory item entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -5231,10 +5233,10 @@ Parameter ID - A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context. + A reference to a parameter within a control, who's catalog has been imported into the current implementation context. - Parameter ID: A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context. + Parameter ID: A reference to a parameter within a control, who's catalog has been imported into the current implementation context. @@ -5242,10 +5244,10 @@ System Identification - A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. + A unique identifier for the system described by this system security plan. - System Identification: A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. + System Identification: A unique identifier for the system described by this system security plan. @@ -5253,10 +5255,10 @@ Identification System Type - Identifies the identification system from which the provided identifier was assigned. + Identifies the identification system from which the provided identifier was assigned. - Identification System Type: Identifies the identification system from which the provided identifier was assigned. + Identification System Type: Identifies the identification system from which the provided identifier was assigned. diff --git a/xml/schema/oscal_catalog_schema.xsd b/xml/schema/oscal_catalog_schema.xsd index a1e4bc9714..59b30e494b 100644 --- a/xml/schema/oscal_catalog_schema.xsd +++ b/xml/schema/oscal_catalog_schema.xsd @@ -53,10 +53,10 @@ Catalog Universally Unique Identifier - A globally unique identifier with cross-instance scope for this catalog instance. This UUID should be changed when this document is revised. + A globally unique identifier for this catalog instance. This UUID should be changed when this document is revised. - Catalog Universally Unique Identifier: A globally unique identifier with cross-instance scope for this catalog instance. This UUID should be changed when this document is revised. + Catalog Universally Unique Identifier: A globally unique identifier for this catalog instance. This UUID should be changed when this document is revised. @@ -116,10 +116,10 @@ Group Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in in this and other OSCAL instances (e.g., profiles). This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. + A unique identifier for a specific group instance that can be used to reference the group within this and in other OSCAL documents. This identifier's uniqueness is document scoped and is intended to be consistent for the same group across minor revisions of the document. - Group Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in in this and other OSCAL instances (e.g., profiles). This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. + Group Identifier: A unique identifier for a specific group instance that can be used to reference the group within this and in other OSCAL documents. This identifier's uniqueness is document scoped and is intended to be consistent for the same group across minor revisions of the document. @@ -183,10 +183,10 @@ Control Identifier - A human-oriented, locally unique identifier with instance scope that can be used to reference this control elsewhere in this and other OSCAL instances (e.g., profiles). This id should be assigned per-subject, which means it should be consistently used to identify the same control across revisions of the document. + A unique identifier for a specific control instance that can be used to reference the control in other OSCAL documents. This identifier's uniqueness is document scoped and is intended to be consistent for the same control across minor revisions of the document. - Control Identifier: A human-oriented, locally unique identifier with instance scope that can be used to reference this control elsewhere in this and other OSCAL instances (e.g., profiles). This id should be assigned per-subject, which means it should be consistently used to identify the same control across revisions of the document. + Control Identifier: A unique identifier for a specific control instance that can be used to reference the control in other OSCAL documents. This identifier's uniqueness is document scoped and is intended to be consistent for the same control across minor revisions of the document. @@ -245,10 +245,10 @@ Part Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. - Part Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Part Identifier: A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. @@ -368,10 +368,10 @@ Parameter Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. - Parameter Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Parameter Identifier: A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. @@ -767,10 +767,10 @@ Location Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. + A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. - Location Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. + Location Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. @@ -778,10 +778,10 @@ Location Reference - A machine-oriented identifier reference to a 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). + References a location defined in metadata. - Location Reference: A machine-oriented identifier reference to a 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 Reference: References a location defined in metadata. @@ -878,10 +878,10 @@ Organizational Affiliation - A machine-oriented identifier reference to another 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). + Identifies that the party object is a member of the organization associated with the provided UUID. - Organizational Affiliation: A machine-oriented identifier reference to another 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). + Organizational Affiliation: Identifies that the party object is a member of the organization associated with the provided UUID. @@ -906,10 +906,10 @@ Party Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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. + A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. - Party Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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 Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. @@ -927,10 +927,10 @@ Party Reference - A machine-oriented identifier reference to another 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). + References a party defined in metadata. - Party Reference: A machine-oriented identifier reference to another 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 Reference: References a party defined in metadata. @@ -1014,9 +1014,11 @@ - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. + Role Identifier + A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. + + Role Identifier: A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. @@ -1024,10 +1026,10 @@ Role Identifier Reference - A human-oriented identifier reference to roles served by the user. + A reference to the roles served by the user. - Role Identifier Reference: A human-oriented identifier reference to roles served by the user. + Role Identifier Reference: A reference to the roles served by the user. @@ -1221,10 +1223,10 @@ Resource Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Resource Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Resource Universally Unique Identifier: A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -1271,10 +1273,10 @@ Property Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. - Property Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Property Universally Unique Identifier: A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. @@ -1407,10 +1409,10 @@ Responsible Role - A human-oriented identifier reference to roles served by the user. + The role that the party is responsible for. - Responsible Role: A human-oriented identifier reference to roles served by the user. + Responsible Role: The role that the party is responsible for. @@ -1456,10 +1458,10 @@ Responsible Role ID - A human-oriented identifier reference to roles responsible for the business function. + The role that is responsible for the business function. - Responsible Role ID: A human-oriented identifier reference to roles responsible for the business function. + Responsible Role ID: The role that is responsible for the business function. @@ -1672,10 +1674,10 @@ Document Identifier - A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. - Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. diff --git a/xml/schema/oscal_complete_schema.xsd b/xml/schema/oscal_complete_schema.xsd index a616dffa3c..64ce1cffb3 100644 --- a/xml/schema/oscal_complete_schema.xsd +++ b/xml/schema/oscal_complete_schema.xsd @@ -59,10 +59,10 @@ Catalog Universally Unique Identifier - A globally unique identifier with cross-instance scope for this catalog instance. This UUID should be changed when this document is revised. + A globally unique identifier for this catalog instance. This UUID should be changed when this document is revised. - Catalog Universally Unique Identifier: A globally unique identifier with cross-instance scope for this catalog instance. This UUID should be changed when this document is revised. + Catalog Universally Unique Identifier: A globally unique identifier for this catalog instance. This UUID should be changed when this document is revised. @@ -122,10 +122,10 @@ Group Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in in this and other OSCAL instances (e.g., profiles). This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. + A unique identifier for a specific group instance that can be used to reference the group within this and in other OSCAL documents. This identifier's uniqueness is document scoped and is intended to be consistent for the same group across minor revisions of the document. - Group Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in in this and other OSCAL instances (e.g., profiles). This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. + Group Identifier: A unique identifier for a specific group instance that can be used to reference the group within this and in other OSCAL documents. This identifier's uniqueness is document scoped and is intended to be consistent for the same group across minor revisions of the document. @@ -189,10 +189,10 @@ Control Identifier - A human-oriented, locally unique identifier with instance scope that can be used to reference this control elsewhere in this and other OSCAL instances (e.g., profiles). This id should be assigned per-subject, which means it should be consistently used to identify the same control across revisions of the document. + A unique identifier for a specific control instance that can be used to reference the control in other OSCAL documents. This identifier's uniqueness is document scoped and is intended to be consistent for the same control across minor revisions of the document. - Control Identifier: A human-oriented, locally unique identifier with instance scope that can be used to reference this control elsewhere in this and other OSCAL instances (e.g., profiles). This id should be assigned per-subject, which means it should be consistently used to identify the same control across revisions of the document. + Control Identifier: A unique identifier for a specific control instance that can be used to reference the control in other OSCAL documents. This identifier's uniqueness is document scoped and is intended to be consistent for the same control across minor revisions of the document. @@ -251,10 +251,10 @@ Part Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. - Part Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Part Identifier: A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. @@ -374,10 +374,10 @@ Parameter Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. - Parameter Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Parameter Identifier: A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. @@ -773,10 +773,10 @@ Location Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. + A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. - Location Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. + Location Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. @@ -784,10 +784,10 @@ Location Reference - A machine-oriented identifier reference to a 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). + References a location defined in metadata. - Location Reference: A machine-oriented identifier reference to a 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 Reference: References a location defined in metadata. @@ -884,10 +884,10 @@ Organizational Affiliation - A machine-oriented identifier reference to another 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). + Identifies that the party object is a member of the organization associated with the provided UUID. - Organizational Affiliation: A machine-oriented identifier reference to another 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). + Organizational Affiliation: Identifies that the party object is a member of the organization associated with the provided UUID. @@ -912,10 +912,10 @@ Party Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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. + A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. - Party Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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 Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. @@ -933,10 +933,10 @@ Party Reference - A machine-oriented identifier reference to another 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). + References a party defined in metadata. - Party Reference: A machine-oriented identifier reference to another 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 Reference: References a party defined in metadata. @@ -1020,9 +1020,11 @@ - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. + Role Identifier + A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. + + Role Identifier: A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. @@ -1030,10 +1032,10 @@ Role Identifier Reference - A human-oriented identifier reference to roles served by the user. + A reference to the roles served by the user. - Role Identifier Reference: A human-oriented identifier reference to roles served by the user. + Role Identifier Reference: A reference to the roles served by the user. @@ -1227,10 +1229,10 @@ Resource Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Resource Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Resource Universally Unique Identifier: A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -1277,10 +1279,10 @@ Property Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. - Property Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Property Universally Unique Identifier: A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. @@ -1413,10 +1415,10 @@ Responsible Role - A human-oriented identifier reference to roles served by the user. + The role that the party is responsible for. - Responsible Role: A human-oriented identifier reference to roles served by the user. + Responsible Role: The role that the party is responsible for. @@ -1462,10 +1464,10 @@ Responsible Role ID - A human-oriented identifier reference to roles responsible for the business function. + The role that is responsible for the business function. - Responsible Role ID: A human-oriented identifier reference to roles responsible for the business function. + Responsible Role ID: The role that is responsible for the business function. @@ -1678,10 +1680,10 @@ Document Identifier - A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. - Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. @@ -1733,11 +1735,11 @@ - Profile Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this profile elsewhere in this or other OSCAL instances. The locally defined UUID of the profile can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance).This identifier should be assigned per-subject, which means it should be consistently used to identify the same profile across revisions of the document. + Catalog Universally Unique Identifier + A globally unique identifier for this profile instance. This UUID should be changed when this document is revised. - Profile Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this profile elsewhere in this or other OSCAL instances. The locally defined UUID of the profile can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance).This identifier should be assigned per-subject, which means it should be consistently used to identify the same profile across revisions of the document. + Catalog Universally Unique Identifier: A globally unique identifier for this profile instance. This UUID should be changed when this document is revised. @@ -1796,10 +1798,6 @@ type="oscal-complete:oscal-profile-as-is-FIELD" minOccurs="0" maxOccurs="1"/> - - - - - Flat - A Flat element indicates that the controls should be structured in a completely flat list. It does not contain any elements or attributes. - - - Flat: A Flat element indicates that the controls should be structured in a completely flat list. It does not contain any elements or attributes. - - @@ -1924,10 +1912,10 @@ Group Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. + A unique identifier for a specific group instance that can be used to reference the group within this and in other OSCAL documents. This identifier's uniqueness is document scoped and is intended to be consistent for the same group across minor revisions of the document. - Group Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. + Group Identifier: A unique identifier for a specific group instance that can be used to reference the group within this and in other OSCAL documents. This identifier's uniqueness is document scoped and is intended to be consistent for the same group across minor revisions of the document. @@ -2023,10 +2011,10 @@ Parameter ID - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Indicates the value of the 'id' flag on a target parameter; i.e. which parameter to set - Parameter ID: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Parameter ID: Indicates the value of the 'id' flag on a target parameter; i.e. which parameter to set @@ -2183,10 +2171,10 @@ Control Identifier Reference - A human-oriented identifier reference to a control with a corresponding 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). + A reference to a control with a corresponding id value. - Control Identifier Reference: A human-oriented identifier reference to a control with a corresponding 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). + Control Identifier Reference: A reference to a control with a corresponding id value. @@ -2351,10 +2339,10 @@ Component Definition Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component definition elsewhere in this or other OSCAL instances. The locally defined UUID of the component definition can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier for this component definition instance. This UUID should be changed when this document is revised. - Component Definition Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component definition elsewhere in this or other OSCAL instances. The locally defined UUID of the component definition can be used to reference the data item locally or globally (e.g., in an imported 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. + Component Definition Universally Unique Identifier: A globally unique identifier for this component definition instance. This UUID should be changed when this document is revised. @@ -2473,10 +2461,10 @@ Component Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. + The unique identifier for the component. - Component Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. + Component Identifier: The unique identifier for the component. @@ -2551,10 +2539,10 @@ Capability Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this capability elsewhere in this or other OSCAL instances. The locally defined UUID of the capability can be used to reference the data item locally or globally (e.g., in an imported 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. + A unique identifier for a capability. - Capability Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this capability elsewhere in this or other OSCAL instances. The locally defined UUID of the capability can be used to reference the data item locally or globally (e.g., in an imported 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. + Capability Identifier: A unique identifier for a capability. @@ -2598,10 +2586,10 @@ Component Reference - A machine-oriented identifier reference to a component. + A reference to a component by its identifier - Component Reference: A machine-oriented identifier reference to a component. + Component Reference: A reference to a component by its identifier @@ -2651,10 +2639,10 @@ Control Implementation Set Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference a set of implemented controls elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation set can be used to reference the data item locally or globally (e.g., in an imported 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. + A unique identifier for the set of implemented controls. - Control Implementation Set Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference a set of implemented controls elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation set can be used to reference the data item locally or globally (e.g., in an imported 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. + Control Implementation Set Identifier: A unique identifier for the set of implemented controls. @@ -2733,20 +2721,20 @@ Control Implementation Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference a specific control implementation elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. + A unique identifier for a specific control implementation. - Control Implementation Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference a specific control implementation elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. + Control Implementation Identifier: A unique identifier for a specific control implementation. Control Identifier Reference - A human-oriented identifier reference to a control with a corresponding 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). + A reference to a control with a corresponding id value. - Control Identifier Reference: A human-oriented identifier reference to a control with a corresponding 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). + Control Identifier Reference: A reference to a control with a corresponding id value. @@ -2807,20 +2795,20 @@ Control Statement Reference - A human-oriented identifier reference to a control statement. + A reference to a control statement by its identifier - Control Statement Reference: A human-oriented identifier reference to a control statement. + Control Statement Reference: A reference to a control statement by its identifier Control Statement Reference Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. The UUID of the control statement in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance). + A globally unique identifier that can be used to reference this control statement entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Control Statement Reference Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. The UUID of the control statement in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance). + Control Statement Reference Universally Unique Identifier: A globally unique identifier that can be used to reference this control statement entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -2954,10 +2942,10 @@ Component Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. + The unique identifier for the component. - Component Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. + Component Identifier: The unique identifier for the component. @@ -3005,10 +2993,10 @@ Service Protocol Information Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier that can be used to reference this service protocol entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Service Protocol Information Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported 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. + Service Protocol Information Universally Unique Identifier: A globally unique identifier that can be used to reference this service protocol entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -3188,10 +3176,10 @@ User Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported 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. + The unique identifier for the user class. - User Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported 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. + User Universally Unique Identifier: The unique identifier for the user class. @@ -3332,10 +3320,10 @@ Component Universally Unique Identifier Reference - A machine-oriented identifier reference to a component that is implemented as part of an inventory item. + A reference to a component that is implemented as part of an inventory item. - Component Universally Unique Identifier Reference: A machine-oriented identifier reference to a component that is implemented as part of an inventory item. + Component Universally Unique Identifier Reference: A reference to a component that is implemented as part of an inventory item. @@ -3360,10 +3348,10 @@ Inventory Item Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier that can be used to reference this inventory item entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Inventory Item Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported 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. + Inventory Item Universally Unique Identifier: A globally unique identifier that can be used to reference this inventory item entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -3410,10 +3398,10 @@ Parameter ID - A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context. + A reference to a parameter within a control, who's catalog has been imported into the current implementation context. - Parameter ID: A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context. + Parameter ID: A reference to a parameter within a control, who's catalog has been imported into the current implementation context. @@ -3421,10 +3409,10 @@ System Identification - A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. + A unique identifier for the system described by this system security plan. - System Identification: A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. + System Identification: A unique identifier for the system described by this system security plan. @@ -3432,10 +3420,10 @@ Identification System Type - Identifies the identification system from which the provided identifier was assigned. + Identifies the identification system from which the provided identifier was assigned. - Identification System Type: Identifies the identification system from which the provided identifier was assigned. + Identification System Type: Identifies the identification system from which the provided identifier was assigned. @@ -3482,10 +3470,10 @@ System Security Plan Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this system security plan (SSP) elsewhere in this or other OSCAL instances. The locally defined UUID of the SSP can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier for this catalog instance. This UUID should be changed when this document is revised. - System Security Plan Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this system security plan (SSP) elsewhere in this or other OSCAL instances. The locally defined UUID of the SSP can be used to reference the data item locally or globally (e.g., in an imported 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. + System Security Plan Universally Unique Identifier: A globally unique identifier for this catalog instance. This UUID should be changed when this document is revised. @@ -3726,10 +3714,10 @@ Information Type Systematized Identifier - A human-oriented, globally unique identifier qualified by the given identification system used, such as NIST SP 800-60. This identifier has cross-instance scope and can be used to reference this system elsewhere in this or other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + An identifier qualified by the given identification system used, such as NIST SP 800-60. - Information Type Systematized Identifier: A human-oriented, globally unique identifier qualified by the given identification system used, such as NIST SP 800-60. This identifier has cross-instance scope and can be used to reference this system elsewhere in this or other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Information Type Systematized Identifier: An identifier qualified by the given identification system used, such as NIST SP 800-60. @@ -3895,10 +3883,10 @@ Information Type Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this information type elsewhere in this or other OSCAL instances. The locally defined UUID of the information type can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier that can be used to reference this information type entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Information Type Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this information type elsewhere in this or other OSCAL instances. The locally defined UUID of the information type can be used to reference the data item locally or globally (e.g., in an imported 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. + Information Type Universally Unique Identifier: A globally unique identifier that can be used to reference this information type entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -4163,10 +4151,10 @@ Diagram ID - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this diagram elsewhere in this or other OSCAL instances. The locally defined UUID of the diagram can be used to reference the data item locally or globally (e.g., in an imported 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. + The identifier for this diagram. - Diagram ID: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this diagram elsewhere in this or other OSCAL instances. The locally defined UUID of the diagram can be used to reference the data item locally or globally (e.g., in an imported 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. + Diagram ID: The identifier for this diagram. @@ -4335,10 +4323,10 @@ party-uuid field - A machine-oriented identifier reference to the party that manages the leveraged system. + A reference to the party that manages the leveraged system. - party-uuid field: A machine-oriented identifier reference to the party that manages the leveraged system. + party-uuid field: A reference to the party that manages the leveraged system. @@ -4367,10 +4355,10 @@ Leveraged Authorization Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope and can be used to reference this leveraged authorization elsewhere in this or other OSCAL instances. The locally defined UUID of the leveraged authorization can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier that can be used to reference this leveraged authorization entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Leveraged Authorization Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope and can be used to reference this leveraged authorization elsewhere in this or other OSCAL instances. The locally defined UUID of the leveraged authorization can be used to reference the data item locally or globally (e.g., in an imported 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. + Leveraged Authorization Universally Unique Identifier: A globally unique identifier that can be used to reference this leveraged authorization entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -4493,20 +4481,20 @@ Control Requirement Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control requirement elsewhere in this or other OSCAL instances. The locally defined UUID of the control requirement can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier that can be used to reference this control requirement entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Control Requirement Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control requirement elsewhere in this or other OSCAL instances. The locally defined UUID of the control requirement can be used to reference the data item locally or globally (e.g., in an imported 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. + Control Requirement Universally Unique Identifier: A globally unique identifier that can be used to reference this control requirement entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. Control Identifier Reference - A human-oriented identifier reference to a control with a corresponding 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). + A reference to a control with a corresponding id value. - Control Identifier Reference: A human-oriented identifier reference to a control with a corresponding 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). + Control Identifier Reference: A reference to a control with a corresponding id value. @@ -4556,20 +4544,20 @@ Control Statement Reference - A human-oriented identifier reference to a control statement. + A reference to a control statement by its identifier - Control Statement Reference: A human-oriented identifier reference to a control statement. + Control Statement Reference: A reference to a control statement by its identifier Control Statement Reference Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. The UUID of the control statement in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance). + A globally unique identifier that can be used to reference this control statement entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Control Statement Reference Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. The UUID of the control statement in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance). + Control Statement Reference Universally Unique Identifier: A globally unique identifier that can be used to reference this control statement entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -4706,10 +4694,10 @@ Provided Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this provided entry elsewhere in this or other OSCAL instances. The locally defined UUID of the provided entry can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier that can be used to reference this provided entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Provided Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this provided entry elsewhere in this or other OSCAL instances. The locally defined UUID of the provided entry can be used to reference the data item locally or globally (e.g., in an imported 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. + Provided Universally Unique Identifier: A globally unique identifier that can be used to reference this provided entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -4772,20 +4760,20 @@ Responsibility Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this responsibility elsewhere in this or other OSCAL instances. The locally defined UUID of the responsibility can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier that can be used to reference this responsibility entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Responsibility Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this responsibility elsewhere in this or other OSCAL instances. The locally defined UUID of the responsibility can be used to reference the data item locally or globally (e.g., in an imported 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. + Responsibility Universally Unique Identifier: A globally unique identifier that can be used to reference this responsibility entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. Provided UUID - A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system. + Identifies a 'provided' assembly associated with this assembly. - Provided UUID: A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system. + Provided UUID: Identifies a 'provided' assembly associated with this assembly. @@ -4851,20 +4839,20 @@ Inherited Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inherited entry elsewhere in this or other OSCAL instances. The locally defined UUID of the inherited control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier that can be used to reference this inherited entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Inherited Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inherited entry elsewhere in this or other OSCAL instances. The locally defined UUID of the inherited control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. + Inherited Universally Unique Identifier: A globally unique identifier that can be used to reference this inherited entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. Provided UUID - A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system. + Identifies a 'provided' assembly associated with this assembly. - Provided UUID: A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system. + Provided UUID: Identifies a 'provided' assembly associated with this assembly. @@ -4927,20 +4915,20 @@ Satisfied Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this satisfied control implementation entry elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier that can be used to reference this satisfied entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Satisfied Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this satisfied control implementation entry elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. + Satisfied Universally Unique Identifier: A globally unique identifier that can be used to reference this satisfied entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Responsibility UUID - A machine-oriented identifier reference to a control implementation that satisfies a responsibility imposed by a leveraged system. + Provided UUID + Identifies a 'provided' assembly associated with this assembly. - Responsibility UUID: A machine-oriented identifier reference to a control implementation that satisfies a responsibility imposed by a leveraged system. + Provided UUID: Identifies a 'provided' assembly associated with this assembly. @@ -4969,20 +4957,20 @@ Component Universally Unique Identifier Reference - A machine-oriented identifier reference to the component that is implemeting a given control. + A reference to the component that is implementing a given control or control statement. - Component Universally Unique Identifier Reference: A machine-oriented identifier reference to the component that is implemeting a given control. + Component Universally Unique Identifier Reference: A reference to the component that is implementing a given control or control statement. By-Component Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this by-component entry elsewhere in this or other OSCAL instances. The locally defined UUID of the by-component entry can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier that can be used to reference this by-component entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - By-Component Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this by-component entry elsewhere in this or other OSCAL instances. The locally defined UUID of the by-component entry can be used to reference the data item locally or globally (e.g., in an imported 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. + By-Component Universally Unique Identifier: A globally unique identifier that can be used to reference this by-component entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -5098,10 +5086,10 @@ Assessment Plan Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment plan in this or other OSCAL instances. The locally defined UUID of the assessment plan can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this assessment plan. This UUID must be changed each time the content of the plan changes. - Assessment Plan Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment plan in this or other OSCAL instances. The locally defined UUID of the assessment plan can be used to reference the data item locally or globally (e.g., in an imported 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. + Assessment Plan Universally Unique Identifier: Uniquely identifies this assessment plan. This UUID must be changed each time the content of the plan changes. @@ -5199,10 +5187,10 @@ Control Identifier Reference - A human-oriented identifier reference to a control with a corresponding 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). + A reference to a control with a corresponding id value. - Control Identifier Reference: A human-oriented identifier reference to a control with a corresponding 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). + Control Identifier Reference: A reference to a control with a corresponding id value. @@ -5263,10 +5251,10 @@ Assessment Method Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment method elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment method can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this defined assessment method. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given assessment method across revisions of the document. - Assessment Method Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment method elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment method can be used to reference the data item locally or globally (e.g., in an imported 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. + Assessment Method Universally Unique Identifier: Uniquely identifies this defined assessment method. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given assessment method across revisions of the document. @@ -5395,10 +5383,10 @@ Step Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this step elsewhere in this or other OSCAL instances. The locally defined UUID of the step (in a series of steps) can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies a step. This UUID may be referenced elsewhere in an OSCAL document when referring to this step. A UUID should be consistently used for a given test step across revisions of the document. - Step Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this step elsewhere in this or other OSCAL instances. The locally defined UUID of the step (in a series of steps) can be used to reference the data item locally or globally (e.g., in an imported 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. + Step Universally Unique Identifier: Uniquely identifies a step. This UUID may be referenced elsewhere in an OSCAL document when referring to this step. A UUID should be consistently used for a given test step across revisions of the document. @@ -5431,10 +5419,10 @@ Assessment Activity Universally Unique Identifier - A machine-oriented, globally unique> identifier with cross-instance scope that can be used to reference this assessment activity elsewhere in this or other OSCAL instances. The locally defined UUID of the activity can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this assessment activity. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given included activity across revisions of the document. - Assessment Activity Universally Unique Identifier: A machine-oriented, globally unique> identifier with cross-instance scope that can be used to reference this assessment activity elsewhere in this or other OSCAL instances. The locally defined UUID of the activity can be used to reference the data item locally or globally (e.g., in an imported 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. + Assessment Activity Universally Unique Identifier: Uniquely identifies this assessment activity. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given included activity across revisions of the document. @@ -5625,10 +5613,10 @@ Task Universally Unique Identifier Reference - A machine-oriented identifier reference to a unique task. + References a unique task by UUID. - Task Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique task. + Task Universally Unique Identifier Reference: References a unique task by UUID. @@ -5684,10 +5672,10 @@ Activity Universally Unique Identifier Reference - A machine-oriented identifier reference to an activity defined in the list of activities. + References an activity defined in the list of activities. - Activity Universally Unique Identifier Reference: A machine-oriented identifier reference to an activity defined in the list of activities. + Activity Universally Unique Identifier Reference: References an activity defined in the list of activities. @@ -5720,10 +5708,10 @@ Task Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this task elsewhere in this or other OSCAL instances. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this assessment task. - Task Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this task elsewhere in this or other OSCAL instances. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. + Task Universally Unique Identifier: Uniquely identifies this assessment task. @@ -5965,10 +5953,10 @@ Control Identifier Reference - A human-oriented identifier reference to a control with a corresponding 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). + A reference to a control with a corresponding id value. - Control Identifier Reference: A human-oriented identifier reference to a control with a corresponding 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). + Control Identifier Reference: A reference to a control with a corresponding id value. @@ -6031,10 +6019,10 @@ Task Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference (in this or other OSCAL instances) an assessment activity to be performed as part of the event. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies an assessment activity to be performed as part of the event. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. - Task Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference (in this or other OSCAL instances) an assessment activity to be performed as part of the event. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. + Task Universally Unique Identifier: Uniquely identifies an assessment activity to be performed as part of the event. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. @@ -6067,10 +6055,10 @@ Assessment Subject Placeholder Universally Unique Identifier - A machine-oriented, globally unique identifier for a set of assessment subjects that will be identified by a task or an activity that is part of a task. The locally defined UUID of the assessment subject placeholder can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task. - Assessment Subject Placeholder Universally Unique Identifier: A machine-oriented, globally unique identifier for a set of assessment subjects that will be identified by a task or an activity that is part of a task. The locally defined UUID of the assessment subject placeholder can be used to reference the data item locally or globally (e.g., in an imported 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. + Assessment Subject Placeholder Universally Unique Identifier: Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task. @@ -6194,10 +6182,10 @@ Subject Universally Unique Identifier Reference - A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. + A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. - Subject Universally Unique Identifier Reference: A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. + Subject Universally Unique Identifier Reference: A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. @@ -6215,10 +6203,10 @@ Identifies the Subject - A human-oriented identifier reference to a resource. Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. + A pointer to a resource based on its universally unique identifier (UUID). Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. - Identifies the Subject: A human-oriented identifier reference to a resource. Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. + Identifies the Subject: A pointer to a resource based on its universally unique identifier (UUID). Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. @@ -6264,10 +6252,10 @@ Subject Universally Unique Identifier Reference - A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. + A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. - Subject Universally Unique Identifier Reference: A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. + Subject Universally Unique Identifier Reference: A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. @@ -6372,10 +6360,10 @@ Component Universally Unique Identifier Reference - A machine-oriented identifier reference to a component that is implemented as part of an inventory item. + A reference to a component that is implemented as part of an inventory item. - Component Universally Unique Identifier Reference: A machine-oriented identifier reference to a component that is implemented as part of an inventory item. + Component Universally Unique Identifier Reference: A reference to a component that is implemented as part of an inventory item. @@ -6400,10 +6388,10 @@ Assessment Platform Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment platform elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment platform can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this assessment Platform. - Assessment Platform Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment platform elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment platform can be used to reference the data item locally or globally (e.g., in an imported 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. + Assessment Platform Universally Unique Identifier: Uniquely identifies this assessment Platform. @@ -6541,10 +6529,10 @@ Finding Target Identifier Reference - A machine-oriented identifier reference for a specific target qualified by the type. + Identifies the specific target qualified by the type. - Finding Target Identifier Reference: A machine-oriented identifier reference for a specific target qualified by the type. + Finding Target Identifier Reference: Identifies the specific target qualified by the type. @@ -6738,10 +6726,10 @@ Observation Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. The locally defined UUID of the observation can be used to reference the data item locally or globally (e.g., in an imorted 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. + Uniquely identifies this observation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given observation across revisions. - Observation Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. The locally defined UUID of the observation can be used to reference the data item locally or globally (e.g., in an imorted 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. + Observation Universally Unique Identifier: Uniquely identifies this observation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given observation across revisions. @@ -6798,10 +6786,10 @@ Actor Universally Unique Identifier Reference - A machine-oriented identifier reference to the tool or person based on the associated type. + A pointer to the tool or person based on the associated type. - Actor Universally Unique Identifier Reference: A machine-oriented identifier reference to the tool or person based on the associated type. + Actor Universally Unique Identifier Reference: A pointer to the tool or person based on the associated type. @@ -6863,10 +6851,10 @@ Assessment Subject Placeholder Universally Unique Identifier Reference - A machine-oriented identifier reference to a unique assessment subject placeholder defined by this task. + References a unique assessment subject placeholder defined by this task. - Assessment Subject Placeholder Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique assessment subject placeholder defined by this task. + Assessment Subject Placeholder Universally Unique Identifier Reference: References a unique assessment subject placeholder defined by this task. @@ -6891,10 +6879,10 @@ Task Universally Unique Identifier Reference - A machine-oriented identifier reference to a unique task. + References a unique task by UUID. - Task Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique task. + Task Universally Unique Identifier Reference: References a unique task by UUID. @@ -7063,20 +7051,20 @@ Mitigating Factor Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mitigating factor elsewhere in this or other OSCAL instances. The locally defined UUID of the mitigating factor can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this mitigating factor. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given mitigating factor across revisions. - Mitigating Factor Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mitigating factor elsewhere in this or other OSCAL instances. The locally defined UUID of the mitigating factor can be used to reference the data item locally or globally (e.g., in an imported 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. + Mitigating Factor Universally Unique Identifier: Uniquely identifies this mitigating factor. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given mitigating factor across revisions. Implementation UUID - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this implementation statement elsewhere in this or other OSCAL instancess. The locally defined UUID of the implementation statement can be used to reference the data item locally or globally (e.g., in an imported 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. + Points to an implementation statement in the SSP. - Implementation UUID: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this implementation statement elsewhere in this or other OSCAL instancess. The locally defined UUID of the implementation statement can be used to reference the data item locally or globally (e.g., in an imported 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. + Implementation UUID: Points to an implementation statement in the SSP. @@ -7235,10 +7223,10 @@ Response Universally Unique Identifier Reference - A machine-oriented identifier reference to a unique risk response. + References a unique risk response by UUID. - Response Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique risk response. + Response Universally Unique Identifier Reference: References a unique risk response by UUID. @@ -7263,10 +7251,10 @@ Risk Log Entry Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk log entry elsewhere in this or other OSCAL instances. The locally defined UUID of the risk log entry can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies a risk log entry. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. - Risk Log Entry Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk log entry elsewhere in this or other OSCAL instances. The locally defined UUID of the risk log entry can be used to reference the data item locally or globally (e.g., in an imported 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. + Risk Log Entry Universally Unique Identifier: Uniquely identifies a risk log entry. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. @@ -7288,10 +7276,10 @@ Observation Universally Unique Identifier Reference - A machine-oriented identifier reference to an observation defined in the list of observations. + References an observation defined in the list of observations. - Observation Universally Unique Identifier Reference: A machine-oriented identifier reference to an observation defined in the list of observations. + Observation Universally Unique Identifier Reference: References an observation defined in the list of observations. @@ -7301,10 +7289,10 @@ Risk Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk elsewhere in this or other OSCAL instances. The locally defined UUID of the risk can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this risk. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given risk across revisions. - Risk Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk elsewhere in this or other OSCAL instances. The locally defined UUID of the risk can be used to reference the data item locally or globally (e.g., in an imported 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. + Risk Universally Unique Identifier: Uniquely identifies this risk. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given risk across revisions. @@ -7321,10 +7309,10 @@ Party UUID Reference - A machine-oriented identifier reference to the party who is making the log entry. + A pointer to the party who is making the log entry. - Party UUID Reference: A machine-oriented identifier reference to the party who is making the log entry. + Party UUID Reference: A pointer to the party who is making the log entry. @@ -7565,10 +7553,10 @@ Required Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this required asset elsewhere in this or other OSCAL instances. The locally defined UUID of the asset can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this required asset. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given required asset across revisions. - Required Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this required asset elsewhere in this or other OSCAL instances. The locally defined UUID of the asset can be used to reference the data item locally or globally (e.g., in an imported 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. + Required Universally Unique Identifier: Uniquely identifies this required asset. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given required asset across revisions. @@ -7597,10 +7585,10 @@ Remediation Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this remediation elsewhere in this or other OSCAL instances. The locally defined UUID of the risk response can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this remediation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given remediation across revisions. - Remediation Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this remediation elsewhere in this or other OSCAL instances. The locally defined UUID of the risk response can be used to reference the data item locally or globally (e.g., in an imported 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. + Remediation Universally Unique Identifier: Uniquely identifies this remediation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given remediation across revisions. @@ -7659,10 +7647,10 @@ Part Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this part elsewhere in this or other OSCAL instances. The locally defined UUID of the part can be used to reference the data item locally or globally (e.g., in an ported 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. + A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. - Part Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this part elsewhere in this or other OSCAL instances. The locally defined UUID of the part can be used to reference the data item locally or globally (e.g., in an ported 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. + Part Identifier: A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. @@ -7766,10 +7754,10 @@ Assessment Results Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment results instance in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this assessment results file. This UUID must be changed each time the content of the results changes. - Assessment Results Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment results instance in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported 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. + Assessment Results Universally Unique Identifier: Uniquely identifies this assessment results file. This UUID must be changed each time the content of the results changes. @@ -8021,10 +8009,10 @@ Assessment Log Entry Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference an assessment event in this or other OSCAL instances. The locally defined UUID of the assessment log entry can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies an assessment event. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. - Assessment Log Entry Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference an assessment event in this or other OSCAL instances. The locally defined UUID of the assessment log entry can be used to reference the data item locally or globally (e.g., in an imported 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. + Assessment Log Entry Universally Unique Identifier: Uniquely identifies an assessment event. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. @@ -8064,10 +8052,10 @@ Results Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this set of results in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this set of results. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given set of results across revisions. - Results Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this set of results in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported 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. + Results Universally Unique Identifier: Uniquely identifies this set of results. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given set of results across revisions. @@ -8132,10 +8120,10 @@ Implementation Statement UUID - A machine-oriented identifier reference to the implementation statement in the SSP to which this finding is related. + Identifies the implementation statement in the SSP to which this finding is related. - Implementation Statement UUID: A machine-oriented identifier reference to the implementation statement in the SSP to which this finding is related. + Implementation Statement UUID: Identifies the implementation statement in the SSP to which this finding is related. @@ -8154,10 +8142,10 @@ Observation Universally Unique Identifier Reference - A machine-oriented identifier reference to an observation defined in the list of observations. + References an observation defined in the list of observations. - Observation Universally Unique Identifier Reference: A machine-oriented identifier reference to an observation defined in the list of observations. + Observation Universally Unique Identifier Reference: References an observation defined in the list of observations. @@ -8176,10 +8164,10 @@ Risk Universally Unique Identifier Reference - A machine-oriented identifier reference to a risk defined in the list of risks. + References an risk defined in the list of risks. - Risk Universally Unique Identifier Reference: A machine-oriented identifier reference to a risk defined in the list of risks. + Risk Universally Unique Identifier Reference: References an risk defined in the list of risks. @@ -8204,10 +8192,10 @@ Finding Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this finding in this or other OSCAL instances. The locally defined UUID of the finding can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this finding. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given finding across revisions. - Finding Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this finding in this or other OSCAL instances. The locally defined UUID of the finding can be used to reference the data item locally or globally (e.g., in an imported 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. + Finding Universally Unique Identifier: Uniquely identifies this finding. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given finding across revisions. @@ -8297,10 +8285,10 @@ POA&M Universally Unique Identifier - A machine-oriented, globally unique identifier with instancescope that can be used to reference this POA&M instance in this 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. + Uniquely identifies this POA&M. This UUID must be changed each time the content of the POA&M changes. - POA&M Universally Unique Identifier: A machine-oriented, globally unique identifier with instancescope that can be used to reference this POA&M instance in this 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. + POA&M Universally Unique Identifier: Uniquely identifies this POA&M. This UUID must be changed each time the content of the POA&M changes. @@ -8419,10 +8407,10 @@ Observation Universally Unique Identifier Reference - A machine-oriented identifier reference to an observation defined in the list of observations. + References an observation defined in the list of observations. - Observation Universally Unique Identifier Reference: A machine-oriented identifier reference to an observation defined in the list of observations. + Observation Universally Unique Identifier Reference: References an observation defined in the list of observations. @@ -8441,10 +8429,10 @@ Risk Universally Unique Identifier Reference - A machine-oriented identifier reference to a risk defined in the list of risks. + References an risk defined in the list of risks. - Risk Universally Unique Identifier Reference: A machine-oriented identifier reference to a risk defined in the list of risks. + Risk Universally Unique Identifier Reference: References an risk defined in the list of risks. @@ -8469,10 +8457,10 @@ POA&M Item Universally Unique Identifier - A machine-oriented, globally unique identifier with instance scope that can be used to reference this POA&M item entry in this 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. + Uniquely identifies the POA&M entry. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given POA&M item across revisions of the document. - POA&M Item Universally Unique Identifier: A machine-oriented, globally unique identifier with instance scope that can be used to reference this POA&M item entry in this 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. + POA&M Item Universally Unique Identifier: Uniquely identifies the POA&M entry. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given POA&M item across revisions of the document. diff --git a/xml/schema/oscal_component_schema.xsd b/xml/schema/oscal_component_schema.xsd index 2b62d39331..23eda146ed 100644 --- a/xml/schema/oscal_component_schema.xsd +++ b/xml/schema/oscal_component_schema.xsd @@ -56,10 +56,10 @@ Component Definition Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component definition elsewhere in this or other OSCAL instances. The locally defined UUID of the component definition can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier for this component definition instance. This UUID should be changed when this document is revised. - Component Definition Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component definition elsewhere in this or other OSCAL instances. The locally defined UUID of the component definition can be used to reference the data item locally or globally (e.g., in an imported 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. + Component Definition Universally Unique Identifier: A globally unique identifier for this component definition instance. This UUID should be changed when this document is revised. @@ -180,10 +180,10 @@ Component Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. + The unique identifier for the component. - Component Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. + Component Identifier: The unique identifier for the component. @@ -258,10 +258,10 @@ Capability Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this capability elsewhere in this or other OSCAL instances. The locally defined UUID of the capability can be used to reference the data item locally or globally (e.g., in an imported 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. + A unique identifier for a capability. - Capability Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this capability elsewhere in this or other OSCAL instances. The locally defined UUID of the capability can be used to reference the data item locally or globally (e.g., in an imported 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. + Capability Identifier: A unique identifier for a capability. @@ -307,10 +307,10 @@ Component Reference - A machine-oriented identifier reference to a component. + A reference to a component by its identifier - Component Reference: A machine-oriented identifier reference to a component. + Component Reference: A reference to a component by its identifier @@ -360,10 +360,10 @@ Control Implementation Set Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference a set of implemented controls elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation set can be used to reference the data item locally or globally (e.g., in an imported 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. + A unique identifier for the set of implemented controls. - Control Implementation Set Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference a set of implemented controls elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation set can be used to reference the data item locally or globally (e.g., in an imported 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. + Control Implementation Set Identifier: A unique identifier for the set of implemented controls. Control Implementation Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference a specific control implementation elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. + A unique identifier for a specific control implementation. - Control Implementation Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference a specific control implementation elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. + Control Implementation Identifier: A unique identifier for a specific control implementation. Control Identifier Reference - A human-oriented identifier reference to a control with a corresponding 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). + A reference to a control with a corresponding id value. - Control Identifier Reference: A human-oriented identifier reference to a control with a corresponding 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). + Control Identifier Reference: A reference to a control with a corresponding id value. @@ -522,20 +522,20 @@ Control Statement Reference - A human-oriented identifier reference to a control statement. + A reference to a control statement by its identifier - Control Statement Reference: A human-oriented identifier reference to a control statement. + Control Statement Reference: A reference to a control statement by its identifier Control Statement Reference Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. The UUID of the control statement in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance). + A globally unique identifier that can be used to reference this control statement entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Control Statement Reference Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. The UUID of the control statement in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance). + Control Statement Reference Universally Unique Identifier: A globally unique identifier that can be used to reference this control statement entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -669,10 +669,10 @@ Component Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. + The unique identifier for the component. - Component Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. + Component Identifier: The unique identifier for the component. @@ -720,10 +720,10 @@ Service Protocol Information Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier that can be used to reference this service protocol entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Service Protocol Information Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported 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. + Service Protocol Information Universally Unique Identifier: A globally unique identifier that can be used to reference this service protocol entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -903,10 +903,10 @@ User Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported 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. + The unique identifier for the user class. - User Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported 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. + User Universally Unique Identifier: The unique identifier for the user class. @@ -1049,10 +1049,10 @@ Component Universally Unique Identifier Reference - A machine-oriented identifier reference to a component that is implemented as part of an inventory item. + A reference to a component that is implemented as part of an inventory item. - Component Universally Unique Identifier Reference: A machine-oriented identifier reference to a component that is implemented as part of an inventory item. + Component Universally Unique Identifier Reference: A reference to a component that is implemented as part of an inventory item. @@ -1077,10 +1077,10 @@ Inventory Item Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier that can be used to reference this inventory item entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Inventory Item Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported 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. + Inventory Item Universally Unique Identifier: A globally unique identifier that can be used to reference this inventory item entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -1129,10 +1129,10 @@ Parameter ID - A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context. + A reference to a parameter within a control, who's catalog has been imported into the current implementation context. - Parameter ID: A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context. + Parameter ID: A reference to a parameter within a control, who's catalog has been imported into the current implementation context. @@ -1140,10 +1140,10 @@ System Identification - A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. + A unique identifier for the system described by this system security plan. - System Identification: A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. + System Identification: A unique identifier for the system described by this system security plan. @@ -1151,10 +1151,10 @@ Identification System Type - Identifies the identification system from which the provided identifier was assigned. + Identifies the identification system from which the provided identifier was assigned. - Identification System Type: Identifies the identification system from which the provided identifier was assigned. + Identification System Type: Identifies the identification system from which the provided identifier was assigned. @@ -1400,10 +1400,10 @@ Location Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. + A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. - Location Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. + Location Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. @@ -1411,10 +1411,10 @@ Location Reference - A machine-oriented identifier reference to a 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). + References a location defined in metadata. - Location Reference: A machine-oriented identifier reference to a 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 Reference: References a location defined in metadata. @@ -1511,10 +1511,10 @@ Organizational Affiliation - A machine-oriented identifier reference to another 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). + Identifies that the party object is a member of the organization associated with the provided UUID. - Organizational Affiliation: A machine-oriented identifier reference to another 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). + Organizational Affiliation: Identifies that the party object is a member of the organization associated with the provided UUID. @@ -1539,10 +1539,10 @@ Party Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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. + A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. - Party Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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 Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. @@ -1560,10 +1560,10 @@ Party Reference - A machine-oriented identifier reference to another 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). + References a party defined in metadata. - Party Reference: A machine-oriented identifier reference to another 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 Reference: References a party defined in metadata. @@ -1647,9 +1647,11 @@ - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. + Role Identifier + A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. + + Role Identifier: A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. @@ -1657,10 +1659,10 @@ Role Identifier Reference - A human-oriented identifier reference to roles served by the user. + A reference to the roles served by the user. - Role Identifier Reference: A human-oriented identifier reference to roles served by the user. + Role Identifier Reference: A reference to the roles served by the user. @@ -1856,10 +1858,10 @@ Resource Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Resource Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Resource Universally Unique Identifier: A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -1906,10 +1908,10 @@ Property Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. - Property Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Property Universally Unique Identifier: A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. @@ -2048,10 +2050,10 @@ Responsible Role - A human-oriented identifier reference to roles served by the user. + The role that the party is responsible for. - Responsible Role: A human-oriented identifier reference to roles served by the user. + Responsible Role: The role that the party is responsible for. @@ -2099,10 +2101,10 @@ Responsible Role ID - A human-oriented identifier reference to roles responsible for the business function. + The role that is responsible for the business function. - Responsible Role ID: A human-oriented identifier reference to roles responsible for the business function. + Responsible Role ID: The role that is responsible for the business function. @@ -2317,10 +2319,10 @@ Document Identifier - A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. - Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. @@ -2382,10 +2384,10 @@ Part Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. - Part Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Part Identifier: A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. @@ -2505,10 +2507,10 @@ Parameter Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. - Parameter Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Parameter Identifier: A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. diff --git a/xml/schema/oscal_poam_schema.xsd b/xml/schema/oscal_poam_schema.xsd index a9dc350968..018e4330a1 100644 --- a/xml/schema/oscal_poam_schema.xsd +++ b/xml/schema/oscal_poam_schema.xsd @@ -67,10 +67,10 @@ POA&M Universally Unique Identifier - A machine-oriented, globally unique identifier with instancescope that can be used to reference this POA&M instance in this 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. + Uniquely identifies this POA&M. This UUID must be changed each time the content of the POA&M changes. - POA&M Universally Unique Identifier: A machine-oriented, globally unique identifier with instancescope that can be used to reference this POA&M instance in this 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. + POA&M Universally Unique Identifier: Uniquely identifies this POA&M. This UUID must be changed each time the content of the POA&M changes. @@ -189,10 +189,10 @@ Observation Universally Unique Identifier Reference - A machine-oriented identifier reference to an observation defined in the list of observations. + References an observation defined in the list of observations. - Observation Universally Unique Identifier Reference: A machine-oriented identifier reference to an observation defined in the list of observations. + Observation Universally Unique Identifier Reference: References an observation defined in the list of observations. @@ -211,10 +211,10 @@ Risk Universally Unique Identifier Reference - A machine-oriented identifier reference to a risk defined in the list of risks. + References an risk defined in the list of risks. - Risk Universally Unique Identifier Reference: A machine-oriented identifier reference to a risk defined in the list of risks. + Risk Universally Unique Identifier Reference: References an risk defined in the list of risks. @@ -239,10 +239,10 @@ POA&M Item Universally Unique Identifier - A machine-oriented, globally unique identifier with instance scope that can be used to reference this POA&M item entry in this 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. + Uniquely identifies the POA&M entry. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given POA&M item across revisions of the document. - POA&M Item Universally Unique Identifier: A machine-oriented, globally unique identifier with instance scope that can be used to reference this POA&M item entry in this 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. + POA&M Item Universally Unique Identifier: Uniquely identifies the POA&M entry. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given POA&M item across revisions of the document. @@ -486,10 +486,10 @@ Location Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. + A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. - Location Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. + Location Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. @@ -497,10 +497,10 @@ Location Reference - A machine-oriented identifier reference to a 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). + References a location defined in metadata. - Location Reference: A machine-oriented identifier reference to a 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 Reference: References a location defined in metadata. @@ -597,10 +597,10 @@ Organizational Affiliation - A machine-oriented identifier reference to another 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). + Identifies that the party object is a member of the organization associated with the provided UUID. - Organizational Affiliation: A machine-oriented identifier reference to another 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). + Organizational Affiliation: Identifies that the party object is a member of the organization associated with the provided UUID. @@ -625,10 +625,10 @@ Party Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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. + A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. - Party Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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 Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. @@ -646,10 +646,10 @@ Party Reference - A machine-oriented identifier reference to another 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). + References a party defined in metadata. - Party Reference: A machine-oriented identifier reference to another 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 Reference: References a party defined in metadata. @@ -733,9 +733,11 @@ - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. + Role Identifier + A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. + + Role Identifier: A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. @@ -743,10 +745,10 @@ Role Identifier Reference - A human-oriented identifier reference to roles served by the user. + A reference to the roles served by the user. - Role Identifier Reference: A human-oriented identifier reference to roles served by the user. + Role Identifier Reference: A reference to the roles served by the user. @@ -940,10 +942,10 @@ Resource Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Resource Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Resource Universally Unique Identifier: A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -990,10 +992,10 @@ Property Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. - Property Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Property Universally Unique Identifier: A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. @@ -1126,10 +1128,10 @@ Responsible Role - A human-oriented identifier reference to roles served by the user. + The role that the party is responsible for. - Responsible Role: A human-oriented identifier reference to roles served by the user. + Responsible Role: The role that the party is responsible for. @@ -1175,10 +1177,10 @@ Responsible Role ID - A human-oriented identifier reference to roles responsible for the business function. + The role that is responsible for the business function. - Responsible Role ID: A human-oriented identifier reference to roles responsible for the business function. + Responsible Role ID: The role that is responsible for the business function. @@ -1391,10 +1393,10 @@ Document Identifier - A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. - Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. @@ -1541,10 +1543,10 @@ Component Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. + The unique identifier for the component. - Component Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. + Component Identifier: The unique identifier for the component. @@ -1592,10 +1594,10 @@ Service Protocol Information Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier that can be used to reference this service protocol entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Service Protocol Information Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported 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. + Service Protocol Information Universally Unique Identifier: A globally unique identifier that can be used to reference this service protocol entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -1775,10 +1777,10 @@ User Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported 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. + The unique identifier for the user class. - User Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported 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. + User Universally Unique Identifier: The unique identifier for the user class. @@ -1919,10 +1921,10 @@ Component Universally Unique Identifier Reference - A machine-oriented identifier reference to a component that is implemented as part of an inventory item. + A reference to a component that is implemented as part of an inventory item. - Component Universally Unique Identifier Reference: A machine-oriented identifier reference to a component that is implemented as part of an inventory item. + Component Universally Unique Identifier Reference: A reference to a component that is implemented as part of an inventory item. @@ -1947,10 +1949,10 @@ Inventory Item Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier that can be used to reference this inventory item entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Inventory Item Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported 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. + Inventory Item Universally Unique Identifier: A globally unique identifier that can be used to reference this inventory item entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -1997,10 +1999,10 @@ Parameter ID - A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context. + A reference to a parameter within a control, who's catalog has been imported into the current implementation context. - Parameter ID: A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context. + Parameter ID: A reference to a parameter within a control, who's catalog has been imported into the current implementation context. @@ -2008,10 +2010,10 @@ System Identification - A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. + A unique identifier for the system described by this system security plan. - System Identification: A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. + System Identification: A unique identifier for the system described by this system security plan. @@ -2019,10 +2021,10 @@ Identification System Type - Identifies the identification system from which the provided identifier was assigned. + Identifies the identification system from which the provided identifier was assigned. - Identification System Type: Identifies the identification system from which the provided identifier was assigned. + Identification System Type: Identifies the identification system from which the provided identifier was assigned. @@ -2073,10 +2075,10 @@ Part Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. - Part Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Part Identifier: A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. @@ -2196,10 +2198,10 @@ Parameter Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. - Parameter Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Parameter Identifier: A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. @@ -2449,10 +2451,10 @@ Control Identifier Reference - A human-oriented identifier reference to a control with a corresponding 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). + A reference to a control with a corresponding id value. - Control Identifier Reference: A human-oriented identifier reference to a control with a corresponding 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). + Control Identifier Reference: A reference to a control with a corresponding id value. @@ -2513,10 +2515,10 @@ Assessment Method Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment method elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment method can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this defined assessment method. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given assessment method across revisions of the document. - Assessment Method Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment method elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment method can be used to reference the data item locally or globally (e.g., in an imported 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. + Assessment Method Universally Unique Identifier: Uniquely identifies this defined assessment method. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given assessment method across revisions of the document. @@ -2645,10 +2647,10 @@ Step Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this step elsewhere in this or other OSCAL instances. The locally defined UUID of the step (in a series of steps) can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies a step. This UUID may be referenced elsewhere in an OSCAL document when referring to this step. A UUID should be consistently used for a given test step across revisions of the document. - Step Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this step elsewhere in this or other OSCAL instances. The locally defined UUID of the step (in a series of steps) can be used to reference the data item locally or globally (e.g., in an imported 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. + Step Universally Unique Identifier: Uniquely identifies a step. This UUID may be referenced elsewhere in an OSCAL document when referring to this step. A UUID should be consistently used for a given test step across revisions of the document. @@ -2681,10 +2683,10 @@ Assessment Activity Universally Unique Identifier - A machine-oriented, globally unique> identifier with cross-instance scope that can be used to reference this assessment activity elsewhere in this or other OSCAL instances. The locally defined UUID of the activity can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this assessment activity. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given included activity across revisions of the document. - Assessment Activity Universally Unique Identifier: A machine-oriented, globally unique> identifier with cross-instance scope that can be used to reference this assessment activity elsewhere in this or other OSCAL instances. The locally defined UUID of the activity can be used to reference the data item locally or globally (e.g., in an imported 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. + Assessment Activity Universally Unique Identifier: Uniquely identifies this assessment activity. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given included activity across revisions of the document. @@ -2871,10 +2873,10 @@ Task Universally Unique Identifier Reference - A machine-oriented identifier reference to a unique task. + References a unique task by UUID. - Task Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique task. + Task Universally Unique Identifier Reference: References a unique task by UUID. @@ -2930,10 +2932,10 @@ Activity Universally Unique Identifier Reference - A machine-oriented identifier reference to an activity defined in the list of activities. + References an activity defined in the list of activities. - Activity Universally Unique Identifier Reference: A machine-oriented identifier reference to an activity defined in the list of activities. + Activity Universally Unique Identifier Reference: References an activity defined in the list of activities. @@ -2966,10 +2968,10 @@ Task Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this task elsewhere in this or other OSCAL instances. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this assessment task. - Task Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this task elsewhere in this or other OSCAL instances. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. + Task Universally Unique Identifier: Uniquely identifies this assessment task. @@ -3211,10 +3213,10 @@ Control Identifier Reference - A human-oriented identifier reference to a control with a corresponding 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). + A reference to a control with a corresponding id value. - Control Identifier Reference: A human-oriented identifier reference to a control with a corresponding 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). + Control Identifier Reference: A reference to a control with a corresponding id value. @@ -3277,10 +3279,10 @@ Task Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference (in this or other OSCAL instances) an assessment activity to be performed as part of the event. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies an assessment activity to be performed as part of the event. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. - Task Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference (in this or other OSCAL instances) an assessment activity to be performed as part of the event. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. + Task Universally Unique Identifier: Uniquely identifies an assessment activity to be performed as part of the event. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. @@ -3313,10 +3315,10 @@ Assessment Subject Placeholder Universally Unique Identifier - A machine-oriented, globally unique identifier for a set of assessment subjects that will be identified by a task or an activity that is part of a task. The locally defined UUID of the assessment subject placeholder can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task. - Assessment Subject Placeholder Universally Unique Identifier: A machine-oriented, globally unique identifier for a set of assessment subjects that will be identified by a task or an activity that is part of a task. The locally defined UUID of the assessment subject placeholder can be used to reference the data item locally or globally (e.g., in an imported 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. + Assessment Subject Placeholder Universally Unique Identifier: Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task. @@ -3440,10 +3442,10 @@ Subject Universally Unique Identifier Reference - A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. + A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. - Subject Universally Unique Identifier Reference: A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. + Subject Universally Unique Identifier Reference: A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. @@ -3461,10 +3463,10 @@ Identifies the Subject - A human-oriented identifier reference to a resource. Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. + A pointer to a resource based on its universally unique identifier (UUID). Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. - Identifies the Subject: A human-oriented identifier reference to a resource. Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. + Identifies the Subject: A pointer to a resource based on its universally unique identifier (UUID). Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. @@ -3510,10 +3512,10 @@ Subject Universally Unique Identifier Reference - A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. + A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. - Subject Universally Unique Identifier Reference: A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. + Subject Universally Unique Identifier Reference: A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. @@ -3618,10 +3620,10 @@ Component Universally Unique Identifier Reference - A machine-oriented identifier reference to a component that is implemented as part of an inventory item. + A reference to a component that is implemented as part of an inventory item. - Component Universally Unique Identifier Reference: A machine-oriented identifier reference to a component that is implemented as part of an inventory item. + Component Universally Unique Identifier Reference: A reference to a component that is implemented as part of an inventory item. @@ -3646,10 +3648,10 @@ Assessment Platform Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment platform elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment platform can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this assessment Platform. - Assessment Platform Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment platform elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment platform can be used to reference the data item locally or globally (e.g., in an imported 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. + Assessment Platform Universally Unique Identifier: Uniquely identifies this assessment Platform. @@ -3787,10 +3789,10 @@ Finding Target Identifier Reference - A machine-oriented identifier reference for a specific target qualified by the type. + Identifies the specific target qualified by the type. - Finding Target Identifier Reference: A machine-oriented identifier reference for a specific target qualified by the type. + Finding Target Identifier Reference: Identifies the specific target qualified by the type. @@ -3984,10 +3986,10 @@ Observation Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. The locally defined UUID of the observation can be used to reference the data item locally or globally (e.g., in an imorted 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. + Uniquely identifies this observation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given observation across revisions. - Observation Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. The locally defined UUID of the observation can be used to reference the data item locally or globally (e.g., in an imorted 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. + Observation Universally Unique Identifier: Uniquely identifies this observation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given observation across revisions. @@ -4044,10 +4046,10 @@ Actor Universally Unique Identifier Reference - A machine-oriented identifier reference to the tool or person based on the associated type. + A pointer to the tool or person based on the associated type. - Actor Universally Unique Identifier Reference: A machine-oriented identifier reference to the tool or person based on the associated type. + Actor Universally Unique Identifier Reference: A pointer to the tool or person based on the associated type. @@ -4109,10 +4111,10 @@ Assessment Subject Placeholder Universally Unique Identifier Reference - A machine-oriented identifier reference to a unique assessment subject placeholder defined by this task. + References a unique assessment subject placeholder defined by this task. - Assessment Subject Placeholder Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique assessment subject placeholder defined by this task. + Assessment Subject Placeholder Universally Unique Identifier Reference: References a unique assessment subject placeholder defined by this task. @@ -4137,10 +4139,10 @@ Task Universally Unique Identifier Reference - A machine-oriented identifier reference to a unique task. + References a unique task by UUID. - Task Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique task. + Task Universally Unique Identifier Reference: References a unique task by UUID. @@ -4309,20 +4311,20 @@ Mitigating Factor Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mitigating factor elsewhere in this or other OSCAL instances. The locally defined UUID of the mitigating factor can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this mitigating factor. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given mitigating factor across revisions. - Mitigating Factor Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mitigating factor elsewhere in this or other OSCAL instances. The locally defined UUID of the mitigating factor can be used to reference the data item locally or globally (e.g., in an imported 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. + Mitigating Factor Universally Unique Identifier: Uniquely identifies this mitigating factor. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given mitigating factor across revisions. Implementation UUID - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this implementation statement elsewhere in this or other OSCAL instancess. The locally defined UUID of the implementation statement can be used to reference the data item locally or globally (e.g., in an imported 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. + Points to an implementation statement in the SSP. - Implementation UUID: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this implementation statement elsewhere in this or other OSCAL instancess. The locally defined UUID of the implementation statement can be used to reference the data item locally or globally (e.g., in an imported 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. + Implementation UUID: Points to an implementation statement in the SSP. @@ -4481,10 +4483,10 @@ Response Universally Unique Identifier Reference - A machine-oriented identifier reference to a unique risk response. + References a unique risk response by UUID. - Response Universally Unique Identifier Reference: A machine-oriented identifier reference to a unique risk response. + Response Universally Unique Identifier Reference: References a unique risk response by UUID. @@ -4509,10 +4511,10 @@ Risk Log Entry Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk log entry elsewhere in this or other OSCAL instances. The locally defined UUID of the risk log entry can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies a risk log entry. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. - Risk Log Entry Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk log entry elsewhere in this or other OSCAL instances. The locally defined UUID of the risk log entry can be used to reference the data item locally or globally (e.g., in an imported 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. + Risk Log Entry Universally Unique Identifier: Uniquely identifies a risk log entry. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. @@ -4534,10 +4536,10 @@ Observation Universally Unique Identifier Reference - A machine-oriented identifier reference to an observation defined in the list of observations. + References an observation defined in the list of observations. - Observation Universally Unique Identifier Reference: A machine-oriented identifier reference to an observation defined in the list of observations. + Observation Universally Unique Identifier Reference: References an observation defined in the list of observations. @@ -4547,10 +4549,10 @@ Risk Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk elsewhere in this or other OSCAL instances. The locally defined UUID of the risk can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this risk. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given risk across revisions. - Risk Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk elsewhere in this or other OSCAL instances. The locally defined UUID of the risk can be used to reference the data item locally or globally (e.g., in an imported 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. + Risk Universally Unique Identifier: Uniquely identifies this risk. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given risk across revisions. @@ -4567,10 +4569,10 @@ Party UUID Reference - A machine-oriented identifier reference to the party who is making the log entry. + A pointer to the party who is making the log entry. - Party UUID Reference: A machine-oriented identifier reference to the party who is making the log entry. + Party UUID Reference: A pointer to the party who is making the log entry. @@ -4811,10 +4813,10 @@ Required Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this required asset elsewhere in this or other OSCAL instances. The locally defined UUID of the asset can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this required asset. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given required asset across revisions. - Required Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this required asset elsewhere in this or other OSCAL instances. The locally defined UUID of the asset can be used to reference the data item locally or globally (e.g., in an imported 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. + Required Universally Unique Identifier: Uniquely identifies this required asset. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given required asset across revisions. @@ -4843,10 +4845,10 @@ Remediation Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this remediation elsewhere in this or other OSCAL instances. The locally defined UUID of the risk response can be used to reference the data item locally or globally (e.g., in an imported 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. + Uniquely identifies this remediation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given remediation across revisions. - Remediation Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this remediation elsewhere in this or other OSCAL instances. The locally defined UUID of the risk response can be used to reference the data item locally or globally (e.g., in an imported 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. + Remediation Universally Unique Identifier: Uniquely identifies this remediation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given remediation across revisions. @@ -4905,10 +4907,10 @@ Part Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this part elsewhere in this or other OSCAL instances. The locally defined UUID of the part can be used to reference the data item locally or globally (e.g., in an ported 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. + A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. - Part Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this part elsewhere in this or other OSCAL instances. The locally defined UUID of the part can be used to reference the data item locally or globally (e.g., in an ported 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. + Part Identifier: A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. diff --git a/xml/schema/oscal_profile_schema.xsd b/xml/schema/oscal_profile_schema.xsd index 60a84655db..92aa271a02 100644 --- a/xml/schema/oscal_profile_schema.xsd +++ b/xml/schema/oscal_profile_schema.xsd @@ -52,11 +52,11 @@ - Profile Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this profile elsewhere in this or other OSCAL instances. The locally defined UUID of the profile can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance).This identifier should be assigned per-subject, which means it should be consistently used to identify the same profile across revisions of the document. + Catalog Universally Unique Identifier + A globally unique identifier for this profile instance. This UUID should be changed when this document is revised. - Profile Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this profile elsewhere in this or other OSCAL instances. The locally defined UUID of the profile can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance).This identifier should be assigned per-subject, which means it should be consistently used to identify the same profile across revisions of the document. + Catalog Universally Unique Identifier: A globally unique identifier for this profile instance. This UUID should be changed when this document is revised. @@ -115,10 +115,6 @@ type="oscal-profile:oscal-profile-as-is-FIELD" minOccurs="0" maxOccurs="1"/> - - - - - Flat - A Flat element indicates that the controls should be structured in a completely flat list. It does not contain any elements or attributes. - - - Flat: A Flat element indicates that the controls should be structured in a completely flat list. It does not contain any elements or attributes. - - @@ -243,10 +229,10 @@ Group Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. + A unique identifier for a specific group instance that can be used to reference the group within this and in other OSCAL documents. This identifier's uniqueness is document scoped and is intended to be consistent for the same group across minor revisions of the document. - Group Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. + Group Identifier: A unique identifier for a specific group instance that can be used to reference the group within this and in other OSCAL documents. This identifier's uniqueness is document scoped and is intended to be consistent for the same group across minor revisions of the document. @@ -342,10 +328,10 @@ Parameter ID - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Indicates the value of the 'id' flag on a target parameter; i.e. which parameter to set - Parameter ID: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Parameter ID: Indicates the value of the 'id' flag on a target parameter; i.e. which parameter to set @@ -502,10 +488,10 @@ Control Identifier Reference - A human-oriented identifier reference to a control with a corresponding 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). + A reference to a control with a corresponding id value. - Control Identifier Reference: A human-oriented identifier reference to a control with a corresponding 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). + Control Identifier Reference: A reference to a control with a corresponding id value. @@ -873,10 +859,10 @@ Location Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. + A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. - Location Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. + Location Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. @@ -884,10 +870,10 @@ Location Reference - A machine-oriented identifier reference to a 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). + References a location defined in metadata. - Location Reference: A machine-oriented identifier reference to a 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 Reference: References a location defined in metadata. @@ -984,10 +970,10 @@ Organizational Affiliation - A machine-oriented identifier reference to another 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). + Identifies that the party object is a member of the organization associated with the provided UUID. - Organizational Affiliation: A machine-oriented identifier reference to another 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). + Organizational Affiliation: Identifies that the party object is a member of the organization associated with the provided UUID. @@ -1012,10 +998,10 @@ Party Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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. + A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. - Party Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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 Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. @@ -1033,10 +1019,10 @@ Party Reference - A machine-oriented identifier reference to another 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). + References a party defined in metadata. - Party Reference: A machine-oriented identifier reference to another 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 Reference: References a party defined in metadata. @@ -1120,9 +1106,11 @@ - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. + Role Identifier + A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. + + Role Identifier: A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. @@ -1130,10 +1118,10 @@ Role Identifier Reference - A human-oriented identifier reference to roles served by the user. + A reference to the roles served by the user. - Role Identifier Reference: A human-oriented identifier reference to roles served by the user. + Role Identifier Reference: A reference to the roles served by the user. @@ -1327,10 +1315,10 @@ Resource Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Resource Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Resource Universally Unique Identifier: A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -1377,10 +1365,10 @@ Property Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. - Property Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Property Universally Unique Identifier: A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. @@ -1513,10 +1501,10 @@ Responsible Role - A human-oriented identifier reference to roles served by the user. + The role that the party is responsible for. - Responsible Role: A human-oriented identifier reference to roles served by the user. + Responsible Role: The role that the party is responsible for. @@ -1562,10 +1550,10 @@ Responsible Role ID - A human-oriented identifier reference to roles responsible for the business function. + The role that is responsible for the business function. - Responsible Role ID: A human-oriented identifier reference to roles responsible for the business function. + Responsible Role ID: The role that is responsible for the business function. @@ -1778,10 +1766,10 @@ Document Identifier - A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. - Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. @@ -1843,10 +1831,10 @@ Part Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. - Part Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Part Identifier: A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. @@ -1966,10 +1954,10 @@ Parameter Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. - Parameter Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Parameter Identifier: A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. diff --git a/xml/schema/oscal_ssp_schema.xsd b/xml/schema/oscal_ssp_schema.xsd index 435545066a..659502cc3d 100644 --- a/xml/schema/oscal_ssp_schema.xsd +++ b/xml/schema/oscal_ssp_schema.xsd @@ -59,10 +59,10 @@ System Security Plan Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this system security plan (SSP) elsewhere in this or other OSCAL instances. The locally defined UUID of the SSP can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier for this catalog instance. This UUID should be changed when this document is revised. - System Security Plan Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this system security plan (SSP) elsewhere in this or other OSCAL instances. The locally defined UUID of the SSP can be used to reference the data item locally or globally (e.g., in an imported 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. + System Security Plan Universally Unique Identifier: A globally unique identifier for this catalog instance. This UUID should be changed when this document is revised. @@ -303,10 +303,10 @@ Information Type Systematized Identifier - A human-oriented, globally unique identifier qualified by the given identification system used, such as NIST SP 800-60. This identifier has cross-instance scope and can be used to reference this system elsewhere in this or other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + An identifier qualified by the given identification system used, such as NIST SP 800-60. - Information Type Systematized Identifier: A human-oriented, globally unique identifier qualified by the given identification system used, such as NIST SP 800-60. This identifier has cross-instance scope and can be used to reference this system elsewhere in this or other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Information Type Systematized Identifier: An identifier qualified by the given identification system used, such as NIST SP 800-60. @@ -472,10 +472,10 @@ Information Type Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this information type elsewhere in this or other OSCAL instances. The locally defined UUID of the information type can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier that can be used to reference this information type entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Information Type Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this information type elsewhere in this or other OSCAL instances. The locally defined UUID of the information type can be used to reference the data item locally or globally (e.g., in an imported 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. + Information Type Universally Unique Identifier: A globally unique identifier that can be used to reference this information type entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -740,10 +740,10 @@ Diagram ID - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this diagram elsewhere in this or other OSCAL instances. The locally defined UUID of the diagram can be used to reference the data item locally or globally (e.g., in an imported 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. + The identifier for this diagram. - Diagram ID: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this diagram elsewhere in this or other OSCAL instances. The locally defined UUID of the diagram can be used to reference the data item locally or globally (e.g., in an imported 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. + Diagram ID: The identifier for this diagram. @@ -912,10 +912,10 @@ party-uuid field - A machine-oriented identifier reference to the party that manages the leveraged system. + A reference to the party that manages the leveraged system. - party-uuid field: A machine-oriented identifier reference to the party that manages the leveraged system. + party-uuid field: A reference to the party that manages the leveraged system. @@ -944,10 +944,10 @@ Leveraged Authorization Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope and can be used to reference this leveraged authorization elsewhere in this or other OSCAL instances. The locally defined UUID of the leveraged authorization can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier that can be used to reference this leveraged authorization entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Leveraged Authorization Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope and can be used to reference this leveraged authorization elsewhere in this or other OSCAL instances. The locally defined UUID of the leveraged authorization can be used to reference the data item locally or globally (e.g., in an imported 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. + Leveraged Authorization Universally Unique Identifier: A globally unique identifier that can be used to reference this leveraged authorization entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -1070,20 +1070,20 @@ Control Requirement Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control requirement elsewhere in this or other OSCAL instances. The locally defined UUID of the control requirement can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier that can be used to reference this control requirement entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Control Requirement Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control requirement elsewhere in this or other OSCAL instances. The locally defined UUID of the control requirement can be used to reference the data item locally or globally (e.g., in an imported 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. + Control Requirement Universally Unique Identifier: A globally unique identifier that can be used to reference this control requirement entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. Control Identifier Reference - A human-oriented identifier reference to a control with a corresponding 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). + A reference to a control with a corresponding id value. - Control Identifier Reference: A human-oriented identifier reference to a control with a corresponding 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). + Control Identifier Reference: A reference to a control with a corresponding id value. @@ -1133,20 +1133,20 @@ Control Statement Reference - A human-oriented identifier reference to a control statement. + A reference to a control statement by its identifier - Control Statement Reference: A human-oriented identifier reference to a control statement. + Control Statement Reference: A reference to a control statement by its identifier Control Statement Reference Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. The UUID of the control statement in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance). + A globally unique identifier that can be used to reference this control statement entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Control Statement Reference Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. The UUID of the control statement in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance). + Control Statement Reference Universally Unique Identifier: A globally unique identifier that can be used to reference this control statement entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -1283,10 +1283,10 @@ Provided Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this provided entry elsewhere in this or other OSCAL instances. The locally defined UUID of the provided entry can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier that can be used to reference this provided entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Provided Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this provided entry elsewhere in this or other OSCAL instances. The locally defined UUID of the provided entry can be used to reference the data item locally or globally (e.g., in an imported 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. + Provided Universally Unique Identifier: A globally unique identifier that can be used to reference this provided entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -1349,20 +1349,20 @@ Responsibility Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this responsibility elsewhere in this or other OSCAL instances. The locally defined UUID of the responsibility can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier that can be used to reference this responsibility entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Responsibility Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this responsibility elsewhere in this or other OSCAL instances. The locally defined UUID of the responsibility can be used to reference the data item locally or globally (e.g., in an imported 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. + Responsibility Universally Unique Identifier: A globally unique identifier that can be used to reference this responsibility entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. Provided UUID - A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system. + Identifies a 'provided' assembly associated with this assembly. - Provided UUID: A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system. + Provided UUID: Identifies a 'provided' assembly associated with this assembly. @@ -1428,20 +1428,20 @@ Inherited Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inherited entry elsewhere in this or other OSCAL instances. The locally defined UUID of the inherited control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier that can be used to reference this inherited entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Inherited Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inherited entry elsewhere in this or other OSCAL instances. The locally defined UUID of the inherited control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. + Inherited Universally Unique Identifier: A globally unique identifier that can be used to reference this inherited entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. Provided UUID - A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system. + Identifies a 'provided' assembly associated with this assembly. - Provided UUID: A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system. + Provided UUID: Identifies a 'provided' assembly associated with this assembly. @@ -1504,20 +1504,20 @@ Satisfied Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this satisfied control implementation entry elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier that can be used to reference this satisfied entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Satisfied Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this satisfied control implementation entry elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. + Satisfied Universally Unique Identifier: A globally unique identifier that can be used to reference this satisfied entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Responsibility UUID - A machine-oriented identifier reference to a control implementation that satisfies a responsibility imposed by a leveraged system. + Provided UUID + Identifies a 'provided' assembly associated with this assembly. - Responsibility UUID: A machine-oriented identifier reference to a control implementation that satisfies a responsibility imposed by a leveraged system. + Provided UUID: Identifies a 'provided' assembly associated with this assembly. @@ -1546,20 +1546,20 @@ Component Universally Unique Identifier Reference - A machine-oriented identifier reference to the component that is implemeting a given control. + A reference to the component that is implementing a given control or control statement. - Component Universally Unique Identifier Reference: A machine-oriented identifier reference to the component that is implemeting a given control. + Component Universally Unique Identifier Reference: A reference to the component that is implementing a given control or control statement. By-Component Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this by-component entry elsewhere in this or other OSCAL instances. The locally defined UUID of the by-component entry can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier that can be used to reference this by-component entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - By-Component Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this by-component entry elsewhere in this or other OSCAL instances. The locally defined UUID of the by-component entry can be used to reference the data item locally or globally (e.g., in an imported 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. + By-Component Universally Unique Identifier: A globally unique identifier that can be used to reference this by-component entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -1803,10 +1803,10 @@ Location Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. + A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. - Location Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. + Location Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. @@ -1814,10 +1814,10 @@ Location Reference - A machine-oriented identifier reference to a 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). + References a location defined in metadata. - Location Reference: A machine-oriented identifier reference to a 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 Reference: References a location defined in metadata. @@ -1914,10 +1914,10 @@ Organizational Affiliation - A machine-oriented identifier reference to another 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). + Identifies that the party object is a member of the organization associated with the provided UUID. - Organizational Affiliation: A machine-oriented identifier reference to another 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). + Organizational Affiliation: Identifies that the party object is a member of the organization associated with the provided UUID. @@ -1942,10 +1942,10 @@ Party Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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. + A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. - Party Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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 Universally Unique Identifier: A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. @@ -1963,10 +1963,10 @@ Party Reference - A machine-oriented identifier reference to another 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). + References a party defined in metadata. - Party Reference: A machine-oriented identifier reference to another 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 Reference: References a party defined in metadata. @@ -2050,9 +2050,11 @@ - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. + Role Identifier + A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. + + Role Identifier: A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. @@ -2060,10 +2062,10 @@ Role Identifier Reference - A human-oriented identifier reference to roles served by the user. + A reference to the roles served by the user. - Role Identifier Reference: A human-oriented identifier reference to roles served by the user. + Role Identifier Reference: A reference to the roles served by the user. @@ -2257,10 +2259,10 @@ Resource Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Resource Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Resource Universally Unique Identifier: A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -2307,10 +2309,10 @@ Property Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. - Property Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Property Universally Unique Identifier: A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. @@ -2443,10 +2445,10 @@ Responsible Role - A human-oriented identifier reference to roles served by the user. + The role that the party is responsible for. - Responsible Role: A human-oriented identifier reference to roles served by the user. + Responsible Role: The role that the party is responsible for. @@ -2492,10 +2494,10 @@ Responsible Role ID - A human-oriented identifier reference to roles responsible for the business function. + The role that is responsible for the business function. - Responsible Role ID: A human-oriented identifier reference to roles responsible for the business function. + Responsible Role ID: The role that is responsible for the business function. @@ -2708,10 +2710,10 @@ Document Identifier - A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. - Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + Document Identifier: A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. @@ -2858,10 +2860,10 @@ Component Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. + The unique identifier for the component. - Component Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. + Component Identifier: The unique identifier for the component. @@ -2909,10 +2911,10 @@ Service Protocol Information Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier that can be used to reference this service protocol entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Service Protocol Information Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported 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. + Service Protocol Information Universally Unique Identifier: A globally unique identifier that can be used to reference this service protocol entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -3092,10 +3094,10 @@ User Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported 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. + The unique identifier for the user class. - User Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported 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. + User Universally Unique Identifier: The unique identifier for the user class. @@ -3236,10 +3238,10 @@ Component Universally Unique Identifier Reference - A machine-oriented identifier reference to a component that is implemented as part of an inventory item. + A reference to a component that is implemented as part of an inventory item. - Component Universally Unique Identifier Reference: A machine-oriented identifier reference to a component that is implemented as part of an inventory item. + Component Universally Unique Identifier Reference: A reference to a component that is implemented as part of an inventory item. @@ -3264,10 +3266,10 @@ Inventory Item Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported 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. + A globally unique identifier that can be used to reference this inventory item entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. - Inventory Item Universally Unique Identifier: A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported 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. + Inventory Item Universally Unique Identifier: A globally unique identifier that can be used to reference this inventory item entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. @@ -3314,10 +3316,10 @@ Parameter ID - A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context. + A reference to a parameter within a control, who's catalog has been imported into the current implementation context. - Parameter ID: A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context. + Parameter ID: A reference to a parameter within a control, who's catalog has been imported into the current implementation context. @@ -3325,10 +3327,10 @@ System Identification - A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. + A unique identifier for the system described by this system security plan. - System Identification: A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. + System Identification: A unique identifier for the system described by this system security plan. @@ -3336,10 +3338,10 @@ Identification System Type - Identifies the identification system from which the provided identifier was assigned. + Identifies the identification system from which the provided identifier was assigned. - Identification System Type: Identifies the identification system from which the provided identifier was assigned. + Identification System Type: Identifies the identification system from which the provided identifier was assigned. @@ -3390,10 +3392,10 @@ Part Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. - Part Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Part Identifier: A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. @@ -3513,10 +3515,10 @@ Parameter Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. - Parameter Identifier: A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + Parameter Identifier: A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. From d2304b559c06bdb944a9e3f36b63ba071500c0a8 Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Wed, 1 Sep 2021 16:59:56 -0400 Subject: [PATCH 03/34] updates to metadata identifiers --- src/metaschema/oscal_metadata_metaschema.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/src/metaschema/oscal_metadata_metaschema.xml b/src/metaschema/oscal_metadata_metaschema.xml index f20a00a3db..8a070adca6 100644 --- a/src/metaschema/oscal_metadata_metaschema.xml +++ b/src/metaschema/oscal_metadata_metaschema.xml @@ -156,7 +156,7 @@ A location, with associated metadata that can be referenced. Location Universally Unique Identifier - A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + A globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in an OSCAL instance. A UUID should be consistently used for a given location across revisions of the document. @@ -240,7 +240,7 @@ A responsible entity which is either a person or an organization. Party Universally Unique Identifier - A unique identifier that can be used to reference this defined location elsewhere in an OSCAL document. A UUID should be consistently used for a given party across revisions of the document. + A globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in an OSCAL instance. A UUID should be consistently used for a given party across revisions of the document. Party Type @@ -351,7 +351,7 @@ Role Identifier - A unique identifier for a specific role instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same role across minor revisions of the document. + A local unique identifier for a specific role instance. This identifier's uniqueness is instance scoped and is intended to be consistent for the same role across minor revisions of the document.

OSCAL has defined a set of standardized roles for consistent use in OSCAL documents. This allows tools consuming OSCAL content to infer specific semantics when these roles are used. These roles are documented in the specific contexts of their use (e.g., responsible-party, responsible-role). When using such a role, it is necessary to define these roles in this list, which will then allow such a role to be referenced.

 @@ -407,7 +407,7 @@ Resource Universally Unique Identifier - A globally unique identifier that can be used to reference this defined resource elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + A globally unique identifier with instance scope that can be used to reference this defined resource elsewhere in an OSCAL instance. A UUID should be consistently used for a given resource across revisions of the document. @@ -600,7 +600,7 @@ Property Universally Unique Identifier - A unique identifier that can be used to reference this property elsewhere in an OSCAL document. A UUID should be consistently used for a given location across revisions of the document. + A globally unique identifier with cross-instance scope that can be used to reference this property elsewhere in an OSCAL instance. A UUID should be consistently used for a given property across revisions of the document. From b1cbba638bf14deabc4e4fbc7cd671d751041447 Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Wed, 1 Sep 2021 20:48:49 -0400 Subject: [PATCH 04/34] updates to catalog identifier descriptions --- src/metaschema/oscal_catalog_metaschema.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/metaschema/oscal_catalog_metaschema.xml b/src/metaschema/oscal_catalog_metaschema.xml index dd7743ca85..174abea5d0 100644 --- a/src/metaschema/oscal_catalog_metaschema.xml +++ b/src/metaschema/oscal_catalog_metaschema.xml @@ -24,7 +24,7 @@ catalog Catalog Universally Unique Identifier - A globally unique identifier for this catalog instance. This UUID should be changed when this document is revised. + A globally unique identifier with cross-instance scope for this catalog instance. This UUID should be changed when this document is revised. @@ -65,7 +65,7 @@ Group Identifier - A unique identifier for a specific group instance that can be used to reference the group within this and in other OSCAL documents. This identifier's uniqueness is document scoped and is intended to be consistent for the same group across minor revisions of the document. + A local unique identifier for a specific group instance that can be used to reference the group within this and in other OSCAL instances. This identifier's uniqueness is instance scoped and is intended to be consistent for the same group across minor revisions of the document. Group Class @@ -130,7 +130,7 @@ Control Identifier - A unique identifier for a specific control instance that can be used to reference the control in other OSCAL documents. This identifier's uniqueness is document scoped and is intended to be consistent for the same control across minor revisions of the document. + A local unique identifier for a specific control instance that can be used to reference the control in other OSCAL instances. This identifier's uniqueness is instance scoped and is intended to be consistent for the same control across minor revisions of the document. Control Class From d0c5eb7f9d812613767e11af162e04fd90d2e08e Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Thu, 14 Oct 2021 13:16:54 -0400 Subject: [PATCH 05/34] metadata section updates --- src/metaschema/oscal_metadata_metaschema.xml | 112 ++++++++++++++++--- 1 file changed, 98 insertions(+), 14 deletions(-) diff --git a/src/metaschema/oscal_metadata_metaschema.xml b/src/metaschema/oscal_metadata_metaschema.xml index 8a070adca6..547832eab4 100644 --- a/src/metaschema/oscal_metadata_metaschema.xml +++ b/src/metaschema/oscal_metadata_metaschema.xml @@ -156,7 +156,15 @@ A location, with associated metadata that can be referenced. Location Universally Unique Identifier - A globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in an OSCAL instance. A UUID should be consistently used for a given location across revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this location in OSCAL catalogs, profiles, SSPs, APs, ARs, and POAMs

+

Consistency: per-subject

+ @@ -212,8 +220,14 @@ Location Reference - References a location defined in metadata. + + A machine-oriented identifier that references a location defined in the metadata section of this OSCAL instance. + + +

Type: machine-oriented

+

Source: instance - References a location a location defined in the metadata section of this OSCAL instance.

+ @@ -225,8 +239,14 @@ Location Reference - References a location defined in metadata. + + A machine-oriented identifier that references a location defined in the metadata section of this OSCAL instance. + + +

Type: machine-oriented

+

Source: instance - References a location a location defined in the metadata section of this OSCAL instance.

+ @@ -240,7 +260,15 @@ A responsible entity which is either a person or an organization. Party Universally Unique Identifier - A globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in an OSCAL instance. A UUID should be consistently used for a given party across revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this party in OSCAL catalogs, profiles, SSPs, APs, ARs, and POAMs

+

Consistency: per-subject

+ Party Type @@ -310,7 +338,14 @@ Organizational Affiliation - Identifies that the party object is a member of the organization associated with the provided UUID. + + A machine-oriented identifier that references another party (person or organization) that this subject is associated with. + + + +

Type: machine-oriented

+

Source: instance - References a party defined in the metadata section of this OSCAL instance.

+ @@ -335,8 +370,14 @@ Party Reference - References a party defined in metadata. + + A machine-oriented identifier that references another party defined in metadata. + + +

Type: machine-oriented

+

Source: instance - References a party defined in the metadata section of this OSCAL instance.

+ @@ -350,10 +391,15 @@ Defines a function assumed or expected to be assumed by a party in a specific situation. - Role Identifier - A local unique identifier for a specific role instance. This identifier's uniqueness is instance scoped and is intended to be consistent for the same role across minor revisions of the document. + + A human-oriented, locally-unique identifier with instance scope that can be used to reference this defined role elsewhere in this 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.

OSCAL has defined a set of standardized roles for consistent use in OSCAL documents. This allows tools consuming OSCAL content to infer specific semantics when these roles are used. These roles are documented in the specific contexts of their use (e.g., responsible-party, responsible-role). When using such a role, it is necessary to define these roles in this list, which will then allow such a role to be referenced.

+ +

Type: human-oriented

+

Uniqueness: locally-unique

+

Scope: instance - Provides an identifier that can be used to refer to this role in the same OSCAL instance.

+

Consistency: per-subject

 @@ -385,7 +431,12 @@ Role Identifier Reference - A reference to the roles served by the user. + + A human-oriented identifier reference to roles served by the user. + +

Type: human-oriented

+

Source: instance - References a role identifer defined in the metadata section of this OSCAL instance

+ @@ -407,7 +458,15 @@ Resource Universally Unique Identifier - A globally unique identifier with instance scope that can be used to reference this defined resource elsewhere in an OSCAL instance. A UUID should be consistently used for a given resource across revisions of the document. + + A machine-oriented, globally unique identifier with instance scope that can be used to reference this defined resource elsewhere in this 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. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: instance - provides an identifier that can be used to refer to this resource in the same OSCAL instance

+

Consistency: per-subject

+ @@ -600,7 +659,15 @@ Property Universally Unique Identifier - A globally unique identifier with cross-instance scope that can be used to reference this property elsewhere in an OSCAL instance. A UUID should be consistently used for a given property across revisions of the document. + + A machine-oriented, globally unique identifier with instance scope that can be used to reference this defined property elsewhere in this 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. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: instance - provides an identifier that can be used to refer to this property in the same OSCAL instance

+

Consistency: per-subject

+ @@ -704,7 +771,12 @@ A reference to a set of organizations or persons that have responsibility for performing a referenced role in the context of the containing object. Responsible Role - The role that the party is responsible for. + + A human-oriented identifier reference to roles served by the user. + +

Type: human-oriented

+

Source: instance - References a role identifer defined in the metadata section of this OSCAL instance

+ @@ -736,7 +808,12 @@ A reference to one or more roles with responsibility for performing a function relative to the containing object. Responsible Role ID - The role that is responsible for the business function. + + A human-oriented identifier reference to roles responsible for the business function. + +

Type: human-oriented

+

Source: instance - References a role identifer defined in the metadata section of this OSCAL instance

+ @@ -914,7 +991,8 @@ Document Identifier - A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + + A document identifier qualified by an identifier scheme. A document identifier provides a globally-unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. identifier @@ -929,6 +1007,12 @@

This element is optional, but it will always have a valid value, as if it is missing the value of "document-id" is assumed to be equal to the UUID of the root. This requirement allows for document creators to retroactively link an update to the original version, by providing a document-id on the new document that is equal to the uuid of the original document.

+ +

Type: human-oriented

+

Uniqueness: globally-unique

+

Scope: cross-instance - Provides an identifier that can be used to refer to this concept in OSCAL catalogs, profiles, APs, ARs, and POAMs.

+

Consistency: per-subject

+

Additional Information:

 From 7dc0c86baf085b0e2879d8efe4a3b19894213f1e Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Mon, 18 Oct 2021 21:12:36 -0400 Subject: [PATCH 06/34] common control metaschema updates --- .../oscal_control-common_metaschema.xml | 31 ++++++++++++++++--- 1 file changed, 26 insertions(+), 5 deletions(-) diff --git a/src/metaschema/oscal_control-common_metaschema.xml b/src/metaschema/oscal_control-common_metaschema.xml index dc03e9e7da..44dc20086f 100644 --- a/src/metaschema/oscal_control-common_metaschema.xml +++ b/src/metaschema/oscal_control-common_metaschema.xml @@ -20,9 +20,17 @@ Part A partition of a control's definition or a child of another part. - + Part Identifier - A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. + + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this and other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: human-oriented

+

Uniqueness: locally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this part in this or other OSCAL instances

+

Consistency: per-subject

+ Part Name @@ -120,9 +128,17 @@ param - + Parameter Identifier - A unique identifier for a specific parameter instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same parameter across minor revisions of the document. + + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: human-oriented

+

Uniqueness: locally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this part in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -264,6 +280,11 @@ Control Identifier Reference - A reference to a control with a corresponding id value. + + A human-oriented identifier reference to a control with a corresponding id value. + +

Type: human-oriented

+

Source: cross-instance - References a control identifer defined in this or another OSCAL instance

+ From f0814016932cd90d15ae487af45d750808b39e7d Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Tue, 19 Oct 2021 23:12:12 -0400 Subject: [PATCH 07/34] catalog and profile identifier description updates --- src/metaschema/oscal_catalog_metaschema.xml | 20 +++++++++++-- src/metaschema/oscal_profile_metaschema.xml | 31 +++++++++++++++++++-- 2 files changed, 46 insertions(+), 5 deletions(-) diff --git a/src/metaschema/oscal_catalog_metaschema.xml b/src/metaschema/oscal_catalog_metaschema.xml index 174abea5d0..9a7f2b3c56 100644 --- a/src/metaschema/oscal_catalog_metaschema.xml +++ b/src/metaschema/oscal_catalog_metaschema.xml @@ -65,7 +65,15 @@ Group Identifier - A local unique identifier for a specific group instance that can be used to reference the group within this and in other OSCAL instances. This identifier's uniqueness is instance scoped and is intended to be consistent for the same group across minor revisions of the document. + + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in this or other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. + + +

Type: human-oriented

+

Uniqueness: locally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this part in this or other OSCAL instances

+

Consistency: per-subject

+ Group Class @@ -130,7 +138,15 @@ Control Identifier - A local unique identifier for a specific control instance that can be used to reference the control in other OSCAL instances. This identifier's uniqueness is instance scoped and is intended to be consistent for the same control across minor revisions of the document. + + A human-oriented, locally unique identifier with instance scope that can be used to reference this control elsewhere in this and other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same control across revisions of the document. + + +

Type: human-oriented

+

Uniqueness: locally unique

+

Scope: instance - provides an identifier that can be used to refer to this control in this or other OSCAL instances

+

Consistency: per-subject

+ Control Class diff --git a/src/metaschema/oscal_profile_metaschema.xml b/src/metaschema/oscal_profile_metaschema.xml index 0701c611ab..5bba9efb48 100644 --- a/src/metaschema/oscal_profile_metaschema.xml +++ b/src/metaschema/oscal_profile_metaschema.xml @@ -22,8 +22,17 @@ Each OSCAL profile is defined by a Profile element profile - Catalog Universally Unique Identifier + Profile Universally Unique Identifier A globally unique identifier for this profile instance. This UUID should be changed when this document is revised. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this profile elsewhere in this and other OSCAL instances. This identifier should be assigned per-subject, which means it should be consistently used to identify the same profile across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this profile in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -145,7 +154,15 @@ Group Identifier - A unique identifier for a specific group instance that can be used to reference the group within this and in other OSCAL documents. This identifier's uniqueness is document scoped and is intended to be consistent for the same group across minor revisions of the document. + + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in this or other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. + + +

Type: human-oriented

+

Uniqueness: locally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this part in this or other OSCAL instances

+

Consistency: per-subject

+ Group Class @@ -196,7 +213,15 @@ Parameter ID - Indicates the value of the 'id' flag on a target parameter; i.e. which parameter to set + + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: human-oriented

+

Uniqueness: locally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this part in this or other OSCAL instances

+

Consistency: per-subject

+ Parameter Class From bb87db11a34c64e4ae64796f36ac175e5e4e582e Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Wed, 27 Oct 2021 14:22:31 -0400 Subject: [PATCH 08/34] implementation layer metaschema updates --- src/metaschema/oscal_component_metaschema.xml | 68 +++++++- ...oscal_implementation-common_metaschema.xml | 76 ++++++++- src/metaschema/oscal_profile_metaschema.xml | 1 - src/metaschema/oscal_ssp_metaschema.xml | 154 ++++++++++++++++-- 4 files changed, 265 insertions(+), 34 deletions(-) diff --git a/src/metaschema/oscal_component_metaschema.xml b/src/metaschema/oscal_component_metaschema.xml index 0fb1cbebb2..20ee0c9d5c 100644 --- a/src/metaschema/oscal_component_metaschema.xml +++ b/src/metaschema/oscal_component_metaschema.xml @@ -33,7 +33,15 @@ component-definition Component Definition Universally Unique Identifier - A globally unique identifier for this component definition instance. This UUID should be changed when this document is revised. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component definition elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this component definition in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -79,7 +87,15 @@ A defined component that can be part of an implemented system. Component Identifier - The unique identifier for the component. This identifier's uniqueness is document scoped and is intended to be consistent for the same component across minor revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this component in this or other OSCAL instances

+

Consistency: per-subject

+ type @@ -249,7 +265,15 @@ A grouping of other components and/or capabilities. Capability Identifier - A unique identifier for a capability. This identifier's uniqueness is document scoped and is intended to be consistent for the same capability across minor revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this capability elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this capability in this or other OSCAL instances

+

Consistency: per-subject

+ Capability Name @@ -289,7 +313,13 @@ TBD Component Reference - A reference to a component by its identifier + + A machine-oriented identifier reference to a component. + + +

Type: human-oriented

+

Source: cross-instance - References a component identifer defined in this or other OSCAL instances

+ @@ -304,7 +334,15 @@ Defines how the component or capability supports a set of controls. Control Implementation Set Identifier - A unique identifier for the set of implemented controls. This identifier's uniqueness is document scoped and is intended to be consistent for the same control implementation set across minor revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference a set of implemented controls elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to a seet of implemented controls in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -346,7 +384,15 @@ Describes how the containing component or capability implements an individual control. Control Implementation Identifier - A unique identifier for a specific control implementation. This identifier's uniqueness is document scoped and is intended to be consistent for the same control implementation across minor revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference a specific control implementation elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to a specific control implementation in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -402,7 +448,15 @@ Control Statement Reference Universally Unique Identifier - A globally unique identifier that can be used to reference this control statement entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this control statement in this or other OSCAL instances

+

Consistency: per-subject

+ diff --git a/src/metaschema/oscal_implementation-common_metaschema.xml b/src/metaschema/oscal_implementation-common_metaschema.xml index a1df3904bc..7477cecf28 100644 --- a/src/metaschema/oscal_implementation-common_metaschema.xml +++ b/src/metaschema/oscal_implementation-common_metaschema.xml @@ -30,7 +30,15 @@ A defined component that can be part of an implemented system. Component Identifier - The unique identifier for the component. This identifier's uniqueness is document scoped and is intended to be consistent for the same component across minor revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this component in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -249,7 +257,15 @@ Information about the protocol used to provide a service. Service Protocol Information Universally Unique Identifier - A globally unique identifier that can be used to reference this service protocol entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this service protocol information in this or other OSCAL instances

+

Consistency: per-subject

+ Protocol Name @@ -337,7 +353,15 @@ A type of user that interacts with the system based on an associated role. User Universally Unique Identifier - The unique identifier for the user class. This identifier's uniqueness is document scoped and is intended to be consistent for the same user universally unique idenfier across minor revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this user class in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -422,7 +446,15 @@ --> Inventory Item Universally Unique Identifier - A globally unique identifier that can be used to reference this inventory item entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this inventory item in this or other OSCAL instances

+

Consistency: per-subject

+ + A machine-oriented identifier reference to a component that is implemented as part of an inventory item. + + +

Type: human-oriented

+

Source: cross-instance - References a component identifer defined in this or other OSCAL instances

+ @@ -631,7 +669,13 @@ --> Control Statement Reference - A reference to a control statement by its identifier + + A human-oriented identifier reference to a control statement. + + +

Type: human-oriented

+

Source: instance - References a control state by its identifer as defined in this OSCAL instance

+ Set Parameter Value @@ -653,11 +697,19 @@ System Identification - A unique identifier for the system described by this system security plan. + + A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this and other OSCAL instances. This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. + + +

Type: human-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this system in this or other OSCAL instances

+

Consistency: per-subject

+ id Identification System Type - Identifies the identification system from which the provided identifier was assigned. This is a globally unique identifier and should be consistently used for a given system across revisions of the document. + Identifies the identification system from which the provided identifier was assigned. The identifier was assigned by FedRAMP. @@ -671,7 +723,13 @@ Parameter ID - A reference to a parameter within a control, who's catalog has been imported into the current implementation context. This identifier's uniqueness is document scoped and is intended to be consistent for the same param across minor revisions of the document. + + A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context. + + +

Type: human-oriented

+

Source: cross-instance - References a parameter defined within a control in this or other OSCAL instances

+ System ISSO diff --git a/src/metaschema/oscal_profile_metaschema.xml b/src/metaschema/oscal_profile_metaschema.xml index 5bba9efb48..c7617afc68 100644 --- a/src/metaschema/oscal_profile_metaschema.xml +++ b/src/metaschema/oscal_profile_metaschema.xml @@ -23,7 +23,6 @@ profile Profile Universally Unique Identifier - A globally unique identifier for this profile instance. This UUID should be changed when this document is revised. A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this profile elsewhere in this and other OSCAL instances. This identifier should be assigned per-subject, which means it should be consistently used to identify the same profile across revisions of the document. diff --git a/src/metaschema/oscal_ssp_metaschema.xml b/src/metaschema/oscal_ssp_metaschema.xml index 2025dd9a3e..60351bece7 100644 --- a/src/metaschema/oscal_ssp_metaschema.xml +++ b/src/metaschema/oscal_ssp_metaschema.xml @@ -34,7 +34,15 @@ system-security-plan System Security Plan Universally Unique Identifier - A globally unique identifier for this catalog instance. This UUID should be changed when this document is revised. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this system security plan (SSP) elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this SSP definition in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -190,7 +198,15 @@ Information Type Universally Unique Identifier - A globally unique identifier that can be used to reference this information type entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this information type elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this information type in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -220,9 +236,17 @@ Information Type Systematized Identifier - An identifier qualified by the given identification system used, such as NIST SP 800-60. + + A human-oriented, globally unique identifier qualified by the given identification system used, such as NIST SP 800-60. This identifier has cross-instance scope and can be used to reference this system elsewhere in this or other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. id + + +

Type: human-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this information system type in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -409,7 +433,15 @@ A graphic that provides a visual representation the system, or some aspect of it. Diagram ID - The identifier for this diagram. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this diagram elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: human-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this diagram in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -539,7 +571,15 @@ Leveraged Authorization Universally Unique Identifier - A globally unique identifier that can be used to reference this leveraged authorization entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope and can be used to reference this leveraged authorization elsewhere in this or other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: human-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this leveraged authorization in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -554,7 +594,13 @@ party-uuid field - A reference to the party that manages the leveraged system. + + A machine-oriented identifier reference to the party that manages the leveraged system. + + +

Type: human-oriented

+

Source: cross-instance - References a party identifer defined in this or other OSCAL instances

+ @@ -683,7 +729,15 @@ Describes how the system satisfies an individual control. Control Requirement Universally Unique Identifier - A globally unique identifier that can be used to reference this control requirement entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control requirement elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this control requirement in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -773,7 +827,15 @@ Control Statement Reference Universally Unique Identifier - A globally unique identifier that can be used to reference this control statement entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this control statement in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -815,11 +877,25 @@ Defines how the referenced component implements a set of controls. Component Universally Unique Identifier Reference - A reference to the component that is implementing a given control or control statement. A UUID should be consistantly used for a given resource across revisions of the document. + + A machine-oriented identifier reference to the component that is implemeting a given control. + + +

Type: human-oriented

+

Source: cross-instance - References a component identifer defined in this or other OSCAL instances

+ By-Component Universally Unique Identifier - A globally unique identifier that can be used to reference this by-component entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this by-component entry elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this by-component entry in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -862,7 +938,15 @@ Provided Universally Unique Identifier - A globally unique identifier that can be used to reference this provided entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this provided entry elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this provided entry in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -896,7 +980,15 @@ Responsibility Universally Unique Identifier - A globally unique identifier that can be used to reference this responsibility entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this responsibility elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this responsibility in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -947,7 +1039,15 @@ Inherited Universally Unique Identifier - A globally unique identifier that can be used to reference this inherited entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inherited entry elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this inherited entry in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -982,7 +1082,15 @@ Satisfied Universally Unique Identifier - A globally unique identifier that can be used to reference this satisfied entry elsewhere in an OSCAL document. A UUID should be consistently used for a given resource across revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this satisfied entry elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this satisfied entry in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -1033,11 +1141,23 @@ Provided UUID - Identifies a 'provided' assembly associated with this assembly. + + A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system. + + +

Type: human-oriented

+

Source: cross-instance - References a provided control implementation in this or other OSCAL instances

+ - Provided UUID - Identifies a 'provided' assembly associated with this assembly. + Responsibility UUID + + A machine-oriented identifier reference to a control implementation that satisfies a responsibility imposed by a leveraged system. + + +

Type: human-oriented

+

Source: cross-instance - References a satisfied control implementation in this or other OSCAL instances

+ From b86418fa8366e1ed8d1011a979e7afc85f63bd87 Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Thu, 28 Oct 2021 14:34:36 -0400 Subject: [PATCH 09/34] assessment layers updates --- .../oscal_assessment-common_metaschema.xml | 246 ++++++++++++++++-- .../oscal_assessment-plan_metaschema.xml | 10 +- .../oscal_assessment-results_metaschema.xml | 64 ++++- src/metaschema/oscal_poam_metaschema.xml | 36 ++- src/metaschema/oscal_ssp_metaschema.xml | 6 +- 5 files changed, 320 insertions(+), 42 deletions(-) diff --git a/src/metaschema/oscal_assessment-common_metaschema.xml b/src/metaschema/oscal_assessment-common_metaschema.xml index 4b8652295e..c0465327ac 100644 --- a/src/metaschema/oscal_assessment-common_metaschema.xml +++ b/src/metaschema/oscal_assessment-common_metaschema.xml @@ -77,7 +77,15 @@ A local definition of a control objective. Uses catalog syntax for control objective and assessment activities. Assessment Method Universally Unique Identifier - Uniquely identifies this defined assessment method. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given assessment method across revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment method elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this assessment method in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -103,7 +111,15 @@ Identifies an assessment or related process that can be performed. In the assessment plan, this is an intended activity which may be associated with an assessment task. In the assessment results, this an activity that was actually performed as part of an assessment. Assessment Activity Universally Unique Identifier - Uniquely identifies this assessment activity. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given included activity across revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment activity elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this assessment activity in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -126,7 +142,15 @@ Step Universally Unique Identifier - Uniquely identifies a step. This UUID may be referenced elsewhere in an OSCAL document when referring to this step. A UUID should be consistently used for a given test step across revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this step elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this step in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -204,7 +228,15 @@ Represents a scheduled event or milestone, which may be associated with a series of assessment actions. Task Universally Unique Identifier - Uniquely identifies this assessment task. This identifier's uniqueness is document scoped and is intended to be consistent for the same task across minor revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this task elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this task in this or other OSCAL instances

+

Consistency: per-subject

+ Task Type @@ -288,7 +320,13 @@ Task Universally Unique Identifier Reference - References a unique task by UUID. + + A machine-oriented identifier reference to a unique task. + + +

Type: machine-oriented

+

Source: cross-instance - References a unique task defined in this or other OSCAL instances

+ @@ -304,7 +342,13 @@ Activity Universally Unique Identifier Reference - References an activity defined in the list of activities. + + A machine-oriented identifier reference to an activity defined in the list of activities. + + +

Type: machine-oriented

+

Source: cross-instance - References an activity (in a list of actifites) defined in this or other OSCAL instances

+ @@ -495,7 +539,15 @@ Used when the assessment subjects will be determined as part of one or more other assessment activities. These assessment subjects will be recorded in the assessment results in the assessment log. Assessment Subject Placeholder Universally Unique Identifier - Uniquely identifies a set of assessment subjects that will be identified by a task or an activity that is part of a task. This identifier's uniqueness is document scoped and is intended to be consistent for the same assessment subject across minor revisions of the document. + + A machine-oriented, globally unique identifier for a set of assessment subjects that will be identified by a task or an activity that is part of a task. This identifier has cross-instance scope, thus it can be used to reference this assessment subject elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: human-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this set of assessment subjects in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -508,7 +560,15 @@ Task Universally Unique Identifier - Uniquely identifies an assessment activity to be performed as part of the event. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference (in this or other OSCAL instances) an assessment activity to be performed as part of the event. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this assessment activity in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -589,7 +649,13 @@ Subject Universally Unique Identifier Reference - A pointer to a component, inventory-item, location, party, user, or resource using it's UUID. + + A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. + + +

Type: machine-oriented

+

Source: cross-instance - References a component, inventory-item, location, party, user, or resource identifer defined in this or other OSCAL instances

+ @@ -609,7 +675,13 @@ Identifies the Subject - A pointer to a resource based on its universally unique identifier (UUID). Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. + + A human-oriented identifier reference to a resource. Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. + + +

Type: human-oriented

+

Source: cross-instance - References a resource

+ type @@ -653,7 +725,15 @@ Assessment Platform Universally Unique Identifier - Uniquely identifies this assessment Platform. This UUID may be referenced elsewhere in an OSCAL document when refering to this information. Once assigned, a UUID should be consistantly used for a given observation across revisions. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment platform elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this assessment platform in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -672,7 +752,13 @@ Component Universally Unique Identifier Reference - A reference to a component that is implemented as part of an inventory item. + + A machine-oriented identifier reference to a component that is implemented as part of an inventory item. + + +

Type: machine-oriented

+

Source: cross-instance - References a component, in this or other OSCAL instances, that is implemented as part of an inventory item

+ @@ -728,7 +814,13 @@ Finding Target Identifier Reference - Identifies the specific target qualified by the type. + + A machine-oriented identifier reference for a specific target qualified by the type. + + +

Type: human-oriented

+

Source: cross-instance - References a finding target

+ @@ -790,7 +882,15 @@ Describes an individual observation. Observation Universally Unique Identifier - Uniquely identifies this observation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given observation across revisions. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this observation in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -930,7 +1030,13 @@ Actor Universally Unique Identifier Reference - A pointer to the tool or person based on the associated type. + + A machine-oriented identifier reference to the tool or person based on the associated type. + + +

Type: machine-oriented

+

Source: cross-instance - References a tool or person defined in this or other OSCAL instances

+ Actor Role @@ -951,7 +1057,13 @@ Identifies an individual task for which the containing object is a consequence of. Task Universally Unique Identifier Reference - References a unique task by UUID. + + A machine-oriented identifier reference to a unique task. + + +

Type: machine-oriented

+

Source: cross-instance - References a unique task defined in this or other OSCAL instances

+ @@ -979,7 +1091,13 @@ Assessment Subject Placeholder Universally Unique Identifier Reference - References a unique assessment subject placeholder defined by this task. + + A machine-oriented identifier reference to a unique assessment subject placeholder defined by this task. + + +

Type: machine-oriented

+

Source: cross-instance - References a unique assessment subject placeholder defined in this or other OSCAL instances

+ @@ -1028,7 +1146,15 @@ An identified risk. Risk Universally Unique Identifier - Uniquely identifies this risk. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given risk across revisions. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this risk in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -1085,11 +1211,27 @@ Mitigating Factor Universally Unique Identifier - Uniquely identifies this mitigating factor. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given mitigating factor across revisions. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mitigating factor elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this mitigating factor in this or other OSCAL instances

+

Consistency: per-subject

+ Implementation UUID - Points to an implementation statement in the SSP. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this implementation statement elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this implementation statement in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -1130,7 +1272,15 @@ Risk Log Entry Universally Unique Identifier - Uniquely identifies a risk log entry. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk log entry elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this risk log entry in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -1170,7 +1320,13 @@ Response Universally Unique Identifier Reference - References a unique risk response by UUID. + + A machine-oriented identifier reference to a unique risk response. + + +

Type: machine-oriented

+

Source: cross-instance - References a unique risk response defined in this or other OSCAL instances

+ @@ -1218,7 +1374,13 @@ Observation Universally Unique Identifier Reference - References an observation defined in the list of observations. + + A machine-oriented identifier reference to an observation defined in the list of observations. + + +

Type: machine-oriented

+

Source: cross-instance - References an observation defined in this or other OSCAL instances

+ @@ -1238,7 +1400,13 @@ Used to indicate who created a log entry in what role. Party UUID Reference - A pointer to the party who is making the log entry. + + A machine-oriented identifier reference to the party who is making the log entry. + + +

Type: machine-oriented

+

Source: cross-instance - References a party defined in this or other OSCAL instances

+ Actor Role @@ -1519,7 +1687,15 @@ Describes either recommended or an actual plan for addressing the risk. Remediation Universally Unique Identifier - Uniquely identifies this remediation. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given remediation across revisions. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this remediation elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this remediation in this or other OSCAL instances

+

Consistency: per-subject

+ Remediation Intent @@ -1561,7 +1737,15 @@ Required Universally Unique Identifier - Uniquely identifies this required asset. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given required asset across revisions. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this required asset elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this required asset in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -1623,7 +1807,15 @@ Part Identifier - A unique identifier for a specific part instance. This identifier's uniqueness is document scoped and is intended to be consistent for the same part across minor revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this part elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this part in this or other OSCAL instances

+

Consistency: per-subject

+ Part Name diff --git a/src/metaschema/oscal_assessment-plan_metaschema.xml b/src/metaschema/oscal_assessment-plan_metaschema.xml index 0bb788c77f..c0c9c5174f 100644 --- a/src/metaschema/oscal_assessment-plan_metaschema.xml +++ b/src/metaschema/oscal_assessment-plan_metaschema.xml @@ -20,7 +20,15 @@ assessment-plan Assessment Plan Universally Unique Identifier - Uniquely identifies this assessment plan. This identifier's uniqueness is document scoped and must be changed each time the content of the plan changes. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment plan in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this assessment plan in this or other OSCAL instances

+

Consistency: per-subject

+ diff --git a/src/metaschema/oscal_assessment-results_metaschema.xml b/src/metaschema/oscal_assessment-results_metaschema.xml index ebb24f1b5c..102c918c0e 100644 --- a/src/metaschema/oscal_assessment-results_metaschema.xml +++ b/src/metaschema/oscal_assessment-results_metaschema.xml @@ -22,7 +22,15 @@ assessment-results Assessment Results Universally Unique Identifier - Uniquely identifies this assessment results file. This UUID must be changed each time the content of the results changes. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment results instance in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this assessment results in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -74,7 +82,15 @@ Used by the assessment results and POA&M. In the assessment results, this identifies all of the assessment observations and findings, initial and residual risks, deviations, and disposition. In the POA&M, this identifies initial and residual risks, deviations, and disposition. Results Universally Unique Identifier - Uniquely identifies this set of results. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given set of results across revisions. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this set of results in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this set of results in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -199,7 +215,15 @@ Assessment Log Entry Universally Unique Identifier - Uniquely identifies an assessment event. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for this schedule across revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference an assessment event in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this assessment event in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -259,7 +283,15 @@ Describes an individual finding. Finding Universally Unique Identifier - Uniquely identifies this finding. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. Once assigned, a UUID should be consistently used for a given finding across revisions. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this finding in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this finding in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -290,7 +322,13 @@ Implementation Statement UUID - Identifies the implementation statement in the SSP to which this finding is related. + + A machine-oriented identifier reference to the implementation statement in the SSP to which this finding is related. + + +

Type: machine-oriented

+

Source: cross-instance - References the implementation statement in this or other OSCAL instances.

+ @@ -299,7 +337,13 @@ Observation Universally Unique Identifier Reference - References an observation defined in the list of observations. + + A machine-oriented identifier reference to an observation defined in the list of observations. + + +

Type: machine-oriented

+

Source: cross-instance - References the implementation an observation in this or other OSCAL instances

+ @@ -309,7 +353,13 @@ Risk Universally Unique Identifier Reference - References an risk defined in the list of risks. + + A machine-oriented identifier reference to a risk defined in the list of risks. + + +

Type: machine-oriented

+

Source: cross-instance - References the a risk in this or other OSCAL instances

+ diff --git a/src/metaschema/oscal_poam_metaschema.xml b/src/metaschema/oscal_poam_metaschema.xml index e7dcd54218..0f7c0c3a43 100644 --- a/src/metaschema/oscal_poam_metaschema.xml +++ b/src/metaschema/oscal_poam_metaschema.xml @@ -23,7 +23,15 @@ plan-of-action-and-milestones POA&M Universally Unique Identifier - Uniquely identifies this POA&M. This UUID may be referenced elsewhere in an OSCAL document when refering to this information. This UUID must be changed each time the content of the POA&M changes. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this POA&M instance in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this POA&M instance in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -88,7 +96,15 @@ Describes an individual POA&M item. POA&M Item Universally Unique Identifier - Uniquely identifies the POA&M entry. This UUID may be referenced elsewhere in an OSCAL document when referring to this information. A UUID should be consistently used for a given POA&M item across revisions of the document. + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this POA&M item entry in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this POA&M item entry in this or other OSCAL instances

+

Consistency: per-subject

+ @@ -132,7 +148,13 @@ Observation Universally Unique Identifier Reference - References an observation defined in the list of observations. + + A machine-oriented identifier reference to an observation defined in the list of observations. + + +

Type: machine-oriented

+

Source: cross-instance - References the implementation an observation in this or other OSCAL instances

+ @@ -143,7 +165,13 @@ Risk Universally Unique Identifier Reference - References an risk defined in the list of risks. + + A machine-oriented identifier reference to a risk defined in the list of risks. + + +

Type: machine-oriented

+

Source: cross-instance - References the a risk in this or other OSCAL instances

+ diff --git a/src/metaschema/oscal_ssp_metaschema.xml b/src/metaschema/oscal_ssp_metaschema.xml index 60351bece7..dcd91c3af7 100644 --- a/src/metaschema/oscal_ssp_metaschema.xml +++ b/src/metaschema/oscal_ssp_metaschema.xml @@ -881,7 +881,7 @@ A machine-oriented identifier reference to the component that is implemeting a given control. -

Type: human-oriented

+

Type: machine-oriented

Source: cross-instance - References a component identifer defined in this or other OSCAL instances

 @@ -1145,7 +1145,7 @@ A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system. -

Type: human-oriented

+

Type: machine-oriented

Source: cross-instance - References a provided control implementation in this or other OSCAL instances

 @@ -1156,7 +1156,7 @@ A machine-oriented identifier reference to a control implementation that satisfies a responsibility imposed by a leveraged system. -

Type: human-oriented

+

Type: machine-oriented

Source: cross-instance - References a satisfied control implementation in this or other OSCAL instances

 From 7da1c66f1140480460cb3c368f02c7f4bbacbd0b Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Tue, 30 Nov 2021 19:35:05 -0500 Subject: [PATCH 10/34] revised identifier descriptions --- .../oscal_assessment-common_metaschema.xml | 136 +++--------------- .../oscal_assessment-plan_metaschema.xml | 20 +-- .../oscal_assessment-results_metaschema.xml | 36 +---- src/metaschema/oscal_catalog_metaschema.xml | 2 +- src/metaschema/oscal_component_metaschema.xml | 56 +------- .../oscal_control-common_metaschema.xml | 24 +--- ...oscal_implementation-common_metaschema.xml | 45 +----- src/metaschema/oscal_metadata_metaschema.xml | 79 ++-------- src/metaschema/oscal_poam_metaschema.xml | 14 -- src/metaschema/oscal_profile_metaschema.xml | 27 +--- src/metaschema/oscal_ssp_metaschema.xml | 108 ++------------ 11 files changed, 73 insertions(+), 474 deletions(-) diff --git a/src/metaschema/oscal_assessment-common_metaschema.xml b/src/metaschema/oscal_assessment-common_metaschema.xml index c0465327ac..b67a8b7261 100644 --- a/src/metaschema/oscal_assessment-common_metaschema.xml +++ b/src/metaschema/oscal_assessment-common_metaschema.xml @@ -78,14 +78,7 @@ Assessment Method Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment method elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this assessment method in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment method elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment method can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -112,14 +105,7 @@ Assessment Activity Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment activity elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this assessment activity in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment activity elsewhere in this or other OSCAL instances. The locally defined UUID of the activity can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -143,14 +129,7 @@ Step Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this step elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this step in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this step elsewhere in this or other OSCAL instances. The locally defined UUID of the step (in a series of steps) can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -229,14 +208,7 @@ Task Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this task elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this task in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this task elsewhere in this or other OSCAL instances. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. Task Type @@ -394,6 +366,7 @@

Identifies the person or organization responsible for performing a specific role related to the task.

+ @@ -540,14 +513,7 @@ Assessment Subject Placeholder Universally Unique Identifier - A machine-oriented, globally unique identifier for a set of assessment subjects that will be identified by a task or an activity that is part of a task. This identifier has cross-instance scope, thus it can be used to reference this assessment subject elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: human-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this set of assessment subjects in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier for a set of assessment subjects that will be identified by a task or an activity that is part of a task. The locally defined UUID of the assessment subject placeholder can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -561,14 +527,7 @@ Task Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference (in this or other OSCAL instances) an assessment activity to be performed as part of the event. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this assessment activity in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference (in this or other OSCAL instances) an assessment activity to be performed as part of the event. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -726,14 +685,7 @@ Assessment Platform Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment platform elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this assessment platform in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment platform elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment platform can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -883,14 +835,7 @@ Observation Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this observation in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. The locally defined UUID of the observation can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -1147,14 +1092,7 @@ Risk Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this risk in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk elsewhere in this or other OSCAL instances. The locally defined UUID of the risk can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -1212,26 +1150,12 @@ Mitigating Factor Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mitigating factor elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this mitigating factor in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mitigating factor elsewhere in this or other OSCAL instances. The locally defined UUID of the mitigating factor can be used to reference the data item locally or globally (e.g., in an imported 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. Implementation UUID - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this implementation statement elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this implementation statement in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this implementation statement elsewhere in this or other OSCAL instances. The locally defined UUID of the implementation statement can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -1273,14 +1197,7 @@ Risk Log Entry Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk log entry elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this risk log entry in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk log entry elsewhere in this or other OSCAL instances. The locally defined UUID of the risk log entry can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -1688,14 +1605,7 @@ Remediation Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this remediation elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this remediation in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this remediation elsewhere in this or other OSCAL instances. The locally defined UUID of the risk response can be used to reference the data item locally or globally (e.g., in an imported 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. Remediation Intent @@ -1738,14 +1648,7 @@ Required Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this required asset elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this required asset in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this required asset elsewhere in this or other OSCAL instances. The locally defined UUID of the asset can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -1808,14 +1711,7 @@ Part Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this part elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this part in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this part elsewhere in this or other OSCAL instances. The locally defined UUID of the part can be used to reference the data item locally or globally (e.g., in an imported 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. Part Name diff --git a/src/metaschema/oscal_assessment-plan_metaschema.xml b/src/metaschema/oscal_assessment-plan_metaschema.xml index c0c9c5174f..95fa85c89d 100644 --- a/src/metaschema/oscal_assessment-plan_metaschema.xml +++ b/src/metaschema/oscal_assessment-plan_metaschema.xml @@ -21,14 +21,7 @@ Assessment Plan Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment plan in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this assessment plan in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment plan in this or other OSCAL instances. The locally defined UUID of the assessment plan can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -126,6 +119,17 @@ + + diff --git a/src/metaschema/oscal_assessment-results_metaschema.xml b/src/metaschema/oscal_assessment-results_metaschema.xml index 102c918c0e..3e3be75bb1 100644 --- a/src/metaschema/oscal_assessment-results_metaschema.xml +++ b/src/metaschema/oscal_assessment-results_metaschema.xml @@ -23,14 +23,7 @@ Assessment Results Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment results instance in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this assessment results in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment results instance in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -83,14 +76,7 @@ Results Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this set of results in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this set of results in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this set of results in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -216,14 +202,7 @@ Assessment Log Entry Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference an assessment event in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this assessment event in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference an assessment event in this or other OSCAL instances. The locally defined UUID of the assessment log entry can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -284,14 +263,7 @@ Finding Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this finding in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this finding in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this finding in this or other OSCAL instances. The locally defined UUID of the finding can be used to reference the data item locally or globally (e.g., in an imported 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. diff --git a/src/metaschema/oscal_catalog_metaschema.xml b/src/metaschema/oscal_catalog_metaschema.xml index 9a7f2b3c56..4318a72c08 100644 --- a/src/metaschema/oscal_catalog_metaschema.xml +++ b/src/metaschema/oscal_catalog_metaschema.xml @@ -66,7 +66,7 @@ Group Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in this or other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document.

Type: human-oriented

diff --git a/src/metaschema/oscal_component_metaschema.xml b/src/metaschema/oscal_component_metaschema.xml index 20ee0c9d5c..41f53bc099 100644 --- a/src/metaschema/oscal_component_metaschema.xml +++ b/src/metaschema/oscal_component_metaschema.xml @@ -34,14 +34,7 @@ Component Definition Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component definition elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this component definition in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component definition elsewhere in this or other OSCAL instances. The locally defined UUID of the component definition can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -88,14 +81,7 @@ Component Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this component in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. type @@ -266,14 +252,7 @@ Capability Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this capability elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this capability in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this capability elsewhere in this or other OSCAL instances. The locally defined UUID of the capability can be used to reference the data item locally or globally (e.g., in an imported 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. Capability Name @@ -335,14 +314,7 @@ Control Implementation Set Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference a set of implemented controls elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to a seet of implemented controls in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference a set of implemented controls elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation set can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -385,14 +357,7 @@ Control Implementation Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference a specific control implementation elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to a specific control implementation in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference a specific control implementation elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -448,15 +413,8 @@ Control Statement Reference Universally Unique Identifier - - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this control statement in this or other OSCAL instances

-

Consistency: per-subject

- + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. The UUID of the control statement in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance). diff --git a/src/metaschema/oscal_control-common_metaschema.xml b/src/metaschema/oscal_control-common_metaschema.xml index 44dc20086f..a4ddb9de25 100644 --- a/src/metaschema/oscal_control-common_metaschema.xml +++ b/src/metaschema/oscal_control-common_metaschema.xml @@ -23,14 +23,7 @@ Part Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this and other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: human-oriented

-

Uniqueness: locally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this part in this or other OSCAL instances

-

Consistency: per-subject

- + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this and other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. Part Name @@ -131,14 +124,7 @@ Parameter Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: human-oriented

-

Uniqueness: locally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this part in this or other OSCAL instances

-

Consistency: per-subject

- + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -281,10 +267,6 @@ Control Identifier Reference - A human-oriented identifier reference to a control with a corresponding id value. - -

Type: human-oriented

-

Source: cross-instance - References a control identifer defined in this or another OSCAL instance

- + A human-oriented identifier reference to a control with a corresponding 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). diff --git a/src/metaschema/oscal_implementation-common_metaschema.xml b/src/metaschema/oscal_implementation-common_metaschema.xml index 7477cecf28..0b4e515145 100644 --- a/src/metaschema/oscal_implementation-common_metaschema.xml +++ b/src/metaschema/oscal_implementation-common_metaschema.xml @@ -31,14 +31,7 @@ Component Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this component in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -258,14 +251,7 @@ Service Protocol Information Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this service protocol information in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported 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. Protocol Name @@ -354,14 +340,7 @@ User Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this user class in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -447,14 +426,7 @@ Inventory Item Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this inventory item in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported 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. System Identification - A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this and other OSCAL instances. This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. - - -

Type: human-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this system in this or other OSCAL instances

-

Consistency: per-subject

- + A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this and other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. id Identification System Type diff --git a/src/metaschema/oscal_metadata_metaschema.xml b/src/metaschema/oscal_metadata_metaschema.xml index 547832eab4..cd96f2a028 100644 --- a/src/metaschema/oscal_metadata_metaschema.xml +++ b/src/metaschema/oscal_metadata_metaschema.xml @@ -157,14 +157,7 @@ Location Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this location in OSCAL catalogs, profiles, SSPs, APs, ARs, and POAMs

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -221,13 +214,8 @@ Location Reference - A machine-oriented identifier that references a location defined in the metadata section of this OSCAL instance. + A machine-oriented identifier that references a 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). - - -

Type: machine-oriented

-

Source: instance - References a location a location defined in the metadata section of this OSCAL instance.

- @@ -240,13 +228,8 @@ Location Reference - A machine-oriented identifier that references a location defined in the metadata section of this OSCAL instance. + A machine-oriented identifier that references a 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). - - -

Type: machine-oriented

-

Source: instance - References a location a location defined in the metadata section of this OSCAL instance.

- @@ -261,14 +244,7 @@ Party Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this party in OSCAL catalogs, profiles, SSPs, APs, ARs, and POAMs

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the party can be used to reference the data item locally or globally (e.g., in an imported 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 Type @@ -339,13 +315,8 @@ Organizational Affiliation - A machine-oriented identifier that references another party (person or organization) that this subject is associated with. + A machine-oriented identifier that references another 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). - - -

Type: machine-oriented

-

Source: instance - References a party defined in the metadata section of this OSCAL instance.

- @@ -371,13 +342,8 @@ Party Reference - A machine-oriented identifier that references another party defined in metadata. + A machine-oriented identifier that references another 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). - - -

Type: machine-oriented

-

Source: instance - References a party defined in the metadata section of this OSCAL instance.

- @@ -392,14 +358,9 @@ - A human-oriented, locally-unique identifier with instance scope that can be used to reference this defined role elsewhere in this 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. + A human-oriented, locally-unique identifier with instance scope that can be used to reference this defined role elsewhere in this OSCAL instance. When referenced from another OSCAL instance, the locally defined ID of the Role from the imported OSCAL instance must be referenced in the context of the containing resource (e.g., import-profile). This ID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.

OSCAL has defined a set of standardized roles for consistent use in OSCAL documents. This allows tools consuming OSCAL content to infer specific semantics when these roles are used. These roles are documented in the specific contexts of their use (e.g., responsible-party, responsible-role). When using such a role, it is necessary to define these roles in this list, which will then allow such a role to be referenced.

- -

Type: human-oriented

-

Uniqueness: locally-unique

-

Scope: instance - Provides an identifier that can be used to refer to this role in the same OSCAL instance.

-

Consistency: per-subject

 @@ -459,14 +420,7 @@ Resource Universally Unique Identifier - A machine-oriented, globally unique identifier with instance scope that can be used to reference this defined resource elsewhere in this 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. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: instance - provides an identifier that can be used to refer to this resource in the same OSCAL instance

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with instance scope that can be used to reference this defined resource elsewhere in this OSCAL instance. The locally defined UUID of the resource can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -660,14 +614,7 @@ Property Universally Unique Identifier - A machine-oriented, globally unique identifier with instance scope that can be used to reference this defined property elsewhere in this 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. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: instance - provides an identifier that can be used to refer to this property in the same OSCAL instance

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with instance scope that can be used to reference this defined property elsewhere in this OSCAL instance. The locally defined UUID of the property can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -992,7 +939,7 @@ Document Identifier - A document identifier qualified by an identifier scheme. A document identifier provides a globally-unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + A document identifier qualified by an identifier scheme. A document identifier provides a globally-unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. The locally defined document-id can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. identifier @@ -1007,12 +954,6 @@

This element is optional, but it will always have a valid value, as if it is missing the value of "document-id" is assumed to be equal to the UUID of the root. This requirement allows for document creators to retroactively link an update to the original version, by providing a document-id on the new document that is equal to the uuid of the original document.

- -

Type: human-oriented

-

Uniqueness: globally-unique

-

Scope: cross-instance - Provides an identifier that can be used to refer to this concept in OSCAL catalogs, profiles, APs, ARs, and POAMs.

-

Consistency: per-subject

-

Additional Information:

 diff --git a/src/metaschema/oscal_poam_metaschema.xml b/src/metaschema/oscal_poam_metaschema.xml index 0f7c0c3a43..b36ec007fa 100644 --- a/src/metaschema/oscal_poam_metaschema.xml +++ b/src/metaschema/oscal_poam_metaschema.xml @@ -25,13 +25,6 @@ POA&M Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this POA&M instance in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this POA&M instance in this or other OSCAL instances

-

Consistency: per-subject

- @@ -98,13 +91,6 @@ POA&M Item Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this POA&M item entry in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this POA&M item entry in this or other OSCAL instances

-

Consistency: per-subject

- diff --git a/src/metaschema/oscal_profile_metaschema.xml b/src/metaschema/oscal_profile_metaschema.xml index c7617afc68..1d0d20bdab 100644 --- a/src/metaschema/oscal_profile_metaschema.xml +++ b/src/metaschema/oscal_profile_metaschema.xml @@ -24,14 +24,7 @@ Profile Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this profile elsewhere in this and other OSCAL instances. This identifier should be assigned per-subject, which means it should be consistently used to identify the same profile across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this profile in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this profile elsewhere in this and other OSCAL instances. The locally defined UUID of the profile can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance).This identifier should be assigned per-subject, which means it should be consistently used to identify the same profile across revisions of the document. @@ -154,14 +147,7 @@ Group Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in this or other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. - - -

Type: human-oriented

-

Uniqueness: locally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this part in this or other OSCAL instances

-

Consistency: per-subject

- + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. Group Class @@ -213,14 +199,7 @@ Parameter ID - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: human-oriented

-

Uniqueness: locally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this part in this or other OSCAL instances

-

Consistency: per-subject

- + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. Parameter Class diff --git a/src/metaschema/oscal_ssp_metaschema.xml b/src/metaschema/oscal_ssp_metaschema.xml index dcd91c3af7..fd99d1dc75 100644 --- a/src/metaschema/oscal_ssp_metaschema.xml +++ b/src/metaschema/oscal_ssp_metaschema.xml @@ -35,14 +35,7 @@ System Security Plan Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this system security plan (SSP) elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this SSP definition in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this system security plan (SSP) elsewhere in this or other OSCAL instances. The locally defined UUID of the SSP can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -199,14 +192,7 @@ Information Type Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this information type elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this information type in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this information type elsewhere in this or other OSCAL instances. The locally defined UUID of the information type can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -240,13 +226,6 @@ A human-oriented, globally unique identifier qualified by the given identification system used, such as NIST SP 800-60. This identifier has cross-instance scope and can be used to reference this system elsewhere in this or other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. id - - -

Type: human-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this information system type in this or other OSCAL instances

-

Consistency: per-subject

- @@ -434,14 +413,7 @@ Diagram ID - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this diagram elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: human-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this diagram in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this diagram elsewhere in this or other OSCAL instances. The locally defined UUID of the diagram can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -572,14 +544,7 @@ Leveraged Authorization Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope and can be used to reference this leveraged authorization elsewhere in this or other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: human-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this leveraged authorization in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope and can be used to reference this leveraged authorization elsewhere in this or other OSCAL instances. The locally defined UUID of the leveraged authorization can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -730,14 +695,7 @@ Control Requirement Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control requirement elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this control requirement in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control requirement elsewhere in this or other OSCAL instances. The locally defined UUID of the control requirement can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -827,15 +785,8 @@ Control Statement Reference Universally Unique Identifier - - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this control statement in this or other OSCAL instances

-

Consistency: per-subject

- + + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. The UUID of the control statement in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance). @@ -888,14 +839,7 @@ By-Component Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this by-component entry elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this by-component entry in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this by-component entry elsewhere in this or other OSCAL instances. The locally defined UUID of the by-component entry can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -939,14 +883,7 @@ Provided Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this provided entry elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this provided entry in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this provided entry elsewhere in this or other OSCAL instances. The locally defined UUID of the provided entry can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -981,14 +918,7 @@ Responsibility Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this responsibility elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this responsibility in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this responsibility elsewhere in this or other OSCAL instances. The locally defined UUID of the responsibility can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -1040,14 +970,7 @@ Inherited Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inherited entry elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this inherited entry in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inherited entry elsewhere in this or other OSCAL instances. The locally defined UUID of the inherited control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -1083,14 +1006,7 @@ Satisfied Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this satisfied entry elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this satisfied entry in this or other OSCAL instances

-

Consistency: per-subject

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this satisfied control implementation entry elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. From 1e25fc631b8ccb4dfe8b2da40efe94779041fbb6 Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Thu, 9 Dec 2021 08:51:15 -0500 Subject: [PATCH 11/34] added identifier use page --- docs/content/concepts/_index.md | 1 + .../content/concepts/identifier-use/_index.md | 204 ++++++++++++++++++ 2 files changed, 205 insertions(+) create mode 100644 docs/content/concepts/identifier-use/_index.md diff --git a/docs/content/concepts/_index.md b/docs/content/concepts/_index.md index 3facc70ace..7bd51ad0c7 100644 --- a/docs/content/concepts/_index.md +++ b/docs/content/concepts/_index.md @@ -18,6 +18,7 @@ This section of the OSCAL website presents: - Key [terminology](terminology/) used in OSCAL; - An overview of the OSCAL [layers and models](layer/), to include who and what processes they apply to; +- An oververview of [identifier use](identifier-use) in OSCAL models; - A [processing specification](processing/) for handling some types of OSCAL content; - Illustrative [examples](examples/) of how to represent control implementation and risk management data in OSCAL XML, JSON, and YAML formats; and - A discussion of how OSCAL [relates](relations-to-other/) to and draws inspiration from other documentary standards. diff --git a/docs/content/concepts/identifier-use/_index.md b/docs/content/concepts/identifier-use/_index.md new file mode 100644 index 0000000000..9b9259e77b --- /dev/null +++ b/docs/content/concepts/identifier-use/_index.md @@ -0,0 +1,204 @@ +--- +title: Identifier Use +description: Provides details on the scope an duniqueness of dientifiers used within the OSCAL models. +suppresstopiclist: true +weight: 50 +toc: + enabled: true +sidenav: + focusrenderdepth: 2 + activerenderdepth: 2 + inactiverenderdepth: 2 +--- + +This page reviews important concepts to be aware of when declaring or referencing identifiers in OSCAL models. + +### **Identifier Type** +By design, OSCAL supports [*machine-oriented*](/concepts/identifier-use/#machine-oriented) and [*human-oriented*](/concepts/identifier-use/#human-oriented) identifiers. The OSCAL models dictate which are used for different data items. + +#### Machine-Oriented + +*Machine-oriented* identifiers are implemented as Universally Unique Identifier (UUID) as defined by [RFC 4122](https://tools.ietf.org/html/rfc4122) and are commonly used to (programmatically) identify or refer to unique information within OSCAL models. Because OSCAL’s *`machine-oriented`* identifiers utilize UUID data types, they can be issued without a central authority, and used across OSCAL instances with low risk of identifier collisions. + +> **NOTE**: While UUIDs are used as machine-oriented identifiers catering to use cases where automated processing is desired, they are not ideal for wildcard matching scenarios. UUIDs should only be used when exact matches are expected. + + +The [OSCAL Reference Index](/reference/latest/complete/xml-index/#/@uuid) provides a complete listing of UUIDs in OSCAL. References to these identifiers typically follow a naming convention of the object type followed by “-uuid”. For example, see the reference index for [location-uuid](/reference/latest/complete/xml-index/#/location-uuid). + +#### Human-Oriented + +OSCAL generally implements *`human-oriented`* identifiers as Token data types, which are non-colonized names (add link to data type). These *`human-oriented`* identifiers have the benefit of allowing authors to incorporate semantics that support readability and processing by humans. For example, control identifiers in a catalog may use a nomenclature that is familiar to the intended audience, allowing them to quickly determine what security control is being referred to, simply by its ID. + +The [OSCAL Reference Index](/reference/latest/complete/xml-index/#/@id) provides a comprehensive listing of the *`human-oriented`* IDs in OSCAL. References to these IDs are typically named according to the referenced object type (e.g., control) followed by “-id”, as seen here in the [Reference Index](/reference/latest/complete/xml-index/#/@control-id). + +### **Uniqueness** +OSCAL identifier uniqueness are categorized as *`locally-unique`* or *`globally-unique`*. As implied by the category name, *`locally-unique`* identifiers must be unique within the current document whereas *`globally-unique`* identifiers are guaranteed to be unique across all other identifiers. OSCAL’s *`machine-oriented`* UUID identifiers are always *`globally-unique`*. *`Human-oriented`* identifiers must be defined and managed organizationally and are more susceptible to identifier duplication or collisions. Thus, *`human-oriented`* identifiers are less likely to be *`globally-unique`*. + +### **Scope** +Identifiers are declared so that data items in OSCAL instances can be referenced accurately and consistently. In the most basic instance, references are made to data items in the same OSCAL instance, but because OSCAL supports instance importing, there are scenarios where data items in an external / imported OSCAL instance need to be referenced as well. Identifiers that are only intended for use within the same OSCAL instance are categorized as *`instance`* scope, but identifiers that can be referenced (from other OSCAL instances) are considered *`cross-instance`* scoped. While *`human-oriented`* identifiers might not be globally unique, they may be *`cross-instance`* scoped. In these cases, the appropriate import attribute (e.g. import, import-component-definitions, import-profile, import-ssp, and import-ap) should be used (similar to a namespacing) to deconflict identifiers with the same values in the associated OSCAL instances. This would allow for the same control IDs to be used and referenced in a profile and its imported catalog(s) for example. The tables below provides a summary of OSCAL unique identifier scoping. + +#### **Catalog Identifiers** +Identifiers defined in a catalog may be referenced locally or from an importing profile. + +|**Defining Model**|**Identifier**|**Catalog**|**Profile**|**Component**|**SSP**|**AP**|**AR**|**POA&M**| +|:------|:-------|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:| +|Catalog|Location uuid|☑|☑|||||| +|Catalog|Party uuid|☑|☑|||||| +|Catalog|Role id|☑|☑|||||| +|Catalog|Resource uuid|☑|☑|||||| +|Catalog|Property uuid|☑|☑|||||| +|Catalog|Document Identifier scheme|☑|☑|||||| +|Catalog|Part id|☑|☑|||||| +|Catalog|Param id|☑|☑|||||| +|Catalog|Catalog uuid|☑|☑|||||| +|Catalog|Control id|☑|☑|||||| +|Catalog|Group id|☑|☑|||||| + +#### **Profile Identifiers** +Identifiers defined in a profile may be referenced locally or from an importing profile or SSP. + +|**Defining Model**|**Identifier**|**Catalog**|**Profile**|**Component**|**SSP**|**AP**|**AR**|**POA&M**| +|:------|:-------|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:| +|Profile|Location uuid||☑||☑|||| +|Profile|Party uuid||☑||☑|||| +|Profile|Role id||☑||☑|||| +|Profile|Resource uuid||☑||☑|||| +|Profile|Property uuid||☑||☑|||| +|Profile|Document Identifier scheme||☑||☑|||| +|Profile|Part id||☑||☑|||| +|Profile|Param id||☑||☑|||| +|Profile|Profile uuid||☑||☑|||| +|Profile|Group id||☑||☑|||| + +#### **Component Definition Identifiers** +Identifiers defined in a component definition may be referenced locally or from an importing component definition instance. + +|**Defining Model**|**Identifier**|**Catalog**|**Profile**|**Component**|**SSP**|**AP**|**AR**|**POA&M**| +|:------|:-------|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:| +|Component Definition|Location uuid|||☑||||| +|Component Definition|Party uuid|||☑||||| +|Component Definition|Role id|||☑||||| +|Component Definition|Resource uuid|||☑||||| +|Component Definition|Property uuid|||☑||||| +|Component Definition|Document Identifier scheme|||☑||||| +|Component Definition|Part id|||☑||||| +|Component Definition|Param id|||☑||||| +|Component Definition|Component Definition uuid|||☑||||| +|Component Definition|Component uuid|||☑||||| +|Component Definition|Capability uuid|||☑||||| +|Component Definition|Control Implementation Set uuid|||☑||||| +|Component Definition|Control Implementation uuid|||☑||||| + +#### **SSP Identifiers** +Identifiers defined in an SSP may be referenced locally or from an importing AP or POA&M. + +|**Defining Model**|**Identifier**|**Catalog**|**Profile**|**Component**|**SSP**|**AP**|**AR**|**POA&M**| +|:------|:-------|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:| +|SSP|Location uuid||||☑|☑||☑| +|SSP|Party uuid||||☑|☑||☑| +|SSP|Role id||||☑|☑||☑| +|SSP|Resource uuid||||☑|☑||☑| +|SSP|Property uuid||||☑|☑||☑| +|SSP|Document Identifier scheme||||☑|☑||☑| +|SSP|Part id||||☑|☑||☑| +|SSP|Param id||||☑|☑||☑| +|SSP|SSP uuid||||☑|☑||☑| +|SSP|Information Type uuid||||☑|☑||☑| +|SSP|Information Type Systematized id||||☑|☑||☑| +|SSP|Diagram uuid||||☑|☑||☑| +|SSP|Leveraged Authorization uuid||||☑|☑||☑| +|SSP|Control Requirement uuid||||☑|☑||☑| +|SSP|By-Component uuid||||☑|☑||☑| +|SSP|Provided uuid||||☑|☑||☑| +|SSP|Responsibility uuid||||☑|☑||☑| +|SSP|Inherited uuid||||☑|☑||☑| +|SSP|Satisfied uuid||||☑|☑||☑| + +#### **AP Identifiers** +Identifiers defined in an AP may be referenced locally or from an importing AR. + +|**Defining Model**|**Identifier**|**Catalog**|**Profile**|**Component**|**SSP**|**AP**|**AR**|**POA&M**| +|:------|:-------|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:| +|AP|Location uuid|||||☑|☑|| +|AP|Party uuid|||||☑|☑|| +|AP|Role id|||||☑|☑|| +|AP|Resource uuid|||||☑|☑|| +|AP|Property uuid|||||☑|☑|| +|AP|Document Identifier scheme|||||☑|☑|| +|AP|Assessment Method uuid|||||☑|☑|| +|AP|Assessment Activity uuid|||||☑|☑|| +|AP|Step uuid|||||☑|☑|| +|AP|Task uuid|||||☑|☑|| +|AP|Assessment Subject Placeholder uuid||||☑|☑|| +|AP|Assessment Platform uuid|||||☑|☑|| +|AP|Observation uuid|||||☑|☑|| +|AP|Risk uuid|||||☑|☑|| +|AP|Mitigating Factor uuid|||||☑|☑|| +|AP|Implementation uuid|||||☑|☑|| +|AP|Risk Log Entry uuid|||||☑|☑|| +|AP|Remediation uuid|||||☑|☑|| +|AP|Required Asset uuid|||||☑|☑|| +|AP|Part uuid|||||☑|☑|| +|AP|Assessment Plan uuid|||||☑|☑|| + +#### **AR Identifiers** +Identifiers defined in an AR may be referenced locally or from an importing POA&M. + +|**Defining Model**|**Identifier**|**Catalog**|**Profile**|**Component**|**SSP**|**AP**|**AR**|**POA&M**| +|:------|:-------|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:| +|AR|Location uuid||||||☑|☑| +|AR|Party uuid||||||☑|☑| +|AR|Role id||||||☑|☑| +|AR|Resource uuid||||||☑|☑| +|AR|Property uuid||||||☑|☑| +|AR|Document Identifier scheme||||||☑|☑| +|AR|Assessment Method uuid||||||☑|☑| +|AR|Assessment Activity uuid||||||☑|☑| +|AR|Step uuid||||||☑|☑| +|AR|Task uuid||||||☑|☑| +|AR|Assessment Subject Placeholder uuid|||||☑|☑| +|AR|Assessment Platform uuid||||||☑|☑| +|AR|Observation uuid||||||☑|☑| +|AR|Risk uuid||||||☑|☑| +|AR|Mitigating Factor uuid||||||☑|☑| +|AR|Implementation uuid||||||☑|☑| +|AR|Risk Log Entry uuid||||||☑|☑| +|AR|Remediation uuid||||||☑|☑| +|AR|Required Asset uuid||||||☑|☑| +|AR|Part uuid||||||☑|☑| +|AR|Assessment Results uuid||||||☑|☑| +|AR|Assessment Result uuid||||||☑|☑| +|AR|Assessment Log Entry uuid||||||☑|☑| +|AR|Finding uuid||||||☑|☑| + +#### **POA&M Identifiers** +Identifiers defined in a POA&M may be referenced locally. + +|**Defining Model**|**Identifier**|**Catalog**|**Profile**|**Component**|**SSP**|**AP**|**AR**|**POA&M**| +|:------|:-------|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:| +|POA&M|Location uuid|||||||☑| +|POA&M|Party uuid|||||||☑| +|POA&M|Role id|||||||☑| +|POA&M|Resource uuid|||||||☑| +|POA&M|Property uuid|||||||☑| +|POA&M|Document Identifier scheme|||||||☑| +|POA&M|Assessment Method uuid|||||||☑| +|POA&M|Assessment Activity uuid|||||||☑| +|POA&M|Step uuid|||||||☑| +|POA&M|Task uuid|||||||☑| +|POA&M|Assessment Subject Placeholder uuid||||||☑| +|POA&M|Assessment Platform uuid|||||||☑| +|POA&M|Observation uuid|||||||☑| +|POA&M|Risk uuid|||||||☑| +|POA&M|Mitigating Factor uuid|||||||☑| +|POA&M|Implementation uuid|||||||☑| +|POA&M|Risk Log Entry uuid|||||||☑| +|POA&M|Remediation uuid|||||||☑| +|POA&M|Required Asset uuid|||||||☑| +|POA&M|Part uuid|||||||☑| +|POA&M|POA&M uuid|||||||☑| +|POA&M|POA&M Item uuid|||||||☑| + +### **Consistency** +Indicates how the identifier (value) should be managed across revisions of the same document. In general, OSCAL identifiers have *`per-subject`* consistency, meaning that object identifiers (whether ID or UUIDs) should remain the same across minor of an OSCAL document IF the identifier refers to the same object (e.g., same location must have the same UUID or same control must have the same control ID as a document is revised). + From 5ddce63139722cc8a9c04dfaee4284362c672e7c Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Thu, 9 Dec 2021 10:08:59 -0500 Subject: [PATCH 12/34] minor edit on identifier use page --- docs/content/concepts/identifier-use/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/concepts/identifier-use/_index.md b/docs/content/concepts/identifier-use/_index.md index 9b9259e77b..522ee7119f 100644 --- a/docs/content/concepts/identifier-use/_index.md +++ b/docs/content/concepts/identifier-use/_index.md @@ -11,7 +11,7 @@ sidenav: inactiverenderdepth: 2 --- -This page reviews important concepts to be aware of when declaring or referencing identifiers in OSCAL models. +This page reviews important concepts to be aware of when declaring or referencing identifiers in OSCAL models, with in-depth explanations of identifier uniqueness and scope. ### **Identifier Type** By design, OSCAL supports [*machine-oriented*](/concepts/identifier-use/#machine-oriented) and [*human-oriented*](/concepts/identifier-use/#human-oriented) identifiers. The OSCAL models dictate which are used for different data items. From a2d7f81ad40f502a3e184fb523f74200fc388396 Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Thu, 9 Dec 2021 15:58:00 -0500 Subject: [PATCH 13/34] metaschema updates --- src/metaschema/oscal_catalog_metaschema.xml | 18 +------- .../oscal_control-common_metaschema.xml | 2 +- src/metaschema/oscal_metadata_metaschema.xml | 45 +++++++------------ src/metaschema/oscal_profile_metaschema.xml | 1 + 4 files changed, 21 insertions(+), 45 deletions(-) diff --git a/src/metaschema/oscal_catalog_metaschema.xml b/src/metaschema/oscal_catalog_metaschema.xml index 4318a72c08..969033abdc 100644 --- a/src/metaschema/oscal_catalog_metaschema.xml +++ b/src/metaschema/oscal_catalog_metaschema.xml @@ -66,14 +66,7 @@ Group Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. - - -

Type: human-oriented

-

Uniqueness: locally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this part in this or other OSCAL instances

-

Consistency: per-subject

- + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in this or other OSCAL instances (e.g., profiles). This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. Group Class @@ -139,14 +132,7 @@ Control Identifier - A human-oriented, locally unique identifier with instance scope that can be used to reference this control elsewhere in this and other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same control across revisions of the document. - - -

Type: human-oriented

-

Uniqueness: locally unique

-

Scope: instance - provides an identifier that can be used to refer to this control in this or other OSCAL instances

-

Consistency: per-subject

- + A human-oriented, locally unique identifier with instance scope that can be used to reference this control elsewhere in this and other OSCAL instances (e.g., profiles). This id should be assigned per-subject, which means it should be consistently used to identify the same control across revisions of the document. Control Class diff --git a/src/metaschema/oscal_control-common_metaschema.xml b/src/metaschema/oscal_control-common_metaschema.xml index a4ddb9de25..b8da1ffe4e 100644 --- a/src/metaschema/oscal_control-common_metaschema.xml +++ b/src/metaschema/oscal_control-common_metaschema.xml @@ -23,7 +23,7 @@ Part Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this and other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this and other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. Part Name diff --git a/src/metaschema/oscal_metadata_metaschema.xml b/src/metaschema/oscal_metadata_metaschema.xml index cd96f2a028..4d94e6783d 100644 --- a/src/metaschema/oscal_metadata_metaschema.xml +++ b/src/metaschema/oscal_metadata_metaschema.xml @@ -157,7 +157,7 @@ Location Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location can be used to reference the data item locally or globally (e.g., in an imported 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. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. @@ -214,7 +214,7 @@ Location Reference - A machine-oriented identifier that references a 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). + A machine-oriented identifier reference to a 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). @@ -228,7 +228,7 @@ Location Reference - A machine-oriented identifier that references a 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). + A machine-oriented identifier reference to a 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). @@ -244,7 +244,7 @@ Party Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the party can be used to reference the data item locally or globally (e.g., in an imported 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. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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 Type @@ -315,7 +315,7 @@ Organizational Affiliation - A machine-oriented identifier that references another 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). + A machine-oriented identifier reference to another 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). @@ -324,8 +324,8 @@ -

Parties of both the person or organization type can be associated with an organization using the member-of-organization. -

+

Parties of both the person or organization type can be associated with an organization using the member-of-organization.

+

See the [Concepts - Identifier Use](https://pages.nist.gov/OSCAL/concepts/identifier-use/#scope) page for additional information about the referenced identifier's scope.

 @@ -342,7 +342,7 @@ Party Reference - A machine-oriented identifier that references another 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). + A machine-oriented identifier reference to another 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). @@ -358,10 +358,8 @@ - A human-oriented, locally-unique identifier with instance scope that can be used to reference this defined role elsewhere in this OSCAL instance. When referenced from another OSCAL instance, the locally defined ID of the Role from the imported OSCAL instance must be referenced in the context of the containing resource (e.g., import-profile). This ID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - -

OSCAL has defined a set of standardized roles for consistent use in OSCAL documents. This allows tools consuming OSCAL content to infer specific semantics when these roles are used. These roles are documented in the specific contexts of their use (e.g., responsible-party, responsible-role). When using such a role, it is necessary to define these roles in this list, which will then allow such a role to be referenced.

- + A human-oriented, locally-unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this and other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. + @@ -387,17 +385,15 @@

Permissible values to be determined closer to the application (e.g. by a receiving authority).

- +

OSCAL has defined a set of standardized roles for consistent use in OSCAL documents. This allows tools consuming OSCAL content to infer specific semantics when these roles are used. These roles are documented in the specific contexts of their use (e.g., responsible-party, responsible-role). When using such a role, it is necessary to define these roles in this list, which will then allow such a role to be referenced.

+

See the [Concepts - Identifier Use](https://pages.nist.gov/OSCAL/concepts/identifier-use/#human-oriented) page for additional information regarding this identifier's uniqueness and scope.

+ Role Identifier Reference A human-oriented identifier reference to roles served by the user. - -

Type: human-oriented

-

Source: instance - References a role identifer defined in the metadata section of this OSCAL instance

- @@ -420,7 +416,7 @@ Resource Universally Unique Identifier - A machine-oriented, globally unique identifier with instance scope that can be used to reference this defined resource elsewhere in this OSCAL instance. The locally defined UUID of the resource can be used to reference the data item locally or globally (e.g., in an imported 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. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -614,7 +610,7 @@ Property Universally Unique Identifier - A machine-oriented, globally unique identifier with instance scope that can be used to reference this defined property elsewhere in this OSCAL instance. The locally defined UUID of the property can be used to reference the data item locally or globally (e.g., in an imported 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. + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this and other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -720,10 +716,6 @@ Responsible Role A human-oriented identifier reference to roles served by the user. - -

Type: human-oriented

-

Source: instance - References a role identifer defined in the metadata section of this OSCAL instance

- @@ -757,10 +749,6 @@ Responsible Role ID A human-oriented identifier reference to roles responsible for the business function. - -

Type: human-oriented

-

Source: instance - References a role identifer defined in the metadata section of this OSCAL instance

- @@ -939,7 +927,7 @@ Document Identifier - A document identifier qualified by an identifier scheme. A document identifier provides a globally-unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. The locally defined document-id can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + A document identifier qualified by an identifier scheme. A document identifier provides a globally-unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. identifier @@ -954,6 +942,7 @@

This element is optional, but it will always have a valid value, as if it is missing the value of "document-id" is assumed to be equal to the UUID of the root. This requirement allows for document creators to retroactively link an update to the original version, by providing a document-id on the new document that is equal to the uuid of the original document.

+

See the [Concepts - Identifier Use](https://pages.nist.gov/OSCAL/concepts/identifier-use/#human-oriented) page for additional information regarding this identifier's uniqueness and scope.

 diff --git a/src/metaschema/oscal_profile_metaschema.xml b/src/metaschema/oscal_profile_metaschema.xml index 1d0d20bdab..02abd1bb41 100644 --- a/src/metaschema/oscal_profile_metaschema.xml +++ b/src/metaschema/oscal_profile_metaschema.xml @@ -37,6 +37,7 @@

An OSCAL document that describes a tailoring of controls from one or more catalogs, with possible modification of multiple controls. It provides mechanisms by which controls may be selected (import), merged or (re)structured (merge), and amended (modify). OSCAL profiles may select subsets of controls, set parameter values for them in application, and even adjust the representation of controls as given in and by a catalog. They may also serve as sources for further modification in and by other profiles, that import them.

+

See the [Concepts - Identifier Use](https://pages.nist.gov/OSCAL/concepts/identifier-use/#machine-oriented) page for additional information regarding this identifier's uniqueness and scope.

 From 156fa24254fdda05ba82843c68c53e53dde5d8ee Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Thu, 6 Jan 2022 14:31:40 -0500 Subject: [PATCH 14/34] fixed component layer remark links --- src/metaschema/oscal_catalog_metaschema.xml | 6 ++++ .../oscal_control-common_metaschema.xml | 9 ++++++ src/metaschema/oscal_metadata_metaschema.xml | 32 ++++++++++++++++--- src/metaschema/oscal_profile_metaschema.xml | 11 ++++++- 4 files changed, 52 insertions(+), 6 deletions(-) diff --git a/src/metaschema/oscal_catalog_metaschema.xml b/src/metaschema/oscal_catalog_metaschema.xml index 969033abdc..8e4b4cbe9a 100644 --- a/src/metaschema/oscal_catalog_metaschema.xml +++ b/src/metaschema/oscal_catalog_metaschema.xml @@ -67,6 +67,9 @@ Group Identifier A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in this or other OSCAL instances (e.g., profiles). This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. + +

See the Concepts - Identifier Use page for additional information regarding this human-oriented identifier's uniqueness and scope.

+ Group Class @@ -133,6 +136,9 @@ Control Identifier A human-oriented, locally unique identifier with instance scope that can be used to reference this control elsewhere in this and other OSCAL instances (e.g., profiles). This id should be assigned per-subject, which means it should be consistently used to identify the same control across revisions of the document. + +

See the [Concepts - Identifier Use page for additional information regarding this human-oriented identifier's uniqueness and scope.

+ Control Class diff --git a/src/metaschema/oscal_control-common_metaschema.xml b/src/metaschema/oscal_control-common_metaschema.xml index b8da1ffe4e..1f2f71b889 100644 --- a/src/metaschema/oscal_control-common_metaschema.xml +++ b/src/metaschema/oscal_control-common_metaschema.xml @@ -24,6 +24,9 @@ Part Identifier A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this and other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + +

See the Concepts - Identifier Use page for additional information regarding this human-oriented identifier's uniqueness and scope.

+ Part Name @@ -125,6 +128,9 @@ Parameter Identifier A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + +

See the Concepts - Identifier Use page for additional information regarding this human-oriented identifier's uniqueness and scope.

+ @@ -268,5 +274,8 @@ Control Identifier Reference A human-oriented identifier reference to a control with a corresponding 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). + +

See the Concepts - Identifier Use page for additional information about the referenced identifier's scope.

+ diff --git a/src/metaschema/oscal_metadata_metaschema.xml b/src/metaschema/oscal_metadata_metaschema.xml index 4d94e6783d..8421a25c01 100644 --- a/src/metaschema/oscal_metadata_metaschema.xml +++ b/src/metaschema/oscal_metadata_metaschema.xml @@ -158,6 +158,9 @@ Location Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -223,6 +226,9 @@ + +

See the Concepts - Identifier Use page for additional information about the referenced identifier's scope.

+ @@ -236,6 +242,9 @@ + +

See the Concepts - Identifier Use page for additional information about the referenced identifier's scope.

+ @@ -245,6 +254,9 @@ Party Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ Party Type @@ -325,7 +337,7 @@

Parties of both the person or organization type can be associated with an organization using the member-of-organization.

-

See the [Concepts - Identifier Use](https://pages.nist.gov/OSCAL/concepts/identifier-use/#scope) page for additional information about the referenced identifier's scope.

+

See the Concepts - Identifier Use page for additional information about the referenced identifier's scope.

 @@ -350,6 +362,9 @@ + +

See the Concepts - Identifier Use page for additional information about the referenced identifier's scope.

+ @@ -358,8 +373,10 @@ - A human-oriented, locally-unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this and other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. - + A human-oriented, locally-unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this and other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. + +

See the Concepts - Identifier Use page for additional information regarding this human-oriented identifier's uniqueness and scope.

+ @@ -386,7 +403,6 @@

Permissible values to be determined closer to the application (e.g. by a receiving authority).

OSCAL has defined a set of standardized roles for consistent use in OSCAL documents. This allows tools consuming OSCAL content to infer specific semantics when these roles are used. These roles are documented in the specific contexts of their use (e.g., responsible-party, responsible-role). When using such a role, it is necessary to define these roles in this list, which will then allow such a role to be referenced.

-

See the [Concepts - Identifier Use](https://pages.nist.gov/OSCAL/concepts/identifier-use/#human-oriented) page for additional information regarding this identifier's uniqueness and scope.

 @@ -417,6 +433,9 @@ Resource Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -611,6 +630,9 @@ Property Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this and other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -942,7 +964,7 @@

This element is optional, but it will always have a valid value, as if it is missing the value of "document-id" is assumed to be equal to the UUID of the root. This requirement allows for document creators to retroactively link an update to the original version, by providing a document-id on the new document that is equal to the uuid of the original document.

-

See the [Concepts - Identifier Use](https://pages.nist.gov/OSCAL/concepts/identifier-use/#human-oriented) page for additional information regarding this identifier's uniqueness and scope.

+

See the Concepts - Identifier Use page for additional information regarding this *machine-oriented* identifier's uniqueness and scope.

 diff --git a/src/metaschema/oscal_profile_metaschema.xml b/src/metaschema/oscal_profile_metaschema.xml index 02abd1bb41..e9b1b41101 100644 --- a/src/metaschema/oscal_profile_metaschema.xml +++ b/src/metaschema/oscal_profile_metaschema.xml @@ -25,6 +25,9 @@ Profile Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this profile elsewhere in this and other OSCAL instances. The locally defined UUID of the profile can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance).This identifier should be assigned per-subject, which means it should be consistently used to identify the same profile across revisions of the document. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -37,7 +40,7 @@

An OSCAL document that describes a tailoring of controls from one or more catalogs, with possible modification of multiple controls. It provides mechanisms by which controls may be selected (import), merged or (re)structured (merge), and amended (modify). OSCAL profiles may select subsets of controls, set parameter values for them in application, and even adjust the representation of controls as given in and by a catalog. They may also serve as sources for further modification in and by other profiles, that import them.

-

See the [Concepts - Identifier Use](https://pages.nist.gov/OSCAL/concepts/identifier-use/#machine-oriented) page for additional information regarding this identifier's uniqueness and scope.

+

See the Concepts - Identifier Use page for additional information regarding this identifier's uniqueness and scope.

 @@ -149,6 +152,9 @@ Group Identifier A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. + +

See the Concepts - Identifier Use page for additional information regarding this human-oriented identifier's uniqueness and scope.

+ Group Class @@ -201,6 +207,9 @@ Parameter ID A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + +

See the Concepts - Identifier Use page for additional information regarding this human-oriented identifier's uniqueness and scope.

+ Parameter Class From a4d19895cab2b0ca082e9b4255c5d3c2be631316 Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Thu, 14 Oct 2021 13:16:54 -0400 Subject: [PATCH 15/34] metadata section updates --- src/metaschema/oscal_metadata_metaschema.xml | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/src/metaschema/oscal_metadata_metaschema.xml b/src/metaschema/oscal_metadata_metaschema.xml index 8421a25c01..0b164892f3 100644 --- a/src/metaschema/oscal_metadata_metaschema.xml +++ b/src/metaschema/oscal_metadata_metaschema.xml @@ -219,6 +219,11 @@ A machine-oriented identifier reference to a 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). + + +

Type: machine-oriented

+

Source: instance - References a location a location defined in the metadata section of this OSCAL instance.

+ @@ -236,6 +241,11 @@ A machine-oriented identifier reference to a 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). + + +

Type: machine-oriented

+

Source: instance - References a location a location defined in the metadata section of this OSCAL instance.

+ @@ -356,6 +366,11 @@ A machine-oriented identifier reference to another 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). + + +

Type: machine-oriented

+

Source: instance - References a party defined in the metadata section of this OSCAL instance.

+ From 1e323f45042c6e368d0f14ad9c8de9acbdf9879c Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Mon, 18 Oct 2021 21:12:36 -0400 Subject: [PATCH 16/34] common control metaschema updates --- .../oscal_control-common_metaschema.xml | 27 +++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/src/metaschema/oscal_control-common_metaschema.xml b/src/metaschema/oscal_control-common_metaschema.xml index 1f2f71b889..035e8d3e87 100644 --- a/src/metaschema/oscal_control-common_metaschema.xml +++ b/src/metaschema/oscal_control-common_metaschema.xml @@ -23,9 +23,19 @@ Part Identifier +<<<<<<< HEAD A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this and other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.

See the Concepts - Identifier Use page for additional information regarding this human-oriented identifier's uniqueness and scope.

+======= + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this and other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: human-oriented

+

Uniqueness: locally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this part in this or other OSCAL instances

+

Consistency: per-subject

+>>>>>>> a25eadc7 (common control metaschema updates) @@ -127,9 +137,19 @@ Parameter Identifier +<<<<<<< HEAD A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.

See the Concepts - Identifier Use page for additional information regarding this human-oriented identifier's uniqueness and scope.

+======= + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: human-oriented

+

Uniqueness: locally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this part in this or other OSCAL instances

+

Consistency: per-subject

+>>>>>>> a25eadc7 (common control metaschema updates) @@ -273,9 +293,16 @@ Control Identifier Reference +<<<<<<< HEAD A human-oriented identifier reference to a control with a corresponding 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).

See the Concepts - Identifier Use page for additional information about the referenced identifier's scope.

+======= + A human-oriented identifier reference to a control with a corresponding id value. + +

Type: human-oriented

+

Source: cross-instance - References a control identifer defined in this or another OSCAL instance

+>>>>>>> a25eadc7 (common control metaschema updates) From 896436dadc951281bcb2b7d64d8b4904c37e546d Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Tue, 19 Oct 2021 23:12:12 -0400 Subject: [PATCH 17/34] catalog and profile identifier description updates --- .../oscal_control-common_metaschema.xml | 27 ------------------- 1 file changed, 27 deletions(-) diff --git a/src/metaschema/oscal_control-common_metaschema.xml b/src/metaschema/oscal_control-common_metaschema.xml index 035e8d3e87..1f2f71b889 100644 --- a/src/metaschema/oscal_control-common_metaschema.xml +++ b/src/metaschema/oscal_control-common_metaschema.xml @@ -23,19 +23,9 @@ Part Identifier -<<<<<<< HEAD A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this and other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.

See the Concepts - Identifier Use page for additional information regarding this human-oriented identifier's uniqueness and scope.

-======= - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this and other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: human-oriented

-

Uniqueness: locally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this part in this or other OSCAL instances

-

Consistency: per-subject

->>>>>>> a25eadc7 (common control metaschema updates) @@ -137,19 +127,9 @@ Parameter Identifier -<<<<<<< HEAD A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.

See the Concepts - Identifier Use page for additional information regarding this human-oriented identifier's uniqueness and scope.

-======= - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: human-oriented

-

Uniqueness: locally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this part in this or other OSCAL instances

-

Consistency: per-subject

->>>>>>> a25eadc7 (common control metaschema updates) @@ -293,16 +273,9 @@ Control Identifier Reference -<<<<<<< HEAD A human-oriented identifier reference to a control with a corresponding 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).

See the Concepts - Identifier Use page for additional information about the referenced identifier's scope.

-======= - A human-oriented identifier reference to a control with a corresponding id value. - -

Type: human-oriented

-

Source: cross-instance - References a control identifer defined in this or another OSCAL instance

->>>>>>> a25eadc7 (common control metaschema updates) From 9575df5f7aa666838620511dc1186d00788f87b2 Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Wed, 27 Oct 2021 14:22:31 -0400 Subject: [PATCH 18/34] implementation layer metaschema updates --- src/metaschema/oscal_ssp_metaschema.xml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/src/metaschema/oscal_ssp_metaschema.xml b/src/metaschema/oscal_ssp_metaschema.xml index fd99d1dc75..25d27cc3e4 100644 --- a/src/metaschema/oscal_ssp_metaschema.xml +++ b/src/metaschema/oscal_ssp_metaschema.xml @@ -226,6 +226,13 @@ A human-oriented, globally unique identifier qualified by the given identification system used, such as NIST SP 800-60. This identifier has cross-instance scope and can be used to reference this system elsewhere in this or other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. id + + +

Type: human-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this information system type in this or other OSCAL instances

+

Consistency: per-subject

+ From c917c3830959c88ff4b1bf6e016c2ac16f355d31 Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Thu, 28 Oct 2021 14:34:36 -0400 Subject: [PATCH 19/34] assessment layers updates --- .../oscal_assessment-common_metaschema.xml | 165 ++++++++++++++++++ .../oscal_assessment-plan_metaschema.xml | 11 ++ .../oscal_assessment-results_metaschema.xml | 44 +++++ src/metaschema/oscal_poam_metaschema.xml | 20 +++ 4 files changed, 240 insertions(+) diff --git a/src/metaschema/oscal_assessment-common_metaschema.xml b/src/metaschema/oscal_assessment-common_metaschema.xml index b67a8b7261..6da93c0d60 100644 --- a/src/metaschema/oscal_assessment-common_metaschema.xml +++ b/src/metaschema/oscal_assessment-common_metaschema.xml @@ -78,7 +78,18 @@ Assessment Method Universally Unique Identifier +<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment method elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment method can be used to reference the data item locally or globally (e.g., in an imported 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. +======= + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment method elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this assessment method in this or other OSCAL instances

+

Consistency: per-subject

+ +>>>>>>> e391783d (assessment layers updates) @@ -105,7 +116,18 @@ Assessment Activity Universally Unique Identifier +<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment activity elsewhere in this or other OSCAL instances. The locally defined UUID of the activity can be used to reference the data item locally or globally (e.g., in an imported 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. +======= + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment activity elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this assessment activity in this or other OSCAL instances

+

Consistency: per-subject

+ +>>>>>>> e391783d (assessment layers updates) @@ -129,7 +151,18 @@ Step Universally Unique Identifier +<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this step elsewhere in this or other OSCAL instances. The locally defined UUID of the step (in a series of steps) can be used to reference the data item locally or globally (e.g., in an imported 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. +======= + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this step elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this step in this or other OSCAL instances

+

Consistency: per-subject

+ +>>>>>>> e391783d (assessment layers updates) @@ -208,7 +241,18 @@ Task Universally Unique Identifier +<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this task elsewhere in this or other OSCAL instances. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. +======= + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this task elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this task in this or other OSCAL instances

+

Consistency: per-subject

+ +>>>>>>> e391783d (assessment layers updates) Task Type @@ -513,7 +557,18 @@ Assessment Subject Placeholder Universally Unique Identifier +<<<<<<< HEAD A machine-oriented, globally unique identifier for a set of assessment subjects that will be identified by a task or an activity that is part of a task. The locally defined UUID of the assessment subject placeholder can be used to reference the data item locally or globally (e.g., in an imported 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. +======= + A machine-oriented, globally unique identifier for a set of assessment subjects that will be identified by a task or an activity that is part of a task. This identifier has cross-instance scope, thus it can be used to reference this assessment subject elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: human-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this set of assessment subjects in this or other OSCAL instances

+

Consistency: per-subject

+ +>>>>>>> e391783d (assessment layers updates) @@ -527,7 +582,18 @@ Task Universally Unique Identifier +<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference (in this or other OSCAL instances) an assessment activity to be performed as part of the event. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. +======= + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference (in this or other OSCAL instances) an assessment activity to be performed as part of the event. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this assessment activity in this or other OSCAL instances

+

Consistency: per-subject

+ +>>>>>>> e391783d (assessment layers updates) @@ -685,7 +751,18 @@ Assessment Platform Universally Unique Identifier +<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment platform elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment platform can be used to reference the data item locally or globally (e.g., in an imported 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. +======= + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment platform elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this assessment platform in this or other OSCAL instances

+

Consistency: per-subject

+ +>>>>>>> e391783d (assessment layers updates) @@ -835,7 +912,18 @@ Observation Universally Unique Identifier +<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. The locally defined UUID of the observation can be used to reference the data item locally or globally (e.g., in an imported 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. +======= + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this observation in this or other OSCAL instances

+

Consistency: per-subject

+ +>>>>>>> e391783d (assessment layers updates) @@ -1092,7 +1180,18 @@ Risk Universally Unique Identifier +<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk elsewhere in this or other OSCAL instances. The locally defined UUID of the risk can be used to reference the data item locally or globally (e.g., in an imported 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. +======= + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this risk in this or other OSCAL instances

+

Consistency: per-subject

+ +>>>>>>> e391783d (assessment layers updates) @@ -1150,12 +1249,34 @@ Mitigating Factor Universally Unique Identifier +<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mitigating factor elsewhere in this or other OSCAL instances. The locally defined UUID of the mitigating factor can be used to reference the data item locally or globally (e.g., in an imported 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. +======= + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mitigating factor elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this mitigating factor in this or other OSCAL instances

+

Consistency: per-subject

+ +>>>>>>> e391783d (assessment layers updates) Implementation UUID +<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this implementation statement elsewhere in this or other OSCAL instances. The locally defined UUID of the implementation statement can be used to reference the data item locally or globally (e.g., in an imported 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. +======= + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this implementation statement elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this implementation statement in this or other OSCAL instances

+

Consistency: per-subject

+ +>>>>>>> e391783d (assessment layers updates) @@ -1197,7 +1318,18 @@ Risk Log Entry Universally Unique Identifier +<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk log entry elsewhere in this or other OSCAL instances. The locally defined UUID of the risk log entry can be used to reference the data item locally or globally (e.g., in an imported 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. +======= + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk log entry elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this risk log entry in this or other OSCAL instances

+

Consistency: per-subject

+ +>>>>>>> e391783d (assessment layers updates) @@ -1605,7 +1737,18 @@ Remediation Universally Unique Identifier +<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this remediation elsewhere in this or other OSCAL instances. The locally defined UUID of the risk response can be used to reference the data item locally or globally (e.g., in an imported 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. +======= + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this remediation elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this remediation in this or other OSCAL instances

+

Consistency: per-subject

+ +>>>>>>> e391783d (assessment layers updates) Remediation Intent @@ -1648,7 +1791,18 @@ Required Universally Unique Identifier +<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this required asset elsewhere in this or other OSCAL instances. The locally defined UUID of the asset can be used to reference the data item locally or globally (e.g., in an imported 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. +======= + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this required asset elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this required asset in this or other OSCAL instances

+

Consistency: per-subject

+ +>>>>>>> e391783d (assessment layers updates) @@ -1711,7 +1865,18 @@ Part Identifier +<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this part elsewhere in this or other OSCAL instances. The locally defined UUID of the part can be used to reference the data item locally or globally (e.g., in an imported 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. +======= + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this part elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this part in this or other OSCAL instances

+

Consistency: per-subject

+ +>>>>>>> e391783d (assessment layers updates) Part Name diff --git a/src/metaschema/oscal_assessment-plan_metaschema.xml b/src/metaschema/oscal_assessment-plan_metaschema.xml index 95fa85c89d..93f583c5f0 100644 --- a/src/metaschema/oscal_assessment-plan_metaschema.xml +++ b/src/metaschema/oscal_assessment-plan_metaschema.xml @@ -21,7 +21,18 @@ Assessment Plan Universally Unique Identifier +<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment plan in this or other OSCAL instances. The locally defined UUID of the assessment plan can be used to reference the data item locally or globally (e.g., in an imported 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. +======= + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment plan in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this assessment plan in this or other OSCAL instances

+

Consistency: per-subject

+ +>>>>>>> e391783d (assessment layers updates) diff --git a/src/metaschema/oscal_assessment-results_metaschema.xml b/src/metaschema/oscal_assessment-results_metaschema.xml index 3e3be75bb1..f72591cb11 100644 --- a/src/metaschema/oscal_assessment-results_metaschema.xml +++ b/src/metaschema/oscal_assessment-results_metaschema.xml @@ -23,7 +23,18 @@ Assessment Results Universally Unique Identifier +<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment results instance in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported 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. +======= + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment results instance in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this assessment results in this or other OSCAL instances

+

Consistency: per-subject

+ +>>>>>>> e391783d (assessment layers updates) @@ -76,7 +87,18 @@ Results Universally Unique Identifier +<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this set of results in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported 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. +======= + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this set of results in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this set of results in this or other OSCAL instances

+

Consistency: per-subject

+ +>>>>>>> e391783d (assessment layers updates) @@ -202,7 +224,18 @@ Assessment Log Entry Universally Unique Identifier +<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference an assessment event in this or other OSCAL instances. The locally defined UUID of the assessment log entry can be used to reference the data item locally or globally (e.g., in an imported 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. +======= + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference an assessment event in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this assessment event in this or other OSCAL instances

+

Consistency: per-subject

+ +>>>>>>> e391783d (assessment layers updates) @@ -263,7 +296,18 @@ Finding Universally Unique Identifier +<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this finding in this or other OSCAL instances. The locally defined UUID of the finding can be used to reference the data item locally or globally (e.g., in an imported 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. +======= + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this finding in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this finding in this or other OSCAL instances

+

Consistency: per-subject

+ +>>>>>>> e391783d (assessment layers updates) diff --git a/src/metaschema/oscal_poam_metaschema.xml b/src/metaschema/oscal_poam_metaschema.xml index b36ec007fa..90eceb6e35 100644 --- a/src/metaschema/oscal_poam_metaschema.xml +++ b/src/metaschema/oscal_poam_metaschema.xml @@ -25,6 +25,16 @@ POA&M Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this POA&M instance in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. +<<<<<<< HEAD +======= + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this POA&M instance in this or other OSCAL instances

+

Consistency: per-subject

+ +>>>>>>> e391783d (assessment layers updates) @@ -91,6 +101,16 @@ POA&M Item Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this POA&M item entry in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. +<<<<<<< HEAD +======= + + +

Type: machine-oriented

+

Uniqueness: globally unique

+

Scope: cross-instance - provides an identifier that can be used to refer to this POA&M item entry in this or other OSCAL instances

+

Consistency: per-subject

+ +>>>>>>> e391783d (assessment layers updates) From 882a560958d7a04ccb00c09522871c144f9e8f1c Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Tue, 30 Nov 2021 19:35:05 -0500 Subject: [PATCH 20/34] revised identifier descriptions --- .../oscal_assessment-common_metaschema.xml | 165 ------------------ .../oscal_assessment-plan_metaschema.xml | 4 + .../oscal_assessment-results_metaschema.xml | 44 ----- src/metaschema/oscal_metadata_metaschema.xml | 17 +- src/metaschema/oscal_poam_metaschema.xml | 20 --- src/metaschema/oscal_ssp_metaschema.xml | 7 - 6 files changed, 5 insertions(+), 252 deletions(-) diff --git a/src/metaschema/oscal_assessment-common_metaschema.xml b/src/metaschema/oscal_assessment-common_metaschema.xml index 6da93c0d60..b67a8b7261 100644 --- a/src/metaschema/oscal_assessment-common_metaschema.xml +++ b/src/metaschema/oscal_assessment-common_metaschema.xml @@ -78,18 +78,7 @@ Assessment Method Universally Unique Identifier -<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment method elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment method can be used to reference the data item locally or globally (e.g., in an imported 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. -======= - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment method elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this assessment method in this or other OSCAL instances

-

Consistency: per-subject

- ->>>>>>> e391783d (assessment layers updates) @@ -116,18 +105,7 @@ Assessment Activity Universally Unique Identifier -<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment activity elsewhere in this or other OSCAL instances. The locally defined UUID of the activity can be used to reference the data item locally or globally (e.g., in an imported 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. -======= - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment activity elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this assessment activity in this or other OSCAL instances

-

Consistency: per-subject

- ->>>>>>> e391783d (assessment layers updates) @@ -151,18 +129,7 @@ Step Universally Unique Identifier -<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this step elsewhere in this or other OSCAL instances. The locally defined UUID of the step (in a series of steps) can be used to reference the data item locally or globally (e.g., in an imported 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. -======= - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this step elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this step in this or other OSCAL instances

-

Consistency: per-subject

- ->>>>>>> e391783d (assessment layers updates) @@ -241,18 +208,7 @@ Task Universally Unique Identifier -<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this task elsewhere in this or other OSCAL instances. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. -======= - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this task elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this task in this or other OSCAL instances

-

Consistency: per-subject

- ->>>>>>> e391783d (assessment layers updates) Task Type @@ -557,18 +513,7 @@ Assessment Subject Placeholder Universally Unique Identifier -<<<<<<< HEAD A machine-oriented, globally unique identifier for a set of assessment subjects that will be identified by a task or an activity that is part of a task. The locally defined UUID of the assessment subject placeholder can be used to reference the data item locally or globally (e.g., in an imported 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. -======= - A machine-oriented, globally unique identifier for a set of assessment subjects that will be identified by a task or an activity that is part of a task. This identifier has cross-instance scope, thus it can be used to reference this assessment subject elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: human-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this set of assessment subjects in this or other OSCAL instances

-

Consistency: per-subject

- ->>>>>>> e391783d (assessment layers updates) @@ -582,18 +527,7 @@ Task Universally Unique Identifier -<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference (in this or other OSCAL instances) an assessment activity to be performed as part of the event. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. -======= - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference (in this or other OSCAL instances) an assessment activity to be performed as part of the event. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this assessment activity in this or other OSCAL instances

-

Consistency: per-subject

- ->>>>>>> e391783d (assessment layers updates) @@ -751,18 +685,7 @@ Assessment Platform Universally Unique Identifier -<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment platform elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment platform can be used to reference the data item locally or globally (e.g., in an imported 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. -======= - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment platform elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this assessment platform in this or other OSCAL instances

-

Consistency: per-subject

- ->>>>>>> e391783d (assessment layers updates) @@ -912,18 +835,7 @@ Observation Universally Unique Identifier -<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. The locally defined UUID of the observation can be used to reference the data item locally or globally (e.g., in an imported 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. -======= - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this observation in this or other OSCAL instances

-

Consistency: per-subject

- ->>>>>>> e391783d (assessment layers updates) @@ -1180,18 +1092,7 @@ Risk Universally Unique Identifier -<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk elsewhere in this or other OSCAL instances. The locally defined UUID of the risk can be used to reference the data item locally or globally (e.g., in an imported 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. -======= - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this risk in this or other OSCAL instances

-

Consistency: per-subject

- ->>>>>>> e391783d (assessment layers updates) @@ -1249,34 +1150,12 @@ Mitigating Factor Universally Unique Identifier -<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mitigating factor elsewhere in this or other OSCAL instances. The locally defined UUID of the mitigating factor can be used to reference the data item locally or globally (e.g., in an imported 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. -======= - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mitigating factor elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this mitigating factor in this or other OSCAL instances

-

Consistency: per-subject

- ->>>>>>> e391783d (assessment layers updates) Implementation UUID -<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this implementation statement elsewhere in this or other OSCAL instances. The locally defined UUID of the implementation statement can be used to reference the data item locally or globally (e.g., in an imported 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. -======= - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this implementation statement elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this implementation statement in this or other OSCAL instances

-

Consistency: per-subject

- ->>>>>>> e391783d (assessment layers updates) @@ -1318,18 +1197,7 @@ Risk Log Entry Universally Unique Identifier -<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk log entry elsewhere in this or other OSCAL instances. The locally defined UUID of the risk log entry can be used to reference the data item locally or globally (e.g., in an imported 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. -======= - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk log entry elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this risk log entry in this or other OSCAL instances

-

Consistency: per-subject

- ->>>>>>> e391783d (assessment layers updates) @@ -1737,18 +1605,7 @@ Remediation Universally Unique Identifier -<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this remediation elsewhere in this or other OSCAL instances. The locally defined UUID of the risk response can be used to reference the data item locally or globally (e.g., in an imported 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. -======= - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this remediation elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this remediation in this or other OSCAL instances

-

Consistency: per-subject

- ->>>>>>> e391783d (assessment layers updates) Remediation Intent @@ -1791,18 +1648,7 @@ Required Universally Unique Identifier -<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this required asset elsewhere in this or other OSCAL instances. The locally defined UUID of the asset can be used to reference the data item locally or globally (e.g., in an imported 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. -======= - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this required asset elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this required asset in this or other OSCAL instances

-

Consistency: per-subject

- ->>>>>>> e391783d (assessment layers updates) @@ -1865,18 +1711,7 @@ Part Identifier -<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this part elsewhere in this or other OSCAL instances. The locally defined UUID of the part can be used to reference the data item locally or globally (e.g., in an imported 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. -======= - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this part elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this part in this or other OSCAL instances

-

Consistency: per-subject

- ->>>>>>> e391783d (assessment layers updates) Part Name diff --git a/src/metaschema/oscal_assessment-plan_metaschema.xml b/src/metaschema/oscal_assessment-plan_metaschema.xml index 93f583c5f0..059058a9a3 100644 --- a/src/metaschema/oscal_assessment-plan_metaschema.xml +++ b/src/metaschema/oscal_assessment-plan_metaschema.xml @@ -21,6 +21,7 @@ Assessment Plan Universally Unique Identifier +<<<<<<< HEAD <<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment plan in this or other OSCAL instances. The locally defined UUID of the assessment plan can be used to reference the data item locally or globally (e.g., in an imported 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. ======= @@ -33,6 +34,9 @@

Consistency: per-subject

>>>>>>> e391783d (assessment layers updates) +======= + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment plan in this or other OSCAL instances. The locally defined UUID of the assessment plan can be used to reference the data item locally or globally (e.g., in an imported 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. +>>>>>>> 890064fc (revised identifier descriptions) diff --git a/src/metaschema/oscal_assessment-results_metaschema.xml b/src/metaschema/oscal_assessment-results_metaschema.xml index f72591cb11..3e3be75bb1 100644 --- a/src/metaschema/oscal_assessment-results_metaschema.xml +++ b/src/metaschema/oscal_assessment-results_metaschema.xml @@ -23,18 +23,7 @@ Assessment Results Universally Unique Identifier -<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment results instance in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported 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. -======= - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment results instance in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this assessment results in this or other OSCAL instances

-

Consistency: per-subject

- ->>>>>>> e391783d (assessment layers updates) @@ -87,18 +76,7 @@ Results Universally Unique Identifier -<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this set of results in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported 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. -======= - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this set of results in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this set of results in this or other OSCAL instances

-

Consistency: per-subject

- ->>>>>>> e391783d (assessment layers updates) @@ -224,18 +202,7 @@ Assessment Log Entry Universally Unique Identifier -<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference an assessment event in this or other OSCAL instances. The locally defined UUID of the assessment log entry can be used to reference the data item locally or globally (e.g., in an imported 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. -======= - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference an assessment event in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this assessment event in this or other OSCAL instances

-

Consistency: per-subject

- ->>>>>>> e391783d (assessment layers updates) @@ -296,18 +263,7 @@ Finding Universally Unique Identifier -<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this finding in this or other OSCAL instances. The locally defined UUID of the finding can be used to reference the data item locally or globally (e.g., in an imported 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. -======= - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this finding in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this finding in this or other OSCAL instances

-

Consistency: per-subject

- ->>>>>>> e391783d (assessment layers updates) diff --git a/src/metaschema/oscal_metadata_metaschema.xml b/src/metaschema/oscal_metadata_metaschema.xml index 0b164892f3..b196eb12a5 100644 --- a/src/metaschema/oscal_metadata_metaschema.xml +++ b/src/metaschema/oscal_metadata_metaschema.xml @@ -219,11 +219,6 @@ A machine-oriented identifier reference to a 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). - - -

Type: machine-oriented

-

Source: instance - References a location a location defined in the metadata section of this OSCAL instance.

- @@ -241,11 +236,6 @@ A machine-oriented identifier reference to a 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). - - -

Type: machine-oriented

-

Source: instance - References a location a location defined in the metadata section of this OSCAL instance.

- @@ -366,11 +356,6 @@ A machine-oriented identifier reference to another 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). - - -

Type: machine-oriented

-

Source: instance - References a party defined in the metadata section of this OSCAL instance.

- @@ -964,7 +949,7 @@ Document Identifier - A document identifier qualified by an identifier scheme. A document identifier provides a globally-unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + A document identifier qualified by an identifier scheme. A document identifier provides a globally-unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. The locally defined document-id can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. identifier diff --git a/src/metaschema/oscal_poam_metaschema.xml b/src/metaschema/oscal_poam_metaschema.xml index 90eceb6e35..b36ec007fa 100644 --- a/src/metaschema/oscal_poam_metaschema.xml +++ b/src/metaschema/oscal_poam_metaschema.xml @@ -25,16 +25,6 @@ POA&M Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this POA&M instance in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. -<<<<<<< HEAD -======= - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this POA&M instance in this or other OSCAL instances

-

Consistency: per-subject

- ->>>>>>> e391783d (assessment layers updates) @@ -101,16 +91,6 @@ POA&M Item Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this POA&M item entry in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. -<<<<<<< HEAD -======= - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this POA&M item entry in this or other OSCAL instances

-

Consistency: per-subject

- ->>>>>>> e391783d (assessment layers updates) diff --git a/src/metaschema/oscal_ssp_metaschema.xml b/src/metaschema/oscal_ssp_metaschema.xml index 25d27cc3e4..fd99d1dc75 100644 --- a/src/metaschema/oscal_ssp_metaschema.xml +++ b/src/metaschema/oscal_ssp_metaschema.xml @@ -226,13 +226,6 @@ A human-oriented, globally unique identifier qualified by the given identification system used, such as NIST SP 800-60. This identifier has cross-instance scope and can be used to reference this system elsewhere in this or other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. id - - -

Type: human-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this information system type in this or other OSCAL instances

-

Consistency: per-subject

- From d37564e15f5eb21fcaf2fbd11234483b6a7eb73a Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Thu, 9 Dec 2021 08:51:15 -0500 Subject: [PATCH 21/34] added identifier use page --- docs/content/concepts/identifier-use/_index.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/content/concepts/identifier-use/_index.md b/docs/content/concepts/identifier-use/_index.md index 522ee7119f..8b8b13d17f 100644 --- a/docs/content/concepts/identifier-use/_index.md +++ b/docs/content/concepts/identifier-use/_index.md @@ -11,7 +11,11 @@ sidenav: inactiverenderdepth: 2 --- +<<<<<<< HEAD This page reviews important concepts to be aware of when declaring or referencing identifiers in OSCAL models, with in-depth explanations of identifier uniqueness and scope. +======= +This page reviews important concepts to be aware of when declaring or referencing identifiers in OSCAL models. +>>>>>>> f992e3ef (added identifier use page) ### **Identifier Type** By design, OSCAL supports [*machine-oriented*](/concepts/identifier-use/#machine-oriented) and [*human-oriented*](/concepts/identifier-use/#human-oriented) identifiers. The OSCAL models dictate which are used for different data items. From ea51575e4b7d259a7d58138b5a01a47cd60a769e Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Thu, 9 Dec 2021 10:08:59 -0500 Subject: [PATCH 22/34] minor edit on identifier use page --- docs/content/concepts/identifier-use/_index.md | 4 ---- .../oscal_assessment-plan_metaschema.xml | 15 --------------- 2 files changed, 19 deletions(-) diff --git a/docs/content/concepts/identifier-use/_index.md b/docs/content/concepts/identifier-use/_index.md index 8b8b13d17f..522ee7119f 100644 --- a/docs/content/concepts/identifier-use/_index.md +++ b/docs/content/concepts/identifier-use/_index.md @@ -11,11 +11,7 @@ sidenav: inactiverenderdepth: 2 --- -<<<<<<< HEAD This page reviews important concepts to be aware of when declaring or referencing identifiers in OSCAL models, with in-depth explanations of identifier uniqueness and scope. -======= -This page reviews important concepts to be aware of when declaring or referencing identifiers in OSCAL models. ->>>>>>> f992e3ef (added identifier use page) ### **Identifier Type** By design, OSCAL supports [*machine-oriented*](/concepts/identifier-use/#machine-oriented) and [*human-oriented*](/concepts/identifier-use/#human-oriented) identifiers. The OSCAL models dictate which are used for different data items. diff --git a/src/metaschema/oscal_assessment-plan_metaschema.xml b/src/metaschema/oscal_assessment-plan_metaschema.xml index 059058a9a3..95fa85c89d 100644 --- a/src/metaschema/oscal_assessment-plan_metaschema.xml +++ b/src/metaschema/oscal_assessment-plan_metaschema.xml @@ -21,22 +21,7 @@ Assessment Plan Universally Unique Identifier -<<<<<<< HEAD -<<<<<<< HEAD A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment plan in this or other OSCAL instances. The locally defined UUID of the assessment plan can be used to reference the data item locally or globally (e.g., in an imported 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. -======= - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment plan in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - - -

Type: machine-oriented

-

Uniqueness: globally unique

-

Scope: cross-instance - provides an identifier that can be used to refer to this assessment plan in this or other OSCAL instances

-

Consistency: per-subject

- ->>>>>>> e391783d (assessment layers updates) -======= - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment plan in this or other OSCAL instances. The locally defined UUID of the assessment plan can be used to reference the data item locally or globally (e.g., in an imported 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. ->>>>>>> 890064fc (revised identifier descriptions) From bfaa855f2c9a9f1e843c8bbfb2cfc9d2baf07c09 Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Thu, 9 Dec 2021 15:58:00 -0500 Subject: [PATCH 23/34] metaschema updates --- src/metaschema/oscal_metadata_metaschema.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/metaschema/oscal_metadata_metaschema.xml b/src/metaschema/oscal_metadata_metaschema.xml index b196eb12a5..8421a25c01 100644 --- a/src/metaschema/oscal_metadata_metaschema.xml +++ b/src/metaschema/oscal_metadata_metaschema.xml @@ -949,7 +949,7 @@ Document Identifier - A document identifier qualified by an identifier scheme. A document identifier provides a globally-unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. The locally defined document-id can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + A document identifier qualified by an identifier scheme. A document identifier provides a globally-unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. identifier From bdf5501d1b0e86a66b3a54f6a9e04443279a90bb Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Thu, 13 Jan 2022 12:34:11 -0500 Subject: [PATCH 24/34] added links to concepts page --- .../oscal_assessment-common_metaschema.xml | 45 +++++++++++++++++++ .../oscal_assessment-plan_metaschema.xml | 3 ++ .../oscal_assessment-results_metaschema.xml | 16 +++++-- src/metaschema/oscal_component_metaschema.xml | 18 ++++++++ ...oscal_implementation-common_metaschema.xml | 15 +++++++ src/metaschema/oscal_poam_metaschema.xml | 6 +++ src/metaschema/oscal_ssp_metaschema.xml | 36 +++++++++++++++ 7 files changed, 136 insertions(+), 3 deletions(-) diff --git a/src/metaschema/oscal_assessment-common_metaschema.xml b/src/metaschema/oscal_assessment-common_metaschema.xml index b67a8b7261..247deef528 100644 --- a/src/metaschema/oscal_assessment-common_metaschema.xml +++ b/src/metaschema/oscal_assessment-common_metaschema.xml @@ -79,6 +79,9 @@ Assessment Method Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment method elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment method can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -106,6 +109,9 @@ Assessment Activity Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment activity elsewhere in this or other OSCAL instances. The locally defined UUID of the activity can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -130,6 +136,9 @@ Step Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this step elsewhere in this or other OSCAL instances. The locally defined UUID of the step (in a series of steps) can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -209,6 +218,9 @@ Task Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this task elsewhere in this or other OSCAL instances. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ Task Type @@ -514,6 +526,9 @@ Assessment Subject Placeholder Universally Unique Identifier A machine-oriented, globally unique identifier for a set of assessment subjects that will be identified by a task or an activity that is part of a task. The locally defined UUID of the assessment subject placeholder can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -528,6 +543,9 @@ Task Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference (in this or other OSCAL instances) an assessment activity to be performed as part of the event. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -686,6 +704,9 @@ Assessment Platform Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment platform elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment platform can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -836,6 +857,9 @@ Observation Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. The locally defined UUID of the observation can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -1093,6 +1117,9 @@ Risk Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk elsewhere in this or other OSCAL instances. The locally defined UUID of the risk can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -1151,11 +1178,17 @@ Mitigating Factor Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mitigating factor elsewhere in this or other OSCAL instances. The locally defined UUID of the mitigating factor can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ Implementation UUID A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this implementation statement elsewhere in this or other OSCAL instances. The locally defined UUID of the implementation statement can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -1198,6 +1231,9 @@ Risk Log Entry Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk log entry elsewhere in this or other OSCAL instances. The locally defined UUID of the risk log entry can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -1606,6 +1642,9 @@ Remediation Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this remediation elsewhere in this or other OSCAL instances. The locally defined UUID of the risk response can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ Remediation Intent @@ -1649,6 +1688,9 @@ Required Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this required asset elsewhere in this or other OSCAL instances. The locally defined UUID of the asset can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -1712,6 +1754,9 @@ Part Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this part elsewhere in this or other OSCAL instances. The locally defined UUID of the part can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ Part Name diff --git a/src/metaschema/oscal_assessment-plan_metaschema.xml b/src/metaschema/oscal_assessment-plan_metaschema.xml index 95fa85c89d..6efc457be1 100644 --- a/src/metaschema/oscal_assessment-plan_metaschema.xml +++ b/src/metaschema/oscal_assessment-plan_metaschema.xml @@ -22,6 +22,9 @@ Assessment Plan Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment plan in this or other OSCAL instances. The locally defined UUID of the assessment plan can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ diff --git a/src/metaschema/oscal_assessment-results_metaschema.xml b/src/metaschema/oscal_assessment-results_metaschema.xml index 3e3be75bb1..58aa553698 100644 --- a/src/metaschema/oscal_assessment-results_metaschema.xml +++ b/src/metaschema/oscal_assessment-results_metaschema.xml @@ -24,6 +24,9 @@ Assessment Results Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment results instance in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -77,6 +80,9 @@ Results Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this set of results in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -203,6 +209,9 @@ Assessment Log Entry Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference an assessment event in this or other OSCAL instances. The locally defined UUID of the assessment log entry can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -264,6 +273,9 @@ Finding Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this finding in this or other OSCAL instances. The locally defined UUID of the finding can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -328,9 +340,7 @@ A machine-oriented identifier reference to a risk defined in the list of risks. - -

Type: machine-oriented

-

Source: cross-instance - References the a risk in this or other OSCAL instances

+

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

 diff --git a/src/metaschema/oscal_component_metaschema.xml b/src/metaschema/oscal_component_metaschema.xml index 41f53bc099..939c435dc5 100644 --- a/src/metaschema/oscal_component_metaschema.xml +++ b/src/metaschema/oscal_component_metaschema.xml @@ -35,6 +35,9 @@ Component Definition Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component definition elsewhere in this or other OSCAL instances. The locally defined UUID of the component definition can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -82,6 +85,9 @@ Component Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ type @@ -253,6 +259,9 @@ Capability Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this capability elsewhere in this or other OSCAL instances. The locally defined UUID of the capability can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ Capability Name @@ -315,6 +324,9 @@ Control Implementation Set Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference a set of implemented controls elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation set can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -358,6 +370,9 @@ Control Implementation Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference a specific control implementation elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -415,6 +430,9 @@ Control Statement Reference Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. The UUID of the control statement in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance). + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ diff --git a/src/metaschema/oscal_implementation-common_metaschema.xml b/src/metaschema/oscal_implementation-common_metaschema.xml index 0b4e515145..ffd565a0de 100644 --- a/src/metaschema/oscal_implementation-common_metaschema.xml +++ b/src/metaschema/oscal_implementation-common_metaschema.xml @@ -32,6 +32,9 @@ Component Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -252,6 +255,9 @@ Service Protocol Information Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ Protocol Name @@ -341,6 +347,9 @@ User Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -427,6 +436,9 @@ Inventory Item Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this and other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. + +

See the Concepts - Identifier Use page for additional information regarding this human-oriented identifier's uniqueness and scope.

+ id Identification System Type diff --git a/src/metaschema/oscal_poam_metaschema.xml b/src/metaschema/oscal_poam_metaschema.xml index b36ec007fa..34a240c78a 100644 --- a/src/metaschema/oscal_poam_metaschema.xml +++ b/src/metaschema/oscal_poam_metaschema.xml @@ -25,6 +25,9 @@ POA&M Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this POA&M instance in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -91,6 +94,9 @@ POA&M Item Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this POA&M item entry in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ diff --git a/src/metaschema/oscal_ssp_metaschema.xml b/src/metaschema/oscal_ssp_metaschema.xml index fd99d1dc75..df261285c9 100644 --- a/src/metaschema/oscal_ssp_metaschema.xml +++ b/src/metaschema/oscal_ssp_metaschema.xml @@ -36,6 +36,9 @@ System Security Plan Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this system security plan (SSP) elsewhere in this or other OSCAL instances. The locally defined UUID of the SSP can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -193,6 +196,9 @@ Information Type Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this information type elsewhere in this or other OSCAL instances. The locally defined UUID of the information type can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -226,6 +232,9 @@ A human-oriented, globally unique identifier qualified by the given identification system used, such as NIST SP 800-60. This identifier has cross-instance scope and can be used to reference this system elsewhere in this or other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. id + +

See the Concepts - Identifier Use page for additional information regarding this human-oriented identifier's uniqueness and scope.

+ @@ -414,6 +423,9 @@ Diagram ID A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this diagram elsewhere in this or other OSCAL instances. The locally defined UUID of the diagram can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -545,6 +557,9 @@ Leveraged Authorization Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope and can be used to reference this leveraged authorization elsewhere in this or other OSCAL instances. The locally defined UUID of the leveraged authorization can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -696,6 +711,9 @@ Control Requirement Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control requirement elsewhere in this or other OSCAL instances. The locally defined UUID of the control requirement can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -787,6 +805,9 @@ Control Statement Reference Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. The UUID of the control statement in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance). + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -840,6 +861,9 @@ By-Component Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this by-component entry elsewhere in this or other OSCAL instances. The locally defined UUID of the by-component entry can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -884,6 +908,9 @@ Provided Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this provided entry elsewhere in this or other OSCAL instances. The locally defined UUID of the provided entry can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -919,6 +946,9 @@ Responsibility Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this responsibility elsewhere in this or other OSCAL instances. The locally defined UUID of the responsibility can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -971,6 +1001,9 @@ Inherited Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inherited entry elsewhere in this or other OSCAL instances. The locally defined UUID of the inherited control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ @@ -1007,6 +1040,9 @@ Satisfied Universally Unique Identifier A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this satisfied control implementation entry elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. + +

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

+ From 5588161e97ba052bd58e22dc31ec97beac3b4e16 Mon Sep 17 00:00:00 2001 From: Rene2mt <76444659+Rene2mt@users.noreply.github.com> Date: Wed, 19 Jan 2022 22:43:58 -0500 Subject: [PATCH 25/34] Update docs/content/concepts/identifier-use/_index.md Co-authored-by: David Waltermire --- docs/content/concepts/identifier-use/_index.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/docs/content/concepts/identifier-use/_index.md b/docs/content/concepts/identifier-use/_index.md index 522ee7119f..752d471f7d 100644 --- a/docs/content/concepts/identifier-use/_index.md +++ b/docs/content/concepts/identifier-use/_index.md @@ -18,7 +18,15 @@ By design, OSCAL supports [*machine-oriented*](/concepts/identifier-use/#machine #### Machine-Oriented -*Machine-oriented* identifiers are implemented as Universally Unique Identifier (UUID) as defined by [RFC 4122](https://tools.ietf.org/html/rfc4122) and are commonly used to (programmatically) identify or refer to unique information within OSCAL models. Because OSCAL’s *`machine-oriented`* identifiers utilize UUID data types, they can be issued without a central authority, and used across OSCAL instances with low risk of identifier collisions. +*Machine-oriented* identifiers provide a persistent identity for an entity within the OSCAL models, which can be used in other locations within related OSCAL models to reference the associated entity. + +These identifiers are intended to be auto-generated by tools when the entity is initially created. In OSCAL, a machine-oriented identifier is implemented using a Universally Unique Identifier (UUID) as defined by [RFC 4122](https://tools.ietf.org/html/rfc4122). A UUID is represented in OSCAL using the UUID datatype (provide link). + +UUIDs were chosen because: + +- Programming interfaces exist in most programming environments to generate a UUID +- UUIDs can be issued without a central authority +- UUIDs are represented in 128bits, providing for a large address space with low risk of identifier collisions for randomly generated values > **NOTE**: While UUIDs are used as machine-oriented identifiers catering to use cases where automated processing is desired, they are not ideal for wildcard matching scenarios. UUIDs should only be used when exact matches are expected. From eab9863ae87b6b7a0404aaa390b4096e2b032931 Mon Sep 17 00:00:00 2001 From: Rene2mt <76444659+Rene2mt@users.noreply.github.com> Date: Wed, 19 Jan 2022 22:44:14 -0500 Subject: [PATCH 26/34] Update docs/content/concepts/identifier-use/_index.md Co-authored-by: David Waltermire --- docs/content/concepts/identifier-use/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/concepts/identifier-use/_index.md b/docs/content/concepts/identifier-use/_index.md index 752d471f7d..ea3c1a2b28 100644 --- a/docs/content/concepts/identifier-use/_index.md +++ b/docs/content/concepts/identifier-use/_index.md @@ -28,7 +28,7 @@ UUIDs were chosen because: - UUIDs can be issued without a central authority - UUIDs are represented in 128bits, providing for a large address space with low risk of identifier collisions for randomly generated values -> **NOTE**: While UUIDs are used as machine-oriented identifiers catering to use cases where automated processing is desired, they are not ideal for wildcard matching scenarios. UUIDs should only be used when exact matches are expected. +The opaque nature of UUIDs, which consist of a series of hexadecimal characters, makes them less than ideal for wildcard matching scenarios. Thus, their use in OSCAL is intended for identification only where an exact match is required. Where wildcard matching is needed, the other data elements associated with the entity should be evaluated for a match instead. The [OSCAL Reference Index](/reference/latest/complete/xml-index/#/@uuid) provides a complete listing of UUIDs in OSCAL. References to these identifiers typically follow a naming convention of the object type followed by “-uuid”. For example, see the reference index for [location-uuid](/reference/latest/complete/xml-index/#/location-uuid). From 8acc09cde48fccdf3d87822cb98e83a685c234af Mon Sep 17 00:00:00 2001 From: Rene2mt <76444659+Rene2mt@users.noreply.github.com> Date: Wed, 19 Jan 2022 22:55:06 -0500 Subject: [PATCH 27/34] Update docs/content/concepts/identifier-use/_index.md Co-authored-by: David Waltermire --- docs/content/concepts/identifier-use/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/concepts/identifier-use/_index.md b/docs/content/concepts/identifier-use/_index.md index ea3c1a2b28..a946ff895f 100644 --- a/docs/content/concepts/identifier-use/_index.md +++ b/docs/content/concepts/identifier-use/_index.md @@ -35,7 +35,7 @@ The [OSCAL Reference Index](/reference/latest/complete/xml-index/#/@uuid) provid #### Human-Oriented -OSCAL generally implements *`human-oriented`* identifiers as Token data types, which are non-colonized names (add link to data type). These *`human-oriented`* identifiers have the benefit of allowing authors to incorporate semantics that support readability and processing by humans. For example, control identifiers in a catalog may use a nomenclature that is familiar to the intended audience, allowing them to quickly determine what security control is being referred to, simply by its ID. +A *`human-oriented`* identifier incorporates semantics that support readability and processing by humans. OSCAL implements *`human-oriented`* identifiers as Token data types, which are non-colonized names (add link to data type). For example, control identifiers in a catalog may use a nomenclature that is familiar to the intended audience, allowing them to quickly determine what security control is being referred to, simply by its identifier value. The [OSCAL Reference Index](/reference/latest/complete/xml-index/#/@id) provides a comprehensive listing of the *`human-oriented`* IDs in OSCAL. References to these IDs are typically named according to the referenced object type (e.g., control) followed by “-id”, as seen here in the [Reference Index](/reference/latest/complete/xml-index/#/@control-id). From 1904a235abe3515ae311cf776d5d633d076e2c35 Mon Sep 17 00:00:00 2001 From: Rene2mt <76444659+Rene2mt@users.noreply.github.com> Date: Wed, 19 Jan 2022 22:56:41 -0500 Subject: [PATCH 28/34] Update docs/content/concepts/identifier-use/_index.md Co-authored-by: David Waltermire --- docs/content/concepts/identifier-use/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/concepts/identifier-use/_index.md b/docs/content/concepts/identifier-use/_index.md index a946ff895f..864af4b431 100644 --- a/docs/content/concepts/identifier-use/_index.md +++ b/docs/content/concepts/identifier-use/_index.md @@ -40,7 +40,7 @@ A *`human-oriented`* identifier incorporates semantics that support readability The [OSCAL Reference Index](/reference/latest/complete/xml-index/#/@id) provides a comprehensive listing of the *`human-oriented`* IDs in OSCAL. References to these IDs are typically named according to the referenced object type (e.g., control) followed by “-id”, as seen here in the [Reference Index](/reference/latest/complete/xml-index/#/@control-id). ### **Uniqueness** -OSCAL identifier uniqueness are categorized as *`locally-unique`* or *`globally-unique`*. As implied by the category name, *`locally-unique`* identifiers must be unique within the current document whereas *`globally-unique`* identifiers are guaranteed to be unique across all other identifiers. OSCAL’s *`machine-oriented`* UUID identifiers are always *`globally-unique`*. *`Human-oriented`* identifiers must be defined and managed organizationally and are more susceptible to identifier duplication or collisions. Thus, *`human-oriented`* identifiers are less likely to be *`globally-unique`*. +OSCAL identifier uniqueness is categorized as *`locally-unique`* or *`globally-unique`*. As implied by the category name, *`locally-unique`* identifiers must be unique within the current document, whereas *`globally-unique`* identifiers are guaranteed to be unique across all other identifiers. OSCAL’s *`machine-oriented`* UUID identifiers are always *`globally-unique`*. *`Human-oriented`* identifiers must be defined and managed organizationally and are more susceptible to identifier duplication or collisions. Thus, *`human-oriented`* identifiers are less likely or cannot be guaranteed to be *`globally-unique`*. ### **Scope** Identifiers are declared so that data items in OSCAL instances can be referenced accurately and consistently. In the most basic instance, references are made to data items in the same OSCAL instance, but because OSCAL supports instance importing, there are scenarios where data items in an external / imported OSCAL instance need to be referenced as well. Identifiers that are only intended for use within the same OSCAL instance are categorized as *`instance`* scope, but identifiers that can be referenced (from other OSCAL instances) are considered *`cross-instance`* scoped. While *`human-oriented`* identifiers might not be globally unique, they may be *`cross-instance`* scoped. In these cases, the appropriate import attribute (e.g. import, import-component-definitions, import-profile, import-ssp, and import-ap) should be used (similar to a namespacing) to deconflict identifiers with the same values in the associated OSCAL instances. This would allow for the same control IDs to be used and referenced in a profile and its imported catalog(s) for example. The tables below provides a summary of OSCAL unique identifier scoping. From 08225f91a43b82f2e2c021e84bc8376a1ef2fd8e Mon Sep 17 00:00:00 2001 From: Rene2mt <76444659+Rene2mt@users.noreply.github.com> Date: Wed, 19 Jan 2022 23:02:20 -0500 Subject: [PATCH 29/34] Update docs/content/concepts/identifier-use/_index.md Co-authored-by: Brad Hards --- docs/content/concepts/identifier-use/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/concepts/identifier-use/_index.md b/docs/content/concepts/identifier-use/_index.md index 864af4b431..2dcda10e7f 100644 --- a/docs/content/concepts/identifier-use/_index.md +++ b/docs/content/concepts/identifier-use/_index.md @@ -26,7 +26,7 @@ UUIDs were chosen because: - Programming interfaces exist in most programming environments to generate a UUID - UUIDs can be issued without a central authority -- UUIDs are represented in 128bits, providing for a large address space with low risk of identifier collisions for randomly generated values +- UUIDs are represented in 128 bits, providing for a large address space with low risk of identifier collisions for randomly generated values The opaque nature of UUIDs, which consist of a series of hexadecimal characters, makes them less than ideal for wildcard matching scenarios. Thus, their use in OSCAL is intended for identification only where an exact match is required. Where wildcard matching is needed, the other data elements associated with the entity should be evaluated for a match instead. From 057f681cfcd3c6e63e38a104f191323353f329de Mon Sep 17 00:00:00 2001 From: Rene2mt <76444659+Rene2mt@users.noreply.github.com> Date: Wed, 19 Jan 2022 23:24:13 -0500 Subject: [PATCH 30/34] Update docs/content/concepts/identifier-use/_index.md Co-authored-by: Brad Hards --- docs/content/concepts/identifier-use/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/concepts/identifier-use/_index.md b/docs/content/concepts/identifier-use/_index.md index 2dcda10e7f..923da4ef88 100644 --- a/docs/content/concepts/identifier-use/_index.md +++ b/docs/content/concepts/identifier-use/_index.md @@ -1,6 +1,6 @@ --- title: Identifier Use -description: Provides details on the scope an duniqueness of dientifiers used within the OSCAL models. +description: Provides details on the scope and uniqueness of identifiers used within the OSCAL models. suppresstopiclist: true weight: 50 toc: From 7f558516c46eabead2f2e38fefaad0c6e2127e91 Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Thu, 20 Jan 2022 00:26:03 -0500 Subject: [PATCH 31/34] identifier use page review edits --- .../content/concepts/identifier-use/_index.md | 227 ++++++------------ .../oscal-model-relationships.svg | 4 + 2 files changed, 71 insertions(+), 160 deletions(-) create mode 100644 docs/content/concepts/identifier-use/oscal-model-relationships.svg diff --git a/docs/content/concepts/identifier-use/_index.md b/docs/content/concepts/identifier-use/_index.md index 923da4ef88..0db6272f8e 100644 --- a/docs/content/concepts/identifier-use/_index.md +++ b/docs/content/concepts/identifier-use/_index.md @@ -14,199 +14,106 @@ sidenav: This page reviews important concepts to be aware of when declaring or referencing identifiers in OSCAL models, with in-depth explanations of identifier uniqueness and scope. ### **Identifier Type** -By design, OSCAL supports [*machine-oriented*](/concepts/identifier-use/#machine-oriented) and [*human-oriented*](/concepts/identifier-use/#human-oriented) identifiers. The OSCAL models dictate which are used for different data items. +By design, OSCAL supports [*machine-oriented*](#machine-oriented) and [*human-oriented*](#human-oriented) identifiers. The OSCAL models dictate which are used for different data items. #### Machine-Oriented -*Machine-oriented* identifiers provide a persistent identity for an entity within the OSCAL models, which can be used in other locations within related OSCAL models to reference the associated entity. - -These identifiers are intended to be auto-generated by tools when the entity is initially created. In OSCAL, a machine-oriented identifier is implemented using a Universally Unique Identifier (UUID) as defined by [RFC 4122](https://tools.ietf.org/html/rfc4122). A UUID is represented in OSCAL using the UUID datatype (provide link). +[*Machine-oriented*](#machine-oriented) identifiers provide a persistent identity for an entity within the OSCAL models, which can be used in other locations within related OSCAL models to reference the associated entity. +These identifiers are intended to be auto-generated by tools when the entity is initially created. In OSCAL, a machine-oriented identifier is implemented using a Universally Unique Identifier (UUID) as defined by [RFC 4122](https://tools.ietf.org/html/rfc4122). A UUID is represented in OSCAL using the [UUID datatype](/reference/datatypes/#uuid). UUIDs were chosen because: - - Programming interfaces exist in most programming environments to generate a UUID - UUIDs can be issued without a central authority - UUIDs are represented in 128 bits, providing for a large address space with low risk of identifier collisions for randomly generated values The opaque nature of UUIDs, which consist of a series of hexadecimal characters, makes them less than ideal for wildcard matching scenarios. Thus, their use in OSCAL is intended for identification only where an exact match is required. Where wildcard matching is needed, the other data elements associated with the entity should be evaluated for a match instead. +>>>>>>> d1b234ed (identifier use page review edits) +{{}}The opaque nature of UUIDs, which consist of a series of hexadecimal characters, makes them less than ideal for wildcard matching scenarios. Thus, their use in OSCAL is intended for identification only where an exact match is required. Where wildcard matching is needed, the other data elements associated with the entity should be evaluated for a match instead. {{}} -The [OSCAL Reference Index](/reference/latest/complete/xml-index/#/@uuid) provides a complete listing of UUIDs in OSCAL. References to these identifiers typically follow a naming convention of the object type followed by “-uuid”. For example, see the reference index for [location-uuid](/reference/latest/complete/xml-index/#/location-uuid). +The [OSCAL XML Reference Index](/reference/latest/complete/xml-index/#/@uuid) and [OSCAL JSON Reference Index](/reference/latest/complete/json-index/#/uuid) provide a listing of UUIDs in the core OSCAL models. References to these identifiers typically follow a naming convention of the object type followed by “-uuid”. For example, see the XML reference index for [location-uuid](/reference/latest/complete/xml-index/#/location-uuid) (or [location-uuids](/reference/latest/complete/json-index/#/uuid) in the JSON reference index). #### Human-Oriented -A *`human-oriented`* identifier incorporates semantics that support readability and processing by humans. OSCAL implements *`human-oriented`* identifiers as Token data types, which are non-colonized names (add link to data type). For example, control identifiers in a catalog may use a nomenclature that is familiar to the intended audience, allowing them to quickly determine what security control is being referred to, simply by its identifier value. +A [*human-oriented*](#human-oriented) identifier incorporates semantic that support readability and processing by humans. OSCAL implements [*human-oriented*](#human-oriented) identifiers as [Token](/reference/datatypes/#token) data types, which are non-colonized names. For example, control identifiers in a catalog may use a nomenclature that is familiar to the intended audience, allowing them to quickly determine what security control is being referred to, simply by its identifier value. -The [OSCAL Reference Index](/reference/latest/complete/xml-index/#/@id) provides a comprehensive listing of the *`human-oriented`* IDs in OSCAL. References to these IDs are typically named according to the referenced object type (e.g., control) followed by “-id”, as seen here in the [Reference Index](/reference/latest/complete/xml-index/#/@control-id). +The [OSCAL XML Reference Index](/reference/latest/complete/xml-index/#/@id) and [OSCAL JSON Reference Index](/reference/latest/complete/json-index/#/id) provide a comprehensive listing of the [*human-oriented*](#human-oriented) IDs in the core OSCAL models. References to these IDs are typically named according to the referenced object type (e.g., control) followed by “-id”, as seen here in the [XML Reference Index](/reference/latest/complete/xml-index/#/@control-id) (and likewise [JSON Reference Index](/reference/latest/complete/json-index/#/control-id) in the JSON reference index). ### **Uniqueness** -OSCAL identifier uniqueness is categorized as *`locally-unique`* or *`globally-unique`*. As implied by the category name, *`locally-unique`* identifiers must be unique within the current document, whereas *`globally-unique`* identifiers are guaranteed to be unique across all other identifiers. OSCAL’s *`machine-oriented`* UUID identifiers are always *`globally-unique`*. *`Human-oriented`* identifiers must be defined and managed organizationally and are more susceptible to identifier duplication or collisions. Thus, *`human-oriented`* identifiers are less likely or cannot be guaranteed to be *`globally-unique`*. +OSCAL identifier uniqueness is categorized as *locally-unique* or *globally-unique*. As implied by the category name, [*locally-unique*](#locally-unique) identifiers must be unique within the current document, whereas [*globally-unique*](#globally-unique) identifiers are guaranteed to be unique across all other identifiers. OSCAL’s [*machine-oriented*](#machine-oriented) UUID identifiers are always [*globally-unique*](#globally-unique). [*Human-oriented*](#human-oriented) identifiers must be defined and managed organizationally and are more susceptible to identifier duplication or collisions. Thus, [*human-oriented*](#human-oriented) identifiers are less likely or cannot be guaranteed to be [*globally-unique*](#globally-unique). ### **Scope** -Identifiers are declared so that data items in OSCAL instances can be referenced accurately and consistently. In the most basic instance, references are made to data items in the same OSCAL instance, but because OSCAL supports instance importing, there are scenarios where data items in an external / imported OSCAL instance need to be referenced as well. Identifiers that are only intended for use within the same OSCAL instance are categorized as *`instance`* scope, but identifiers that can be referenced (from other OSCAL instances) are considered *`cross-instance`* scoped. While *`human-oriented`* identifiers might not be globally unique, they may be *`cross-instance`* scoped. In these cases, the appropriate import attribute (e.g. import, import-component-definitions, import-profile, import-ssp, and import-ap) should be used (similar to a namespacing) to deconflict identifiers with the same values in the associated OSCAL instances. This would allow for the same control IDs to be used and referenced in a profile and its imported catalog(s) for example. The tables below provides a summary of OSCAL unique identifier scoping. + +Identifiers that are only intended for use within the same OSCAL instance are categorized as *instance* scope. However, since OSCAL supports composition relationships, there are cases where identifiers in a source OSCAL instance need to be referenced from other OSCAL instances. These are considered *cross-instance* scoped identifier references. The figure below illustrates how OSCAL models relationships are established through import and link mechanisms. + +![A diagram depicting the relationships between OSCAL models. The solid black arrows depict relationships implemented via the import mechanism (e.g., import, import-profile, import-component-definition, import-ssp, and import-ap), whereas the dashed red line arrows illustrate relationships established through links.](oscal-model-relationships.svg) + +The following import types are supported: +- import - see [XML index](/reference/latest/complete/xml-index/#/import) or [JSON index](/reference/latest/complete/json-index/#/imports) +- import-component-definition - see [XML index](/reference/latest/complete/xml-index/#/import-component-definition) or [JSON index](/reference/latest/complete/json-index/#/import-component-definitions) +- import-profile - see [XML index](/reference/latest/complete/xml-index/#/import-profile) or [JSON index](/reference/latest/complete/json-index/#/import-profile) +- import-ssp - see [XML index](/reference/latest/complete/xml-index/#/import-ssp) or [JSON index](/reference/latest/complete/json-index/#/import-ssp) +- import-ap - see [XML index](/reference/latest/complete/xml-index/#/import-ap) or [JSON index](/reference/latest/complete/json-index/#/import-ap) + +When implementing [*cross-instance*](#cross-instance) references, the appropriate import attribute should be used (similar to a namespacing) to deconflict identifiers with the same values in the associated OSCAL instances. This is particularly important for [*human-oriented*](#human-oriented) identifiers that may not be globally unique but still require [*cross-instance*](#cross-instance) scoping. For example, this technique allows for the same control IDs to be used and referenced in a profile and its imported catalog(s) without conflict. + +The next secttion describes the identifier scoping per defining model. #### **Catalog Identifiers** -Identifiers defined in a catalog may be referenced locally or from an importing profile. - -|**Defining Model**|**Identifier**|**Catalog**|**Profile**|**Component**|**SSP**|**AP**|**AR**|**POA&M**| -|:------|:-------|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:| -|Catalog|Location uuid|☑|☑|||||| -|Catalog|Party uuid|☑|☑|||||| -|Catalog|Role id|☑|☑|||||| -|Catalog|Resource uuid|☑|☑|||||| -|Catalog|Property uuid|☑|☑|||||| -|Catalog|Document Identifier scheme|☑|☑|||||| -|Catalog|Part id|☑|☑|||||| -|Catalog|Param id|☑|☑|||||| -|Catalog|Catalog uuid|☑|☑|||||| -|Catalog|Control id|☑|☑|||||| -|Catalog|Group id|☑|☑|||||| +Identifiers defined in a catalog may be referenced locally or from an importing profile ([see the diagram in theScope section](#scope)). Additionally, identifiers defined in a catalog may be referenced in other upstream OSCAL instances in a hierarchical set of associated OSCAL documents (e.g., SSPs, assessment plans, assessment results, and POA&Ms). + +|**Defining Model**|**Identifier Type**|**Identifiers**| +|:------|:-------|:-----:| +|Catalog|Machine-Oriented|[XML Index](/reference/latest/catalog/xml-index/#/@uuid) | [JSON Index](/reference/latest/catalog/json-index/#/uuid)| +|Catalog|Human-Oriented|[XML Index](/reference/latest/catalog/xml-index/#/@id) | [JSON Index](/reference/latest/catalog/json-index/#/id)| #### **Profile Identifiers** -Identifiers defined in a profile may be referenced locally or from an importing profile or SSP. - -|**Defining Model**|**Identifier**|**Catalog**|**Profile**|**Component**|**SSP**|**AP**|**AR**|**POA&M**| -|:------|:-------|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:| -|Profile|Location uuid||☑||☑|||| -|Profile|Party uuid||☑||☑|||| -|Profile|Role id||☑||☑|||| -|Profile|Resource uuid||☑||☑|||| -|Profile|Property uuid||☑||☑|||| -|Profile|Document Identifier scheme||☑||☑|||| -|Profile|Part id||☑||☑|||| -|Profile|Param id||☑||☑|||| -|Profile|Profile uuid||☑||☑|||| -|Profile|Group id||☑||☑|||| +Identifiers defined in a profile may be referenced locally or from an importing profile or SSP ([see the diagram in the Scope section](#scope)). Component definitions may also reference these identifiers through its [control-implementation - source](/reference/latest/component-definition/xml-reference/#/component-definition/component/control-implementation/@source) reference to the profile. The other OSCAL models in the table can also reference these identifiers via the hierarchical set of associated OSCAL documents. + +|**Defining Model**|**Identifier Type**|**Identifiers**| +|:------|:-------|:-----:| +|Profile|Machine-Oriented|[XML Index](/reference/latest/profile/xml-index/#/@uuid) | [JSON Index](/reference/latest/profile/json-index/#/uuid)| +|Profile|Human-Oriented|[XML Index](/reference/latest/profile/xml-index/#/@id) | [JSON Index](/reference/latest/profile/json-index/#/id)| #### **Component Definition Identifiers** -Identifiers defined in a component definition may be referenced locally or from an importing component definition instance. - -|**Defining Model**|**Identifier**|**Catalog**|**Profile**|**Component**|**SSP**|**AP**|**AR**|**POA&M**| -|:------|:-------|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:| -|Component Definition|Location uuid|||☑||||| -|Component Definition|Party uuid|||☑||||| -|Component Definition|Role id|||☑||||| -|Component Definition|Resource uuid|||☑||||| -|Component Definition|Property uuid|||☑||||| -|Component Definition|Document Identifier scheme|||☑||||| -|Component Definition|Part id|||☑||||| -|Component Definition|Param id|||☑||||| -|Component Definition|Component Definition uuid|||☑||||| -|Component Definition|Component uuid|||☑||||| -|Component Definition|Capability uuid|||☑||||| -|Component Definition|Control Implementation Set uuid|||☑||||| -|Component Definition|Control Implementation uuid|||☑||||| +Identifiers defined in a component definition may be referenced locally or from an importing component definition instance ([see the diagram in the Scope section](#scope)). SSPs may also reference identifiers from a component definitions through its implementation of links for a given component. + +|**Defining Model**|**Identifier Type**|**Identifiers**| +|:------|:-------|:-----:| +|Component Definition|Machine-Oriented|[XML Index](/reference/latest/component-definition/xml-index/#/@uuid) | [JSON Index](/reference/latest/component-definition/json-index/#/uuid)| +|Component Definition|Human-Oriented|[XML Index](/reference/latest/component-definition/xml-index/#/@id) | [JSON Index](/reference/latest/component-definition/json-index/#/id)| #### **SSP Identifiers** -Identifiers defined in an SSP may be referenced locally or from an importing AP or POA&M. - -|**Defining Model**|**Identifier**|**Catalog**|**Profile**|**Component**|**SSP**|**AP**|**AR**|**POA&M**| -|:------|:-------|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:| -|SSP|Location uuid||||☑|☑||☑| -|SSP|Party uuid||||☑|☑||☑| -|SSP|Role id||||☑|☑||☑| -|SSP|Resource uuid||||☑|☑||☑| -|SSP|Property uuid||||☑|☑||☑| -|SSP|Document Identifier scheme||||☑|☑||☑| -|SSP|Part id||||☑|☑||☑| -|SSP|Param id||||☑|☑||☑| -|SSP|SSP uuid||||☑|☑||☑| -|SSP|Information Type uuid||||☑|☑||☑| -|SSP|Information Type Systematized id||||☑|☑||☑| -|SSP|Diagram uuid||||☑|☑||☑| -|SSP|Leveraged Authorization uuid||||☑|☑||☑| -|SSP|Control Requirement uuid||||☑|☑||☑| -|SSP|By-Component uuid||||☑|☑||☑| -|SSP|Provided uuid||||☑|☑||☑| -|SSP|Responsibility uuid||||☑|☑||☑| -|SSP|Inherited uuid||||☑|☑||☑| -|SSP|Satisfied uuid||||☑|☑||☑| +Identifiers defined in an SSP may be referenced locally or from an importing AP or POA&M ([see the diagram in the Scope section](#scope)). These identifiers can also be referenced from the AR through its hierarchical relationship with AP. + +|**Defining Model**|**Identifier Type**|**Identifiers**| +|:------|:-------|:-----:| +|SSP|Machine-Oriented|[XML Index](/reference/latest/system-security-plan/xml-index/#/@uuid) | [JSON Index](/reference/latest/system-security-plan/json-index/#/uuid)| +|SSP|Human-Oriented|[XML Index](/reference/latest/system-security-plan/xml-index/#/@id) | [JSON Index](/reference/latest/system-security-plan/json-index/#/id)| #### **AP Identifiers** -Identifiers defined in an AP may be referenced locally or from an importing AR. - -|**Defining Model**|**Identifier**|**Catalog**|**Profile**|**Component**|**SSP**|**AP**|**AR**|**POA&M**| -|:------|:-------|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:| -|AP|Location uuid|||||☑|☑|| -|AP|Party uuid|||||☑|☑|| -|AP|Role id|||||☑|☑|| -|AP|Resource uuid|||||☑|☑|| -|AP|Property uuid|||||☑|☑|| -|AP|Document Identifier scheme|||||☑|☑|| -|AP|Assessment Method uuid|||||☑|☑|| -|AP|Assessment Activity uuid|||||☑|☑|| -|AP|Step uuid|||||☑|☑|| -|AP|Task uuid|||||☑|☑|| -|AP|Assessment Subject Placeholder uuid||||☑|☑|| -|AP|Assessment Platform uuid|||||☑|☑|| -|AP|Observation uuid|||||☑|☑|| -|AP|Risk uuid|||||☑|☑|| -|AP|Mitigating Factor uuid|||||☑|☑|| -|AP|Implementation uuid|||||☑|☑|| -|AP|Risk Log Entry uuid|||||☑|☑|| -|AP|Remediation uuid|||||☑|☑|| -|AP|Required Asset uuid|||||☑|☑|| -|AP|Part uuid|||||☑|☑|| -|AP|Assessment Plan uuid|||||☑|☑|| +Identifiers defined in an AP may be referenced locally or from an importing AR ([see the diagram in the Scope section](#scope)). + +|**Defining Model**|**Identifier Type**|**Identifiers**| +|:------|:-------|:-----:| +|AP|Machine-Oriented|[XML Index](/reference/latest/assessment-plan/xml-index/#/@uuid) | [JSON Index](/reference/latest/assessment-plan/json-index/#/uuid)| +|AP|Human-Oriented|[XML Index](/reference/latest/assessment-plan/xml-index/#/@id) | [JSON Index](/reference/latest/assessment-plan/json-index/#/id)| #### **AR Identifiers** -Identifiers defined in an AR may be referenced locally or from an importing POA&M. - -|**Defining Model**|**Identifier**|**Catalog**|**Profile**|**Component**|**SSP**|**AP**|**AR**|**POA&M**| -|:------|:-------|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:| -|AR|Location uuid||||||☑|☑| -|AR|Party uuid||||||☑|☑| -|AR|Role id||||||☑|☑| -|AR|Resource uuid||||||☑|☑| -|AR|Property uuid||||||☑|☑| -|AR|Document Identifier scheme||||||☑|☑| -|AR|Assessment Method uuid||||||☑|☑| -|AR|Assessment Activity uuid||||||☑|☑| -|AR|Step uuid||||||☑|☑| -|AR|Task uuid||||||☑|☑| -|AR|Assessment Subject Placeholder uuid|||||☑|☑| -|AR|Assessment Platform uuid||||||☑|☑| -|AR|Observation uuid||||||☑|☑| -|AR|Risk uuid||||||☑|☑| -|AR|Mitigating Factor uuid||||||☑|☑| -|AR|Implementation uuid||||||☑|☑| -|AR|Risk Log Entry uuid||||||☑|☑| -|AR|Remediation uuid||||||☑|☑| -|AR|Required Asset uuid||||||☑|☑| -|AR|Part uuid||||||☑|☑| -|AR|Assessment Results uuid||||||☑|☑| -|AR|Assessment Result uuid||||||☑|☑| -|AR|Assessment Log Entry uuid||||||☑|☑| -|AR|Finding uuid||||||☑|☑| +Identifiers defined in an AR may be referenced locally ([see the diagram in the Scope section](#scope)). However, observations, risks, and findings may also be referenced in the POA&M. + +|**Defining Model**|**Identifier Type**|**Identifiers**| +|:------|:-------|:-----:| +|AR|Machine-Oriented|[XML Index](/reference/latest/assessment-results/xml-index/#/@uuid) | [JSON Index](/reference/latest/assessment-results/json-index/#/uuid)| +|AR|Human-Oriented|[XML Index](/reference/latest/assessment-results/xml-index/#/@id) | [JSON Index](/reference/latest/assessment-results/json-index/#/id)| #### **POA&M Identifiers** -Identifiers defined in a POA&M may be referenced locally. - -|**Defining Model**|**Identifier**|**Catalog**|**Profile**|**Component**|**SSP**|**AP**|**AR**|**POA&M**| -|:------|:-------|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:| -|POA&M|Location uuid|||||||☑| -|POA&M|Party uuid|||||||☑| -|POA&M|Role id|||||||☑| -|POA&M|Resource uuid|||||||☑| -|POA&M|Property uuid|||||||☑| -|POA&M|Document Identifier scheme|||||||☑| -|POA&M|Assessment Method uuid|||||||☑| -|POA&M|Assessment Activity uuid|||||||☑| -|POA&M|Step uuid|||||||☑| -|POA&M|Task uuid|||||||☑| -|POA&M|Assessment Subject Placeholder uuid||||||☑| -|POA&M|Assessment Platform uuid|||||||☑| -|POA&M|Observation uuid|||||||☑| -|POA&M|Risk uuid|||||||☑| -|POA&M|Mitigating Factor uuid|||||||☑| -|POA&M|Implementation uuid|||||||☑| -|POA&M|Risk Log Entry uuid|||||||☑| -|POA&M|Remediation uuid|||||||☑| -|POA&M|Required Asset uuid|||||||☑| -|POA&M|Part uuid|||||||☑| -|POA&M|POA&M uuid|||||||☑| -|POA&M|POA&M Item uuid|||||||☑| +Identifiers defined in a POA&M may be referenced locally ([see the diagram in the Scope section](#scope)). However, observations, risks, and poam items may also be referenced in the AR. -### **Consistency** -Indicates how the identifier (value) should be managed across revisions of the same document. In general, OSCAL identifiers have *`per-subject`* consistency, meaning that object identifiers (whether ID or UUIDs) should remain the same across minor of an OSCAL document IF the identifier refers to the same object (e.g., same location must have the same UUID or same control must have the same control ID as a document is revised). +|**Defining Model**|**Identifier Type**|**Identifiers**| +|:------|:-------|:-----:| +|POA&M|Machine-Oriented|[XML Index](/reference/latest/plan-of-action-and-milestones/xml-index/#/@uuid) | [JSON Index](/reference/latest/plan-of-action-and-milestones/json-index/#/uuid)| +|POA&M|Human-Oriented|[XML Index](/reference/latest/plan-of-action-and-milestones/xml-index/#/@id) | [JSON Index](/reference/latest/plan-of-action-and-milestones/json-index/#/id)| +### **Consistency** +Identifier (value) must be managed across revisions of the same document. In general, [OSCAL identifiers](/concepts/layer/overview/#identifier-use) have *per-subject* consistency. They should only be changed if the underlying identified subject has changed in a significant way that no longer represents the same identified subject. diff --git a/docs/content/concepts/identifier-use/oscal-model-relationships.svg b/docs/content/concepts/identifier-use/oscal-model-relationships.svg new file mode 100644 index 0000000000..a6bbc35f3f --- /dev/null +++ b/docs/content/concepts/identifier-use/oscal-model-relationships.svg @@ -0,0 +1,4 @@ + + + +
import-profile
import-profile
Catalog
Catalog
import
import
import
import
Profile
Profile
SSP
SSP
Component Definition
Component Def...
link
link
POAM
POAM
import-ap
import-ap
AR
AR
AP
AP
import-component-definition
import-component-definition
import-ssp
import-ssp
control implementation source
control implementation source
observations, risks, findings/poam items
observations, risks, findings/poam itemsText is not SVG - cannot display \ No newline at end of file From 673e910ba2970b689e69a60d8ee4367b0311665e Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Thu, 20 Jan 2022 22:58:51 -0500 Subject: [PATCH 32/34] identifier documentation updates --- .../content/concepts/identifier-use/_index.md | 24 ++- .../oscal-model-relationships.svg | 2 +- .../oscal_assessment-common_metaschema.xml | 183 ++++-------------- .../oscal_assessment-plan_metaschema.xml | 5 +- .../oscal_assessment-results_metaschema.xml | 45 +---- src/metaschema/oscal_catalog_metaschema.xml | 10 +- src/metaschema/oscal_component_metaschema.xml | 39 +--- .../oscal_control-common_metaschema.xml | 15 +- ...oscal_implementation-common_metaschema.xml | 52 ++--- src/metaschema/oscal_metadata_metaschema.xml | 52 ++--- src/metaschema/oscal_poam_metaschema.xml | 28 +-- src/metaschema/oscal_profile_metaschema.xml | 15 +- src/metaschema/oscal_ssp_metaschema.xml | 96 ++------- 13 files changed, 134 insertions(+), 432 deletions(-) diff --git a/docs/content/concepts/identifier-use/_index.md b/docs/content/concepts/identifier-use/_index.md index 0db6272f8e..322ce7fa65 100644 --- a/docs/content/concepts/identifier-use/_index.md +++ b/docs/content/concepts/identifier-use/_index.md @@ -40,11 +40,15 @@ A [*human-oriented*](#human-oriented) identifier incorporates semantic that supp The [OSCAL XML Reference Index](/reference/latest/complete/xml-index/#/@id) and [OSCAL JSON Reference Index](/reference/latest/complete/json-index/#/id) provide a comprehensive listing of the [*human-oriented*](#human-oriented) IDs in the core OSCAL models. References to these IDs are typically named according to the referenced object type (e.g., control) followed by “-id”, as seen here in the [XML Reference Index](/reference/latest/complete/xml-index/#/@control-id) (and likewise [JSON Reference Index](/reference/latest/complete/json-index/#/control-id) in the JSON reference index). ### **Uniqueness** -OSCAL identifier uniqueness is categorized as *locally-unique* or *globally-unique*. As implied by the category name, [*locally-unique*](#locally-unique) identifiers must be unique within the current document, whereas [*globally-unique*](#globally-unique) identifiers are guaranteed to be unique across all other identifiers. OSCAL’s [*machine-oriented*](#machine-oriented) UUID identifiers are always [*globally-unique*](#globally-unique). [*Human-oriented*](#human-oriented) identifiers must be defined and managed organizationally and are more susceptible to identifier duplication or collisions. Thus, [*human-oriented*](#human-oriented) identifiers are less likely or cannot be guaranteed to be [*globally-unique*](#globally-unique). +OSCAL identifier uniqueness is categorized as *locally-unique* or *globally-unique*. As implied by the category name, [*locally-unique*](#locally-unique) identifiers must be unique within the current document, whereas [*globally-unique*](#globally-unique) identifiers are guaranteed to be unique across all other identifiers. OSCAL’s [*machine-oriented*](#machine-oriented) UUID identifiers are always [*globally-unique*](#globally-unique). [*Human-oriented*](#human-oriented) identifiers must be defined and managed organizationally and are more susceptible to identifier duplication or collisions. Thus, [*human-oriented*](#human-oriented) identifiers are less likely or cannot be guaranteed to be [*globally-unique*](#globally-unique). ### **Scope** +<<<<<<< HEAD Identifiers that are only intended for use within the same OSCAL instance are categorized as *instance* scope. However, since OSCAL supports composition relationships, there are cases where identifiers in a source OSCAL instance need to be referenced from other OSCAL instances. These are considered *cross-instance* scoped identifier references. The figure below illustrates how OSCAL models relationships are established through import and link mechanisms. +======= +Identifiers that are only intended for use within the same OSCAL instance are categorized as *instance* scope. However, since OSCAL supports composition relationships, there are many cases where identifiers in a source OSCAL instance need to be referenced from other OSCAL instances. These are considered *cross-instance* scoped identifier references. The figure below illustrates how the core OSCAL models relationships are established through import and link mechanisms, enabling [*cross-instance*](#cross-instance) references. +>>>>>>> 59a25042 (identifier documentation updates) ![A diagram depicting the relationships between OSCAL models. The solid black arrows depict relationships implemented via the import mechanism (e.g., import, import-profile, import-component-definition, import-ssp, and import-ap), whereas the dashed red line arrows illustrate relationships established through links.](oscal-model-relationships.svg) @@ -55,12 +59,12 @@ The following import types are supported: - import-ssp - see [XML index](/reference/latest/complete/xml-index/#/import-ssp) or [JSON index](/reference/latest/complete/json-index/#/import-ssp) - import-ap - see [XML index](/reference/latest/complete/xml-index/#/import-ap) or [JSON index](/reference/latest/complete/json-index/#/import-ap) -When implementing [*cross-instance*](#cross-instance) references, the appropriate import attribute should be used (similar to a namespacing) to deconflict identifiers with the same values in the associated OSCAL instances. This is particularly important for [*human-oriented*](#human-oriented) identifiers that may not be globally unique but still require [*cross-instance*](#cross-instance) scoping. For example, this technique allows for the same control IDs to be used and referenced in a profile and its imported catalog(s) without conflict. +When implementing [*cross-instance*](#cross-instance) references, identifier must be referenced in the context of the containing resource. The appropriate import attribute should be used (similar to a namespacing) to deconflict identifiers with the same values in the associated OSCAL instances. This is particularly important for [*human-oriented*](#human-oriented) identifiers that may not be globally unique but still require [*cross-instance*](#cross-instance) scoping. For example, this technique allows for the same control IDs to be used and referenced in a profile and its imported catalog(s) without conflict. -The next secttion describes the identifier scoping per defining model. +The next section describes the identifier scoping per defining model. #### **Catalog Identifiers** -Identifiers defined in a catalog may be referenced locally or from an importing profile ([see the diagram in theScope section](#scope)). Additionally, identifiers defined in a catalog may be referenced in other upstream OSCAL instances in a hierarchical set of associated OSCAL documents (e.g., SSPs, assessment plans, assessment results, and POA&Ms). +Identifiers defined in a catalog may be referenced locally or from an importing profile ([see the diagram in the Scope section](#scope)). Additionally, identifiers defined in a catalog may be referenced in other upstream OSCAL instances in a hierarchical set of associated OSCAL documents (e.g., SSPs, assessment plans, assessment results, and POA&Ms). The table below provides a listing of the core OSCAL catalog model identifiers. |**Defining Model**|**Identifier Type**|**Identifiers**| |:------|:-------|:-----:| @@ -68,7 +72,7 @@ Identifiers defined in a catalog may be referenced locally or from an importing |Catalog|Human-Oriented|[XML Index](/reference/latest/catalog/xml-index/#/@id) | [JSON Index](/reference/latest/catalog/json-index/#/id)| #### **Profile Identifiers** -Identifiers defined in a profile may be referenced locally or from an importing profile or SSP ([see the diagram in the Scope section](#scope)). Component definitions may also reference these identifiers through its [control-implementation - source](/reference/latest/component-definition/xml-reference/#/component-definition/component/control-implementation/@source) reference to the profile. The other OSCAL models in the table can also reference these identifiers via the hierarchical set of associated OSCAL documents. +Identifiers defined in a profile may be referenced locally or from an importing profile or SSP ([see the diagram in the Scope section](#scope)). Component definitions can reference these identifiers through its [control-implementation - source](/reference/latest/component-definition/xml-reference/#/component-definition/component/control-implementation/@source) reference to the profile. Other upstream OSCAL models, including assessment plans, assessment results, and POA&Ms can also reference these profile identifiers via the hierarchical set of associated OSCAL documents. The table below provides a listing of the core OSCAL profile model identifiers. |**Defining Model**|**Identifier Type**|**Identifiers**| |:------|:-------|:-----:| @@ -76,7 +80,7 @@ Identifiers defined in a profile may be referenced locally or from an importing |Profile|Human-Oriented|[XML Index](/reference/latest/profile/xml-index/#/@id) | [JSON Index](/reference/latest/profile/json-index/#/id)| #### **Component Definition Identifiers** -Identifiers defined in a component definition may be referenced locally or from an importing component definition instance ([see the diagram in the Scope section](#scope)). SSPs may also reference identifiers from a component definitions through its implementation of links for a given component. +Identifiers defined in a component definition may be referenced locally or from an importing component definition instance ([see the diagram in the Scope section](#scope)). SSPs may also reference identifiers from a component definitions through its implementation of links for a given component.Other upstream OSCAL models, including assessment plans, assessment results, and POA&Ms can also reference these component definition indirectly (e.g., via reference to an SSP component that has a a link to a component definition). The table below provides a listing of the core OSCAL component definition model identifiers. |**Defining Model**|**Identifier Type**|**Identifiers**| |:------|:-------|:-----:| @@ -84,7 +88,7 @@ Identifiers defined in a component definition may be referenced locally or from |Component Definition|Human-Oriented|[XML Index](/reference/latest/component-definition/xml-index/#/@id) | [JSON Index](/reference/latest/component-definition/json-index/#/id)| #### **SSP Identifiers** -Identifiers defined in an SSP may be referenced locally or from an importing AP or POA&M ([see the diagram in the Scope section](#scope)). These identifiers can also be referenced from the AR through its hierarchical relationship with AP. +Identifiers defined in an SSP may be referenced locally or from an importing AP or POA&M ([see the diagram in the Scope section](#scope)). SSP identifiers can also be referenced from the AR through its hierarchical relationship with AP. The table below provides a listing of the core OSCAL SSP model identifiers. |**Defining Model**|**Identifier Type**|**Identifiers**| |:------|:-------|:-----:| @@ -92,7 +96,7 @@ Identifiers defined in an SSP may be referenced locally or from an importing AP |SSP|Human-Oriented|[XML Index](/reference/latest/system-security-plan/xml-index/#/@id) | [JSON Index](/reference/latest/system-security-plan/json-index/#/id)| #### **AP Identifiers** -Identifiers defined in an AP may be referenced locally or from an importing AR ([see the diagram in the Scope section](#scope)). +Identifiers defined in an AP may be referenced locally or from an importing AR ([see the diagram in the Scope section](#scope)). The table below provides a listing of the core OSCAL AP model identifiers. |**Defining Model**|**Identifier Type**|**Identifiers**| |:------|:-------|:-----:| @@ -100,7 +104,7 @@ Identifiers defined in an AP may be referenced locally or from an importing AR ( |AP|Human-Oriented|[XML Index](/reference/latest/assessment-plan/xml-index/#/@id) | [JSON Index](/reference/latest/assessment-plan/json-index/#/id)| #### **AR Identifiers** -Identifiers defined in an AR may be referenced locally ([see the diagram in the Scope section](#scope)). However, observations, risks, and findings may also be referenced in the POA&M. +Identifiers defined in an AR may be referenced locally ([see the diagram in the Scope section](#scope)). However, observations, risks, and findings may also be referenced implicitly in the POA&M. The table below provides a listing of the core OSCAL AR model identifiers. |**Defining Model**|**Identifier Type**|**Identifiers**| |:------|:-------|:-----:| @@ -108,7 +112,7 @@ Identifiers defined in an AR may be referenced locally ([see the diagram in the |AR|Human-Oriented|[XML Index](/reference/latest/assessment-results/xml-index/#/@id) | [JSON Index](/reference/latest/assessment-results/json-index/#/id)| #### **POA&M Identifiers** -Identifiers defined in a POA&M may be referenced locally ([see the diagram in the Scope section](#scope)). However, observations, risks, and poam items may also be referenced in the AR. +Identifiers defined in a POA&M are only referenced locally ([see the diagram in the Scope section](#scope)). The table below provides a listing of the core OSCAL POA&M model identifiers. |**Defining Model**|**Identifier Type**|**Identifiers**| |:------|:-------|:-----:| diff --git a/docs/content/concepts/identifier-use/oscal-model-relationships.svg b/docs/content/concepts/identifier-use/oscal-model-relationships.svg index a6bbc35f3f..5fa0fa4236 100644 --- a/docs/content/concepts/identifier-use/oscal-model-relationships.svg +++ b/docs/content/concepts/identifier-use/oscal-model-relationships.svg @@ -1,4 +1,4 @@ -
import-profile
import-profile
Catalog
Catalog
import
import
import
import
Profile
Profile
SSP
SSP
Component Definition
Component Def...
link
link
POAM
POAM
import-ap
import-ap
AR
AR
AP
AP
import-component-definition
import-component-definition
import-ssp
import-ssp
control implementation source
control implementation source
observations, risks, findings/poam items
observations, risks, findings/poam itemsText is not SVG - cannot display \ No newline at end of file +
import-profile
import-profile
Catalog
Catalog
import
import
import
import
Profile
Profile
SSP
SSP
Component Definition
Component Def...
link
link
import-ssp
import-ssp
POAM
POAM
import-ap
import-ap
AR
AR
AP
AP
import-component-definition
import-component-definition
import-ssp
import-ssp
control implementation source
control implementation source
observations, risks, findings/poam items
observations, risks, findings/poam itemsText is not SVG - cannot display \ No newline at end of file diff --git a/src/metaschema/oscal_assessment-common_metaschema.xml b/src/metaschema/oscal_assessment-common_metaschema.xml index 247deef528..84b3912c75 100644 --- a/src/metaschema/oscal_assessment-common_metaschema.xml +++ b/src/metaschema/oscal_assessment-common_metaschema.xml @@ -78,10 +78,7 @@ Assessment Method Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment method elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment method can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment method elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment method can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -108,10 +105,7 @@ Assessment Activity Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment activity elsewhere in this or other OSCAL instances. The locally defined UUID of the activity can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique> identifier with cross-instance scope that can be used to reference this assessment activity elsewhere in this or other OSCAL instances. The locally defined UUID of the activity can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -135,10 +129,7 @@ Step Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this step elsewhere in this or other OSCAL instances. The locally defined UUID of the step (in a series of steps) can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this step elsewhere in this or other OSCAL instances. The locally defined UUID of the step (in a series of steps) can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -217,10 +208,7 @@ Task Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this task elsewhere in this or other OSCAL instances. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this task elsewhere in this or other OSCAL instances. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. Task Type @@ -304,13 +292,8 @@ Task Universally Unique Identifier Reference - - A machine-oriented identifier reference to a unique task. - - -

Type: machine-oriented

-

Source: cross-instance - References a unique task defined in this or other OSCAL instances

- + + A machine-oriented identifier reference to a unique task. @@ -326,13 +309,8 @@ Activity Universally Unique Identifier Reference - - A machine-oriented identifier reference to an activity defined in the list of activities. - - -

Type: machine-oriented

-

Source: cross-instance - References an activity (in a list of actifites) defined in this or other OSCAL instances

- + + A machine-oriented identifier reference to an activity defined in the list of activities. @@ -525,10 +503,7 @@ Assessment Subject Placeholder Universally Unique Identifier - A machine-oriented, globally unique identifier for a set of assessment subjects that will be identified by a task or an activity that is part of a task. The locally defined UUID of the assessment subject placeholder can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier for a set of assessment subjects that will be identified by a task or an activity that is part of a task. The locally defined UUID of the assessment subject placeholder can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -542,10 +517,7 @@ Task Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference (in this or other OSCAL instances) an assessment activity to be performed as part of the event. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference (in this or other OSCAL instances) an assessment activity to be performed as part of the event. The locally defined UUID of the task can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -626,13 +598,8 @@ Subject Universally Unique Identifier Reference - - A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. - - -

Type: machine-oriented

-

Source: cross-instance - References a component, inventory-item, location, party, user, or resource identifer defined in this or other OSCAL instances

- + + A machine-oriented identifier reference to a component, inventory-item, location, party, user, or resource using it's UUID. @@ -652,13 +619,8 @@ Identifies the Subject - - A human-oriented identifier reference to a resource. Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. - - -

Type: human-oriented

-

Source: cross-instance - References a resource

- + + A human-oriented identifier reference to a resource. Use type to indicate whether the identified resource is a component, inventory item, location, user, or something else. type @@ -703,10 +665,7 @@ Assessment Platform Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment platform elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment platform can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment platform elsewhere in this or other OSCAL instances. The locally defined UUID of the assessment platform can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -725,13 +684,8 @@ Component Universally Unique Identifier Reference - - A machine-oriented identifier reference to a component that is implemented as part of an inventory item. - - -

Type: machine-oriented

-

Source: cross-instance - References a component, in this or other OSCAL instances, that is implemented as part of an inventory item

- + + A machine-oriented identifier reference to a component that is implemented as part of an inventory item. @@ -787,13 +741,8 @@ Finding Target Identifier Reference - - A machine-oriented identifier reference for a specific target qualified by the type. - - -

Type: human-oriented

-

Source: cross-instance - References a finding target

- + + A machine-oriented identifier reference for a specific target qualified by the type. @@ -856,10 +805,7 @@ Observation Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. The locally defined UUID of the observation can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this observation elsewhere in this or other OSCAL instances. The locally defined UUID of the observation can be used to reference the data item locally or globally (e.g., in an imorted 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. @@ -999,13 +945,8 @@ Actor Universally Unique Identifier Reference - - A machine-oriented identifier reference to the tool or person based on the associated type. - - -

Type: machine-oriented

-

Source: cross-instance - References a tool or person defined in this or other OSCAL instances

- + + A machine-oriented identifier reference to the tool or person based on the associated type. Actor Role @@ -1026,13 +967,8 @@ Identifies an individual task for which the containing object is a consequence of. Task Universally Unique Identifier Reference - - A machine-oriented identifier reference to a unique task. - - -

Type: machine-oriented

-

Source: cross-instance - References a unique task defined in this or other OSCAL instances

- + + A machine-oriented identifier reference to a unique task. @@ -1060,13 +996,8 @@ Assessment Subject Placeholder Universally Unique Identifier Reference - - A machine-oriented identifier reference to a unique assessment subject placeholder defined by this task. - - -

Type: machine-oriented

-

Source: cross-instance - References a unique assessment subject placeholder defined in this or other OSCAL instances

- + + A machine-oriented identifier reference to a unique assessment subject placeholder defined by this task. @@ -1116,10 +1047,7 @@ Risk Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk elsewhere in this or other OSCAL instances. The locally defined UUID of the risk can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk elsewhere in this or other OSCAL instances. The locally defined UUID of the risk can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -1177,18 +1105,12 @@ Mitigating Factor Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mitigating factor elsewhere in this or other OSCAL instances. The locally defined UUID of the mitigating factor can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this mitigating factor elsewhere in this or other OSCAL instances. The locally defined UUID of the mitigating factor can be used to reference the data item locally or globally (e.g., in an imported 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. Implementation UUID - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this implementation statement elsewhere in this or other OSCAL instances. The locally defined UUID of the implementation statement can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this implementation statement elsewhere in this or other OSCAL instancess. The locally defined UUID of the implementation statement can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -1230,10 +1152,7 @@ Risk Log Entry Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk log entry elsewhere in this or other OSCAL instances. The locally defined UUID of the risk log entry can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this risk log entry elsewhere in this or other OSCAL instances. The locally defined UUID of the risk log entry can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -1273,13 +1192,8 @@ Response Universally Unique Identifier Reference - - A machine-oriented identifier reference to a unique risk response. - - -

Type: machine-oriented

-

Source: cross-instance - References a unique risk response defined in this or other OSCAL instances

- + + A machine-oriented identifier reference to a unique risk response. @@ -1327,13 +1241,8 @@ Observation Universally Unique Identifier Reference - - A machine-oriented identifier reference to an observation defined in the list of observations. - - -

Type: machine-oriented

-

Source: cross-instance - References an observation defined in this or other OSCAL instances

- + + A machine-oriented identifier reference to an observation defined in the list of observations. @@ -1353,13 +1262,8 @@ Used to indicate who created a log entry in what role. Party UUID Reference - - A machine-oriented identifier reference to the party who is making the log entry. - - -

Type: machine-oriented

-

Source: cross-instance - References a party defined in this or other OSCAL instances

- + + A machine-oriented identifier reference to the party who is making the log entry. Actor Role @@ -1641,10 +1545,7 @@ Remediation Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this remediation elsewhere in this or other OSCAL instances. The locally defined UUID of the risk response can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this remediation elsewhere in this or other OSCAL instances. The locally defined UUID of the risk response can be used to reference the data item locally or globally (e.g., in an imported 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. Remediation Intent @@ -1687,10 +1588,7 @@ Required Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this required asset elsewhere in this or other OSCAL instances. The locally defined UUID of the asset can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this required asset elsewhere in this or other OSCAL instances. The locally defined UUID of the asset can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -1753,10 +1651,7 @@ Part Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this part elsewhere in this or other OSCAL instances. The locally defined UUID of the part can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this part elsewhere in this or other OSCAL instances. The locally defined UUID of the part can be used to reference the data item locally or globally (e.g., in an ported 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. Part Name diff --git a/src/metaschema/oscal_assessment-plan_metaschema.xml b/src/metaschema/oscal_assessment-plan_metaschema.xml index 6efc457be1..24ee462070 100644 --- a/src/metaschema/oscal_assessment-plan_metaschema.xml +++ b/src/metaschema/oscal_assessment-plan_metaschema.xml @@ -21,10 +21,7 @@ Assessment Plan Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment plan in this or other OSCAL instances. The locally defined UUID of the assessment plan can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment plan in this or other OSCAL instances. The locally defined UUID of the assessment plan can be used to reference the data item locally or globally (e.g., in an imported 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. diff --git a/src/metaschema/oscal_assessment-results_metaschema.xml b/src/metaschema/oscal_assessment-results_metaschema.xml index 58aa553698..28ef12b224 100644 --- a/src/metaschema/oscal_assessment-results_metaschema.xml +++ b/src/metaschema/oscal_assessment-results_metaschema.xml @@ -23,10 +23,7 @@ Assessment Results Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment results instance in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this assessment results instance in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -79,10 +76,7 @@ Results Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this set of results in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this set of results in this or other OSCAL instances. The locally defined UUID of the assessment result can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -208,10 +202,7 @@ Assessment Log Entry Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference an assessment event in this or other OSCAL instances. The locally defined UUID of the assessment log entry can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference an assessment event in this or other OSCAL instances. The locally defined UUID of the assessment log entry can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -272,10 +263,7 @@ Finding Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this finding in this or other OSCAL instances. The locally defined UUID of the finding can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this finding in this or other OSCAL instances. The locally defined UUID of the finding can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -306,13 +294,8 @@ Implementation Statement UUID - - A machine-oriented identifier reference to the implementation statement in the SSP to which this finding is related. - - -

Type: machine-oriented

-

Source: cross-instance - References the implementation statement in this or other OSCAL instances.

- + + A machine-oriented identifier reference to the implementation statement in the SSP to which this finding is related. @@ -321,13 +304,8 @@ Observation Universally Unique Identifier Reference - - A machine-oriented identifier reference to an observation defined in the list of observations. - - -

Type: machine-oriented

-

Source: cross-instance - References the implementation an observation in this or other OSCAL instances

- + + A machine-oriented identifier reference to an observation defined in the list of observations. @@ -337,11 +315,8 @@ Risk Universally Unique Identifier Reference - - A machine-oriented identifier reference to a risk defined in the list of risks. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + + A machine-oriented identifier reference to a risk defined in the list of risks. diff --git a/src/metaschema/oscal_catalog_metaschema.xml b/src/metaschema/oscal_catalog_metaschema.xml index 8e4b4cbe9a..b89d40e74b 100644 --- a/src/metaschema/oscal_catalog_metaschema.xml +++ b/src/metaschema/oscal_catalog_metaschema.xml @@ -66,10 +66,7 @@ Group Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in this or other OSCAL instances (e.g., profiles). This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. - -

See the Concepts - Identifier Use page for additional information regarding this human-oriented identifier's uniqueness and scope.

- + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in in this and other OSCAL instances (e.g., profiles). This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. Group Class @@ -135,10 +132,7 @@ Control Identifier - A human-oriented, locally unique identifier with instance scope that can be used to reference this control elsewhere in this and other OSCAL instances (e.g., profiles). This id should be assigned per-subject, which means it should be consistently used to identify the same control across revisions of the document. - -

See the [Concepts - Identifier Use page for additional information regarding this human-oriented identifier's uniqueness and scope.

- + A human-oriented, locally unique identifier with instance scope that can be used to reference this control elsewhere in this and other OSCAL instances (e.g., profiles). This id should be assigned per-subject, which means it should be consistently used to identify the same control across revisions of the document. Control Class diff --git a/src/metaschema/oscal_component_metaschema.xml b/src/metaschema/oscal_component_metaschema.xml index 939c435dc5..fb97e12319 100644 --- a/src/metaschema/oscal_component_metaschema.xml +++ b/src/metaschema/oscal_component_metaschema.xml @@ -34,10 +34,7 @@ Component Definition Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component definition elsewhere in this or other OSCAL instances. The locally defined UUID of the component definition can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component definition elsewhere in this or other OSCAL instances. The locally defined UUID of the component definition can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -84,10 +81,7 @@ Component Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. type @@ -258,10 +252,7 @@ Capability Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this capability elsewhere in this or other OSCAL instances. The locally defined UUID of the capability can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this capability elsewhere in this or other OSCAL instances. The locally defined UUID of the capability can be used to reference the data item locally or globally (e.g., in an imported 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. Capability Name @@ -301,13 +292,8 @@ TBD Component Reference - - A machine-oriented identifier reference to a component. - - -

Type: human-oriented

-

Source: cross-instance - References a component identifer defined in this or other OSCAL instances

- + + A machine-oriented identifier reference to a component. @@ -323,10 +309,7 @@ Control Implementation Set Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference a set of implemented controls elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation set can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference a set of implemented controls elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation set can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -369,10 +352,7 @@ Control Implementation Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference a specific control implementation elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference a specific control implementation elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -429,10 +409,7 @@ Control Statement Reference Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. The UUID of the control statement in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance). - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. The UUID of the control statement in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance). diff --git a/src/metaschema/oscal_control-common_metaschema.xml b/src/metaschema/oscal_control-common_metaschema.xml index 1f2f71b889..931dddae7d 100644 --- a/src/metaschema/oscal_control-common_metaschema.xml +++ b/src/metaschema/oscal_control-common_metaschema.xml @@ -23,10 +23,7 @@ Part Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this and other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - -

See the Concepts - Identifier Use page for additional information regarding this human-oriented identifier's uniqueness and scope.

- + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined part elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. Part Name @@ -127,10 +124,7 @@ Parameter Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - -

See the Concepts - Identifier Use page for additional information regarding this human-oriented identifier's uniqueness and scope.

- + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -273,9 +267,6 @@ Control Identifier Reference - A human-oriented identifier reference to a control with a corresponding 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). - -

See the Concepts - Identifier Use page for additional information about the referenced identifier's scope.

- + A human-oriented identifier reference to a control with a corresponding 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). diff --git a/src/metaschema/oscal_implementation-common_metaschema.xml b/src/metaschema/oscal_implementation-common_metaschema.xml index ffd565a0de..40dedfef70 100644 --- a/src/metaschema/oscal_implementation-common_metaschema.xml +++ b/src/metaschema/oscal_implementation-common_metaschema.xml @@ -31,10 +31,7 @@ Component Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this component elsewhere in this or other OSCAL instances. The locally defined UUID of the component can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -254,10 +251,7 @@ Service Protocol Information Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this service protocol information elsewhere in this or other OSCAL instances. The locally defined UUID of the service protocol can be used to reference the data item locally or globally (e.g., in an imported 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. Protocol Name @@ -346,10 +340,7 @@ User Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this user class elsewhere in this or other OSCAL instances. The locally defined UUID of the system user can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -435,10 +426,7 @@ Inventory Item Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported 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. - A machine-oriented identifier reference to a component that is implemented as part of an inventory item. - - -

Type: human-oriented

-

Source: cross-instance - References a component identifer defined in this or other OSCAL instances

- + + A machine-oriented identifier reference to a component that is implemented as part of an inventory item. @@ -653,13 +636,8 @@ --> Control Statement Reference - - A human-oriented identifier reference to a control statement. - - -

Type: human-oriented

-

Source: instance - References a control state by its identifer as defined in this OSCAL instance

- + + A human-oriented identifier reference to a control statement. Set Parameter Value @@ -682,10 +660,7 @@ System Identification - A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this and other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. - -

See the Concepts - Identifier Use page for additional information regarding this human-oriented identifier's uniqueness and scope.

- + A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document. id Identification System Type @@ -703,13 +678,8 @@ Parameter ID - - A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context. - - -

Type: human-oriented

-

Source: cross-instance - References a parameter defined within a control in this or other OSCAL instances

- + + A human-oriented reference to a parameter within a control, who's catalog has been imported into the current implementation context. System ISSO diff --git a/src/metaschema/oscal_metadata_metaschema.xml b/src/metaschema/oscal_metadata_metaschema.xml index 8421a25c01..2487f072a9 100644 --- a/src/metaschema/oscal_metadata_metaschema.xml +++ b/src/metaschema/oscal_metadata_metaschema.xml @@ -157,10 +157,7 @@ Location Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined location elsewhere in this or other OSCAL instances. The locally defined UUID of the location 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. @@ -217,7 +214,7 @@ Location Reference - A machine-oriented identifier reference to a 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). + A machine-oriented identifier reference to a 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). @@ -226,15 +223,12 @@ - -

See the Concepts - Identifier Use page for additional information about the referenced identifier's scope.

- Location Reference - A machine-oriented identifier reference to a 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). + A machine-oriented identifier reference to a 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). @@ -253,10 +247,7 @@ Party Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined party elsewhere in this or other OSCAL instances. The locally defined UUID of the 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 Type @@ -327,7 +318,7 @@ Organizational Affiliation - A machine-oriented identifier reference to another 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). + A machine-oriented identifier reference to another 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). @@ -337,7 +328,6 @@

Parties of both the person or organization type can be associated with an organization using the member-of-organization.

-

See the Concepts - Identifier Use page for additional information about the referenced identifier's scope.

 @@ -354,7 +344,7 @@ Party Reference - A machine-oriented identifier reference to another 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). + A machine-oriented identifier reference to another 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). @@ -373,10 +363,7 @@ - A human-oriented, locally-unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this and other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. - -

See the Concepts - Identifier Use page for additional information regarding this human-oriented identifier's uniqueness and scope.

- + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined role elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, the locally defined ID of the 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. @@ -408,8 +395,8 @@ Role Identifier Reference - - A human-oriented identifier reference to roles served by the user. + + A human-oriented identifier reference to roles served by the user. @@ -432,10 +419,7 @@ Resource Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined resource elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -629,10 +613,7 @@ Property Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this and other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this defined property elsewhere in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. @@ -736,8 +717,8 @@ A reference to a set of organizations or persons that have responsibility for performing a referenced role in the context of the containing object. Responsible Role - - A human-oriented identifier reference to roles served by the user. + + A human-oriented identifier reference to roles served by the user. @@ -769,8 +750,8 @@ A reference to one or more roles with responsibility for performing a function relative to the containing object. Responsible Role ID - - A human-oriented identifier reference to roles responsible for the business function. + + A human-oriented identifier reference to roles responsible for the business function. @@ -949,7 +930,7 @@ Document Identifier - A document identifier qualified by an identifier scheme. A document identifier provides a globally-unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. + A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element. identifier @@ -964,7 +945,6 @@

This element is optional, but it will always have a valid value, as if it is missing the value of "document-id" is assumed to be equal to the UUID of the root. This requirement allows for document creators to retroactively link an update to the original version, by providing a document-id on the new document that is equal to the uuid of the original document.

-

See the Concepts - Identifier Use page for additional information regarding this *machine-oriented* identifier's uniqueness and scope.

 diff --git a/src/metaschema/oscal_poam_metaschema.xml b/src/metaschema/oscal_poam_metaschema.xml index 34a240c78a..65936c509d 100644 --- a/src/metaschema/oscal_poam_metaschema.xml +++ b/src/metaschema/oscal_poam_metaschema.xml @@ -24,10 +24,7 @@ POA&M Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this POA&M instance in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with instancescope that can be used to reference this POA&M instance in this 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. @@ -93,10 +90,7 @@ POA&M Item Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this POA&M item entry in this or other OSCAL instances. This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with instance scope that can be used to reference this POA&M item entry in this 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. @@ -140,13 +134,8 @@ Observation Universally Unique Identifier Reference - - A machine-oriented identifier reference to an observation defined in the list of observations. - - -

Type: machine-oriented

-

Source: cross-instance - References the implementation an observation in this or other OSCAL instances

- + + A machine-oriented identifier reference to an observation defined in the list of observations. @@ -157,13 +146,8 @@ Risk Universally Unique Identifier Reference - - A machine-oriented identifier reference to a risk defined in the list of risks. - - -

Type: machine-oriented

-

Source: cross-instance - References the a risk in this or other OSCAL instances

- + + A machine-oriented identifier reference to a risk defined in the list of risks. diff --git a/src/metaschema/oscal_profile_metaschema.xml b/src/metaschema/oscal_profile_metaschema.xml index e9b1b41101..18e2aad3ce 100644 --- a/src/metaschema/oscal_profile_metaschema.xml +++ b/src/metaschema/oscal_profile_metaschema.xml @@ -24,10 +24,7 @@ Profile Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this profile elsewhere in this and other OSCAL instances. The locally defined UUID of the profile can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance).This identifier should be assigned per-subject, which means it should be consistently used to identify the same profile across revisions of the document. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this profile elsewhere in this or other OSCAL instances. The locally defined UUID of the profile can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance).This identifier should be assigned per-subject, which means it should be consistently used to identify the same profile across revisions of the document. @@ -151,10 +148,7 @@ Group Identifier - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. - -

See the Concepts - Identifier Use page for additional information regarding this human-oriented identifier's uniqueness and scope.

- + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined group elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same group across revisions of the document. Group Class @@ -206,10 +200,7 @@ Parameter ID - A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. - -

See the Concepts - Identifier Use page for additional information regarding this human-oriented identifier's uniqueness and scope.

- + A human-oriented, locally unique identifier with cross-instance scope that can be used to reference this defined parameter elsewhere in this or other OSCAL instances. When referenced from another OSCAL instance, this identifier must be referenced in the context of the containing resource (e.g., import-profile). This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. Parameter Class diff --git a/src/metaschema/oscal_ssp_metaschema.xml b/src/metaschema/oscal_ssp_metaschema.xml index df261285c9..cb5a6a65c5 100644 --- a/src/metaschema/oscal_ssp_metaschema.xml +++ b/src/metaschema/oscal_ssp_metaschema.xml @@ -35,10 +35,7 @@ System Security Plan Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this system security plan (SSP) elsewhere in this or other OSCAL instances. The locally defined UUID of the SSP can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this system security plan (SSP) elsewhere in this or other OSCAL instances. The locally defined UUID of the SSP can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -195,10 +192,7 @@ Information Type Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this information type elsewhere in this or other OSCAL instances. The locally defined UUID of the information type can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this information type elsewhere in this or other OSCAL instances. The locally defined UUID of the information type can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -229,12 +223,9 @@ Information Type Systematized Identifier - A human-oriented, globally unique identifier qualified by the given identification system used, such as NIST SP 800-60. This identifier has cross-instance scope and can be used to reference this system elsewhere in this or other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. + A human-oriented, globally unique identifier qualified by the given identification system used, such as NIST SP 800-60. This identifier has cross-instance scope and can be used to reference this system elsewhere in this or other OSCAL instances. This id should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document. id - -

See the Concepts - Identifier Use page for additional information regarding this human-oriented identifier's uniqueness and scope.

- @@ -422,10 +413,7 @@ Diagram ID - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this diagram elsewhere in this or other OSCAL instances. The locally defined UUID of the diagram can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this diagram elsewhere in this or other OSCAL instances. The locally defined UUID of the diagram can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -556,10 +544,7 @@ Leveraged Authorization Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope and can be used to reference this leveraged authorization elsewhere in this or other OSCAL instances. The locally defined UUID of the leveraged authorization can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope and can be used to reference this leveraged authorization elsewhere in this or other OSCAL instances. The locally defined UUID of the leveraged authorization can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -574,13 +559,8 @@ party-uuid field - - A machine-oriented identifier reference to the party that manages the leveraged system. - - -

Type: human-oriented

-

Source: cross-instance - References a party identifer defined in this or other OSCAL instances

- + + A machine-oriented identifier reference to the party that manages the leveraged system. @@ -710,10 +690,7 @@ Control Requirement Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control requirement elsewhere in this or other OSCAL instances. The locally defined UUID of the control requirement can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control requirement elsewhere in this or other OSCAL instances. The locally defined UUID of the control requirement can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -804,10 +781,7 @@ Control Statement Reference Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. The UUID of the control statement in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance). - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this control statement elsewhere in this or other OSCAL instances. The UUID of the control statement in the source OSCAL instance is sufficient to reference the data item locally or globally (e.g., in an imported OSCAL instance). @@ -849,21 +823,13 @@ Defines how the referenced component implements a set of controls. Component Universally Unique Identifier Reference - - A machine-oriented identifier reference to the component that is implemeting a given control. - - -

Type: machine-oriented

-

Source: cross-instance - References a component identifer defined in this or other OSCAL instances

- + + A machine-oriented identifier reference to the component that is implemeting a given control. By-Component Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this by-component entry elsewhere in this or other OSCAL instances. The locally defined UUID of the by-component entry can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this by-component entry elsewhere in this or other OSCAL instances. The locally defined UUID of the by-component entry can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -907,10 +873,7 @@ Provided Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this provided entry elsewhere in this or other OSCAL instances. The locally defined UUID of the provided entry can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this provided entry elsewhere in this or other OSCAL instances. The locally defined UUID of the provided entry can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -945,10 +908,7 @@ Responsibility Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this responsibility elsewhere in this or other OSCAL instances. The locally defined UUID of the responsibility can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this responsibility elsewhere in this or other OSCAL instances. The locally defined UUID of the responsibility can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -1000,10 +960,7 @@ Inherited Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inherited entry elsewhere in this or other OSCAL instances. The locally defined UUID of the inherited control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inherited entry elsewhere in this or other OSCAL instances. The locally defined UUID of the inherited control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -1039,10 +996,7 @@ Satisfied Universally Unique Identifier - A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this satisfied control implementation entry elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. - -

See the Concepts - Identifier Use page for additional information regarding this machine-oriented identifier's uniqueness and scope.

- + A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this satisfied control implementation entry elsewhere in this or other OSCAL instances. The locally defined UUID of the control implementation can be used to reference the data item locally or globally (e.g., in an imported 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. @@ -1093,23 +1047,13 @@ Provided UUID - - A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system. - - -

Type: machine-oriented

-

Source: cross-instance - References a provided control implementation in this or other OSCAL instances

- + + A machine-oriented identifier reference to an inherited control implementation that a leveraging system is inheriting from a leveraged system. Responsibility UUID - - A machine-oriented identifier reference to a control implementation that satisfies a responsibility imposed by a leveraged system. - - -

Type: machine-oriented

-

Source: cross-instance - References a satisfied control implementation in this or other OSCAL instances

- + + A machine-oriented identifier reference to a control implementation that satisfies a responsibility imposed by a leveraged system. From 0973b64ea64556590ebfdc90926cc3f6721f9634 Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Thu, 20 Jan 2022 23:44:18 -0500 Subject: [PATCH 33/34] fix bug on identifier use page --- docs/content/concepts/identifier-use/_index.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/docs/content/concepts/identifier-use/_index.md b/docs/content/concepts/identifier-use/_index.md index 322ce7fa65..bc40f8e9cc 100644 --- a/docs/content/concepts/identifier-use/_index.md +++ b/docs/content/concepts/identifier-use/_index.md @@ -27,7 +27,6 @@ UUIDs were chosen because: - UUIDs are represented in 128 bits, providing for a large address space with low risk of identifier collisions for randomly generated values The opaque nature of UUIDs, which consist of a series of hexadecimal characters, makes them less than ideal for wildcard matching scenarios. Thus, their use in OSCAL is intended for identification only where an exact match is required. Where wildcard matching is needed, the other data elements associated with the entity should be evaluated for a match instead. ->>>>>>> d1b234ed (identifier use page review edits) {{}}The opaque nature of UUIDs, which consist of a series of hexadecimal characters, makes them less than ideal for wildcard matching scenarios. Thus, their use in OSCAL is intended for identification only where an exact match is required. Where wildcard matching is needed, the other data elements associated with the entity should be evaluated for a match instead. {{}} @@ -44,11 +43,7 @@ OSCAL identifier uniqueness is categorized as *locally-u ### **Scope** -<<<<<<< HEAD -Identifiers that are only intended for use within the same OSCAL instance are categorized as *instance* scope. However, since OSCAL supports composition relationships, there are cases where identifiers in a source OSCAL instance need to be referenced from other OSCAL instances. These are considered *cross-instance* scoped identifier references. The figure below illustrates how OSCAL models relationships are established through import and link mechanisms. -======= Identifiers that are only intended for use within the same OSCAL instance are categorized as *instance* scope. However, since OSCAL supports composition relationships, there are many cases where identifiers in a source OSCAL instance need to be referenced from other OSCAL instances. These are considered *cross-instance* scoped identifier references. The figure below illustrates how the core OSCAL models relationships are established through import and link mechanisms, enabling [*cross-instance*](#cross-instance) references. ->>>>>>> 59a25042 (identifier documentation updates) ![A diagram depicting the relationships between OSCAL models. The solid black arrows depict relationships implemented via the import mechanism (e.g., import, import-profile, import-component-definition, import-ssp, and import-ap), whereas the dashed red line arrows illustrate relationships established through links.](oscal-model-relationships.svg) From 70b1c1641808d8afd196ebcc591cdaf82f5b4801 Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Tue, 25 Jan 2022 16:57:07 -0500 Subject: [PATCH 34/34] update token datatype reference --- docs/content/concepts/identifier-use/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/concepts/identifier-use/_index.md b/docs/content/concepts/identifier-use/_index.md index bc40f8e9cc..25dd314d50 100644 --- a/docs/content/concepts/identifier-use/_index.md +++ b/docs/content/concepts/identifier-use/_index.md @@ -34,7 +34,7 @@ The [OSCAL XML Reference Index](/reference/latest/complete/xml-index/#/@uuid) an #### Human-Oriented -A [*human-oriented*](#human-oriented) identifier incorporates semantic that support readability and processing by humans. OSCAL implements [*human-oriented*](#human-oriented) identifiers as [Token](/reference/datatypes/#token) data types, which are non-colonized names. For example, control identifiers in a catalog may use a nomenclature that is familiar to the intended audience, allowing them to quickly determine what security control is being referred to, simply by its identifier value. +A [*human-oriented*](#human-oriented) identifier incorporates semantic that support readability and processing by humans. OSCAL implements [*human-oriented*](#human-oriented) identifiers as [token](/reference/datatypes/#token) data types, which are non-colonized names. For example, control identifiers in a catalog may use a nomenclature that is familiar to the intended audience, allowing them to quickly determine what security control is being referred to, simply by its identifier value. The [OSCAL XML Reference Index](/reference/latest/complete/xml-index/#/@id) and [OSCAL JSON Reference Index](/reference/latest/complete/json-index/#/id) provide a comprehensive listing of the [*human-oriented*](#human-oriented) IDs in the core OSCAL models. References to these IDs are typically named according to the referenced object type (e.g., control) followed by “-id”, as seen here in the [XML Reference Index](/reference/latest/complete/xml-index/#/@control-id) (and likewise [JSON Reference Index](/reference/latest/complete/json-index/#/control-id) in the JSON reference index).