Community level Beacon identifier's assignment

[sduvaud]

Currently, the Beacon identifier is just an ID, assigned by the developer of the Beacon.
Of course, it is everybody’s best interest to use a unique ID, and in the worth case it shouldn’t be a problem if the ID is not unique. Anyway, it may be a good practise to set up a kind of central authority to assign Beacon unique identifiers.

[jrambla]

Couldn't we use the reversed namespace approach? i.e. org.ega-archive.beacon

[mcupak]

+1, the reverse domain approach sounds like a good idea.

[antbro]

+1

Tony

---

From: Miro Cupak [[email protected]]
Sent: 28 June 2016 15:54
To: ga4gh/beacon-team
Subject: Re: [ga4gh/beacon-team] Community level Beacon identifier's assignment (#55)

+1, the reverse domain approach sounds like a good idea.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com//issues/55#issuecomment-229074393, or mute the threadhttps://github.com/notifications/unsubscribe/AI_EVOYNsXBe8Mdkgk47TCN3wU5HSyg4ks5qQTWUgaJpZM4IqlgI.

[sdelatorrep]

+1