igsn:29_august_2014_friday_namespace_allocation_call
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
igsn:29_august_2014_friday_namespace_allocation_call [2014/08/29 15:53] lhsu |
igsn:29_august_2014_friday_namespace_allocation_call [2015/05/05 15:30] (current) lhsu |
||
|---|---|---|---|
| Line 23: | Line 23: | ||
| - We May need to set up a namespace subcommittee (mentioned in the text) | - We May need to set up a namespace subcommittee (mentioned in the text) | ||
| - One of the flowcharts is out of date for the Namespace Approval Procedure, if not rejected right away, there is an appeals period. (vs. an approval period). If the IGSN e.V. membership does not react, is an approval. If we seek an approval, we need a vote for all cases, but if it is an appeals period then it goes through unless there is a rejection. The persons who would appeal would be the persons that objected. | - One of the flowcharts is out of date for the Namespace Approval Procedure, if not rejected right away, there is an appeals period. (vs. an approval period). If the IGSN e.V. membership does not react, is an approval. If we seek an approval, we need a vote for all cases, but if it is an appeals period then it goes through unless there is a rejection. The persons who would appeal would be the persons that objected. | ||
| - | - A top level namespace can only be given to a new allocating agent. Or, an existing allocation agent serves a new community and wants another top level namespace. For Example: IEDA is building sample registration system for the critical zone observatories. The will ask for the top level namespace CZ. It's agreed, that the top level namespaces are under the responsibility of the Allocating Agent to adhere to the rules of the handbook. | + | - A top level namespace can only be given to a new allocating agent. Or, an existing allocation agent serves a new community and wants another top level namespace. For Example: IEDA is building sample registration system for the critical zone observatories. The will ask for the top level namespace CZ. It's agreed, that the top level namespaces are under the responsibility of the Allocating Agent to adhere to the rules of the handbook. |
| - **Rules and Responsibilities of members** | - **Rules and Responsibilities of members** | ||
| - CC: in the invoicing letter, we wanted to tell members what the rules and responsibilities are. Must adhere to the namespace policies. What happens if members don't use their namespace, then what? Membership rules refer to the statutes. But something else about the rules of the procedures should be included. If members don't come to the meetings (are not active), then after a warning, they may not be members anymore. If There is a member that pays their dues and attends the meetings, and they propose a namespace, at that point there is not much else besides saying that the namespace is unique and conforms to the understood rules. But after that, what happens if the group doesn' | - CC: in the invoicing letter, we wanted to tell members what the rules and responsibilities are. Must adhere to the namespace policies. What happens if members don't use their namespace, then what? Membership rules refer to the statutes. But something else about the rules of the procedures should be included. If members don't come to the meetings (are not active), then after a warning, they may not be members anymore. If There is a member that pays their dues and attends the meetings, and they propose a namespace, at that point there is not much else besides saying that the namespace is unique and conforms to the understood rules. But after that, what happens if the group doesn' | ||
| - | - AA: every year at the General Assembly, then we will get some summary of what has happens. There is a summary once per year. Total, new IGSNs assigned per year. (1) Looking at the activity is something that DataCite does as well, to give a people an overview of what is happening. (2) If a namespace is not being used, for one year, then it should be revoked. There could also be a warning period. | + | - AK: every year at the General Assembly, then we will get some summary of what has happens. There is a summary once per year. Total, new IGSNs assigned per year. (1) Looking at the activity is something that DataCite does as well, to give a people an overview of what is happening. (2) If a namespace is not being used, for one year, then it should be revoked. There could also be a warning period. |
| - **IGSN Syntax beyond the suggested syntax** | - **IGSN Syntax beyond the suggested syntax** | ||
| - KL: Does there need to be an approval process for changing the syntax of IGSN, and to what level should this be controlled? It's easy to control 9 digits. If someone wants 11 digits, then something would need to be implemented at the top level registry that allows 11 digits for that allocating agent. Maybe you suggest deviations from 9 characters, you need to provide the resources to do the checks. JK: at the moment the system checks if you are allowed to register in that namespace and the webspace, it doesn' | - KL: Does there need to be an approval process for changing the syntax of IGSN, and to what level should this be controlled? It's easy to control 9 digits. If someone wants 11 digits, then something would need to be implemented at the top level registry that allows 11 digits for that allocating agent. Maybe you suggest deviations from 9 characters, you need to provide the resources to do the checks. JK: at the moment the system checks if you are allowed to register in that namespace and the webspace, it doesn' | ||
| - | - The Original use case works fine with 9 characters. There are other use cases (very large repositories) that cannot use only 9 characters. But if IGSN e.V. allows allocating agents to do // | + | - The Original use case works fine with 9 characters. There are other use cases (very large repositories) that cannot use only 9 characters. But if IGSN e.V. allows allocating agents to do // |
| - There seems to be agreement that the capacity to have longer names needs some logic behind it and it needs to be discussed by the IGSN e.V. group. i.e. There are lengths that are " | - There seems to be agreement that the capacity to have longer names needs some logic behind it and it needs to be discussed by the IGSN e.V. group. i.e. There are lengths that are " | ||
| - **Does there need to be a Quorum to decide on namespaces? | - **Does there need to be a Quorum to decide on namespaces? | ||
igsn/29_august_2014_friday_namespace_allocation_call.1409327601.txt.gz · Last modified: 2014/08/29 15:53 by lhsu
Page Tools
