11.3.8 Glossary Document Part

Content Type:

application/vnd.openxmlformats-officedocument.wordprocessingml.document.glossary+xml

Root Namespace:

http://purl.oclc.org/ooxml/wordprocessingml/main

Source Relationship:

http://purl.oclc.org/ooxml/officeDocument/relationships/glossaryDocument

An instance of this part type is a supplementary document storage location which stores the definition and content for content that shall be carried with the document for future insertion and/or use, but which shall not be visible within the contents of the main document story. [Example: A legal contract template might include one or more optional clauses that shall not appear in the document until those clauses are inserted explicitly via a user action. To store these optional clauses until they are inserted, their contents are placed in the glossary document part. end example]

[Note: This part is intended for storage of optional “document fragments” which are often used to perform document assembly. The use of the word glossary is a reference to the fact that each of these entries was historically referenced by its first word in legacy word processing applications, like definitions of terms in a traditional glossary. end note]

The root element for a part of this content type shall be glossaryDocument.

[Example: The following part contains two building blocks. The first block is named “rainbow colors”, belongs to a category called “Misc”, belongs to a gallery called “docParts”, and contains the text “The colors … and violet.” The details of the second block have been omitted:

<w:glossaryDocument xmlns:w="…" >
  <w:docParts>
    <w:docPart>
      <w:docPartPr>
        <w:name w:val="rainbow colors"/>
        <w:style w:val="Normal"/>
        <w:category>
          <w:name w:val="Misc"/>
          <w:gallery w:val="docParts"/>
        </w:category>
      </w:docPartPr>
      <w:docPartBody>
        <w:p>
          <w:r>
            <w:t>The colors of the rainbow are red, orange, yellow,
              green, blue, indigo, and violet.</w:t>
          </w:r>
        </w:p>
      </w:docPartBody>
    </w:docPart>
    <w:docPart>
      …
    </w:docPart>
  </w:docParts>
</w:glossaryDocument>

end example]

A package shall contain at most one Glossary Document part, and that part shall be the target of an implicit relationship from the Main Document (11.3.10) part.

[Example: The following Main Document part-relationship item contains a relationship to a Glossary Document part, which is stored in the ZIP item glossary/document.xml:

<Relationships xmlns="…">
  <Relationship Id="rId4"
    Type="http://…/glossaryDocument" Target="glossary/document.xml"/>
</Relationships>

end example]

A Glossary Document part shall be located within the package containing the relationships part (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Glossary Document part is permitted to have implicit relationships to the following parts defined by ISO/IEC 29500:

• Comments (11.3.2)
• Document Settings (11.3.3)
• Endnotes (11.3.4)
• Font Table (11.3.5)
• Footnotes (11.3.7)
• Numbering Definitions (11.3.11)
• Style Definitions (11.3.11)

A Glossary Document part is permitted to have explicit relationships to the following parts defined by ISO/IEC 29500:

• Alternative Format Import (11.3.1)
• Chart (14.2.1)
• Content Part (15.2.4)
• Diagrams: Diagram Colors (14.2.3), Diagram Data (14.2.4), Diagram Layout Definition (14.2.5) and
• Diagram Styles (14.2.6)
• Embedded Control Persistence (15.2.9)
• Embedded Object (15.2.10)
• Embedded Package (15.2.11)
• Footer (11.3.6)
• Header (11.3.9)
• Hyperlinks (15.3)
• Images (15.2.14)
• Printer Settings (15.2.15)
• Video (15.2.17)

A Glossary Document part shall not have implicit or explicit relationships to any other part defined by ISO/IEC 29500.