The NTAC is a NIEMOpen Technical Steering Committee, responsible for the NIEM technical architecture. This repo contains its meeting minutes and discussion papers.
Other
3
stars
4
forks
source link
Should Publication Process PN include process for getting to OASIS Standard #44
In particular pointing out that it is a decision (ie we might decide for a given document just to keep it at PS without going to OS. However note that only OS can be considered for ANSI, ISO, or ITU standards) and deciding the process to reach that decision (eg do the TSC's recommend to PGB or is it just the PGB without involving the TSC's?).
Another specific item to note (since not paying attention to it has caused other OS's to miss schedules) is 'the 3 statements of use' that are required. A template for the email, or links to examples might help. Historically getting these in other groups has taken longer than anticipated because of worry about who can send the statement and whether legal has to get involved.
The project note on the NIEMOpen Publication Process (https://github.com/niemopen/ntac-admin/blob/main/project-notes/docs/niem-pubs-v1.0-pn01/niem-pubs-v1.0-pn01.md) currently has sections on how to get to a published, approved, Project Specification. It does not contain info about continuing on to OASIS Standard (albeit that is a standard process documented in https://www.oasis-open.org/policies-guidelines/open-projects-process/#oasis-standard-approval-external-submissions). The referenced documents references yet other documents and it might be good to have a NIEM-specific summary in the project note.
In particular pointing out that it is a decision (ie we might decide for a given document just to keep it at PS without going to OS. However note that only OS can be considered for ANSI, ISO, or ITU standards) and deciding the process to reach that decision (eg do the TSC's recommend to PGB or is it just the PGB without involving the TSC's?).
Another specific item to note (since not paying attention to it has caused other OS's to miss schedules) is 'the 3 statements of use' that are required. A template for the email, or links to examples might help. Historically getting these in other groups has taken longer than anticipated because of worry about who can send the statement and whether legal has to get involved.