← Prev in month
← Prev in thread
Next in thread →
Next in month →
Indexing inconsistency
I've noticed an inconsistency in the spec topics about indexing.
I used bold formatting to draw your attention to the relevant
bits:
3.5.3.5 <sort-as> (http://docs.oasis-open.org/dita/dita/v1.3/errata01/os/complete/part3-all-inclusive/langRef/base/sort-as.html)
Processors SHOULD expect to encounter <sort-as> elements in
the above locations. Processors that sort SHOULD use the following
precedence rules:
A <sort-as> element that is specified in a title takes
precedence over a <sort-as> element that is specified as
a child of the topic prolog.
Except for instances in the topic prolog, processors only
apply <sort-as> elements that are either a direct child
of the element to be sorted or a direct child of the title- or
label-defining element of the element to be sorted.
When an element contains multiple, direct-child,
<sort-as> elements, the first direct-child
<sort-as> element in document order takes precedence.
When located within the <indexterm> element, the
<sort-as> element is equivalent to
<index-sort-as>. It is an error for an <indexterm>
element to directly contain both <sort-as> and
<index-sort-as> elements.
Sort phrases are determined after filtering and content
reference resolution occur.
3.4.2.5 <index-sort-as> (http://docs.oasis-open.org/dita/dita/v1.3/errata01/os/complete/part3-all-inclusive/langRef/base/index-sort-as.html)
It is an error if there is more than one <index-sort-as>
child for a given <indexterm>. An implementation might
give an error message, and might recover from this error
condition by ignoring all but the last <index-sort-as>.
Best,
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 622-1501; kriseberlein (skype)
← Prev in month
← Prev in thread
Next in thread →
Next in month →