On the fourth day of the TAG (Thursday 9th March) we will be holding an all-day working session for the secretariat’s Technical Team to collaborate with the growing number of IATI experts in the community in progressing improvements to the standard as well as associated rules and guidelines.
We will work to a formal agenda and minutes will be taken. Papers covering all issues to be discussed will be prepared and published well in advance. The meeting will be co-chaired by John Adams as TAG Chair and myself as Technical Lead. We will attempt to reach consensus wherever possible.
The agenda will be restricted to proposals that relate directly to specific changes to the standard or associated rules and guidelines. For example, fixing the result element to accurately deal with aggregation and disaggregation is on the agenda. Discussion on how results reporting should be improved in general is not – but will no doubt be a key issue in the TAG proper on day 2 or 3.
A proposed draft agenda can be found here. Everyone is welcome to add to this agenda provided that the item contains a specific proposal and can be supported by written argument to be shared with the community on this forum.
It will be possible to add matters arising during the first two days of the TAG into the agenda, provided that they are presented as concrete, actionable proposals.
The agenda is already quite full. If we need to trim, we will do so as transparently as possible.
There is no restriction on attendance provided you inform us in advance so that we know how many to cater for. HOWEVER, all discussions will be technical and will assume that you have a good working knowledge of the standard and its implementation. Novices are welcome to attend as observers, but no attempt will be made to explain matters to you.
Our work should lead to:
- The content for the Version 2.03 decimal upgrade. Formal work on this will begin immediately after the TAG and should go live by the end of the first quarter of 2017.
- The clarification and definition of some key rules and guidelines that cannot be enforced by the schema.
- The earmarking of certain proposals for Version 3.01 integer upgrade (for which there is still no planned date) and consensus to drop some items that have been proposed over the past years, but have never ‘made the grade’.