==============================================================
Minutes TAB call (Apr 25, 2014)
==============================================================


Info

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


Agenda

1. Admin:
1.1 minutes Apr 4, approval
1.2 short action items status (see below)

2. Status on Excellence award

3. Current guidelines:

3.1 PR Checklist new version with more complete Process category (to be uploaded)
current version at:
https://www.oasis-open.org/apps/org/workgroup/tab/download.php/52557/TAB-ReviewChecklist-rev5.doc
- Checklist for reviewers, but in what form to communicate requirements to editors?

3.2. Conformance Clause guideline:
- toward a short, evolutive guide, easy to read.
- see email:
https://www.oasis-open.org/apps/org/workgroup/tab/email/archives/201404/msg00518.html
- see some initial draft: https://www.oasis-open.org/apps/org/workgroup/tab/download.php/52663/TAB-ConformanceGuide-rev2.doc
- reuse of content from previous Conformance guidelines.

4. PR status.
- Recent reviews, pipeline status (latest: CloudAuthZ), structural issues, other.
- Preparing to generate stats.


Roll:

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


Short Action Items status: those currently open + those that just changed in this meeting

AI-12: [open](in progress) Chet and Patrick: adding comment buttons to HTML specs.
(got it working, still in progress, will send samples for a next PR)
Patrick: AI-12 - minimal form, categories: editorial/technical - impact high/med/low - and wording changes
Patrick: AI-12 - need fix the TOCs links as well
- Script needs more work but it is being used in production. Chet and Patrick will continue to refine.
- still expect we'll have inconsistency due to variety of formats from TCs. For TAB perspective, already used in production. We'll keep refining it. Can close.
-closed

AI-43: [open] Jacques :to validate Patrick's proposal for AI-39.
- we have a way to distinguish several PRs for same spec, in JIRA "version" (Chet)
- closed

AI-44: [open] TAB: how should we make past public review comments available to OASIS members? For long term: search & filter old issues is enough.
- Question: where to make the comments "dumps" available to public?
- chet: load the excel files in KAVI rep, but list them in main TAB KAVI page (e.g. a table in TAB wiki). DOnt believe a nicer interface can work. A navigational page would do.
- Patrick will write something up on this.
- remains open

AI-45: [open] Chet: to check if we can remove aged out Version names without affecting the issues.
- versions can be deleted - but that deletes all issues or erase version # from the issues. That affects other issues material.
- Chet will look into archiving.
- remains open (archiving)

AI-46: [open] Patrick/Jacques: will send examples of good and bad conf clauses before the next meeting
- now part of COnformance guidelines work item.
- closed

AI-48: [open] (new) Chet - to open new JIRA TAB issue on documents in general (follow-up of AI-37) clean-up needed .
- Chet: It isn't clear that the Testability Guidelines was ever on the Policies page
- Chet: keep that material on the WIKI and link to the wiki page from TAB page
- Chet: see JIRA issue: https://tools.oasis-open.org/issues/browse/TAB-981
- closed

AI-50: [open] (new) Patrick to make a page on Wiki for hosting our PR comments available to members.
- open. Per TC name, or per date. Could a script automatically populate the page?
- remain open

AI-51: [all] review / finalize proposed content for TAB public page.
- chet: get our TAB PR comments (some of) links added to the page, then ask Jose to make it public.
Here is the link to TAB Kavi page - http://www.oasis-open.org/apps/org/workgroup/tab
- Robin Cover: Just let me know: I can make the web pages public when we are ready...
- Issue still open pending final request to Robin to make it public
- open + agenda next.


Long-lasting AIs (recorded in JIRA):

AI-TAB-20: [open] (in progress) RFC 2119 / ISO Keyword Guidelines.

AI-TAB-424: [open] (in progress) Define TAB process for Excellence Award

AI-TAB-435: CItation database (RFC)


Minutes: (assisted by: Chet)

1. Admin:
1.1 minutes Apr 4, approval: no discussion, no objs. Minutes approved unanimously
1.2 short action items status (see above)

2. Status on Excellence award
- some time in next cople of weeks, staff will start discussion on distinguished TC contributors. Just wait.

3. Current guidelines:

3.1 PR Checklist new version with more complete Process category (to be uploaded) current version at:
https://www.oasis-open.org/apps/org/workgroup/tab/download.php/52557/TAB-ReviewChecklist-rev5.doc
- Checklist for reviewers, but in what form to communicate requirements to editors?
- deferred to next meeting: people need more time to review latest.

3.2. Conformance Clause guideline:
- toward a short, evolutive guide, easy to read.
- see email:
https://www.oasis-open.org/apps/org/workgroup/tab/email/archives/201404/msg00518.html

- Board asked Scott about every document/guidelines on the OASIS page. Conf guideline just a part of this process.
- short term decision: we'll update the current ly published Conformance Clause guideline, with 2 changes:
o Add preamble saying that the TAB reviewed the doc in April of 2014 and continues to believe this is sound guidance.
o Then replace section three with one paragraph that links readers to the published keywords guideline document.
- AI to Chet to download the current HTML version and add as a document in the TAB's KAVI document repository as a starting point.
- Ashok : The dates in the footer should be updated
- Chet: need add mention that conf clauses is where specs have issues

- Longer term upgrade of Conformance guideline material:
-Jacques presented the "annex" additional material currently in:
https://www.oasis-open.org/apps/org/workgroup/tab/download.php/52839/TAB-ConformanceGuide-rev3.doc
- ... the annex includes a tutorial (how to write a Conformance clause(s)), and 10 rules (dos and dont)
- Chet: need more concrete examples of CC from real specs, and show how to improve them.
- Jacques: real conf. clauses can be in appendix of new guideline. But not that simple: need a lot of context to understand a sampling of conf. clauses. Need normative material from spec.
- Patrick: different work products from this draft ? e.g. 10 rules can be extracted as a separate sheet 1 page

- Chet: need address business process type of Conf clauses. Also various cases such as:
... e.g. XML spec did not use MUST / SHOULD, so need to illustrate this too.
- Chet: separate annexes would let us continue to work on core document and produce useful, shorter documents quickly for member use
- Ashok - commented on the copy Jacques posted yesterday

- Chet: will pull the HTML of current guideline, and we'll use as a source.
- Patrick: Normative content guidelines: another doc should expand on Normative statements
- Jacques: process beyond the quick fix above:
(1) we will start from old/current published Clause guideline in an evolutionary way: file issues against it, propose some diffs.
(2) in parallel, we'll work on new content (tutorial, rules, samples) through other document(s) (e.g. see "annex" posted by Jacques) that could be pubished separately on the TAB page but might/not be in the main guideline document on the Policies & Guidelines page.

4. PR status.
- Recent reviews, pipeline status (latest: CloudAuthZ), structural issues, other.
- Preparing to generate stats.

- Chet: upcoming 30 day CSD PR:
- Cross-Enterprise Security and Privacy Authorization (XSPA)
Profile of SAML v2.0 for Healthcare Version 2.0Committee Specification Draft 01 / Public Review Draft 0115 April 2014
http://docs.oasis-open.org/xspa/saml-xspa/v2.0/csprd01/saml-xspa-v2.0-csprd01.doc
http://docs.oasis-open.org/xspa/saml-xspa/v2.0/csprd01/saml-xspa-v2.0-csprd01.html
http://docs.oasis-open.org/xspa/saml-xspa/v2.0/csprd01/saml-xspa-v2.0-csprd01.pdf
- Chet to send the CND as well as CSD 30 day PRs that are coming up to the TAB mailing list
- Patrick went through past reviews and categorized many comments. We'll generate stats from the Excell sheet.

Next meeting date: Friday, May 9th, for 60 or 90 minutes TBD
Meeting adjourned.


CategoryCategory

20140425 (last edited 2014-05-13 20:23:27 by chet.ensign)