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

Subject: Re: [jats-list] BITS index terms: sort key attribute
From: "Soichi Tokizane tokizane@xxxxxxxxxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 7 Oct 2014 10:21:46 -0000
Gerrit and Debbie,

I submitted a similar request last year, proposing the <sortkey> tag
instead.  Debbie replied that she preferred to having @sortkey
rather than a new tag.  Her answer below follows the same line.

Our challege is that there can be multiple sortkeys in Japanese
books depending on how a publisher typesets indexes.

See the example below.

<Index terms>
HiNET
cc<c=c
c+f$g4"
cccf$g4"
PATOLIS
PubMed
cc<cc*c3c/

<Sortkey in Japanese kana>
c/cc-c#c(
c1c<cc*ccccc
c0c#c!cccc
c1c(c
c
c1c6cc)
c1c<c>c
cc

<Sortkey in Roman alphabet>
HiNET
paasonaru kensaku
Bacchi kensaku
PATOLIS
Pubmed
Paamarinku

If we use @sortas for example, probably I have to write

<index-term>
  <term sortas="c/cc-c#c(" xml:lang="ja">Hinet</term>
  <term sortas="HiNET" xml:lang="en">Hinet</term>
</index-term>

which does not seem good.

So I still would like to propose introducing the <sortkey> element as:

<index-term>
  <term>Hinet</term>
  <sortkey xml:lang="ja">c/cc-c#c(</term>
  <sortkey xml:lang="ja">HiNET</term>
</index-term>

Soichi
-----------------------------------


Debbie Lapeyre dalapeyre@xxxxxxxxxxxxxxxx ccc/f8c c>cc:
Gerrit--

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

--Debbie

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

--dal


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
element.

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
GeschC$ftsfC<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, http://www.le-tex.de

Registergericht / Commercial Register: Amtsgericht Leipzig
Registernummer / Registration Number: HRB 24930

GeschC$ftsfC<hrer: Gerrit Imsieke, Svea Jelonek,
Thomas Schmidt, Dr. Reinhard VC6ckler



================================================================
Deborah A Lapeyre              mailto:dalapeyre@xxxxxxxxxxxxxxxx
Mulberry Technologies, Inc.      http://www.mulberrytech.com
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
================================================================







-- --------------------------------------------------------- fe.ch1!d8 (tokizane@xxxxxxxxxxxxx) (c(c cc-ccccc!)

(d8g$>) fe 1g'e-&f
h!e
d< (http://www.infosta.or.jp/)cd<i7
f1d:,e$'e-& e$'e-&g7efh2g g)6c;c3c?c< ie88e$h,e8+
fg%e$'e-& ie88e$h,e8+
tokizane@xxxxxxxxxxxxxxxxxxxx: 090-3452-5501
Twitter @stokizane
ORCID ID: 0000-0003-1236-1930

cc<c cc<c8 http://tokizane.jp/
i;e-c8c#c<c
c+c.eec(fe 1f: http://ejournal.jp/

ccc%c<c9f ece,e1e)g(c+icicc&c
(ff% 2012/4/5
fe
cg'c.h&g9c
)
http://bit.ly/HpPAxj
cg13e=cc8c?c+e,e1e3f8i$( (Digital Public Library of America:
DPLA)c
(e3
f8i$(ih*. 2013, 107(2), 118-120.) http://p.tl/8Gjh
---------------------------------------------------------

Current Thread