Minutes Jan 16, 2014

----------------------------------------

DRAFT MINUTES

OASIS WS-BRSP TC Meeting

16 January 2014, 11:00am to noon PDT

----------------------------------------

Scribe: Jacques Durand

0. Call to Order and roll call

Jacques Durand calls the meeting to order and welcomes everyone.

* Roll call:

Ram Jeyaraman

Doug Davis

Jacques Durand

Tom Rutt

Micah Hainline

Tom Link (observer)

Excused:

Alessio Soldano

Gershon Janssen

This meeting is quorate.

Agenda adopted.

1. Administrative: min Nov 21. (to be posted).

2. Public Review feedback:

- Follow-up on the "must fix" issues (category C1,

see https://www.oasis-open.org/apps/org/workgroup/ws-brsp/document.php?document_id=51486&referring_url=%2Fkws )

- Tom's proposed fixes (issues about references)

- Jacques proposed clarification (issues about conformance)

- overall plan to comments disposition.

Minutes:

1. Administrative:

min Nov 21. (to be posted): postponed

min Oct 31: approved.

2. Public Review feedback:

- Follow-up on the "must fix" issues (category C1,

- Tom's proposed fixes (issues about references)

- Jacques proposed clarification (issues about conformance)

- overall plan to comments disposition.

- comments with category C1 will not result in changes to the profiles.

- comments with category C2 are non material comments which

will be addressed to add clarifications to the profile

- comments with category C3 would require material changes to the profiles.

These would require another public review (none of these in PR comments)

- Category C4 (unknown)

- The JIRA ratings for the comments are the reviewer's prospective.

Those comments addressed as "blocking" need to be addressed, even if they are categorized by us as C1

- "Critical" need to be addressed.

- "Major" and "Minor" reviewer comments are less important to be addressed.

- There are no C3 comments since any comments which would require material change,

were classified as C1. For example the requests for later version of the referenced specs

is outside of the scope of the Profiles, which are tied to dated versions of the base specs.

- there is a question as to whether the clarification of normative vs

non-normative sections and conformance would require a new public review.

- So far none of the proposals would change any test assertion, or

would require re-running the TAs on the logs we have from WS-I activities

- Tom took action item to update the spreadsheet to reflect the

proposed resolutions and to determine the remaining C2 comments which we should consider

- Conformance / normative comments (disposition) from Jacques:

https://www.oasis-open.org/apps/org/workgroup/ws-brsp/download.php/51972/BasicProfile-v1.2-WD03-b.doc

- Tom also took an action item to change the inline http links

to external specs to use the normative and non normative reference labels.

This involves adding normative and non-normative references to clauses 1.7 and 1.8

- Jacques proposed resolutions are for Includes disposition (see diffs) for:

TAB-313

TAB-314

TAB-315

TAB-316

TAB-317

TAB-319

TAB-320

TAB-330

TAB-344

- No other content is normative outside the numbered Requirements in this document. In particular:

-Examples material is not normative and only intended as illustrative.

-Appendix material is not normative.

-Test Assertions associated with this profile specification are not normative.

-Explanatory text introducing Requirements is not normative.

-Notes are not normative.

-Schemas are not normative

- Add a statement "Only the numbered requirements in this documrnat

are normative" before the statement on what is not normative

- Only the numbered requirements in this documrnat are normative.

- Micah asked if there are any normative statements that are not directly related

to claims of conformance in these profiles

- Micah: original documents stated that conformance to this profile,

requires adhering to the numbered requirements in the document

- suggestion: The numbered requirements in this profile are the only

statements which are related to Conformance to this profile.

Thus, only the numbered requirements in this profile are considered normative"

- Micah sugested moving the new statments into section 1 on notational conventions

rather than in section 2, on requirements semantics.

- Jacques raised a questionas to the conformance claims mechanisms are a

normative part of conformance to this spec. suggested we remove the "MUST' kewords

from section 2.5 to remove them from the normative scope of the profile

- Action Item: Jacques to update his proposal to resolve normative/non normative aspects of the profiles.

- Meeting adjourned, next meeting Feb 27 tentative.

ws-brsp message