Comment #1Amendment: Proposed MINHERS Addendum 32f, Amendment Effective Dates, Transition Period and Publication, Draft PDS-03Page Number: 6Paragraph / Figure / Table / Note: 502.4.2.3Comment Intent: Not an ObjectionComment Type: EditorialComment: The language is unclear to me. Does this allow the effective date to be a date other than January 1 or July 1st? If so, it seems to get away from the intent of the biannual update and I would object. Recommend that the effective date still be restricted to the next Jan 1st or July 1st. Proposed Change: 502.4.2.3 For amendments that require Approved Software Rating Tools to be updated and accredited, the Effective Date is permitted to be the next Jan 1st or July 1st after the default Effective Date at the discretion of if the Standards Management Board chooses to allow additional time to update and accredit Approved Software Rating Tools, and shall not be less than 60 days after the Publication Date.
The language is unclear to me. Does this allow the effective date to be a date other than January 1 or July 1st? If so, it seems to get away from the intent of the biannual update and I would object. Recommend that the effective date still be restricted to the next Jan 1st or July 1st.
502.4.2.3 For amendments that require Approved Software Rating Tools to be updated and accredited, the Effective Date is permitted to be the next Jan 1st or July 1st after the default Effective Date at the discretion of if the Standards Management Board chooses to allow additional time to update and accredit Approved Software Rating Tools, and shall not be less than 60 days after the Publication Date.
Return to Proposed MINHERS Addendum 32f, Amendment Effective Dates, Transition Period and Publication, Draft PDS-03