-
Notifications
You must be signed in to change notification settings - Fork 25
Beacon specification #1
Comments
have a look at http://mcupak.github.io/beacon-of-beacons/beacons.html http://mcupak.github.io/beacon-of-beacons/beacons.html
|
@skeenan Yes, I that is one of the implementations I had looked at. |
@pdl The official spec is indeed the Avro schema you listed. As you correctly pointed out, it's work in progress. The fact that it shares the repository with other independently developed schemas makes it difficult to tag it properly, which is why we started doing so on the Beacon Network site. If you're starting to implement a beacon now, the 0.2 version listed there is what you should be implementing. As for the URL structure, the de facto standard is to provide 2 endpoints returning data in JSON:
Several institutions implemented beacons, but due to the lack of standardization at the time, they're using different variations of the API, and often don't conform to 0.1 or 0.2. Beacon Network takes care of the conversions and wraps beacons in a unified API, which can be queried through http://beacon-network.org/. |
Is it worth adding some of this information to the readme of this repo? I attempted to raise a similar issue (ga4gh/ga4gh-schemas#256 (comment)) but didn't get a response which could resolve the issue. There needs to be some canonical documentaion. |
Here is one of the JSON beacon implementation which has a short descriptive
text and example requests:
http://genome.ucsc.edu/cgi-bin/hgBeacon
|
Emphasising the association in the class that connects the genotype and the phenotype
Is there a specification for Beacon? If so, where is it?
The only things approaching a specification I can find relating to it is an Avro schema, which is described as a work in progress, doesn't seem to exist in the two tagged versions of that repository, only in the current 'master' branch (although two versions are described here, apparently 0.1 and 0.2), and doesn't describe URL structure requirements or format expectations.
I notice that 19 institutions have apparently implemented Beacon, and some of the implementations are available (e.g. https://github.com/mcupak/beacon-of-beacons) - was there once a specification which has since disappeared or been deprecated?
We were hoping to put up a Beacon implementation but don't want to start unless we know that it's actually achievable at the moment, i.e. that we will be able to verify for ourselves that we have (or haven't) built a compliant implementation, by reference to a specification or a test suite.
Other resources that I've had a look at, to no avail:
The text was updated successfully, but these errors were encountered: