Update doco re Amd1

pdf-association · Oct 27, 2023 · fbc25f9 · fbc25f9
1 parent d945696
commit fbc25f9
Show file tree

Hide file tree

Showing 3 changed files with 7 additions and 24 deletions.
diff --git a/ERRATA-AS-XFDF.md b/ERRATA-AS-XFDF.md
@@ -47,25 +47,18 @@ XFDF/FDF designed for a "master" ISO publication to suit whatever an national bo
 
 ## Additional notes related to ISO Amendments
 
-- we do not know how long an ISO Amendment document can be. ISO has the right to not permit an Amendment.
-   - _current expectation is about 60 pages, including ISO front matter!_
+- ISO Amendment documents have to be _very_ short. As WG8 learned, if it is too long ISO has the right to not permit an Amendment.
+   - _current expectation is less than 8-10 pages, including ISO front matter!_
 
-- ISO Amendments require "location statements" prior to each errata. These have now
-been added and published to https://pdf-issues.pdfa.org.
-   - this also increases the length of an ISO Amendment.
+- ISO Amendments require "location statements" prior to each fully reiterated errata. 
+   - _this increases the length of an ISO Amendment_.
 
-- we do not know if ISO will accept our pseudo "track changes" colored markup style which makes changes more visually apparent than the simplistic RICE model of "_change X to Y_"
-   - but this does also increase the length of an ISO Amendment.
+- ISO do not permit the pseudo "track changes" colored markup shown at https://pdf-issues.pdfa.org/ but insteasd require explicit location statements "_change X to Y_"
+   - _this increases the length of an ISO Amendment_.
 
-- ISO Amendments are NOT allowed to have a Table of Contents. This has been confirmed.
+- ISO Amendments are **NOT** allowed to have a Table of Contents. This has been confirmed.
    - This is _unlike_ the original 1,000 page ISO 32000-2:2020 PDF and the utility ToCs published at the top of each HTML page for top level clauses to https://pdf-issues.pdfa.org (as well as a list of Tables that have been updated at https://pdf-issues.pdfa.org/32000-2-2020/) so navigating such a large number of errata will be extremely difficult!
 
 - ISO Amendments are **not** free, unlike previous Technical Corrigenda.
 
 - ISO Directives state can only do a maximum of 2 ISO Amendments per ISO publication.
-
-## Deadlines
-
-- a draft ISO Amendment for consideration during the May 2022 WG8 meeting (and that could form the basis for a PDAM ballot) is desired by the end of March 2022, pending response from ISO to the questions above.
-
-- Both [ISO 14289-2](https://www.iso.org/standard/82278.html) (PDF/UA-2) and [ISO/TS 32005](https://www.iso.org/standard/45878.html) "_PDF 1.7 and 2.0 structure namespace inclusion in ISO 32000-2_" require some current and pending "industry approved" errata to be ISO approved, so that can officially normatively reference them.
diff --git a/README.md b/README.md
@@ -42,12 +42,8 @@ GitHub Issue numbers will appear as popup tooltips when hovering over changes an
 closed GitHub pdf-issues</a>. 
 
 * If a small blue ISO logo is also shown ![ISO approved logo](docs/assets/Logo-ISO-small.png), then that errata has been approved by both the PDF Association's appropriate TWG and the appropriate [ISO working groups responsible for PDF](https://www.pdfa.org/iso-status/). 
-    - For ISO 32000-2:2020 (PDF 2.0), this means the resolution will be included in the forthcoming [Amendment 1](https://www.iso.org/standard/85145.html). Amendment 1 includes [these 89 closed errata labelled with "ISO 32000-2 Amd1"](https://github.com/pdf-association/pdf-issues/issues?q=is%3Aissue+label%3A%22ISO+32000-2+Amd1%22+). 
-
 
 * If a small gray ISO logo is also shown ![ISO submitted logo](docs/assets/Logo-ISO-submitted-small.png), then that errata has been approved by the PDF Association's appropriate TWG and submitted to the appropriate ISO working group and is waiting for approval. 
-    - For ISO 32000-2:2020 (PDF 2.0), these errata have been technically approved by ISO TC 171 SC 2 WG 8, but do not yet have an identified ISO document.
-
 
 * If no ISO logo is shown then the errata has been resolved by the PDF Association's [PDF Technical Working Group](https://www.pdfa.org/community/pdf-technical-working-group/) but has not yet been submitted to ISO for ratification.
 

diff --git a/docs/index.md b/docs/index.md
@@ -28,16 +28,10 @@ closed GitHub pdf-issues</a>.
 <ul>
   <li>
   If a small blue ISO logo is also shown <img src="assets/Logo-ISO-small.png" alt="Small blue ISO logo" />, then that errata has been approved by both the PDF Association's appropriate TWG and the appropriate <a href="https://www.pdfa.org/iso-status/">ISO working group responsible for PDF</a>. 
-    <ul>
-      <li>For ISO 32000-2:2020 (PDF 2.0), this means the resolution will be included in the forthcoming <a href="https://www.iso.org/standard/85145.html">Amendment 1</a>.</li>
-    </ul>
   </li>
 
   <li>
   If a small gray ISO logo is also shown <img src="assets/Logo-ISO-submitted-small.png" alt="Small grey ISO logo" />, then that errata has been approved by the appropriate <a href="https://www.pdfa.org/community/">PDF Association technical working group</a> and submitted to the appropriate <a href="https://www.pdfa.org/iso-status/">ISO working group responsible</a> and is waiting for approval. 
-    <ul>
-      <li>For ISO 32000-2:2020 (PDF 2.0), these errata have been technically approved by ISO TC 171 SC 2 WG 8, but do not yet have an identified ISO document.</li>
-    </ul>
   </li>
 
   <li>