OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

oasis-member-discuss message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [oasis-member-discuss] Comments on proposed policy changes

Hi Dave,Â

I have prepared a comment log for the Board's review. We'll publish that once all comments have been received, considered, and resolved.Â

Quickly, on #2 - yes, we consider markdown the editable source. WhateverÂformat the committee uses to author and edit a spec is what we point to as the editable source. You're not in violation.Â

Hope this helps,Â


On Thu, Sep 17, 2020 at 4:54 PM Lemire, Dave (HII-TSD) <david.lemire@hii-tsd.com> wrote:

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 per

calendar 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




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



Chet Ensign
Chief Technical Community Steward
OASIS: Advancing open source & open standards for the information society

Mobile: +1 201-341-1393Â

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]