12.1.18. <change>

<change> (change) documents a change or set of changes made during the production of a source document, or during the revision of an electronic file. [2.6. The Revision Description 2.4.1. Creation 12.7. Identifying Changes and Revisions]

Module header — Specification

Attributes

att.global
- @xml:id
- @n
- @xml:lang
- @xml:base
- att.global.analytic
  - @ana
- att.global.change
  - @change
- att.global.facs
  - @facs
- att.global.linking
  - @corresp
  - @synch
  - @sameAs
  - @copyOf
  - @next
  - @prev
  - @exclude
  - @select
- att.global.rendition
  - @rend
  - @style
  - @rendition
- att.global.responsibility
  - @cert
  - @resp
- att.global.source
  - @source
att.ascribed
- @who
att.datable
- @period
- att.datable.custom
  - @when-custom
  - @notBefore-custom
  - @notAfter-custom
  - @from-custom
  - @to-custom
  - @datingPoint
  - @datingMethod
- att.datable.iso
  - @when-iso
  - @notBefore-iso
  - @notAfter-iso
  - @from-iso
  - @to-iso
- att.datable.w3c
  - @when
  - @notBefore
  - @notAfter
  - @from
  - @to
att.docStatus
- @status
att.typed
- @type
- @subtype

target

(target) points to one or more elements that belong to this change.

Status	Optional
Datatype	1–∞ occurrences of teidata.pointer separated by whitespace

Contained by

header: revisionDesc

May contain

analysis: c pc

core: abbr bibl biblStruct cit date desc email expan graphic list listBibl name note p quote ref ruby term title

dictionaries: lang

figures: figure

gaiji: g

header: idno

linking: seg

namesdates: affiliation forename orgName persName persPronouns placeName state surname trait

tagdocs: ident

transcr: metamark

character data

Note

The who attribute may be used to point to any other element, but will typically specify a <respStmt> or <person> element elsewhere in the header, identifying the person responsible for the change and their role in making it.

It is recommended that changes be recorded with the most recent first. The status attribute may be used to indicate the status of a document following the change documented.

Example

<titleStmt>
 <title> ... </title>
 <editor xml:id="LDB">Lou Burnard</editor>
 <respStmt xml:id="BZ">
  <resp>copy editing</resp>
  <name>Brett Zamir</name>
 </respStmt>
</titleStmt>
<!-- ... -->
<revisionDesc status="published">
 <change who="#BZ" when="2008-02-02"
  status="public">Finished chapter 23</change>
 <change who="#BZ" when="2008-01-02"
  status="draft">Finished chapter 2</change>
 <change n="P2.2" when="1991-12-21"
  who="#LDB">Added examples to section 3</change>
 <change when="1991-11-11" who="#MSM">Deleted chapter 10</change>
</revisionDesc>

Example

<profileDesc>
 <creation>
  <listChange>
   <change xml:id="DRAFT1">First draft in pencil</change>
   <change xml:id="DRAFT2"
    notBefore="1880-12-09">First revision, mostly
       using green ink</change>
   <change xml:id="DRAFT3"
    notBefore="1881-02-13">Final corrections as
       supplied to printer.</change>
  </listChange>
 </creation>
</profileDesc>

Content model

<content>
 <macroRef key="macro.specialPara"/>
</content>
    ⚓

Schema Declaration


element change
{
   att.global.attributes,
   att.ascribed.attributes,
   att.datable.attributes,
   att.docStatus.attributes,
   att.typed.attributes,
   attribute target { list { + } }?,
   macro.specialPara
}⚓