[[TracNav(TracNav/PcaSig)]]

= The POSC Caesar SIG Technical Advisory Board =
 * [wiki:SigTabMandate Mandate for the TAB]
 * [wiki:SigTabMembers Listing of the current PCA TAB members]
 * [wiki:SigTabAgendaMinutes Agenda and Minutes]

Also see the [wiki:Sig Special Interest Groups] main page.

== TAB / SIG / MMT Framework ==
 * Top Layer - TAB - Technical ''Advisory ''Board
   * board appointed representatives of all SIG's and working groups.
   * primarily for road-map coordination, management visibility of work and deliverable progress, resourcing, priorities, etc.
   * coordination with collaborating external work-groups & potentially competing initiatives. More, wider cooperation is always possible and valuable, but pragmatically limited by need to focus on delivering on already agreed collaborations and initiatives.
 * Mid Layer - SME SIG's - Subject Matter Special Interest Groups
   * focussing on agreeing subject matter definitions and requirements for reference data,
   * authority on SME content and usage, reporting deliverables to TAB.
   * any appropriate deliverable format. PCA / JORD-supported sandboxes ideally / ultimately.
   * formation of new SME SIG's generally "ground-up" by groups discovering interest in creating new content.
   * SIG membership limited to members of participating membership organisations, except where TAB authorizes participation by valuable non-member contributors.
   * any non-SME-specific modelling and technology issues / questions routed to Technical SIG's
 * Bottom Layer - Technical SIG's - technical subjects common across all working SIG's.
   * Includes MMT SIG and Technology Architecture SIG
   * Core MMT Group within MMT SIG for '''''commitment '''''to formal expert review, and a deadlock-breaker group with decisive '''''authority '''''on otherwise incomplete technical agreements. Authority comes from main PCA board (and MoU's with collaborating boards) via the TAB appointment of the core and deadlock-breaker groups.

== Roadmap - Goals and Planned Results ==
== Table of Contents ==
=== General ===
=== Ongoing Work ===
=== Related work ===
=== Actions ===
||Meeting||Action nr||Description||Responsible||Deadline||Status||Comments||
||2013-12-05||1||Update the JORD ID Spec document||PCA||||Completed (date?)||||
||2014-01-09||1||Create a status page for namespace implementation.||PCA||||Completed (date?)||||
||2014-01-09||2||Create a new page on posccaesar.org for landscape with linkage between SIG's, other SIG's and external projects||PCA||||?||||
||2014-01-09||3||Mark will forward some relevant info to Håvard and Robin.||Mark Palmer||||Completed (date?)||||
||2014-01-16||1||Create an information page on the PCA website detailing the process for data submission to the RDL||PCA||||Completed (date?)||||
||2014-01-16||2||Magne and Nils will discuss options for participating in the ISO 80000 alignment review for the UOM classes. Contact Mark about combining resources. Status: Nils will come back to Mark with an answer by the end of the week.||PCA||||||||
||2014-02-06||1||Action list items from the TAB should be collected in a spreadsheet with related documentation (responsible, progress, result etc.) (PCA)||PCA||||Completed (date?)||||
||2014-02-06||2||Produce Master RDL Action Item List and email list of interested people (Robin)||Robin||||Completed (date?)||||
||2014-02-06||3||Add numbers to headings for the maintenance procedures||PCA||||Completed (date?)||||
||2014-02-06||4||Write down specification for validation criteria||PCA||||||||
||2014-02-20||1||Organise TAB-SIG meetings monthly, TAB-MRAIL weekly (except for TAB-SIG meetings) with extra people from "MRAIL Team.xslx"||PCA||||Completed (date?)||||
||2014-02-27||1||Meeting about processes and configuration management March 5th 13:00 CET.||PCA||||Completed (date?)||||