com.cultureblocs.venue.listing
DEPRECATED — do not write new records. Use community.lexicon.calendar.event instead: it is the shared event record of the open social web, so a venue's nights appear in every calendar app on the network rather than only in CultureBlocs. Cultural extras that the community event does not carry (who is on, works performed) live in com.cultureblocs.venue.lineup, which references the event. This schema remains published so existing records stay resolvable.
Details · record, key tid
| Kind | record |
|---|---|
| Record key | tid |
| Authority | venue.cultureblocs.com |
| Indexed |
Record
record · key tidProperties
billing
arrayWho is on: performers, artists, speakers, DJs. `did` links to a creative profile where one exists.
maxLength: 20
When this record was first stamped. The only immutable field: everything else may be revised by publishing a new commit.
description
stringmaxGraphemes: 2000
end
string · datetimeevent
refInterop hook: a general-purpose event record elsewhere that this listing corresponds to. Prefer pointing over duplicating.
externalIds
arraymaxLength: 20
links
arrayTickets, event page, the venue's own listing.
maxLength: 8
status
stringmaxGraphemes: 32knownValues: scheduled | cancelled | postponed | soldout
tags
arraymaxLength: 8
maxGraphemes: 64
maxGraphemes: 300
venue
unionThe venue profile record, or a named place when the venue has no CultureBlocs identity.
works
arrayWorks shown or performed, where the listing is specific about them.
maxLength: 20
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
DEPRECATED — do not write new records. Use com.cultureblocs.place.lineup, identical except that `venue` is renamed `place`. This schema remains published so existing records stay resolvable. Original description: cultural detail attached to an event that the shared calendar record does not carry: who is on, and what is performed or shown. A layer, not a replacement — it references an event by strongRef and never duplicates it. The same discipline as the creative namespace: layers reference the c
-
Cultural detail attached to an event that the shared calendar record does not carry: who is on, and what is performed or shown. A layer, not a replacement — it references an event by strongRef and never duplicates it. Supersedes com.cultureblocs.venue.lineup, renamed with venue.profile → place.profile so the namespace stays consistent; the shape is unchanged except that `venue` is now `place`. If these fields prove generally useful they belong upstream in the community calendar lexicon, not here
-
DEPRECATED — do not write new records. Use com.cultureblocs.place.profile with spaceTypes including 'venue': the same publishing-party record, widened to cover rehearsal rooms, studios, suppliers and shops. This schema remains published so existing records stay resolvable; readers map it to place.profile as { spaceTypes: ['venue'], location, capacity, accessibility, links, externalIds, tags }. Original description: a venue or organiser as a publishing party: the small amount a grassroots space n
-
A show a project is playing, announced by one of its managers in their own repo. The show itself is the community.lexicon.calendar.event that `event` points to, written to the same repo with the same record key so calendar apps can read it. This record ties it to the project and copies what listings need from it, so the directory can index shows without indexing every calendar event on the network. When the event changes after this was written, its CID no longer matches `event`.
-
app.rocksky.event.music
recordMarks a community.lexicon.calendar.event as a music event (concert, festival, club night...) and links it to the artists performing. The calendar event carries the name, dates and venue; this record carries what is specific to music. Rocksky only indexes calendar events that have one of these attached.