ModuleDraft 0.2, for comment

On this page
  1. Sketch
  2. Purchasing (sketch, not implemented anywhere)
  3. Open questions
  4. Prior art

Catalog and Commerce module (draft 0.2)

Status: draft for comment. Namespace: org.openmusiccollection.catalog. Needs: Core 2.0.

The core describes what a person has. This module describes what exists and where it can be had: which services carry a recording, what it costs to buy, and where its artist would like people to listen and buy. It is how an app takes someone from "I like this" to "it's in my collection, and the artist got paid", with as few steps as possible.

Sketch

Offers. An offer says that a recording or release can be had on a source, and how:

{ "item_ids": { "isrc": "QZES72600001" },
  "platform": "music.example.net",
  "ref": "night-drive",
  "url": "https://music.example.net/night-drive",
  "access": ["stream", "purchase"],
  "price": { "amount": "1.50", "currency": "EUR", "format": "flac" },
  "published_by": "artist",
  "signature": "…" }

published_by is artist, label, platform or user. An offer the artist published and signed is the artist's own preference, and apps SHOULD show it first.

Resolvers. A resolver answers "what offers exist for this item?" from its identifiers, GET {resolver}/offers?isrc=…, and "where else is this?" from a copy: GET {resolver}/links?platform=spotify&ref=…&want=youtube,bandcamp answers the copies it knows on the platforms named in want (all it knows, without want). Anyone can run one, and a resolver needs no access to anyone's collection. Where else a song can be found isn't part of the collection, which holds what the person keeps; it is a resolver's question. The standard defines the questions and the answers. The catalog behind them is the resolver's own.

Purchases end on the seller's own checkout. After a purchase, the person's collection gains a copy with ownership: digital on that source. Payment is not part of the standard.

Purchasing (sketch, not implemented anywhere)

How an app could take someone from an offer to a purchase that lands in their collection, without the app ever seeing payment details. Written down so the pieces fit; nothing here is built.

  1. An offer says its terms. Besides price, an offer may carry license (what the buyer gets: download, stream, a Creative Commons licence), minimum (for pay-what-you-want, the least price) and referral (an id the seller pays a share to, so an app or a curator that sent the person is credited).
  2. The app sends the person to the seller. POST {seller}/checkout with the offer and the referral answers a URL on the seller's own site, where the person pays. The app is never in the payment.
  3. The seller tells the home. With the person's consent (given at checkout, naming their home), the seller sends a signed receipt to POST {home}/purchases: the item, the copy on the seller's source with ownership: digital, the price paid and the seller's signature. The home combines the item like any addition, and the Collector module can keep what was paid.
  4. A refund revokes it. The seller sends the receipt again with revoked: true; the home turns the copy's ownership back to none (or removes the copy) and /changes reports the item, so the apps that showed it as bought see the change.

Open questions

  1. How does an artist prove they are the artist, so their signed offers can be trusted?
  2. Regional prices and availability: one offer per region, or a list inside one offer?
  3. Can a purchase be confirmed back to the app that sent the person, without sharing payment details? (The sketch above says: through the referral only.)

Prior art

DDEX (how labels deliver releases and deal terms to stores), MusicBrainz identifiers, Schema.org MusicRecording and Offer.