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.

Sign up for GitHub

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

Jump to bottom

Document Schema File Naming Conventions #391

Merged
merged 7 commits into from
Jun 5, 2019
Merged

Document Schema File Naming Conventions #391

merged 7 commits into from
Jun 5, 2019

Conversation

david-waltermire
Copy link
Contributor

Committer Notes

This PR addresses issue #49 by documenting schema naming conventions, and by cleaning up all OSCAL schema in the repository.

All Submissions:

  • Have you followed the guidelines in our Contributing document?
  • Have you checked to ensure there aren't other open Pull Requests for the same update/change?
  • Have you squashed any non-relevant commits and commit messages? [instructions]

Changes to Core Features:

  • Have you added an explanation of what your changes do and why you'd like us to include them?
  • Have you written new tests for your core changes, as applicable?
  • Have you included examples of how to use your new feature(s)?

@david-waltermire
Copy link
Contributor Author

Still need to update CI/CD to generate the correct file names.

@david-waltermire david-waltermire force-pushed the issue49 branch 3 times, most recently from 087fec3 to 5b94019 Compare June 5, 2019 16:48
@david-waltermire david-waltermire marked this pull request as ready for review June 5, 2019 16:49
@david-waltermire
Added file naming conventions for XSL conversion templates
c35dd02 
Renamed schema files to follow the naming guidance
@david-waltermire
reorganized metaschema docuemntation
1f52dd5 
reorganized metaschema docuemntation
@david-waltermire
refactored scripts to produce file using correct names
6551ade
@david-waltermire
Updated image link to fix broken link
b003d92
@david-waltermire
generated files
4965a64 
Fixed validation script to use new config format

fixed scripts for content conversion

fixed broken links

fixed spelling errors and broken links

fixed spelling errors and broken links

fixed spelling errors and broken links

partial fix to document generators

Added initial markdown checking configuration

Fixed stylesheets (#2)

Fixed parameter errors

adjusted scripts
@david-waltermire
Added markdown-link-checker
4887570 
fixed filename

Adjusting XSLT parameter settings (#3)

Minor build tweeks

Updated stylesheets

Enhanced messages

Added working_dir message

Fixed path

Repaired broken path logic in docs generation (#4)
@david-waltermire
Added support for JSON min and Yaml generation
996521c 
fixed pathing in model generation script

Added support for JSON prettyprint and yaml generation

fixed bad output path

ensure doc dir exists
@david-waltermire david-waltermire merged commit 1c7f1d6 into usnistgov:master Jun 5, 2019
@david-waltermire david-waltermire mentioned this pull request Jun 5, 2019
Closed
david-waltermire added a commit to david-waltermire/OSCAL that referenced this pull request Jun 6, 2019
@david-waltermire
Document Schema File Naming Conventions (usnistgov#391)
b2bcd48 
- Added file naming conventions for XSL conversion templates
- Renamed schema files to follow the naming guidance
- Reorganized metaschema docuemntation
- Refactored scripts to produce files using correct names
- Fixed broken links in repo and website
- Fixed spelling errors and broken links
- Added markdown-link-checker to CI process to check PRs for broken links
- Added colorization to many build messages
- Added support for JSON min and YAML content generation from JSON files (using prettyprint)
david-waltermire added a commit to david-waltermire/OSCAL that referenced this pull request Jun 6, 2019
@david-waltermire
Document Schema File Naming Conventions (usnistgov#391)
97de36a 
- Added file naming conventions for XSL conversion templates
- Renamed schema files to follow the naming guidance
- Reorganized metaschema docuemntation
- Refactored scripts to produce files using correct names
- Fixed broken links in repo and website
- Fixed spelling errors and broken links
- Added markdown-link-checker to CI process to check PRs for broken links
- Added colorization to many build messages
- Added support for JSON min and YAML content generation from JSON files (using prettyprint)
david-waltermire added a commit to david-waltermire/OSCAL that referenced this pull request Jun 6, 2019
@david-waltermire
Document Schema File Naming Conventions (usnistgov#391)
5444422 
- Added file naming conventions for XSL conversion templates
- Renamed schema files to follow the naming guidance
- Reorganized metaschema docuemntation
- Refactored scripts to produce files using correct names
- Fixed broken links in repo and website
- Fixed spelling errors and broken links
- Added markdown-link-checker to CI process to check PRs for broken links
- Added colorization to many build messages
- Added support for JSON min and YAML content generation from JSON files (using prettyprint)
david-waltermire added a commit to david-waltermire/OSCAL that referenced this pull request Jun 6, 2019
@david-waltermire
Document Schema File Naming Conventions (usnistgov#391)
2a05842 
- Added file naming conventions for XSL conversion templates
- Renamed schema files to follow the naming guidance
- Reorganized metaschema docuemntation
- Refactored scripts to produce files using correct names
- Fixed broken links in repo and website
- Fixed spelling errors and broken links
- Added markdown-link-checker to CI process to check PRs for broken links
- Added colorization to many build messages
- Added support for JSON min and YAML content generation from JSON files (using prettyprint)
@david-waltermire david-waltermire deleted the issue49 branch June 6, 2019 11:18
david-waltermire added a commit to david-waltermire/OSCAL that referenced this pull request Jun 6, 2019
@david-waltermire
Document Schema File Naming Conventions (usnistgov#391)
27bcab9 
- Added file naming conventions for XSL conversion templates
- Renamed schema files to follow the naming guidance
- Reorganized metaschema docuemntation
- Refactored scripts to produce files using correct names
- Fixed broken links in repo and website
- Fixed spelling errors and broken links
- Added markdown-link-checker to CI process to check PRs for broken links
- Added colorization to many build messages
- Added support for JSON min and YAML content generation from JSON files (using prettyprint)
david-waltermire added a commit to david-waltermire/OSCAL that referenced this pull request Jun 11, 2019
@david-waltermire
Document Schema File Naming Conventions (usnistgov#391)
bc4b3c3 
- Added file naming conventions for XSL conversion templates
- Renamed schema files to follow the naming guidance
- Reorganized metaschema docuemntation
- Refactored scripts to produce files using correct names
- Fixed broken links in repo and website
- Fixed spelling errors and broken links
- Added markdown-link-checker to CI process to check PRs for broken links
- Added colorization to many build messages
- Added support for JSON min and YAML content generation from JSON files (using prettyprint)
aj-stein-nist referenced this pull request in aj-stein-nist/OSCAL-forked Jan 25, 2023
@david-waltermire
Document Schema File Naming Conventions (#391)
caae1b3 
- Added file naming conventions for XSL conversion templates
- Renamed schema files to follow the naming guidance
- Reorganized metaschema docuemntation
- Refactored scripts to produce files using correct names
- Fixed broken links in repo and website
- Fixed spelling errors and broken links
- Added markdown-link-checker to CI process to check PRs for broken links
- Added colorization to many build messages
- Added support for JSON min and YAML content generation from JSON files (using prettyprint)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@david-waltermire