igsn:namespace_allocation_proposal
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
igsn:namespace_allocation_proposal [2013/05/03 14:49] lhsu created |
igsn:namespace_allocation_proposal [2016/03/24 10:15] (current) ulbricht |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====Procedure for Namespace Allocation ==== | ||
| - | Discussed by the IGSN e.V. on 15 April 2013 | ||
| - | Currently SESAR assigns IGSNs with three-digit namespaces and 6-digits for unique identification within a namespace. In the future we will have longer namespaces and fewer digits for unique identification, | + | :!: The documentation |
| - | + | ||
| - | Each allocating agent will have a two digit supernamespace code, e.g. IE for IEDA, and will have complete authority to assign any subnamespace within it. The user may chose a personal namespace that will come after the allocating agent code. e.g. HS becomes IEHS or HSU becomes IEHSU. The allocating agent is responsible for making sure it assigns unique namespaces within its domain e.g. IE, and can assign any subnamespace under IE immediately. IGSN e.V. does not enforce a set length for the total namespace, though it is suggested that the total namespace (including 2 digit code) is 4-6 digits in length. | + | |
| - | + | ||
| - | If the user wants a namespace that is not a subnamespace | + | |
| - | + | ||
| - | A module that will complete the task of namespace assignment (described above) is planned for development, | + | |
igsn/namespace_allocation_proposal.1367592564.txt.gz · Last modified: 2013/05/03 14:49 by lhsu
Page Tools
