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

feat(DemandAndCapacityNotification): added notificationIds #692

Merged
merged 11 commits into from
Mar 18, 2024
Merged

feat(DemandAndCapacityNotification): added notificationIds #692

merged 11 commits into from
Mar 18, 2024

Conversation

tom-rm-meyer-ISST
Copy link
Contributor

@tom-rm-meyer-ISST tom-rm-meyer-ISST commented Mar 4, 2024 •
edited by agg3fe
Loading

Description

-->

Closes #691

MS2 Criteria

(to be filled out by PR reviewer)

  • the model validates with the SAMM SDS SDK in the version specified in the Readme.md of this repository by the time of the MS2 check (e.g., 'java -jar samm-cli.jar aspect <path-to-aspect-model> validate ). The SAMM CLI is available here and in GitHub
  • use Camel-Case (e.g., "MyModelElement" or "TimeDifferenceGmtId", when in doubt follow https://google.github.io/styleguide/javaguide.html#s5.3-camel-case)
  • the identifiers for all model elements start with a capital letter except for properties
  • the identifier for properties starts with a small letter
  • all model elements at least contain the fields "preferred name" and "description" in English language. The description must be comprehensible. It is not required to write full sentences but style should be consistent over the whole model
  • Property and the referenced Characteristic should not have the same name
  • the versioning in the URN follows semantic versioning, where minor version bumps are backwards compatible and major version bumps are not backwards compatible.
  • use abbreviations only when necessary and if these are sufficiently common
  • avoid redundant prefixes in property names (consider adding properties to an enclosing Entity or even adapt the namespace of the model elements, e.g., instead of having two properties DismantlerId and DismantlerName use an Entity Dismantler with the properties name and id or use a URN like io.catenax.dismantler:0.0.1)
  • fields preferredName and description are not the same
  • preferredName should be human readable and follow normal orthography (e.g., no camel case but normal word separation)
  • name of aspect is singular except if it only has one property which is a Collection, List or Set. In theses cases, the aspect name is plural.
  • units are referenced from the SAMM unit catalog whenever possible
  • use constraints to make known constraints from the use case explicit in the aspect model
  • when relying on external standards, they are referenced through a "see" element
  • all properties with an simple type have an example value
  • metadata.json exists with status "release"
  • generated json schema validates against example json payload
  • file RELEASE_NOTES.md exists and contains entries for proposed model changes
  • all contributors to this model are mentioned in copyright header of model file

MS3 Criteria

(to be filled out by semantic modeling team before merge to main-branch)

  • All required reviewers have approved this PR (see reviewers section)
  • The new aspect (version) will be implemented by at least one data provider
  • The new aspect (version) will be consumed by at least one data consumer
  • There exists valid test data
  • In case of a new (incompatible) major version to an existing version, a migration strategy has been developed
  • The model has at least version '1.0.0'
  • If a previous model exists, model deprecation has been checked for previous model
  • The release date in the Release Note is set to the date of the MS3 approval

@tom-rm-meyer-ISST tom-rm-meyer-ISST requested a review from agg3fe March 4, 2024 13:28
@github-actions GitHub Actions
Copy link

github-actions bot commented Mar 4, 2024

Validation Report for io.catenax.demand_and_capacity_notification/2.0.0/DemandAndCapacityNotification.ttl

Input model is valid

stiwan8020
stiwan8020 reviewed Mar 4, 2024
View reviewed changes
io.catenax.demand_and_capacity_notification/2.0.0/DemandAndCapacityNotification.ttl Outdated
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix : <urn:samm:io.catenax.demand_and_capacity_notification:1.0.0#> .
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2.0.0

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for pointing out! Fixed

@github-actions GitHub Actions
Copy link

github-actions bot commented Mar 4, 2024

Validation Report for io.catenax.demand_and_capacity_notification/2.0.0/DemandAndCapacityNotification.ttl

Input model is valid

@github-actions GitHub Actions
Copy link

github-actions bot commented Mar 4, 2024

Validation Report for io.catenax.demand_and_capacity_notification/2.0.0/DemandAndCapacityNotification.ttl

Input model is valid

1 similar comment
@github-actions GitHub Actions
Copy link

github-actions bot commented Mar 4, 2024

Validation Report for io.catenax.demand_and_capacity_notification/2.0.0/DemandAndCapacityNotification.ttl

Input model is valid

@github-actions GitHub Actions
Copy link

github-actions bot commented Mar 4, 2024

Validation Report for io.catenax.demand_and_capacity_notification/2.0.0/DemandAndCapacityNotification.ttl

Input model is valid

@github-actions GitHub Actions
Copy link

github-actions bot commented Mar 4, 2024

Validation Report for io.catenax.demand_and_capacity_notification/2.0.0/DemandAndCapacityNotification.ttl

Input model is valid

@github-actions GitHub Actions
Copy link

github-actions bot commented Mar 4, 2024

Validation Report for io.catenax.demand_and_capacity_notification/2.0.0/DemandAndCapacityNotification.ttl

Syntax error in line 129, column 1: Broken token (newline): urn:uuid:d9452f24-3bf3-4134-b3eb-68858f1b2362 .

  124: :notificationId a samm:Property ;
  125:    samm:preferredName "Notification ID"@en ;
  126:    samm:description "Unique ID identifying the notification."@en ;
  127:    samm:characteristic ext-uuid:UuidV4Trait ;
  128:    samm:exampleValue "urn:uuid:d9452f24-3bf3-4134-b3eb-68858f1b2362 .
->129: 
  130: :relatedNotificationId a samm:Property ;
  131:    samm:preferredName "Related Notification ID"@en ;
  132:    samm:description "Unique ID identifying another notification somehow related to the current one."@en ;
  133:    samm:characteristic ext-uuid:UuidV4Trait ;
  134:    samm:exampleValue "urn:uuid:d05cef4a-b692-45bf-87cc-eda2d84e4c04" .

@github-actions GitHub Actions
Copy link

github-actions bot commented Mar 5, 2024

Validation Report for io.catenax.demand_and_capacity_notification/2.0.0/DemandAndCapacityNotification.ttl

Input model is valid

@github-actions GitHub Actions
Copy link

github-actions bot commented Mar 6, 2024

Validation Report for io.catenax.demand_and_capacity_notification/2.0.0/DemandAndCapacityNotification.ttl

Input model is valid

agg3fe
agg3fe reviewed Mar 7, 2024
View reviewed changes
io.catenax.demand_and_capacity_notification/2.0.0/DemandAndCapacityNotification.ttl Outdated
samm:dataType xsd:string .

:TextLengthConstraint a samm-c:LengthConstraint ;
samm:preferredName "UserInputConstraint"@en ;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no camel case

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

resolved, thanks for pointing out!

agg3fe
agg3fe approved these changes Mar 7, 2024
View reviewed changes
Copy link
Contributor

@agg3fe agg3fe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@agg3fe
Copy link
Contributor

agg3fe commented Mar 7, 2024

@tom-rm-meyer-ISST please check one comment.

@github-actions GitHub Actions
Copy link

github-actions bot commented Mar 7, 2024

Validation Report for io.catenax.demand_and_capacity_notification/2.0.0/DemandAndCapacityNotification.ttl

Input model is valid

@tom-rm-meyer-ISST tom-rm-meyer-ISST requested a review from agg3fe March 7, 2024 16:27
agg3fe
agg3fe approved these changes Mar 8, 2024
View reviewed changes
Copy link
Contributor

@agg3fe agg3fe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@agg3fe agg3fe added the MS2_Approved Checklist "MS2 Valid Model" is approved. label Mar 8, 2024
agg3fe
agg3fe reviewed Mar 11, 2024
View reviewed changes
io.catenax.demand_and_capacity_notification/RELEASE_NOTES.md Outdated
@@ -1,6 +1,21 @@
# Changelog
All notable changes to this model will be documented in this file.

## [2.0.0] - 2024-03-04
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please change the date to 11th

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated

@agg3fe 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
@github-actions GitHub Actions
Copy link

Validation Report for io.catenax.demand_and_capacity_notification/2.0.0/DemandAndCapacityNotification.ttl

Input model is valid

agg3fe
agg3fe approved these changes Mar 18, 2024
View reviewed changes
Copy link
Contributor

@agg3fe agg3fe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@agg3fe agg3fe merged commit 68e72e4 into eclipse-tractusx:main Mar 18, 2024
4 checks passed
@tom-rm-meyer-ISST tom-rm-meyer-ISST deleted the feat/691-dcm-notification branch March 19, 2024 06:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@stiwan8020 stiwan8020 stiwan8020 left review comments

@agg3fe agg3fe agg3fe approved these changes

Assignees
No one assigned
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
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

[Model Update]: DemandAndCapacityNotification to include notification Ids
3 participants
@tom-rm-meyer-ISST @agg3fe @stiwan8020