-
Notifications
You must be signed in to change notification settings - Fork 14
fix: change callbackAddress in ContractAgreementMessage and ContractOfferMessage #155
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
fix: change callbackAddress in ContractAgreementMessage and ContractOfferMessage #155
Conversation
|
I would kindly ask you to wait with PRs after raising an issue. Thanks! I left a comment in the issue, see here. |
|
Seems that leaving the In this case i would convert this issue in order to add the
WDYT? which they have a potential follow-up |
juliapampus
left a comment
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.
Waiting for feedback in #154
juliapampus
left a comment
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.
callbackAddress must be removed from ContractAgreementMessage in dspace.jsonld @wolf4ood
195241a to
bdd78ce
Compare
|
@jimmarino as asked I've amended this PR reflecting the #154 |
1ba2e0b
into
eclipse-dataspace-protocol-base:main
What this PR changes/adds
Removes
callbackAddressfromContractAgreementMessageit also changes
ContractOfferMessage. ThecallbackAddressis not mandatory anymore, but instead as suggestedin #154
one of
consumerPidorcallbackAddressare mandatory depending if it's a counterOffer or a provider initiated CNWhy it does that
Redundant property
Further notes
List other areas of the documents that have changed but are not necessarily linked to the main feature. This could be editorial changes or mistakes in example files that were encountered and were fixed inline, etc.
Linked Issue(s)
Relates #154
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.