Merged
Conversation
pmai
force-pushed
the
fix/move-to-ssp20
branch
from
6540cf1 to
177c293
Compare
| | Content | Optional | <<sec-contenttype>> | ||
| | Signature | Optional | <<sec-signaturetype>> | ||
| | Content | Optional | See SSP Specification | ||
| | Signature | Optional | See SSP Specification |
Contributor
There was a problem hiding this comment.
Should either user the ssc prefix or ssc prefixes should be ommitted for all element names.
| | GResourceOrReference | Optional | <<sec-gresourceorreference>> | ||
| | Responsible | Mandatory | <<sec-responsibletype>> | ||
| | Signature | Optional | <<sec-signaturetype>> | ||
| | Signature | Optional | See SSP Specification |
Contributor
There was a problem hiding this comment.
Should either use the ssc prefix or ssc prefixes should be ommitted for all element names.
specification/5___stc.adoc
Outdated
| | Summary | Optional | <<sec-summary>> | ||
| | Metadata | Optional | <<sec-metadata>> | ||
| | Signature | Optional | <<sec-signaturetype>> | ||
| | ssc:Metadata | Optional | See SSP Specification |
Contributor
There was a problem hiding this comment.
Should either user the ssc prefix or ssc prefixes should be ommitted for all element names.
specification/5___stc.adoc
Outdated
| | Metadata | Optional | <<sec-metadata>> | ||
| | Signature | Optional | <<sec-signaturetype>> | ||
| | ssc:Metadata | Optional | See SSP Specification | ||
| | ssc:Signature | Optional | See SSP Specification |
Contributor
There was a problem hiding this comment.
Should either user the ssc prefix or ssc prefixes should be ommitted for all element names.
Update references and sub-module, remove now duplicated meta-data related types in STC.xsd, adjust documentation.
Align with SSP 2.0 practice, fix documentation (fixes #92).
peter-lobner
approved these changes
Mar 12, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Move everything to an SSP 2.0 base now that has been released, and remove duplication to take advantage of added content from SSP Traceability in SSP Core.