Re: [niso-sts] Encoding Bibliography

Subject: Re: [niso-sts] Encoding Bibliography
From: "Imsieke, Gerrit, le-tex gerrit.imsieke@xxxxxxxxx" <niso-sts-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 10 Oct 2018 14:15:30 -0000
I second this view, and thatbs why I created these schematron rules:

The first rule in this pattern:
If you attached a title to a ref-list, it asks you to put the title on a surrounding sec or app.

If the ref-list is immediately below back, the other rule will ask you to wrap it in an app.

These rules are only suggestions toward a consistent use of seamlessly interoperable NISO STS. This list is a good place to discuss these rules specifically or whether it is a good idea at all to try to encode best practices in Schematron rules.

The rules are intended as a library from which SDOs can configure their individual checking profiles. The aim, though, is not to have a plethora of individual profiles but a single baseline profile on top of which the institutes can encode their specific checking rules.

I presented this idea during JATS-Con this spring, and I was optimistic that Ibd have a demo this summer with the suggested STS4i baseline profile and with an additional German profile (DIN, VDE, b&) on top of it. Unfortunately, due to loads of other work, I havenbt completed anything yet. To have something working for next JATS-Con will be a realistic goalb&


On 10.10.2018 15:35, DorothC)e Stadler doro@xxxxxxxxxxx wrote:
Hi Tommie,
Thanks for your answer on this, which I thought made sense when I read it first. Now that Ibm trying to implement this logic however I find myself with the challenge that there is no way to enter text in between references.
In our standards it often happens that the Bibliography is bsplitb into functional sections, see this example:



For dokumenter som det er gjort normative referanser til i teksten, se punkt 2 /Normative referanser. /

*Norsk Standard*

NS 8405B B B B B B B B B B B B B B B B B B B B B Norsk bygge- og anleggskontrakt

NS-EN 536B B B B B B B B B B B B B B B B B Veibyggingsmaskiner b Asfaltblandeanlegg b Sikkerhetskrav


*Annen litteratur*

ICAO A14B B B B B B B B B B B B B B B B B B B (International Civil Aviation Organization): /Annex 14 - Volume I - Aerodromes design and operations./B Third edition. July 1999**

Statens vegvesen /HC%ndbok 025,/ /Prosesskode 1 - Standard arbeidsbeskrivelse for vegkontrakter. Hovedprosess 1-7./B Vegdirektoratet. Oslo, 2007



So how would I encode this with using <ref-list>? Should I then create a total of three <ref-lists>, the first one without any references in them to hold the first part, and then two more bchildb <ref-list> elements for the Norsk Standard and Annex literature parts?

I have to be honest, I donbt quite see the usefulness of using <ref-list> directly rather than having a section with type bbiblb and having my <ref-list> elements in there. Obviously since ISO (and presumably CEN) are doing it this way too I would prefer to align, but donbt see how I can accommodate cases like the aboveb& Unless it is possible to change NISO to allow text and other elements between <ref> elements? Is there a reason why this was prohibited in the first place?

Thanks for your continued help, I really appreciate how fast this group always responds!
Have a nice day.

DorothC)e Stadler

Rathenower Str. 38
10559 Berlin
Tel: +49 1525 840 85 93
doro@xxxxxxxxxxx <mailto:doro@xxxxxxxxxxx>

On 27. Sep 2018, at 18:41, Tommie Usdin btusdin@xxxxxxxxxxxxxxxx <mailto:btusdin@xxxxxxxxxxxxxxxx> <niso-sts-list-service@xxxxxxxxxxxxxxxxxxxxxx <mailto:niso-sts-list-service@xxxxxxxxxxxxxxxxxxxxxx>> wrote:

Hello DorothC)e b

It will take this community some time to develop best practices.

It seems to me that the most semantically specific markup available is generally best. Since there is an element (<ref-list>) specific to your use and it is available in the location you want to put the bibliography, I suggest that you should use it.

<sec sec-type=bbiblb> is available for those instances where there are bibliographies in other locations in the document. For example, some very large standards have bibliographies at the end of each major section/chapter, and I have heard that there are some standards that have bibliographies in other places in the body of the text.

b Tommie

On Sep 27, 2018, at 12:34 PM, DorothC)e Stadler doro@xxxxxxxxxxx <mailto:doro@xxxxxxxxxxx> <niso-sts-list-service@xxxxxxxxxxxxxxxxxxxxxx <mailto:niso-sts-list-service@xxxxxxxxxxxxxxxxxxxxxx>> wrote:

Hello everyone,
I have a question about how to best encode the Bibliography as part of the back matter.
To me, the most logical thing to do is use <sec> with @sec-type=bbiblb. Now I see in the NISO documentation of <sec> that it should be used as follows:
b" Within the back matter (<back>) to tag material that has not been explicitly named as one of the other back matter components, that is, it is not named as an annex (<app>), an acknowledgment (<ack>), a bibliography (<ref-list>), etc.

I am now confused. Should the bibliography always be encoded using <ref-list>, as it is also currently done by ISO using the ISOSTS? If so, why do we even have an @sec-type=bbiblb?
Any enlightenment would be much appreciated!
Kind regards
DorothC)e Stadler

Rathenower Str. 38
10559 Berlin
Tel: +49 1525 840 85 93
doro@xxxxxxxxxxx <mailto:doro@xxxxxxxxxxx>

You are subscribed as gerrit.imsieke@xxxxxxxxx to NISO STS Discussion by Mulberry Technologies, Inc. <>
EasyUnsubscribe <-sts-list/225679> (by email <>)

-- 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,

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

GeschC$ftsfC<hrer / Managing Directors:
Gerrit Imsieke, Svea Jelonek, Thomas Schmidt
Warum wir dieses Jahr nicht auf der Frankfurter Buchmesse sind:

Current Thread