The Lexicon Community lexicon schemas forked from lexicon.community/lexicons

schemas don't validate #1

Closed chrisshank.me
Closed opened by chrisshank.me

A couple mechanical issue I noticed:

  • itemData lists required: ["data"], but the property is named metadata. It also has no createdAt, though the post's example has one.
  • collection has no key (the others say tid).
  • defs#scheme is a union whose refs include an inline {type: string}. Lexicon unions can only ref object defs, so the example post's schemes: ["https", {type: "at", ...}] mix of bare strings and objects isn't expressible. It needs to be all objects (e.g. {scheme: "https"}).

ah thanks for catching these, fixing them now!

collection has no key (the others say tid).

was feeling indecisive and forgot to come back to this, but I'm leaning towards "key": "any" because there could be collections with permanence like bluesky bookmarks or Semble's concept of a library where the key should be a name instead of a TID.

Sign up or Sign in to add to the discussion.