[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [dataspace-protocol-base-dev] [Dataspace Protocol] DSP extension for Contract Retirement
|
Letâs talk about this. I would like to avoid adding complexity or a lot of work, which would be implied by another state machine. I also think this can get very complicated because cancellation may depend on policies and legal conditions that vary greatly.Â
I also think this should not be part of the base protocol, but rather a separate overlay, potentially done by expanding the event types already present in the base protocol.
Letâs discuss.
Jim
Hi everyone,
now that the DSP base specification is in the voting process in the EDWG spec committee, I'd like to add something to the agenda that we've been talking about for a while now but decided it shouldn't be part of the core spec: Retiring existing Agreements.
ununhexium has described the requirement quite well in this discussion [1]. I'm envisioning something like a "reverse contract negotiation protocol". As opposed to a profile (which further specifies already existing payloads), this would be an extension as
it would be an optional set of new endpoints and schemas in a separate doc, repo and json-ld context. I would however suggest to host it under the eclipse-dataspace-protocol-base GitHub org [2]. Depending on everyone's feedback, I'll create a PR to open a
new repo.
Cheers,
Arno
