Map q=source and delete onto the domain #186

Closed
opened 2026-08-12 04:14:05 +00:00 by rosa · 1 comment
Owner

Map: #181
Blocked by: #182 (Survey Micropub media-endpoint extensions and client behavior) — the wire shapes come from its findings.
Blocked by: #183 (Does Media grow user-facing metadata?) — the q=source response can only carry metadata that exists.

Question

Map q=source and delete onto the domain through the Micropub Adapter. Given the research findings on client expectations and wire shapes, decide:

  • The exact q=source request/response the endpoint implements (params honored, JSON shape, paging/limit, single-item url= lookup or not).
  • The delete wire shape and its scope enforcement — media scope, delete scope, or both? Same warn-and-allow semantics as the web library can't apply over a protocol with no confirm step: does Micropub delete detach referencing Photos silently, or refuse when referenced?
  • Whether listing/delete reuse exactly the domain ops the library page uses (they should, per ADR-0019's one-op-behind-adapters stance) and what, if anything, q=config should newly advertise.

Resolve through /grilling + /domain-modeling.

Map: #181 Blocked by: #182 (Survey Micropub media-endpoint extensions and client behavior) — the wire shapes come from its findings. Blocked by: #183 (Does Media grow user-facing metadata?) — the `q=source` response can only carry metadata that exists. ## Question Map `q=source` and delete onto the domain through the Micropub Adapter. Given the research findings on client expectations and wire shapes, decide: - The exact `q=source` request/response the endpoint implements (params honored, JSON shape, paging/limit, single-item `url=` lookup or not). - The delete wire shape and its scope enforcement — `media` scope, `delete` scope, or both? Same warn-and-allow semantics as the web library can't apply over a protocol with no confirm step: does Micropub delete detach referencing Photos silently, or refuse when referenced? - Whether listing/delete reuse exactly the domain ops the library page uses (they should, per ADR-0019's one-op-behind-adapters stance) and what, if anything, `q=config` should newly advertise. Resolve through /grilling + /domain-modeling.
Author
Owner

Ruled out of scope — the map's destination was redrawn to drop the Micropub media-endpoint growth: Micropub's client base is too small to justify the extra protocol surface. The media endpoint keeps plain upload as-is; listing and delete will live in the web library only. The wire-shape findings from Survey Micropub media-endpoint extensions and client behavior remain on record should this return as a fresh effort.

Ruled out of scope — the map's destination was redrawn to drop the Micropub media-endpoint growth: Micropub's client base is too small to justify the extra protocol surface. The media endpoint keeps plain upload as-is; listing and delete will live in the web library only. The wire-shape findings from [Survey Micropub media-endpoint extensions and client behavior](https://code.cosmicrose.dev/rosa/vernier/issues/182) remain on record should this return as a fresh effort.
rosa closed this issue 2026-08-12 04:48:41 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
rosa/vernier#186
No description provided.