Package-level declarations
Types
Where the issuer placed a TicketDetail on the original pass.
Input model for creating or updating a ticket — the complete writable state, minus the server-managed fields (Ticket.uri, Ticket.artifactUri, Ticket.images, timestamps, Ticket.etag).
The binary pass images to store alongside a ticket on create, one slot per pkpass image role. Each non-null slot is uploaded into the ticket's container as {role}.png and linked from the ticket document (see TicketImages).
A wallet ticket stored on the pod as a schema:Ticket resource — the complete read model.
The binary content of a ticket's original imported artifact read from the pod (e.g. the .pkpass file the ticket was created from).
One barcode on a ticket (solidshare:Barcode). A pass may carry several.
The barcode symbology of a ticket's payload, stored on a TicketBarcode as solidshare:symbology so the exact barcode the issuer produced can be re-rendered for gate scanners. NONE marks a barcode-less pass.
A Bluetooth beacon that should surface the pass nearby (solidshare:Beacon).
The kind of pass a ticket represents. Stored as a literal (solidshare:category) and used to pick the reservation/trip RDF types — see documents/TICKET_VOCAB.md §1.
A label/value field the importer could not map to a typed term (solidshare:Detail).
The event an event ticket admits to (schema:Event or a subtype).
Whether and how an event was rescheduled (schema:eventStatus).
The pod URIs of a ticket's stored pass images (solidshare:logoImage …), one per pkpass image role. They live inside the ticket's own container, next to its document and artifact, so sharing the container shares the complete pass.
The two-ended journey a travel ticket admits to (schema:Flight / TrainTrip / BusTrip / BoatTrip).
A list of TicketSummary rows, wrapped as one Parcelable so it can cross the AIDL boundary.
A loyalty / frequent-flyer membership (schema:ProgramMembership).
The issuing organisation (schema:Organization, or schema:Airline when iataCode is set).
The ticket holder (schema:Person).
A venue (schema:Place) — the location of an event ticket.
A location that should surface the pass on the lock screen (solidshare:RelevantLocation).
The booking envelope (schema:Reservation or a subtype) — everything about the booking itself.
Booking lifecycle state (schema:reservationStatus).
A seat assignment (schema:Seat). Repeatable — a pass may cover several seats.
How a ticket entered the pod, stored as a literal (solidshare:source).
One end of a journey — an airport, station, stop, or terminal.
The pass's presentation (solidshare:PassStyle) — colours and image URIs. Entirely minted, so the wallet can re-render a pass faithfully and export it back to .pkpass.
One cached row of a tickets index — enough to render a wallet list without fetching each ticket document.
A Wi-Fi network associated with the pass (solidshare:WifiNetwork).
The mode of a journey — selects the schema:*Trip type and its per-mode predicates.
Properties
Document name minted for a ticket inside its per-ticket container ({tickets}/{uuid}/ticket). The container also holds the ticket's binary attachments (artifact, pass images). Extension-less like TICKETS_INDEX_NAME.
Fragment identifying a ticket's primary subject within its document.
Where a new tickets container is allocated: {storage}datamodule/tickets/.
Document name minted for the tickets index inside a tickets container. Extension-less on purpose: the index is linked data reached by URL — the type index links to this document and its rows link to each ticket — so the URI never encodes a representation (the module reads and writes JSON-LD; how the server persists it is its own business). Only used when bootstrapping; discovery always follows the registered URL, whatever it is named.
Path suffix appended to a storage root when allocating the tickets container.