Welcome to the Beacon v2 Documentation
!!! Note "Approved GA4GH Standard"
On [2022-04-21](formats-standards/#dates-and-times) Beacon v2 has been approved as an official [GA4GH standard](https://www.ga4gh.org/) through the GA4GH steering committee.
With growing interest from the community in the implementation of the Beacon protocol into resources and workflows, the major 2.0 release in 2022 introduced a large range of new features which were considered important by the community.
!!! Warn "Move to Beacon v2"
With the release of Beacon v2 implementations of v1 and earlier are not longer supported.
Deployers of Beacon instances or networks are advised to migrate to v2 of the
standard. The functionality of Beacon v1 [can be easily implemented in v2](/FAQ/#v1-emulation).
The core documentation (i.e. this document) can be found on here.
Informations for Different Types of Beacon Users
The Beacon documentation provides information for different types of users, depending on their interests and use cases. Although those will overlap, we highlight information relevant for some general scenarios throughout the documentation.
Users
A Beacon user (or end-user) is interested in querying Beacon instances and networks, either through web interfaces by using the Beacon API. While users of Beacon web forms in principle do not need to understand the underlying query syntax and response formats they too may benefit from some insights into the general capabilities of the underlying protocol.
!!! Warning "User" * Beacon v2 Models * Knowing what is available in an instance * Data Models and Schemas * Beacon Flavours & Response Granularity * Security * Other Request, Response & Error Elements * Using Beacon v2 Features * Genomic Variant Queries * Filters for Phenotypes, Diseases & Other Parameters * Alternative Schemas Link
Deployers and Implementers
A Beacon Deployer is someone who wants to make their genomics resource accessible through the Beacon protocol, without necessarily being interested or experienced in the computational aspects; while a Beacon Implementer provides the technical expertise (and potentially may get involved with Beacon development itself, e.g. to extend the protocol for novel use cases).
!!! Important "Deployer"
* Beacon v2 [Models](models.md)
* Reference Implementation [Link](https://b2ri-documentation.readthedocs.io/en/latest/)
* Infrastructure requirements
* How to install
* [Configuration](https://github.com/EGA-archive/beacon-2.x)
* Cohorts and/or Datasets
* Entry types
* Filtering terms
* Alternative schemas
* Granularity & Security
* Administration
* Testing the instance
!!! Note "Implementer"
* Beacon v2
* [Framework](framework.md)
* [Models](models.md)
* Protocol basics
* [Requests](variant-queries.md), responses & errors
* [OpenAPI](https://www.openapis.org)
* Beacon v2 Features
* [Filters](filters.md)
* Alternative schemas [Link](models.md)
* Configuration
* Granularity & security [Link](framework.md)
* Verifying [compliance](https://ga4gh-approval-service-registry-demo.ega-archive.org/)
Stakeholder
!!! Danger "Stakeholder" * Integration into GA4GH * Leveraging The Beacon Framework in other domains * Success Stories: * Implementations * Real world data