<organization>

The <organization> element contains the name of a business unit.

Specialization hierarchy

The <organization> element is specialized from <data>. It is defined in the bookmap module.

Content model

(Text | <data> | <sort-as> | <foreign> | <keyword> | <markupname> | <apiname> | <option> | <parmname> | <cmdname> | <msgnum> | <varname> | <wintitle> | <numcharref> | <parameterentity> | <textentity> | <xmlatt> | <xmlelement> | <xmlnsname> | <xmlpi> | <term> | <abbreviated-form> | <text> )*

Zero or more

Attributes

The following attributes are available on this element: data-element attributes, link-relationship attributes, and universal attributes.

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

@datatype (data-element attributes)
Specifies the type of data contained in the @value attribute or within the <data> element. A typical use of @datatype will be the identifying URI for an XML Schema datatype.
@format (link-relationship attributes)
Specifies the format of the resource that is referenced. See STUB CONTENT for detailed information on supported values and processing implications.
@href (link-relationship attributes)
Specifies a reference to a resource. See STUB CONTENT for detailed information on supported values and processing implications.
@name (data-element attributes)
Defines a unique name for the object.
@scope (link-relationship attributes)
Specifies the closeness of the relationship between the current document and the referenced resource. The following values are valid: local, peer, external, and -dita-use-conref-target.

See STUB CONTENT for detailed information on supported values and processing implications.

@type (link-relationship attributes)
Describes the target of a reference. See STUB CONTENT for detailed information on supported values and processing implications.
@value (data-element attributes)
Specifies a value associated with the current property or element.

Example

This section is non-normative.

The following code sample shows how the <organization> element can be used to specify the business units responsible for publishing, editing, and approving the book as well as the business unit that owns the copyrights to the book:

<bookmeta>
  <publisherinformation>
      <organization>NY Publishing</organization>
      <printlocation>United States of America</printlocation>
  </publisherinformation>
   <bookid>
    <isbn>123-0-456-12345-1</isbn>
    <maintainer>
      <person>John Smith</person>
    </maintainer>
  </bookid>
  <bookchangehistory>
    <reviewed>
      <person>Jack</person>
      <completed><month>July</month><year>2022</year></completed>
    </reviewed>
    <edited>
      <organization>XYZ Editing</organization>
      <completed><month>January</month><year>2023</year></completed>
    </edited>
    <approved>
      <organization>OASIS</organization>
    </approved>
  </bookchangehistory>
  <bookrights>
    <copyrfirst><year>2020</year></copyrfirst>
    <copyrlast><year>2023</year></copyrlast>
    <bookowner>
      <organization>OASIS</organization>
    </bookowner>
  </bookrights>
</bookmeta>