-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consistency of grouping names #780
Comments
Relates to #717 |
Can you provide a listing similar to the above which shows |
Here is a comprehensive listing of definition references each with its given name, the "used name" if given on the reference (usually the same) and its grouping name. (Used names declared on definitions at the top level are not included as that would not be a one-liner.) All the grouping names are given, including multiplicates, since they each have a group name and in theory it could be different. They are sorted alphabetically within each module for legibility and comparison. Here is the XPath to produce a Markdown table listing the definitions or references designated with grouping names in each of the metaschema modules. The listing was produced from metaschemas in the
Catalog
Control common
Metadata
Profile
SSP
Component
POA&M
Implementation common
Assessment plan
Assessment results
Assessment common
|
We need to take a look at the following: Metadata
SSP
POA&M
Assessment plan
Assessment results
Assessment common
|
PR #794 addresses the changes I posted above. |
User Story:
In order to review consistency of the grouping names given to objects in OSCAL ...
Doing some analysis of the current OSCAL metaschema files, this path will return all the grouping names for arrays or compound objects in JSON or object notation (YAML) OSCAL variants:
... executed over the file set (allowing for namespaces), returns a list of hits in oXygen. I save out this result (report) in oXygen. I then performed a bit of XQuery over this file (actually this is still XPath):
to receive this output (pasted directly, so with Markdown rendered):
oscal_assessment-common_metaschema.xml:
properties
,annotations
,links
,control-group
,control-objective-group
,objectives
,assessment-methods
,include-controls
,exclude-controls
,include-objectives
,exclude-objectives
,subject-references
,parts
,components
,test-methods
,include-activities
,exclude-activities
,test-steps
,role-ids
,party-uuids
,tasks
,activity-uuids
,location-uuids
,findings
,observations
,threat-ids
,risks
,observation-methods
,observation-types
,assessors
,origins
,relevant-evidence-group
,risk-metrics
,mitigating-factors
,remediation-group
,tracking-entries
,requirements
oscal_assessment-plan_metaschema.xml:
includes
,excludes
,components
,inventory-items
,users
oscal_assessment-results_metaschema.xml:
results_group
,includes
,excludes
,components
,inventory-items
,users
oscal_catalog_metaschema.xml:
parameters
,controls
,groups
,properties
,annotations
,links
,parts
oscal_component_metaschema.xml:
import-component-definitions
,components
,capabilities
,properties
,annotations
,links
,responsible-roles
,protocols
,control-implementations
,incorporates-components
,implemented-requirements
,set-parameters
,statements
oscal_control-common_metaschema.xml:
properties
,annotations
,parts
,links
,constraints
,guidelines
,values
,tests
,choice
oscal_framework-common_metaschema.xml:
implemented-requirements
,properties
,annotations
,links
,statements
oscal_implementation-common_metaschema.xml:
properties
,annotations
,links
,responsible-roles
,protocols
,port-ranges
,role-ids
,authorized-privileges
,functions-performed
,responsible-parties
,implemented-components
,party-uuids
,values
oscal_metadata_metaschema.xml:
revision-history
,document-ids
,properties
,annotations
,links
,roles
,locations
,parties
,responsible-parties
,email-addresses
,telephone-numbers
,urls
,external-ids
,addresses
,location-uuids
,member-of-organizations
,resources
,rlinks
,hash-values
,party-uuids
,postal-address
oscal_poam_metaschema.xml:
components
,inventory-items
,properties
,annotations
,poam-item-group
,observations
,threat-ids
,risks
,party-uuids
oscal_profile_metaschema.xml:
imports
,groups
,id-selectors
,pattern-selectors
,parameters
,properties
,annotations
,links
,parts
,parameter-settings
,alterations
,constraints
,guidelines
,values
,removals
,additions
oscal_ssp_metaschema.xml:
system-ids
,properties
,annotations
,links
,responsible-parties
,information-types
,information-type-ids
,diagrams
,leveraged-authorizations
,users
,components
,inventory-items
,implemented-requirements
,by-components
,responsible-roles
,parameter-settings
,statements
,provided-group
,responsibilities
,inherited-group
,satisfied-group
Goals:
Review this list for consistency and correctness.
For example, I can see several names with underscores
_
do we want those?Dependencies:
None known: this is independent of other Metaschema checks.
Acceptance Criteria
{The items above are general acceptance criteria for all User Stories. Please describe anything else that must be completed for this issue to be considered resolved.}
The text was updated successfully, but these errors were encountered: