-
Notifications
You must be signed in to change notification settings - Fork 47
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
[Model Update]: Refurbishing_Certificate v3.0.0 #685
Merged
agg3fe
merged 8 commits into
eclipse-tractusx:main
from
tanweersalah:feature-refurbishing
Mar 12, 2024
Merged
[Model Update]: Refurbishing_Certificate v3.0.0 #685
agg3fe
merged 8 commits into
eclipse-tractusx:main
from
tanweersalah:feature-refurbishing
Mar 12, 2024
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
@agg3fe Please review once the recycling strategy is MS3 approved, Thanks |
@tanweersalah can you change the version to 3.0.0 for all certificates? |
Validation Report for io.catenax.refurbishing_certificate/3.0.0/RefurbishingCertificate.ttlInput model is valid |
Merged recycling strategy 3.0.0
Validation Report for io.catenax.refurbishing_certificate/3.0.0/RefurbishingCertificate.ttlInput model is valid |
Validation Report for io.catenax.shared.recycling_strategy_certificate/3.0.0/RecyclingStrategyCertificate.ttlInput model is valid |
Validation Report for io.catenax.refurbishing_certificate/3.0.0/RefurbishingCertificate.ttlInput model is valid |
tanweersalah
changed the title
[Model Update]: Refurbishing_Certificate v2.1.0
[Model Update]: Refurbishing_Certificate v3.0.0
Mar 7, 2024
@agg3fe updated |
agg3fe
approved these changes
Mar 7, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Validation Report for io.catenax.refurbishing_certificate/3.0.0/RefurbishingCertificate.ttlInput model is valid |
agg3fe
added
the
MS3_Approved
Checklist "MS3 Release Model" is approved. The associated pull request can be merged to the "main-br
label
Mar 11, 2024
Validation Report for io.catenax.refurbishing_certificate/3.0.0/RefurbishingCertificate.ttlInput model is valid |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
MS2_Approved
Checklist "MS2 Valid Model" is approved.
MS3_Approved
Checklist "MS3 Release Model" is approved. The associated pull request can be merged to the "main-br
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.
Description
[Model Update]: Refurbishing_Certificate v3.0.0
link to the current version of the Refurbishing_Certificate (v2.0.0):
https://github.com/eclipse-tractusx/sldt-semantic-models/blob/main/io.catenax.refurbishing_certificate/2.0.0/RefurbishingCertificate.ttl
Issue : #615
-->
Closes #615
MS2 Criteria
(to be filled out by PR reviewer)
DismantlerId
andDismantlerName
use an EntityDismantler
with the propertiesname
andid
or use a URN likeio.catenax.dismantler:0.0.1
)preferredName
anddescription
are not the samepreferredName
should be human readable and follow normal orthography (e.g., no camel case but normal word separation)MS3 Criteria
(to be filled out by semantic modeling team before merge to main-branch)