Subject: Re: [jats-list] Computer algorithms|
From: "Mary Seligy mary.seligy@xxxxxxxxxxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 13 Mar 2018 15:28:03 -0000
These are all interesting ideas and will surely help in my planning for this. Thanks all Mary ________________________________________ From: Alexander Schwarzman aschwarzman@xxxxxxxxx [jats-list-service@xxxxxxxxxxxxxxxxxxxxxx] Sent: Tuesday, March 13, 2018 11:14 AM To: jats-list@xxxxxxxxxxxxxxxxxxxxxx Subject: Re: [jats-list] Computer algorithms Hi, Mary: I think, your decision might depend on the complexity of algorithms. We did consider using <code> and rejected that approach because the <code>'s content model is not rich enough for our needs. We use <table-wrap id="algo1" content-type="algorithm" position="float"> for displayed algorithms and <table-wrap id="algo2" content-type="algorithm" position="anchor"> for in-text algorithms. There are business rules related to id's, labels, captions, and content of algorithms that are checked via Schematron. We use <table-wrap>, rather than <fig>, because we make full use of alignment mechanisms and other table facilities to deal properly with the elaborate nature of algorithms published in OSA journals. Good luck, Alexander ('Sasha') Schwarzman, Content Technology Architect phone: +1.202.416.1979 | e-mail: aschwarzman@xxxxxxx The Optical Society (OSA) 2010 Massachusetts Ave., NW Washington, DC 20036 USA www.osa.org On Tue, Mar 13, 2018 at 11:04 AM, Mary Seligy mary.seligy@xxxxxxxxxxxxxxxxx <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > 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 > Mary > ________________________________________ > From: Nikos Markantonatos nikos@xxxxxxxxxx [jats-list-service@xxxxxxxxxxxxxxxxxxxxxx] > 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>. > > Regards, > Nikos > > 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: www.cdnscipub.com <http://cdnsciencepub.com/>, >> www.nrcresearchpress.com >> JATS-List info and archive <http://www.mulberrytech.com/JATS/JATS-List/> >> 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.