[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [tag] I need the TC to remediate some problems with the CSD and CND requests
I was rummaging through my mail folders to see if I zoned out on the change of Test Guidelines back to a CSD from a CND. I found this about how specific our motions must be and I realize that our last motion, to forward documents for balloting as 2x CS and 1x CN is also defective in the manner pointed out here. Our ballot motions do not include specific links to the authoritative (editable) versions that are to be carried forward. I confess that I did not give this enough attention to make sure the requisite vote statement was embedded in my DNA as TC Secretary. For that, I apologize. - Dennis -----Original Message----- From: Chet Ensign [mailto:chet.ensign@oasis-open.org] Sent: Sunday, July 24, 2011 15:12 To: Jacques Durand; tag@lists.oasis-open.org Cc: Robin Cover; Paul Knight; Scott McGrath Subject: [tag] I need the TC to remediate some problems with the CSD and CND requests Jacques & members of the Test Assertions Guidelines TC, We started work on TCADMIN-541, 542 and 543 and encountered problems with each submission that require me to ask for clarifying action from the TC before we proceed. I have listed the problems with each of the tickets below, why we have to ask for remedial action and described the actions I'm asking the TC to take to clear them up. I'm sorry that this adds further delays onto your committee drafts and public reviews but the TC Process rules are clear and we must follow them. - TCADMIN-541, CSD Creation / Upload Request for Test Assertions Model Version 1.0 (http://tools.oasis-open.org/issues/browse/TCADMIN-541) - The approval motions referenced in the meeting minutes provided do not contain the link to the Working Draft to be approved by the TC and the ballot referenced describes a PDF document, not editable source. In addition, the minutes are from May 24th, but the document URL in the ticket is to a file loaded on June 9th. The rules require that the motion to approve the CSD include the URL to the working draft being approved by the TC and the working draft must include editable source. The purpose of the rule is to ensure that the CSDs/CNDs created by TC Admin and loaded to the OASIS Library are created from the exact WD approved by the TC. Because we cannot make the connection between what was approved and what was submitted to us, we cannot proceed. - To remedy this, I ask that you hold another vote to approve the work product package that the TC wants promoted to CSD. Either a voice vote recorded in your meeting minutes or an electronic ballot will be fine. Motion language such as: Motion: That the OASIS Test Assertions Guidelines TC approve Test Assertions Model Version 1.0, Working Draft 04 (URI http://www.oasis-open.org/apps/org/workgroup/tag/document.php?document_id=42481) as Committee Specification Draft 04 and submit same to TC Administrator for use in ticket TCADMIN-541 (http://tools.oasis-open.org/issues/browse/TCADMIN-541)." will satisfy the requirement. (Obviously substitute whatever Working Draft URL links to the version that you want to approve.) When you have made and documented the vote, you can update the ticket directly with the link to the approving minutes and the link to the Working Draft or you can send them to me and I will update the ticket, whichever is more convenient. - TCADMIN-542, CND Creation / Upload Request for Test Assertions Guidelines Version 1.0 (http://tools.oasis-open.org/issues/browse/TCADMIN-542) - The approval motion in the meeting minutes does not include a URL to the Working Draft to be approved by the TC. The minutes simply say "2.2 TA GUIDELINES … Paul moved, Kevin seconded that the June 3 working draft be approved as CND03. The motion was approved by unanimous consent." In addition, the minutes are from June 7 but the document URL in the ticket is to a file loaded on June 14th. As above, we are unable to make the connection between the description in the meeting minutes and the document linked in the ticket - To remedy this, I ask that you hold another vote to approve the work product package that the TC wants promoted to CND. Either a voice vote recorded in your meeting minutes or an electronic ballot will be fine. Motion language such as: Motion: That the OASIS Test Assertions Guidelines TC approve Test Assertions Guidelines Version 1.0, Working Draft 03 (URI http://www.oasis-open.org/apps/org/workgroup/tag/document.php?document_id=42529) as Committee Note Draft 03 and submit same to TC Administrator for use in ticket TCADMIN-542 (http://tools.oasis-open.org/issues/browse/TCADMIN-542)." will satisfy the requirement. Again, you can update the ticket with the links to minutes and document or you can send to me. - TCADMIN-543, CSD Creation / Upload Request for Test Assertion Markup Language Version 1.0 - The approval motion in the meeting minutes does not include a URL to the Working Draft to be approved by the TC. The minutes simply say "2.1 TAML … Paul moved, Kevin seconded that the June 2 working draft, with the agreed change, be approved as CSD05. The motion was approved by unanimous consent." The minutes themselves are dated June 7 but the URL provided was loaded to Kavi on June 14 and there appear to be differences between the files dated June 2nd and the file in the provided URL. As above, we are unable to make the connection between the description in the meeting minutes and the document linked in the ticket. Also, we cannot accept motions to approve working drafts contingent on someone making changes after the approval. The motions must approve a complete and completed working draft. - To remedy this, I ask that you hold another vote to approve the work product package that the TC wants promoted to CSD. Either a voice vote recorded in your meeting minutes or an electronic ballot will be fine. Motion language such as: Motion: That the OASIS Test Assertions Guidelines TC approve Test Assertions Markup Language Version 1.0, Working Draft 05 (URI http://www.oasis-open.org/apps/org/workgroup/tag/document.php?document_id=42522 ) as Committee Note Draft 03 and submit same to TC Administrator for use in ticket TCADMIN-543 (http://tools.oasis-open.org/issues/browse/TCADMIN-543)." will satisfy the requirement. Again, you can update the ticket with the links to minutes and document or you can send to me. Again, I regret that this is further delaying work on your requests. We will hold the tickets in their current position in the queue and resume work on them as soon as you provide us with the TC approvals and URL's as described above. Please let me know if you have any questions or if I can be of help in expediting the resolution. -- /chet ---------------- Chet Ensign Director of Standards Development and TC Administration OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-378-3472 Mobile: +1 201-341-1393 Follow OASIS on: LinkedIn: http://linkd.in/OASISopen Twitter: http://twitter.com/OASISopen Facebook: http://facebook.com/oasis.open --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]