Abstract Numbering Definition Identifier. When the object is serialized out as xml, its qualified name is w:nsid.
Assembly: DocumentFormat.OpenXml (in DocumentFormat.OpenXml.dll)
[ISO/IEC 29500-1 1st Edition]
nsid (Abstract Numbering Definition Identifier)
This element associates a unique hexadecimal ID to the parent abstract numbering definition. This number shall be identical for two abstract numbering definitions that are based from the same initial numbering definition - if a document is repurposed and the underlying numbering definition is changed, it shall maintain its original nsid.
If this element is omitted, then the list shall have no nsid and one can be added by a producer arbitrarily.
[Note: This element can be used to determine the abstract numbering definition to be applied to a numbered paragraph copied from one document and pasted into another. Consider a case in which a given numbered paragraph associated with a abstract numbering definition with nsid FFFFFF23, is pasted among numbered paragraphs associated with a completely different appearance and an abstract numbering definition with an nsid of FFFFFF23. Here, because of the distinction enabled by the identical nsid values, the hosting application would not have to arbitrarily keep the pasted numbered paragraph associated with its original abstract numbering definition, as it might use the information provided by the abstract numbering definition's identical nsid values to know that those two numbering sets are identical, and merge the paragraphs into the target numbering format. end note]
[Example: Consider the WordprocessingML for an abstract numbering definition below:
<w:abstractNum w:abstractNumId="3"> <w:nsid w:val="FFFFFF89" /> <w:multiLevelType w:val="singleLevel" /> <w:tmpl w:val="D9842532" /> … </w:abstractNum>
In this example, the given abstract numbering definition is associated with the unique hexadecimal ID FFFFFF89. end example]
val (Long Hexadecimal Number Value)
Specifies a number value specified as a four digit hexadecimal number), whose contents of this decimal number are interpreted based on the context of the parent XML element.
[Example: Consider the following value for an attribute of simple type ST_LongHexNumber: 00BE2C6C.
This value is permitted, as it contains four hexadecimal digits, each an encoding of an octet of the actual decimal number value. It can therefore be interpreted as desired in the context of the parent XML element, end example]
The possible values for this attribute are defined by the ST_LongHexNumber simple type (§17.18.50).
[Note: The W3C XML Schema definition of this element’s content model (CT_LongHexNumber) is located in §A.1. end note]
© ISO/IEC29500: 2008.