Re: [jats-list] Error in DTD subset using MSXML

["Jacques Legare jlegare@xxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

I wouldn't be surprised if MSXML is actually using an SGML parser under the
hood, feeding it a declaration that makes said SGML parser behave mostly
like an XML parser. I believe the construct in question is forbidden by the
SGML specification (section 10.1.3), but is allowed by the XML
specification.

No, this doesn't help you resolve your problem. But I hit the same issue
with OmniMark's built-in XML parser when processing the NLM and JATS DTDs.

-----
Jacques LC)garC)                       jlegare@xxxxxxxxx
Stilo International plc              info@xxxxxxxxx

This message, including any attachments, is for the sole use of the
intended recipient(s) and may contain confidential and privileged
information. Any unauthorized review, use, disclosure, copying, or
distribution is strictly prohibited. If you are not the intended
recipient(s) please contact the sender by reply email and destroy all
copies of the original message and any attachments.



On Thu, Apr 25, 2019 at 6:26 PM Charles O'Connor coconnor@xxxxxxxxxxxx <
jats-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:

> Thanks, Tommie
>
> I'll give that a try before holding my breath and demanding a parser that
> works.
>
> --Charles
>
> -----Original Message-----
> From: B Tommie Usdin btusdin@xxxxxxxxxxxxxxxx <
> jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>
> Sent: Thursday, April 25, 2019 6:16 PM
> To: jats-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: [jats-list] Error in DTD subset using MSXML
>
> Hi Charles b
>
> The only thing I can think of would be to completely flatten the DTD,
> resolving all of the parameter entities. That would create a bulky,
> completely unreadable, but functional DTD that would *probably* work in
> MSXML. I say *probably* because while it would get around this bug it might
> hit another.
>
> There used to be DTD flattening tools floating around; there probably
> still are.
>
> b Tommie
>
>
>
> > On Apr 25, 2019, at 5:57 PM, Charles O'Connor coconnor@xxxxxxxxxxxx <
> jats-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
> >
> > Howdy Folks,
> >
> > Slightly technical question here.
> >
> > I've subsetted JATS, starting with JATS 1.2d1 and just recently
> transferring the altered content models to JATS 1.2 with MathML3 (XHTML
> only).
> >
> > The DTD validates fine in Oxygen (Xerxes), and XML documents validate
> fine against it.
> >
> > However, when our engineers put it up in our .NET environment they got
> the error: The parameter entity replacement text must nest properly within
> markup declarations.
> >
> > I set up a custom validation in Oxygen to use MSXML.NET and my subset,
> and alas, I get the same error. I then set up a validation using MSXML.NET
> and JATS 1.2d1 (Archiving). I get the same errors here as well.
> >
> > So, maybe, it's not me?
> >
> > I've Duck Duck Go'd the error text and found various indications that
> this is a result of a bug in MSXML, and of course Microsoft doesn't support
> it:
> >
> >
>
https://groups.google.com/forum/?hl=en#!topic/microsoft.public.xml/3HlKr3WQXT
0
> > https://www.w3.org/2002/04/xml_bugs/#bug2
> >
> > So, my question is: Is there anything I can do to edit the DTD to make
> it work? Or does the very idea of using MSXML fill you with such horror
> that, for goodness sake, will we please use Xerxes or RXP or maybe two
> rocks rubbed together instead?
> >
> > Thanks,
> > Charles
> >
> >
> >
> >
>
> ======================================================================
> B. Tommie Usdin                        mailto:btusdin@xxxxxxxxxxxxxxxx
> Mulberry Technologies, Inc.               https://www.mulberrytech.com
> 17 West Jefferson Street                           Phone: 301/315-9631
> Suite 207                                    Direct Line: 301/315-9634
> Rockville, MD  20850                                 Fax: 301/315-8285
> ----------------------------------------------------------------------
> Mulberry Technologies: A Consultancy Specializing in XML and SGML
>
> ======================================================================