Skip to content
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

Rename reference mechanic in the Metaschema #442

Closed
7 tasks
david-waltermire opened this issue Jun 20, 2019 · 4 comments
Closed
7 tasks

Rename reference mechanic in the Metaschema #442

david-waltermire opened this issue Jun 20, 2019 · 4 comments
Assignees
Labels
enhancement Scope: Metaschema Issues targeted at the metaschema pipeline Scope: Modeling Issues targeted at development of OSCAL formats User Story

Comments

@david-waltermire
Copy link
Contributor

User Story:

As an OSCAL model developer, I need a clear indicator that a flag specified in a define-field or define-assembly is defined locally or globally. I would also like the feature used to reference global define-assembly, define-field, and define-flag to be consistent.

Goals:

  • Rename @named to @ref in all assembly, field, and flag references. Also, use @name for locally defined flag elements within a define-field or define-assembly.
  • Update all XSLTs used to generate schema, documentation, and content converters.

Dependencies:

#435 is related to this issue.

Acceptance Criteria

  • All generated XML and JSON schema, content converters, and document generators are updated to reflect these changes.
  • The Metaschema definitions are updated in a way that result in no changes to associated content.
  • Documentation on the use of Metaschema is updated to fully document use of the @ref and @name features.
  • No content is changed as a result of these changes.
  • A single PR is approved that contains the above changes.
@david-waltermire david-waltermire added enhancement User Story Scope: Metaschema Issues targeted at the metaschema pipeline Scope: Modeling Issues targeted at development of OSCAL formats labels Jun 20, 2019
@wendellpiez
Copy link
Contributor

@iMichaela
Copy link
Contributor

7/11/2019

This issue and the related ones (noted in #435 ) for the metaschema need to be reviewed together and unitested. However, more unit tests need to be created for the other features.

@david-waltermire
Copy link
Contributor Author

This will be closed once PR #464 is pulled.

@david-waltermire
Copy link
Contributor Author

This has been completed in PR #464.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Scope: Metaschema Issues targeted at the metaschema pipeline Scope: Modeling Issues targeted at development of OSCAL formats User Story
Projects
None yet
Development

No branches or pull requests

3 participants