<change-item>

The <change-item> element represents a record of a change to a DITA topic or map.

Specialization hierarchy

The <change-item> element is specialized from <data>. It is defined in the release-management domain module.

Content model

(<change-person> | <change-organization>)*, <change-revisionid>?, <change-request-reference>?, <change-started>?, <change-completed>, <change-summary>*, <data>*

Contained by

<change-historylist>

In order
  1. Zero or more of the following
  2. Optional <change-revisionid>
  3. Optional <change-request-reference>
  4. Optional <change-started>
  5. <change-completed>
  6. Zero or more <change-summary>
  7. Zero or more <data>

Contained by

Inheritance

+ topic/data relmgmt-d/change-item

The <change-item> element is specialized from <data>. It is defined in the relmgmt-domain module.

Attributes

The following attributes are available on this element: universal attributes and @name.

The following attributes are available on this element: universal attributes and the attributes defined below.

@name (data-element attributes)
Defines a unique name for the object.

Example

This section is non-normative.

The following code sample shows how the <change-item> element can be used to detail a change. This example includes two changes, one that is applicable to products A and B and one that is applicable to only product A.

<change-historylist>
  <change-item product="productA productB">
    <change-person>Tom Cihak</change-person>
    <change-organization>JEDEC</change-organization>
    <change-started>2019-01-15</change-started>
    <change-completed>2019-03-23</change-completed>
    <change-summary>Made change 1 to both products</change-summary>
    <data>Details of change 1</data>
  </change-item>
  <change-item product="productA">
    <change-person>Tom Cihak</change-person>
    <change-completed>2019-06-07</change-completed>
    <change-summary>Made change 2 to product A</change-summary>
    <data>Details of change 2</data>
  </change-item>
</change-historylist>