[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Raw Chat Loge for 1/16/2014 WS-BRSP Teleconf
Tom Rutt (Fujitsu): email link for broken references https://www.oasis-open.org/apps/org/workgroup/ws-brsp/email/archives/201401/msg00003.html Jacques (Fujitsu): References comments fixes from Tom: https://www.oasis-open.org/apps/org/workgroup/ws-brsp/download.php/51970/bp12-bp20-rsp10-ReferencesFixes.zip Jacques (Fujitsu): 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 Rutt (Fujitsu): https://www.oasis-open.org/apps/org/workgroup/ws-brsp/email/archives/201401/msg00002.html Tom Rutt (Fujitsu): Minutes of 10/31/2013 approved unan Tom Rutt (Fujitsu): delay approval of November minutes until next meeting Tom Rutt (Fujitsu): October minutes https://www.oasis-open.org/apps/org/workgroup/ws-brsp/email/archives/201311/msg00012.html Tom Rutt (Fujitsu): Topic: Public Review comments Tom Rutt (Fujitsu): comments with category C1 will not result in changes to the profiles. Tom Rutt (Fujitsu): comments with category C2 are non material comments which will be addressed to add clarifications to the profile Tom Rutt (Fujitsu): comments with category C3 would require material changes to the profiles. These would require another public review (none of these in PR comments) Tom Rutt (Fujitsu): Category C4 (unknown) Tom Rutt (Fujitsu): 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 Tom Rutt (Fujitsu): Critical need to be addressed. Tom Rutt (Fujitsu): Major and Minor reviewer comments are less important to be addressed. Tom Rutt (Fujitsu): 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. Tom Rutt (Fujitsu): there is a question as to whether the clarification of normative vs non-normative sections and conformance would require a new public review. Tom Rutt (Fujitsu): 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 Rutt (Fujitsu): just a minute my phone dropped calling back in Tom Rutt (Fujitsu): Tom took action item to update the spreadsheet to reflect the proposed resolutions and to determine the remaining C2 comments which we should consider Jacques (Fujitsu): 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 Rutt (Fujitsu): 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 Tom Rutt (Fujitsu): 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 Jacques (Fujitsu): 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 Tom Rutt (Fujitsu): Add a statement "Only the numbered requirements in this documrnat are normative" before the statement on what is not normative Jacques (Fujitsu): Only the numbered requirements in this documrnat are normative. 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 Tom Rutt (Fujitsu): Micah asked if there are any normative statements that are not directly related to claims of conformance in these profiles Tom Rutt (Fujitsu): Micah: original documents stated that conformance to this profile, requires adhering to the numbered requirements in the document Tom Rutt (Fujitsu): 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" Tom Rutt (Fujitsu): Micah sugested moving the new statments into section 1 on notational conventions rather than in section 2, on requirements semantics. Tom Rutt (Fujitsu): Jacques raised a questionas to the conformance claims mechanisms are a normative part of conformance to this spec. Tom Rutt (Fujitsu): He suggested we remove the "MUST' kewords from section 2.5 to remove them from the normative scope of the profile Tom Rutt (Fujitsu): Action Item: Jacques to update his proposal to resolve normative/non normative aspects of the profiles. Tom Rutt (Fujitsu): Next meeting Tom Rutt (Fujitsu): Feb 27 Tom Rutt (Fujitsu): Meeting closed 3:08 EST.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]