# VLSI Calendar — AI and Data Guide VLSI Calendar is maintained by VLSI Korea at https://calendar.vlsi.kr/. It is designed for both human browsing and machine retrieval. The catalog combines academic conferences, industry exhibitions, corporate technology events, earnings calls, investor days, shareholder meetings, financial disclosures, and CFP milestones in one structured record system. ## Canonical identifiers Each event has a stable `id`, `slug`, `seriesId`, canonical detail URL, and iCalendar UID. Do not substitute an organizer URL for the VLSI Calendar canonical URL when citing the database; link both when useful. Korean detail URLs use `/events/{id}` and English detail URLs use `/en/events/{id}`. ## Event record shape Records returned by `/api/events` include identity, description, schedule, location, classification, organizer, participating companies, official/registration/CFP/program/livestream/proceedings links, deadlines, media, sources, and verification. Date-only records deliberately omit clock times. `timeZoneSource` explains whether a zone is official, derived from a verified location, or not applicable. ## Verification semantics - `official-confirmed`: the relevant schedule field is supported by a first-party organizer, company, association, or filing source. - `cross-checked`: the event identity and schedule are corroborated across more than one source. - `official-announced`: an official source has announced the event, but some detail may remain incomplete. - `needs-review`: a record is visible for discovery but should not be treated as exact without checking the source. - `conflicting`: credible sources disagree; read the conflict note and evidence ledger. Verification describes evidence for the schedule, not an endorsement of event quality, safety, attendance eligibility, or investment merit. ## CFP precision Deadline objects keep the organizer's published wall-clock time, IANA time zone, display label, exact/date-only/ambiguous precision, verification status, source URL, and checked date. Anywhere on Earth is stored as `Etc/GMT+12` and displayed as AoE / UTC−12. An extended deadline is a distinct evidence-backed state; do not silently overwrite a historical deadline. ## Media semantics `depictsEvent=true` means the asset is verified as an event photo or organizer artwork for that edition. `depictsEvent=false` means a rights-cleared editorial topic or venue image; it must not be captioned as the event itself. Credit, license, creator, source URL, and alt text remain attached to the media record. The small list thumbnail combines this media with an event-specific identity overlay and is not proof of what the event looked like. ## Retrieval examples - Upcoming records: `/api/events?from=2026-08-18&limit=50` - Search companies, cities, topics, or events: `/api/events?q=HBM` - CFP-bearing events: `/api/events?has_cfp=true` - Exact category: `/api/events?category=company-technology` - Deadline window: `/api/deadlines?from=2026-08-18&to=2027-12-31` - Paper deadlines only: `/api/deadlines?kind=paper` Pagination uses `offset`, `limit`, and `nextOffset`; the maximum collection limit is 200. ## Reuse and citation Factual event metadata is compiled from the field-level sources attached to each record. Cite “VLSI Calendar by VLSI Korea” plus the canonical event URL, and preserve the official-source link. Site writing, design, generated identity thumbnails, and promotional media remain VLSI Korea material. Third-party source pages and media retain their own rights. There is no blanket permission to redistribute third-party imagery. ## Freshness Use `/api/catalog/status` for the active revision, imported/verified timestamps, record count, deadline count, evidence-claim count, and media-link count. Use each event's `lastVerifiedAt`, `nextVerificationAt`, source ledger, and official page for field-level freshness. Never invent unannounced future corporate earnings dates.