1. IGSN-IO progress report
2. IGSN e.V. General Assembly at AGU
3. IGSN syntax proposal
4. IGSN namespace governance proposal
5. IGSN for BGR Berlin/Hannover

1. Gen Assembly has been set for Monday Dec 3, 2012 at AGU (Simon Cox will call in)
2. Gen Assembly Misc item: New members. How to address potential new members at AGU
   1. Need to have current list of potential new members
   2. Invite observer from their institute to General Assembly
   3. Have promotional material (update or enhance brochure)
   4. Have formal procedure ready for them (written proposal)
3. Gen Assembly Misc item: Who else is interested in becoming an Allocating Agent?
4. JK: The current IGSNs are not registered with the handle service currently
5. CC: Question about current status, for the Treasurer's Report at Gen Assembly
   1. Geographical logistics, need two signatures at Potsdam (?)
   2. JK is waiting for letter with KL's signature, which was sent on 11/3/2012 by LH
   3. Need to define when charges will start, and mechanism
6. Syntax proposal
   1. http://dokuwiki.gfz-potsdam.de/datawiki/doku.php?id=igsn:syntax
   2. MP: How is the namespace handled? (That is in a separate document/proposal) http://dokuwiki.gfz-potsdam.de/datawiki/doku.php?id=igsn:namespaces
   3. KL: Who will ensure that the 6-digit code is unique, the Allocating Agent or the user? JK: The Allocating Agent is responsible.
   4. How many allocating agents are there expected? JK: Differentiate between clearinghouse/SESAR and the allocating agents
   5. AK: but then the clearinghouse/SESAR will need to take in other syntax that are not the strict syntax of the current SESAR
   6. KL: SESAR will be split into IEDA as allocating agent and SESAR as the global metadata clearinghouse (higher level service). This should be discussed at the General Assembly. The current SESAR is not the global metadata clearinhouse.
   7. AK: are namespaces in a 1:1 relationship with an allocating agent? e.g. KOP is with SESAR, in the future can a different allocating agent assign KOP? KL: the different allocating agents have different rules for syntax, so this is an interesting case/question.
   8. MP: will there be a downloadable package to mimic SESAR? or will new registries need to be coded up independently?
   9. KL: There are many technical questions that need to be resolved that are difficult to resolve over telecon. Perhaps there should be a dedicated meeting in person for a core group to work on the technical questions.
   10. DK: If I want to increase the number of digits in the code, how is this implemented? Can I keep adding digits as needed? AK: can be flexible but it is determined by the Allocating Agent.
   11. KL: do we need to keep track of what each Allocating Agent sets as the rules JK: yes, we can do that. That is a useful service to the user. KL: as part of becoming an Allocating Agent, they must report the rules to IGSN e.V. AK: there can be a list of rules on a page and the user can go review them
7. Namespace proposal : http://dokuwiki.gfz-potsdam.de/datawiki/doku.php?id=igsn:namespaces
   1. On the current page, “Assigning Agent” = “Allocating Agent”
   2. MP: Is the subnamespace embedded into the n-digit long string? Or in the three digit namespace? SC: different allocating agents will use different patterns, but all will have three character codes that are unique across the whole thing
   3. KL: do we set a limit of how many namespaces an allocating agent can request? JK: this is where subnamespaces come in.
   4. AK: we could advocate that individual users register as a subnamespace associated with a university namespace
   5. DF: question about the distinction between the namespace and the n-digit code (when n is variable) JK: the analogous example of telephone codes is relevant
   6. KL: there are implications for text-mining from Elsevier, etc.
   7. KL: next step is to set up the system that can deal with the namespace requests from different Allocating Agents. JK: this is more or less in place with our metadata store. Administrative workflow is not yet implemented. JK will send around proposal with current system.
8. AK: would be nice to have a wire diagram that explains the process (KL: there was a previous version of something created by Celine Chan - this could be updated)
9. IGSN for BGR Berlin/Hannover
   1. agree on namespace for BGR over email, then start assigning IGSNs

1. Circulate list of curent and potential new members to IGSN e.V. (LH, KL) : http://goo.gl/tfOkk
2. Update the current brochure before AGU (ask for feedback) (LH)
   1. http://dokuwiki.gfz-potsdam.de/datawiki/lib/exe/fetch.php?media=igsn:igsn_brochure_v11.pdf
3. Start defining Allocating Agent procedures
   1. action 1?
4. Register current IGSNs with the existing handle service - begin process (KL, Lulin Song) (11/15, has been assigned)
5. Start planning an in-person meeting
   1. Discuss this at the General Assembly
   2. Possibly another hour could be set up at AGU (not the actual workshop)
6. JK will create and disseminate a proposal for the administrative workflow for the namespace allocation

1. Opening and Welcome
2. Appointment of the meeting chairperson
3. Appointment of the minute taker
4. Establishment of the quorum
5. Approval of the agenda
6. Report by the members of the executive board and discussion
7. Budget proposal for 2013 and discussion
8. Appointment of the electoral officer
9. Election of the members of the executive board
10. Election of the annual accounts auditor
11. Miscellaneous
    1. New members: invite someone from the institution to be an observer
       1. e.g. GNS New Zealand
    2. Allocating Agents
    3. Discuss In-person meeting for Technical Workshop

Back to all minutes: minutes