[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: 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:
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>. Kris Kristen James Eberlein Chair, OASIS DITA Technical Committee Principal consultant, Eberlein Consulting www.eberleinconsulting.com +1 919 622-1501; kriseberlein (skype) |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]