Re: [jats-list] Computer algorithms

Subject: Re: [jats-list] Computer algorithms
From: "Mary Seligy mary.seligy@xxxxxxxxxxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 13 Mar 2018 15:04:22 -0000
Thanks Nikos.

Ah OK... Unfortunately we're in 1.0 and it seems that <code> is not available
until 1.1, which is yet another reason for us to move on.

Thanks again
From: Nikos Markantonatos nikos@xxxxxxxxxx
Sent: Tuesday, March 13, 2018 10:40 AM
To: jats-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [jats-list] Computer algorithms

Hi Mary.

It seems that <code> would be best suited for an algorithm. You can even
use @code-type attribute to qualify that it's really an algorithm.
Element <code> can reside inside a <fig>, so "Algorithm 1" can be a
figure <label> and the trailing description a <caption>.


On 03/13/2018 04:28 PM, Mary Seligy mary.seligy@xxxxxxxxxxxxxxxxx wrote:
> Hi all
> Perhaps this has been asked and answered before, but I could not find
> anything related in the archives.
> We have taken on a new journal which has computer algorithms in its
> content. This is a new object for us, and I'm wondering how others
> capture this in the XML.
> My personal feeling about it is that it can be considered a kind of list
> (a list of lines of code, with a title on it).
> Here's part of an example:
> Algorithm 1 Cyclic Self-Learning training procedure
> function DECODE(c1,c2,!&cn, %h)
> 01:  for i = 1 to m do
> 02:  "9Cycle self-training
> 03:    for i = 1 to n do
> 04:       "9 Generate Candidate Label
> 05:       YS!g(*
> I would really appreciate knowing if there is already a common way of
> capturing this.
> Thanks very much
> Mary
> Mary Seligy
> Sr. Business Analyst
> Canadian Science Publishing (NRC Research Press)
> 65 Auriga Drive, Suite 203, Ottawa, ON  K2E 7W6
> T: 613-656-9846 ext. 225 | F: 613-656-9838
> Websites: <>,
> JATS-List info and archive <>
> EasyUnsubscribe <-list/244090>
> (by email <>)

Confidentiality Notice:  This email and any attachments are for the sole
use of the intended recipient(s) and contain information that may be
confidential and/or legally privileged.  If you have received this email
in error, please notify the sender by reply email and delete the
message.  Any disclosure, copying, distribution or use of this
communication by someone other than the intended recipient is prohibited.

Current Thread