You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The draft makes proposals subsettable unless binding terms mandate linked
execution. Does the proposal need an explicit min_line_items to require a
bundle purchase, or is that left to buyer discretion and the binding terms?
What would settle it: whether sellers actually merchandise bundles that must
be bought whole, and whether "binding terms" is a precise enough hook.
This is the tracking issue for open question 5. Answer it here, in the comments. Evidence from implementation or real inventory carries the most weight (comment process).
Comment period: 2026-09-22 → 2026-10-22. This repository is public, so anonymise any examples.
Change request #23 proposes linked_execution on the proposal and requires on line items. linked_execution: all would cover the all-or-nothing case this question asks about, and requires would cover bundles that are partly linked.
We propose that this open question be dispositioned together with #23 at adjudication. It remains open until then, and comments are welcome on either issue.
A count alone doesn't capture these, because the bundle is a specific set, not "at least N". So I'd back #23's linked_execution: all over a bare min_line_items, with requires for partly linked cases. A domination with optional add-on units is the case requires handles.
Thanks, @premesh, for the OOH evidence. Our packages PR answers this question with a specific set, not a count, as you suggest. A package encloses the line items sold only together, such as a full line, a showing, or a station domination, and the add-ons sold only with it. requires and linked_execution go.
One gap stays open, as § 8 question 5: what cancelling one line item of an agreed package does to the rest.
Analyzed and generated with the help of Claude, fully reviewed by me.
@KonstantinMirin on the open question of cancelling one line item of an agreed package, from the OOH side: a package sold whole is usually cancelled whole. Cancelling one line item of a domination or a full line breaks what was sold, so the seller either cancels the package under the package's cancellation terms or agrees a substitution. When part of a package can't deliver (a screen outage, say), the normal remedy is a makegood on that part, not a cancellation. I'd make partial cancellation of an agreed package a change request the seller must accept, not a buyer right.
Thanks, @premesh. Our packages PR now follows that in § 4.1.4. A buyer cancels the line items of an agreed package only together. One request cancels the same share of each from the same requested date, where each line item's cancellation_policy allows it. A notice on only some of them exercises no option. It is a change request (§ 4.4) the seller MAY decline, unless terms_refs[] gives that change. The PR adds no package-level cancellation terms, and an add-on keeps its own cancellation_policy.
Analyzed and generated with the help of Claude, fully reviewed by me.
Activity
Sirajmx commentedon Oct 8, 2026
Change request #23 proposes
linked_executionon the proposal andrequireson line items.linked_execution: allwould cover the all-or-nothing case this question asks about, andrequireswould cover bundles that are partly linked.We propose that this open question be dispositioned together with #23 at adjudication. It remains open until then, and comments are welcome on either issue.
premesh commentedon Oct 27, 2026
Evidence from OOH: yes, sellers sell bundles that have to be bought whole, and they're common. Examples, anonymised:
A count alone doesn't capture these, because the bundle is a specific set, not "at least N". So I'd back #23's
linked_execution: allover a bare min_line_items, withrequiresfor partly linked cases. A domination with optional add-on units is the caserequireshandles.KonstantinMirin commentedon Nov 5, 2026
Thanks, @premesh, for the OOH evidence. Our packages PR answers this question with a specific set, not a count, as you suggest. A package encloses the line items sold only together, such as a full line, a showing, or a station domination, and the add-ons sold only with it.
requiresandlinked_executiongo.One gap stays open, as § 8 question 5: what cancelling one line item of an agreed package does to the rest.
Analyzed and generated with the help of Claude, fully reviewed by me.
premesh commentedon Nov 7, 2026
@KonstantinMirin on the open question of cancelling one line item of an agreed package, from the OOH side: a package sold whole is usually cancelled whole. Cancelling one line item of a domination or a full line breaks what was sold, so the seller either cancels the package under the package's cancellation terms or agrees a substitution. When part of a package can't deliver (a screen outage, say), the normal remedy is a makegood on that part, not a cancellation. I'd make partial cancellation of an agreed package a change request the seller must accept, not a buyer right.
KonstantinMirin commentedon Nov 7, 2026
Thanks, @premesh. Our packages PR now follows that in § 4.1.4. A buyer cancels the line items of an agreed package only together. One request cancels the same share of each from the same requested date, where each line item's
cancellation_policyallows it. A notice on only some of them exercises no option. It is a change request (§ 4.4) the seller MAY decline, unlessterms_refs[]gives that change. The PR adds no package-level cancellation terms, and an add-on keeps its owncancellation_policy.Analyzed and generated with the help of Claude, fully reviewed by me.