=============================================================
Minutes TAB call (April 17, 2015)
=============================================================


Info
Time: 2pmET
Dial:
Host confcall: Fujitsu
US Toll Free: 877-995-3314
US Toll/International: 210-339-1806


Agenda

1. Admin and general status:
- Approval Minutes Apr 3
- plans for July meetings

2. Workplan 2015: open source project support to OASIS Technical Committees (Chet).
- follow-up: how we define this more precisely as a TAB project, expected timeline.

3. Review of short action items (in Kavi), and citation resource work.

4. PRs: status, process and outputs.
- current PR pipeline (see minutes 4/3: EDXL-HAVE, DocBook), UBL-NDR done.

5. Conformance Clause follow-up:
- conformance templates (Ashok, Jacques)
- non-machine-processable specs: (Patrick)(TGF ,...)


Roll:
Kevin Mangold (NIST)
Jacques Durand (Fujitsu)
Ashok Malhotra (Oracle)
Chet Ensign (staff)
Patrick Durusau (individual)

excused:
Gershon Janssen (Board liaison)


Action Items:

AI: (TAB) TAB to review charter between now and the July meeting.

AI: (TAB) TAB to answer questions in the email from Chet about OSS program at OASIS. Staff would appreciate any feedback on the general proposal and the documents. TAB might consider how TC Process could allow for 'invited experts' since that does in fact happen

AI: Patrick to investigate how we could achieve something similar to commenting technique in IETF (needs XSLT?)
--> #315

AI: (still open) Ashok to investigate W3C "annotations"
--> #316

AI: (still open) (Jacques/Ashok) improve on the conf clause template + include the "surroundings" ? (conf clause section structure)
--> #317

AI: (new) Jacques to show/discuss w Patrick UBL mix of non-machine processable + processable.


Minutes:

1. Admin and general status:
- Approval Minutes Apr 3: - no discussion, no objections, minutes approved.
- plans for July meetings: July Wed 29 all day + Thu 30 likely half day. Oracle has offered us meeting space in their offices.Board is meeting that Tuesday, Wednesday and Thursday morning until 11:00 am
- Board meeting on 4/27 about TAB reform: Jacques to check who can attend.
- Patrick: question for Chet - am i correct that Board has already made the decision? Chet: yes - they passed a motion so it is a done deal.
- Chet: in prep for July mtg, I will set up times for us all to have individual brainstorming chats so that we can come together around a group of proposals we can share with the Board in July.

2. Workplan 2015: open source project support to OASIS Technical Committees (Chet).
- Chet: Open source repository proposal.
- Jacques comments: https://lists.oasis-open.org/archives/tab/201504/msg00034.html
- Focus on 3 questions:
1- How do you think this will be received? More particularly, do you see anything that might cause a negative reaction among open source advocates?
2- The procedures are high-level. Do you have any thoughts on how it should be put into practice? Have we made any flawed assumptions? Are there likely to be complexities lurking behind simple sentences that we need to think through more closely?
3- Is anything missing? Have we failed to consider any requirements or use cases that we need to address to make this work.
- Chet: these 2 worlds (OSS, standards) are not in conflict, essentially. Vocabulary alignment needed. Experienced misunderstandings.
- Chet: Meeting with MITRE. "versions" have different meanings - COnfig management, use cases... misunderstandings about terminology. need to align views of users of OSS vs. standards, make it consistent. Like "versioning" is different in both.
- Patrick: Version means something different between the two. standards don't have versions that aren't approved. OSS can have versions not officially released yet.
- Chet: ... "non-standard track" work hs specific OASIS meaning, but used in different sense outside. We should not try to apply TC concepts to OSS work. TC should not be involved in OSS process.
- Patrick: one thing TAB could do is collect up both formally defined and informally understood OASIS terminology to make sure we don't cause any confusion in discussions.
- Ashok: trying to understand what the motivation is for this initiative. are there customers? OSS folks need be interested in this. Are they going to be holding off?
- Chet: motivation: staff had talks with orgs willing to migrate theyr work into standards, but saw OASIS not open enough w OSS mode. a good number of TCs already have a good number of OSS initiatives going on. OASIS cannot ignore this. Business-development driven initiative.
- Jacques: motivation seems to be: (a) demonstrate implementability of the standard, (b) quick feedback to the TC, (c) a good code base to help align and speed-up future private implementations (by definition, forks from the code base), (d) improve interoperability of these from the start.
- J: freedom to fork under umbrella of standard is actually an added benefit - as opposed to OSS projects that do not want to fork code because they are making a single product.
- Chet: goal is not to attract OSS projects in OASIS, but instead be complementary to them (OASIS 1st objective is to support std process). also some preexisting early project may want to become a standardized. --> OASIS OSS project.
- J: this is complementary to standardization, not in conflict.
- on question #2: Chet: not trying to put any roadblock or be too intrusive in the OSS project. TC will assign "maintainers" to the Open repos.
- J: also consider that the # of TC members who participate in the OS project is likely to be low. Important for TC to have a checkpoint on the code to make sure participants don't have undue sway.
- on question #3:
- J: Risk of TC conflict : an OSS team member wanting to commit some code that other TC members do not like? For these reasons it might be wise for the TC to keep a close supervision on OSS work. I.e. use the TC as supreme court for such conflicts about contributions disagreement, as supportive or not of the standard i.e. to rely on TC vote. TC may want to regularly "bless" the current OSS release as supportive and aligned with the standard.

3. Review of short action items (in Kavi), and citation resource work.
- postponed (no progress).

4. PRs: status, process and outputs.
- current PR pipeline (see minutes 4/3: EDXL-HAVE, DocBook), UBL-NDR done and posted.
- remaining:
o DocBook: ends 21 April 2015 : https://lists.oasis-open.org/archives/tab/201503/msg00011.html
o EDXL-HAVE: (Hospital Availability Matrix), ends 15 May 2015 : https://lists.oasis-open.org/archives/tab/201503/msg00008.html

5. Conformance Clause follow-up:
- conformance templates (Ashok, Jacques)
- non-machine-processable specs: (Patrick)(TGF ,...)

- example of mixed requirements in UBL-NDR spec (machine-processable + non-machine-processable).
- AI: Jacques to show/discuss w Patrick UBL mix of non-machine processable + processable.
- conformance templates: need expand with conformance section structure (?), and be part of guidelines rev2 + in another "templates" repository?

Next meeting:
Apr 24, for 1h.
Then tentative May 1st, 1h max. (Jacques to be unable to meet on 5/8, 5/15)

20150417 (last edited 2015-04-29 17:46:15 by chet.ensign)