Beacon API versus EGA Beacon

[Eva]

Dear all,

I am sure this is a stupid question, but since I`m new to this theme I`ll try anyway;

I don`t understand the  difference between regular beacons and EGA beacon.

If I understand it right the first versions of the Beacon API worked in the way: "a researcher asks for a specific variant across other beacons, and either gets yes/no back".

Then the Beacon API started a cooperation with Elixir and the Beacons got the three tired Access (Public, registered, controlled).

Now where in this picture does EGA Beacon come in? Is this in reality the  same as the Beacon-Elixir three tired Access? Or is it something new? And if yes, what is the difference?

I really appreciate all answers!

Kind regards,

 

[Miro Cupak]

Hi Evita,

Beacon is a GA4GH standard and lives here: https://github.com/ga4gh-beacon/specification. It basically describes what a Beacon service looks like, and how to implement it, including access tiers. The standard itself is not a service you can run, it’s more like a guide for implementing one.

There are tens of implementations of this standard by various institutions out there, incl. ELIXIR and EGA itself. I don’t know what exactly you mean by "Beacon-Elixir" or “EGA beacon”, but I’m guessing you’re probably referring to the implementations by the two respective institutions. I’m not familiar with the details of these, you’ll need to contact those institutions for more info.

Hope that helps clarify things,
Miro

> --
> You received this message because you are subscribed to the Google Groups "GA4GH Beacon Network" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to ga4gh-beacon-net...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/ga4gh-beacon-network/a89432ae-eef4-41d9-bc6f-3113d40e88f8%40googlegroups.com.

[Eva]

Thank you very much, that actually clarifies a lot.

I thought there was only one standard that needed to be implemented from one institution, but now I understand why Elixir and EGA offers two implementations that in fact function in the same way.

Thank you again!

Kind regards

mandag 16. desember 2019 18.59.46 UTC+1 skrev Miro Cupak følgende:

Hi,

Beacon is a GA4GH standard and lives here: https://github.com/ga4gh-beacon/specification. It basically describes what a Beacon service looks like, and how to implement it, including access tiers. The standard itself is not a service you can run, it’s more like a guide for implementing one.

There are tens of implementations of this standard by various institutions out there, incl. ELIXIR and EGA itself. I don’t know what exactly you mean by "Beacon-Elixir" or “EGA beacon”, but I’m guessing you’re probably referring to the implementations by the two respective institutions. I’m not familiar with the details of these, you’ll need to contact those institutions for more info.

Hope that helps clarify things,
Miro

> On Dec 15, 2019, at 4:00 PM, Eva <evita....@gmail.com> wrote:
>
> Dear all,
> I am sure this is a stupid question, but since I`m new to this theme I`ll try anyway;
> I don`t understand the  difference between regular beacons and EGA beacon.
> If I understand it right the first versions of the Beacon API worked in the way: "a researcher asks for a specific variant across other beacons, and either gets yes/no back".
> Then the Beacon API started a cooperation with Elixir and the Beacons got the three tired Access (Public, registered, controlled).
>
> Now where in this picture does EGA Beacon come in? Is this in reality the  same as the Beacon-Elixir three tired Access? Or is it something new? And if yes, what is the difference?
>
> I really appreciate all answers!
>
> Kind regards,
>
>
>  
>
> --
> You received this message because you are subscribed to the Google Groups "GA4GH Beacon Network" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to ga4gh-beacon-network+unsub...@googlegroups.com.