Re: [jats-list] BITS index terms: sort key attribute

Subject: Re: [jats-list] BITS index terms: sort key attribute
From: "Debbie Lapeyre dalapeyre@xxxxxxxxxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 1 Oct 2014 15:59:28 -0000

I think the @sortas on <index-term> is a very good idea.

There is already a @sort-key attribute on <index-entry>,
so maybe we should use that.

   sort-key   CDATA   #IMPLIED


P.S. Actually, we modeled the index terms on DocBook,
which were themselves modeled on an older model.


On Oct 1, 2014, at 11:13 AM, Imsieke, Gerrit, le-tex gerrit.imsieke@xxxxxxxxx
<jats-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:

> Sometimes it's necessary to specify an explicit sorting key for an index
term. Consider this DocBook example:
> <indexterm>
>  <primary sortas="Zielintention">(Ziel-)Intention</primary>
> </indexterm>
> This will be sorted as 'z' and not as '('.
> What would be the BITS equivalent of @sortas? Without the sort key, the
index term is
> <index-term>
>  <term>(Ziel-)Intention</term>
> </index-term>
> Apparently there's no sortas or equivalent attribute permitted on the term
> What I'm planning to do is to use the specific-use attribute and put the
sort key in there, like this:
> <index-term>
>  <term specific-use="Zielintention">(Ziel-)Intention</term>
> </index-term>
> Although it probably isn't outright misuse of specific-use, I think it would
be useful to have a distinct attribute for this.
> It is an open question whether this attribute should be on index-term or on
term. Probably on index-term since term is also used in other context where a
sort-as attribute may or may not make sense.
> In contrast to DocBook where the sortas attributes have to be on primary,
secondary, or tertiary rather than on indexterm itself, BITS' index-term
element might be a suitable place for such an attribute, due to the recursive
content model.
> In TEI, however, after which BITS' index terms seem to be modeled, each
/term/ may carry a sortKey attribute.
> What do you think? Do we need such a sort key? Or am I missing that it is
already there? If we need it, should it be on index-term or on term? What do
you think of the specific-use interim solution?
> Gerrit
> --
> Gerrit Imsieke
> Geschdftsf|hrer / Managing Director
> le-tex publishing services GmbH
> Weissenfelser Str. 84, 04229 Leipzig, Germany
> Phone +49 341 355356 110, Fax +49 341 355356 510
> gerrit.imsieke@xxxxxxxxx,
> Registergericht / Commercial Register: Amtsgericht Leipzig
> Registernummer / Registration Number: HRB 24930
> Geschdftsf|hrer: Gerrit Imsieke, Svea Jelonek,
> Thomas Schmidt, Dr. Reinhard Vvckler

Deborah A Lapeyre              mailto:dalapeyre@xxxxxxxxxxxxxxxx
Mulberry Technologies, Inc.
17 West Jefferson Street         Phone: 301-315-9631 (USA)
Suite 207                        Fax:   301-315-8385
Rockville, MD 20850
Mulberry Technologies: Consultancy for XML, XSLT, and Schematron

Current Thread