Correct figures for data specifications #437
Merged
Conversation
This file contains 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
Collaborator
BirgitBoss
commented
Jun 3, 2024
BirgitBoss
commented
- no idShort for DataSpecification Template
- no Part 1a but Part 1 in overview figure for Data Specifications
#418 CHANGE (Editorial, the schemas implemented it like this) Annex UML Tables: "0..*" or "0..3" etc. means that the list may be either not available (optional) or the list is not empty.
BirgitBoss
changed the title
BirgitBoss
added a commit
that referenced
this pull request
Jun 20, 2024
* update to V3.0.1( DataTypeDefXsd, PathType) (#430) * V3.0.1: fix figure (xs:float not at correct place) + update Changelog accordingly * Now PathType change already part of V3.0.1 ChangeLog changed accordingly * add subchapter for better structuring * Incorporate changes from V3.0.1 (#436) * V3.0.1: fix figure (xs:float not at correct place) + update Changelog accordingly * Now PathType change already part of V3.0.1 ChangeLog changed accordingly * add subchapter for better structuring * • (Editorial) correct information in Changes V3.0 vs. V3.0RC02 w.r.t. VersionType and RevisionType * #438 correct Figure AssetInformation w.r.t. Resource/path and Resource/value cardinality + update changeLog * Correct figures for data specifications (#437) * correct figure (no idShort for DataSpecification) * no message * V3.0.1 changes * V3.0.1 changes #418 CHANGE (Editorial, the schemas implemented it like this) Annex UML Tables: "0..*" or "0..3" etc. means that the list may be either not available (optional) or the list is not empty. * Remove remaining "IDTA-01xxx_"-Prefixes in refs * Remove Imprint.adoc, as not used * Remove unused duplicated file * Rename adoc files acc. to other spec parts - Removed uppercases in file names acc. to Antora docs: "Although not required, we strongly recommend that you always use lowercase for filenames. Some filesystems are case sensitive, while others are not. By always using lowercase, you avoid any problems that occur if the filesystem, webserver, or transfer tool does not preserve the casing." (https://docs.antora.org/antora/latest/organize-content-files/#storing-your-content-source-files) --------- Co-authored-by: Birgit Boss <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.