Closed johannsvarela closed 3 months ago
@johannsvarela is this going to be common/shared between other models also? If yes, then please change the package structure to io.catenax.shared.--, like for shared message header model.
modeling_team
FYI @jonbckr @BenediktMuellerIML @jacewski-bosch
@johannsvarela is this going to be common/shared between other models also? If yes, then please change the package structure to io.catenax.shared.--, like for shared message header model.
This is not shared.
@johannsvarela could you please update your branch with main branch. As your code does not include message header 2.0.0, so it is failing.
@agg3fe Done! :)
@agg3fe Done! :)
Thanks. assigned MS2 again. Let's do MS3 together in next meeting.
@agg3fe @catroest No required anymore, therefore this PR will be closed by myself! :)
Description
Notifications are - in contrast to classical data offers - a way to push data from a sender to a receiver. This model describes the message for quality investigations and alerts. It contains standardized attributes for message content common across most use cases in CatenaX. It belongs to the same group of aspects as the MessageHeader Aspect Model: io.catenax.shared.message_header
The bugfix (#476) of the shared Message Header aspect model must be done before this PR can be continued!
Closes #305 and replaces #311
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)