Re: [jats-list] Using JATS DTDs with Oxygen XML Editor

Subject: Re: [jats-list] Using JATS DTDs with Oxygen XML Editor
From: "Wendell Piez wapiez@xxxxxxxxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 4 Mar 2021 21:51:44 -0000
Dear Michael,

It is good to hear it's working. Sometimes we have to do what is expedient.
It's a pretty nice solution in its way. :-)

As to schema or DTD munging / modification, absolutely, there are always
options here. (I think oXygen may even have a thing built in.) However, in
the case of JATS -- even the older JATS DTDs -- these are carefully crafted
to relate nicely to one another as given -- that is, inasmuch as Blue is a
clean subset of Green, you can always point a document, whether nominally
Blue or Green, at a Green DTD, and get green-level validation. (Which
applies equally to Blue.) Then when you have a Blue document, you can
*additionally* validate it as Blue. (Because Blue is the same as Green,
only tighter.)

For a user in oXygen, I might consider deploying a set of Validation
Scenarios to support a layered approach like that. How you then signal
behind the scenes that this document is Blue not Green (and is thus subject
to the tighter rules) becomes an issue but I can imagine several approaches
to that. CSS skinning gives you a way to distinguish visually between
classes of documents (it too could be wired to apply dynamically). All
within one framework. Indeed the requirement for different frameworks for
the different document types is puzzling inasmuch as they share so much
(since so much of what is inside Green, is Blue). OTOH I don't know maybe
there are good reasons for that.

In that context it is very nice to hear you have gotten mileage from the
JATSKit work, which was meant to be good enough to improve on. :-)

Cheers, Wendell








On Thu, Mar 4, 2021 at 4:33 PM Michael Boudreau mboudreau@xxxxxxxxxxxx <
jats-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:

> Hi, Wendell,
>
>
>
> I finally have this working after making a second attempt to change all
> the public identifiers and corresponding filenames in one of the two DTDs.
> (Itbs possible that it wasnbt necessary to change the filenames and I
was
> simply more thorough with the public identifiers on the second attempt.)
>
>
>
> Youbre right about the folks at Oxygenbthey are indeed very helpful,
and
> Ibve worked with Radu in the Forum on this problem and others.
>
>
>
> Although the problem is solved for the time being, Ibm wondering if
> combining either the modified blue or the unmodified green DTD into a
> single file would have been a reasonable solution (on the assumption that
> it would eliminate all but one of the public identifiersbthe one
> corresponding to the main DTD file). Are there good tools that will read in
> a modular DTD and output a single file?
>
>
>
> I have in fact used the JATS framework you contributed to Oxygen,
> particularly the CSS files, from which I borrowed heavily (read: lifted
> wholesale) for my own NLM and JATS-related frameworks.
>
>
>
> --
>
> Michael R. Boudreau
>
> Electronic Publishing Technology Manager
>
> The University of Chicago Press
>
> 1427 E. 60th Street
>
> Chicago, IL 60637
>
> www.journals.uchicago.edu
>
>
>
>
>
> *From: *"Wendell Piez wapiez@xxxxxxxxxxxxxxx" <
> jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>
> *Reply-To: *"jats-list@xxxxxxxxxxxxxxxxxxxxxx" <
> jats-list@xxxxxxxxxxxxxxxxxxxxxx>
> *Date: *Thursday, March 4, 2021 at 8:20 AM
> *To: *"jats-list@xxxxxxxxxxxxxxxxxxxxxx" <jats-list@xxxxxxxxxxxxxxxxxxxxxx
> >
> *Subject: *Re: [jats-list] Using JATS DTDs with Oxygen XML Editor
>
>
>
> Michael,
>
>
>
> For sure you should ask the folks at oXygen who are very helpful with this
> kind of thing. There are features that can be used to assign an import
> hierarchy for the frameworks; also these settings can be saved per project,
> for example, as can the active frameworks, etc.
>
>
>
> So the short answer might be there is no really short answer, if you
> really need two separate frameworks (whose bindings conflict or overlap) to
> be active at the same time, but there might be options, and those would be
> oXygen features.
>
>
>
> Of course, feel free to borrow or adapt from
> https://github.com/wendellpiez/JATSKit
>
<https://urldefense.com/v3/__https:/github.com/wendellpiez/JATSKit__;!!BpyFHL
RN4TMTrA!tOXkwJ7e05zk6whnLbk5S1UVpJpYImQz8IlD6BBIBdaWRNeqiUMvKifX6E_JCmEkAML4
$>
> (which doesn't use those DTDs IIRC but which could be adapted).
>
>
>
> Good luck,
>
> Wendell
>
>
>
>
>
>
>
> On Wed, Mar 3, 2021 at 9:47 PM Michael Boudreau mboudreau@xxxxxxxxxxxx <
> jats-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> Greetings!
>
>
>
> Is anyone using Oxygen XML Editor to work with instances of the various
> JATS DTDs (e.g., blue and green)?
>
>
>
> Ibm currently trying to create frameworks in Oxygen to handle instances
of
> JATS Journal Publishing 1.2 (a slightly modified version of which we use
> in-house for editing) and JATS Archiving 1.2 (which we send to our platform
> vendor). However, I find that if both frameworks are active, the one that
> loads first (Archiving, green) prevents the other (Publishing, blue) from
> working, apparently because of the common public identifiers and
> corresponding filenames used in both DTDs.
>
>
>
> I have tried changing all the public identifiers and filenames in one of
> the two DTDs, so far without success. I suspect that another possible
> solution would be to provide one of the two DTDs entirely in a single file
> (thus eliminating the need to map public identifiers to filenames) but
> havenbt tried that yet; Ibd be happier if I could get the frameworks to
> behave with the DTDs in their default structure.
>
>
>
> If youbve encountered this problem and found a solution, Ibd love to
know
> what you did.
>
>
>
> --
>
> Michael R. Boudreau
>
> Electronic Publishing Technology Manager
>
> The University of Chicago Press
>
> 1427 E. 60th Street
>
> Chicago, IL 60637
>
> www.journals.uchicago.edu
>
>
>
>
>
>
> --
>
> ...Wendell Piez... ...wendell -at- nist -dot- gov...
> ...wendellpiez.com... ...pellucidliterature.org... ...pausepress.org...
> ...github.com/wendellpiez.
>
<https://urldefense.com/v3/__http:/github.com/wendellpiez.__;!!BpyFHLRN4TMTrA
!tOXkwJ7e05zk6whnLbk5S1UVpJpYImQz8IlD6BBIBdaWRNeqiUMvKifX6E_JCqPD8IfE$>..
> ...gitlab.coko.foundation/wendell...
>
> JATS-List info and archive
>
<https://urldefense.com/v3/__http:/www.mulberrytech.com/JATS/JATS-List/__;!!B
pyFHLRN4TMTrA!tOXkwJ7e05zk6whnLbk5S1UVpJpYImQz8IlD6BBIBdaWRNeqiUMvKifX6E_JCov
OWC6O$>
>
> EasyUnsubscribe
>
<https://urldefense.com/v3/__http:/lists.mulberrytech.com/unsub/jats-list/298
6360__;!!BpyFHLRN4TMTrA!tOXkwJ7e05zk6whnLbk5S1UVpJpYImQz8IlD6BBIBdaWRNeqiUMvK
ifX6E_JCpO8RBiu$>
> (by email <>)
>


--
...Wendell Piez... ...wendell -at- nist -dot- gov...
...wendellpiez.com... ...pellucidliterature.org... ...pausepress.org...
...github.com/wendellpiez... ...gitlab.coko.foundation/wendell...

Current Thread