-
Notifications
You must be signed in to change notification settings - Fork 45
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
Metadata.Json Standaradize for Trace Models #440
base: main
Are you sure you want to change the base?
Conversation
modeling_team |
@@ -1 +1 @@ | |||
{ "status" : "release"} | |||
{ "status" : "standardize"} |
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.
All the models which are going to be standardize, we need to convert them to SAMM model. as this model is still written in BAMM, can you please change this to SAMM and raise new PR.
@@ -1 +1 @@ | |||
{"status":"release"} | |||
{"status":"standardize"} |
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.
same BAMM to SAMM conversion required here also.
@@ -1 +1 @@ | |||
{ "status" : "release"} | |||
{ "status" : "standardize"} |
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.
same BAMM to SAMM conversion required here also.
@jonbckr We need to convert three models from your request to SAMM from BAMM. This is important for us. Could you please check this and initiate this. |
@agg3fe we plan to adapt the mentioned aspect models in the next sprints, so that we can include the migration from BAMM to SAMM within these stories:
The adaptation of these aspect models will start earliest in the next sprint PI11 S2. |
Description
Changed the status in the metadata.json to 'Standardize', for standardized Traceability aspect models.
-->
Closes #439
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)