Skip to content

OQ-2 — Do seller catalogs (catalog_ref) belong in 3.0? #3

Open

Description

@Sirajmx

Spec: § 2.2 · OpenProposal 3.0 draft 1 (§ 8, question 2)

Or should the object stay fully inline until a later version? catalog_ref
buys compactness across a large shelf at the cost of a resolution step during
discovery and a versioning regime sellers must operate.

What would settle it: how large a real shelf gets, and whether sellers
already maintain versioned, immutable catalog entries or would have to build
that.


This is the tracking issue for open question 2. 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.

Activity

  1. pinned this issue on Sep 24, 2026
  2. pkanna000 commented on Nov 7, 2026

    @pkanna000

    One security consideration for OQ-2. A catalog_ref resolves to seller-controlled content that buying agents fetch at discovery time and, for prose entries, feed to a model. If catalogs stay in 3.0, two things make them safe to dereference at machine speed: a content digest so the pinned version can be checked (#129), and the same rules as for inline free text, so typed fields govern and resolved text never directs the reading agent (proposed in #155). With both, catalogs cost no more trust than inline values.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions