==============================================================
Minutes TAB call (Oct 18, 2013)
==============================================================


Info

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


Agenda

1. Admin:
- minutes Sept 27, (to be posted)
- action items status
- status of using JIRA to track TAB's work (if any update)
- Filing of Potential new major work items (non machine-processable deliverables, charter creation guidelines)

2. Normative Keyword directives : status
2.5: IT infrastructure update status (migration to Cloud)

3. PR process:
- feedback from initial process application (CAMP), use of JIRA and exports.

4. charter creation guidelines
- a first cut at it. Can we outline what are the items to take care of? the mistakes to avoid?

5. Conformance Guidelines 2.0,
- review and input for a "fundamental" subset of issues.: #11, 14, 15, 17
- Two overarching questions we need to settle (in above issues):
(a) where to use/not keywords (conf clause? keyword-less normative content ?),
(b) can a conf clause override normative content?


Roll:

Ashok Malhotra (Oracle)
Chet Ensign (staff)
Patrick Durusau (individual)
Jacques Durand (Fujitsu)
Zhexuan Song (Huawei)


Action Items status: those currently open + those that just changed status:

AI-4: [closed] Chet: propose rewording of Policy statements for keywords on spec templates. - still open
AI-11: [open](in progress) Chet: to write down best practices to create, save and share JIRA views on issues.
AI-12: [open](in progress) Chet and Patrick: adding comment buttons to HTML specs
AI-13: [open] Chet: to experiment with TC = JIRA issue assignee, how that works with JIRA workflow..
AI-14: [closed] Patrick: spruce-up front page and upload document "Keywords Guidelines for OASIS Specifications and Standards"
AI-15: [closed] Jacques to send the URL to the final version of Keywords Guidelines to Zhexuan for presentation to the Board and to the Chairs list for review and comment.
AI-16: [open] Chet: to create the Component and Versions for charter guidelines and non-machine processable conformance clauses.
AI-17: [open] Chet/Jacques: to follow up on Normative Keyword guidelines after the board meeting.
AI-18: [open] Patrick: to verify whether issues can be imported in some way under new JIRA.


Minutes: (assisted by: Chet)

1. Admin:
- minutes Sept 27, (to be posted)
o Minutes from Sept 27 - chet moves to approve, Patrick seconds. minutes approved
- Action Items specifics:
o AI-13: woudl be a mistake to flood TC mail list with JIRA mail (also don't want to subscribe TAB to every TC)
o Patrick: we agreed to make ourselves the assignee and bulk open the issues when they are sent to the TC.
- status of using JIRA to track TAB's work (if any update)
o Chet: no status update - we should write up how we're using it
- Filing of Potential new major work items (non machine-processable deliverables, charter creation guidelines):
o AI to Chet to create the Component and Versions for charter guidelines and non-machine processable conformance clauses

2. Normative Keyword guidelines : status
o Chet: brought Normative Keyword directives to Board attention. Got some wires crossed... motion made back in July failed about RFC2119... now in form of a guidelines (not directives). There has been confusion about RFC2119 in TC Process.
o the Normative Keyword guide is a guineapig for BoD to set the right process for this kind of deliverables
o AI to Jacques and Chet to follow up after the board meeting, to keep track of it.

2.5: IT infrastructure update status (migration to Cloud)
o Chet: no more hardware in the OASIS data center - had a deadline before renewing contract
o still work to be done including JIRA upgrade
o Ashok: did OASIS get guarantees on uptime etc. SLA?
o Chet: yes. tiered levels of services (from critical, to less critical - affect acceptable downtime, recovery time, capacity, etc.). Kavi now working faster, but Kavi is on hosted Kavi server - not OASIS Cloud.

3. PR process:
- feedback from initial process application (CAMP), use of JIRA and exports.
o Overall it worked for CAMP: spreadheet allows convenient handling of large number of comments.
o However: CAMP was not happy at having to cut & paste TAB issues into their JIRA instance. Cumbersome. Could this be improved?
o P: we haven't found a way to import - when we upgrade, there may be that ability
o AI to Patrick to verify whether issues can be imported in some way under new JIRA
o Chet: migrating to latest JIRA V6 needed? we currently run on very old V3. Next V allows imports. see: https://confluence.atlassian.com/display/JIRA/Importing+Data+From+CSV
("The JIRA Importers plugin assumes that your CSV file is based off a default Microsoft Excel-styled CSV file. Fields are separated by commas")

4. charter creation guidelines
- a first cut at it. Can we outline what are the items to take care of? the mistakes to avoid?
o J: share informally on the mailing list items for the new charter guidelines work

5. Conformance Guidelines 2.0,
- review and input for a "fundamental" subset of issues.: #11, 14, 15, 17
- Two overarching questions we need to settle (in above issues):
(a) where to use/not keywords (conf clause? keyword-less normative content ?),
(b) can a conf clause override normative content?
o J: conformance and normative content should have a high priority: TCs are today facing these questions.

o TAB-11 - Conformance design questions: can a conf clause override a normative statement in the body of the specification?
o J: Different levels of conformance may have different requirements, can a conformance clause make a "should" into a "must?"
o PLD: Open Formula had different levels of conformance. Make normative statements first and then use should/must to define conformance.
o A: agrees that normative content comes first, requirements come later (should/must)
o J: Then Ideally body of specification should not overly bother with should/must - these keywords are more important when referring to this normative content later e.g. in a conf clause.
On some extreme case, no keywords in the normative body of text, only in conformance clauses.

o TAB-14: guidance needed about meta-statements like "this section is normative", or "this section is non-normative"?
o PLD: Need to distinguish normative from non-normative, normative will be subject to invocation by a conformance clause, non-normative is just prose.
o Use of keywords clearly indicate normative content, but a section that does not use normative keywords still needs to be qualified as normative (or non-normative). Is it sufficient to be referred by a conf clause?

Next TAB meeting: 11/1.

Meeting adjourned.

20131018 (last edited 2013-12-05 18:24:36 by chet.ensign)