Request Title 

Abbreviations, acronyms, initialisms, and short forms can be confusing or unreadable to users of some adaptive technologies like screen readers and to some readers with learning disabilities. The Abbr tag provides semantic markup to disambiguate these terms. PDF/UA requires ambiguous Abbr content to be expanded using an E key; see PDF/UA's Text module for details.

Provides compatibilitly with HTML 4.x and XHTML 1.x and 2.x (PDF collapses ABBR and ACRONYM onto ABBR) and HTML5, XHTML5, and XHTML 2.0.

Add a new Structure Type in Table 338 as follows:

Request Title 

Add a new Structure Type in Table 338 as follows:

Request Title 

Add a new Structure Type in Table 338 as follows:

Request Title 

Add a new Structure Type in Table 338 as follows:

Request Title 

Add a new Structure Type in Table 338 as follows:

Request Title 

Add a new Structure Type in Table 338 as follows:

Request Title 

Add a new Structure Type in Table 338 as follows:

Request Title 

A dek is a short summary of an article following a heading and preceding the article text. It is usually longer than a heading (sometimes several paragraphs in length), yet does not function as a heading or as main-article text.

Preferred usage: As a child of other structural elements (e.g., inside Art or Sect), following any heading tag and preceding full text of an article or other content.

NB:  The correct spelling is dek, not deck; the words have different spellings so that the word “dek” never appears in published copy. (Editors search for “dek” and ensure it appears solely in comments or other internal instructions.)

Add a new Structure Type in Table 338 as follows:

Description for Table 340:

Request Title 

Update Table 334 to include a CL type to the "List Elements / "Structure Types" table-cell.

Add the following item to Table 336:

Request Title 

Below are the steps suggested.  Two new subsections (one for MathML elements and one for their attributes) need to be added.  These both introduce tables that need to be added. The text refers to table numbers.  In the text below, they are labeled as mmm and nnn and values need to be given to them based on the numbering in the spec.

Note:  It appears that elements and attributes in the PDF spec are "CamelCased" (capital letters for each new word as in "ColSpan").  In MathML, all lowercase letters are used.  In the proposal below, all lowercase letters are used, but nothing is broken if they are switched to the PDF convention.  It would be slightly simpler for exporters to XHTML if lowercase were used, but I doubt it makes any real difference.

Here are the recommendations for what to change:

1. Table 340 (Standard structure types for illustration elements) should have the "Formula" modified to be

   Structure Type	Description
   Formula	(Formula) A mathematical formula. This structure type is used to identify an entire content element as a formula. Formula can only directly contain the math element.  See table mmm.

2. The last paragraph of 14.8.4.5 (Illustration Elements) should be modified to read:
   
   "For accessibility to users with disabilities and other text extraction purposes, an illustration element should have an Alt entry or an ActualText entry (or both) in its structure element dictionary (see 14.9.3, “Alternate Descriptions,” and 14.9.4, “Replacement Text”). The Formula structure element should contain MathML structure elements corresponding to the subexpressions for maximum accessibility. Alt is a description of the illustration, whereas ActualText gives the exact text equivalent of a graphical illustration that has the appearance of text."
   
3. A new subsection of 14.8.4.5 (Illustration Elements) should be added at the end of 14.8.4.5.  The text of that section is shown below.
   
   
4. The following row should be added to the bottom of table 341:
   

   Owner	Description
   MathML-2.0	Attributes associated with MathML structure elements (Table mmm).

   
   MathML   Attributes governing the layout of mathematical expressions.
   
5. A new section should be added after 14.8.5.7 (Table Attributes) that lists the MathML attributes in Table nnn. The text of that section is shown below
   

New subsection of 14.8.4.5 (Illustration Elements)

The structure types described in table mmm, "MathML Elements", are used to describe formulas. The math element should only appear inside of a Formula element, and all of the other elements in the table should only appear inside of other MathML elements.

Note:  Strictly speaking, the elements listed in Table mmm are neither BLSEs or ILSEs.

The elements in Table mmm are specified in detail in the MathML 2.0 recommendation and are summarized below. With the exception of the math, semantics, annotation, and annotation-xml elements, these elements are part of chapter 3 (Presentation Markup) of the MathML 2.0 recommendation.

Note:  MathML contains a set of "content" elements that are notation-independent semantic elements. These elements do not have a specific layout and so are not meaningful in PDF unless they are inside of a semantics element.

New Section after 14.8.5.7 (Table Attributes)

The attribute owner "MathML-2.0" shall be associated with the attributes listed below.

Table nnn lists all of the attributes associated with the MathML elements listed in Table mmm. The description of each attribute is given in MathML 2.0 recommendation. They are listed below for completeness.

Unless otherwise noted:

• these attributes are not inherited (i.e., they apply only to the current element of the structure tree, not the children of the element);
• these attributes are optional;
• the "type" for each value is "string";
• "class", "id", "style", "xref", and "xlink:href" are legal attributes for all MathML elements.
  

The attributes exist for compatibility with MathML generation tools and to allow translation of the math to an XML dialect.

Table nnn  Standard math attributes

Request Title 

The Note to Table 337 says "Lookup is heuristic".  This will lead to incompatible behavior by AT. No algorithm is given in ISO 32000 when header cell IDs and table data cell IDs are not present.

In the case that header data cell IDs and table data cell IDs are specified, PDF/UA specifies an algorithm to associate table header cell(s) with table data cell(s). This algorithm is flawed. The recursive lookup mentioned in Table 349 (Headers) is ambiguous in that the headers might be only associated with a row, a column, or both. The following change to Table 349 requires that a recursion be explicit.  In particular:

• HEADER lookup through IDs is not recursive
• ID order is specified 

The PDF/UA specification provides an algorithm for both of the cases above so that all AT will associate the same table header cells and table data cells. The new descriptions and their rationale are described in PDF/UA Tables specification.

Request Title 

Request Submitted By 

Language codes shall now be derived from BCP 47, “Tags for Identifying Languages,” which supersedes the standards listed in PDF 1.7.

 All content with language codes.

ISO is no longer the source of the standard for language codes. BCP 47 is an alias to the current RFC 4646/4647, which contains all language codes previously listed in ISO 639-1, -2, and -3 (minor errors corrected) and new language codes.

Change all references to ISO 639-x or RFC 4646/4647 to BCP 47. As BCP 47 grandfathers all previous language codes, there is no need to make a different provision for PDF documents created before ISO 32000 was enacted.

Request Title 

Request Submitted By 

Update the Lang key in Table 124. Remove “If this entry is absent, the language shall be considered to be unknown.” Replace with “If this entry is absent, such absence provides no information as to the language of the document; in particular, an absence of this entry does not by itself mean the language of the document is unknown.”

Request Title 

Non-linguistic content.

Add a new paragraph at the end of 14.9.2.2 as follows:

Non-linguistic content should be marked with language code "zxx" (See ISO 639-2).