I have the following comments on the TC Process document included in the proposed policy changes distributed to OASIS members on 2 September 2020 by Chet Ensign:
Â
ONE: ÂÂSections 1.7, 2.6, and 2.8.2 all state (in slightly varying words): "Comments to the TC made by non-TC Members, including from the public, must be made via the TC's comment facility, and shall not be accepted via any other means."
However, GitHub repos established by OASIS for the development of TC work products include the following language in the CONTRIBUTING.md file: âPersons who are not TC members are invited to open issues and provide comments using this repository's GitHub Issues tracking facility or using the TC's comment facility.â (Example copied from https://github.com/oasis-tcs/oc2arch/blob/master/CONTRIBUTING.md)
The TC Process document should address GitHub as a venue for commenting, and define any terms or conditions that apply to comments submitted via GitHub that differ from use of the TCâs âcomment facilityâ.Â
Â
TWO:ÂÂ Section 2.2.2 states: All approved versions of OASIS Deliverables must be published in (1) editable source, (2) HTML or XHTML, and (3) PDF formats. The TC must explicitly designate one of those formats as the authoritative document."
The OpenC2 TC has been declaring the Markdown (.md) format files developed in its GitHub repositories as the authoritative document; is that in violation of the TC Process? Or is the markdown format covered under â(1) editable sourceâ?
THREE: ÂÂRegarding: "[OBPC-65] 15 or more of eligible OASIS Members have submitted valid objections, the Committee Specification shall be deemed to have been rejected and shall not progress to OASIS Standard."
Wouldn't it be better to specify this in terms of a percentage of OASIS members, rather than a hard number?
FOUR: Section 1.6 Leave of Absence state âEvery Voting Member of an OASIS TC may request one Leave of Absence percalendar year.â What is the purpose of limiting LOAs to one per year? If the intent is that a second or subsequent LOA would require TC approval, the language currently does not convey that intent.
Â
Â
Thank you for the opportunity to review and comment on the proposed policy changes
Â
Dave
Â
David Lemire
Systems Engineer
HII Mission Driven Innovated Solutions (HII-MDIS)
Technical Solutions Division
302 Sentinel Drive | Annapolis Junction, MD 20701
Work (301)Â575-5190 | MobileÂ(443)Â535-1182
Â
