<change-organization>

The <change-organization> element specifies the name of the business unit that required the change.

Specialization hierarchy

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

Content model

(Text | <text>)*

Contained by

<change-item>

Zero or more of the following
  • Text
  • <text>

Contained by

Inheritance

+ topic/data relmgmt-d/change-organization

The <change-organization> 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.
Draft comment: robander
Do we need to specify the scope of "unique" here?

Draft comment: robander
TO RESOLVE 13 May 2026: ha, it often won't be unique because you often use the same name for all instances of a specific type of metadata. Maybe we just get rid of "unique"

Example

This section is non-normative.

The following code sample shows how the <change-organization> element can be used to specify the business unit that required the change:

<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-historylist>