[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: index-sort-as proposed wording changes
Proposed wording for index-sort-as. > -----Original Message----- > From: Grosso, Paul [mailto:pgrosso@ptc.com] > Sent: Tuesday, 2006 September 26 11:37 > To: dita@lists.oasis-open.org > Subject: RE: [dita] review of index* elements > > index-sort-as > > ------------- > > There remains lots of issues about "global sort order" > > using indexterms within the prolog. For one thing, this > > contradicts other decisions we made about what an indexterm > > within the prolog means. See also my email of July 26: > > http://lists.oasis-open.org/archives/dita/200607/msg00076.html > > with other questions/issues about sort-as that have > > never been answered. > > > > Issue: Given what we've recently decided about indexterms > in the prolog, are we still planning to allow index-sort-as > within the prolog define "global sort order"? > > Proposed resolution: > > Do away with the "global sort order" concept for DITA 1.1. > If and when we do define such, we should use different > markup than the usual indexterm/index-sort-as. > > ACTION to Paul: Provide suggested wording (or delete some > existing wording as necessary). > > --- > > Issue: What happens when two indexterms with different > content have identical sort-as values? > > Proposed resolution: > > The indexterm textual content itself is effectively considered > as a "secondary sort field" in addition to the sort-as value, > so two indexterms with different content will never merge into > the same index entry. > > ACTION to Paul: Provide suggested wording. > > > Furthermore, it isn't clear to me how to use sort-as for > > a multilevel index term. > > > > Proposed resolution: > > An index-sort-as provides the sort key for the indexterm > that is its parent. > > ACTION to Paul: Provide suggested wording. > I've attached an updated dita document wherein: 1. I deleted the paragraph about global sort order. 2. I added proposed wording to indicate that the indexterm textual content itself helps differential resulting index entries. 3. I added proposed wording indicating that index-sort-as relates just to its parent indexterm. 4. Added wording saying it is an error for there to be more than one index-sort-as for a given indexterm.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]