Project

Profile

Help

Support #5652 ยป Re_ [Saxon - Support #5652] Questions about Xlink Schema - 2022-08-20T08_50_19Z.eml

Norm Tovey-Walsh, 2022-08-20 10:50

 
X-He-Spam-Score: -1.8
Return-Path: <norm@saxonica.com>
Delivered-To: dropbox@plan.io
Received: from m.launch.gmbh ([127.0.0.1])
by m.launch.gmbh with LMTP id uFQkMwygAGPkAgAAJzdhvw
for <dropbox@plan.io>; Sat, 20 Aug 2022 10:49:16 +0200
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on m.launch.gmbh
X-Spam-Level:
X-Spam-Status: No, score=-1.8 required=5.0 tests=BAYES_00,DKIMWL_WL_MED,
DKIM_SIGNED,DKIM_VALID,DMARC_NONE,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,
SPF_NONE,SPF_NONE_IGNORE,T_SCC_BODY_TEXT_LINE autolearn=ham
autolearn_force=no version=3.4.2
X-Spam-Report:
* -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at
* https://www.dnswl.org/, no trust
* [35.156.234.212 listed in list.dnswl.org]
* -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
* [score: 0.0000]
* 0.1 DMARC_NONE DMARC record not found
* -2.0 SPF_NONE_IGNORE m.launch.gmbh does not consider absent SPF
* records
* 2.0 SPF_NONE SPF record not found
* 0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record
* -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
* 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily
* valid
* -0.0 T_SCC_BODY_TEXT_LINE No description available.
* -0.0 DKIMWL_WL_MED DKIMwl.org - Medium trust sender
X-Spam-Score: -1.8
Envelope-to: inbox+saxonica+f38e+saxon@plan.io
Authentication-Results: m.launch.gmbh; dmarc=none (p=none dis=none) header.from=saxonica.com
Authentication-Results: m.launch.gmbh; spf=none smtp.mailfrom=norm@saxonica.com
Authentication-Results: m.launch.gmbh;
dkim=pass (2048-bit key; unprotected) header.d=outbound.mailhop.org header.i=@outbound.mailhop.org header.b="FmKOiwfO";
dkim-atps=neutral
Received: from outbound5i.eu.mailhop.org (outbound5i.eu.mailhop.org [35.156.234.212])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
(No client certificate requested)
by m.launch.gmbh (Postfix) with ESMTPS id 2041782DD7
for <inbox+saxonica+f38e+saxon@plan.io>; Sat, 20 Aug 2022 10:49:15 +0200 (CEST)
ARC-Seal: i=1; a=rsa-sha256; t=1660985354; cv=none;
d=outbound.mailhop.org; s=arc-outbound20181012;
b=K3b4MtTFEmFfgEEy3lL9+M5duPSWYakMcSPoVP8KUZl3H5okFN8MbgEgAaFDcMEpWcxZCxOmkM9TV
mufeYnbF2cFw1K2JhClPIl6Y2Si4I/M6mIH1gaEEv5ENWKLW46/aIUwQxU9G5WjvgEqzHtPq4nbNjD
l8cbxJJUiMRh4afV3RsvcBGJnKd0cZP4zRnwMEcJ0SMerTMWzWI4cZvMq/pBW7PMfpLgNxqmfn+rcz
w6JP7lwsBcqqpwi7qUmyovYS1htUo9SBQC0Bmstq0VSUzAiPXa+kOB/2MnbRWW2SamqUhcVJrkhvET
iXZXLBYmiHvAdvVt8FcGuPhseL/VE2w==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed;
d=outbound.mailhop.org; s=arc-outbound20181012;
h=content-type:mime-version:message-id:in-reply-to:date:subject:to:from:
references:dkim-signature:from;
bh=V37Z3fnnKCvx00zVhmaTnI156vb/UDMJktJhYRdNq2w=;
b=dTsx16amwL1HNiSv4rOfAyPGgCUcQ7+7NrRVCQuMckdDUS45U2n+41PEahceBJv1lmFF4mf75Xsql
LkCp/4nISm2PFfNOwHppH7CHJw9IrgvVdOKYiTK9tF5wJES+g8YbG9Sy1JLGdSew/4OhpvAVroVcJZ
FaeImCAB9VwF2fSrHxnhEUza2lsAM5t0FTlv0KJpiXY0Qzil+mdwMyG6TCiR/99psld66oq2pudVs9
leV1AbbZQMGY2Vm+D42QRXlS65G4xOAqheuuxn+1D4hbMNwn3Fs4YSzeY2NlG5agM6FFP9o41gniCn
tlIk0LT/I/5hWx2pnAW2zWdY9Nrt64g==
ARC-Authentication-Results: i=1; outbound2.eu.mailhop.org;
spf=none smtp.mailfrom=saxonica.com smtp.remote-ip=146.70.133.10;
dmarc=none header.from=saxonica.com;
arc=none header.oldest-pass=0;
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=outbound.mailhop.org; s=dkim-high;
h=content-type:mime-version:message-id:in-reply-to:date:subject:to:from:
references:from;
bh=V37Z3fnnKCvx00zVhmaTnI156vb/UDMJktJhYRdNq2w=;
b=FmKOiwfOzGhNC8NnK+nBi4uT/6iBPAhXG+bIA/gz64kulsbA0IHGOhkm/A7JnHW47BJKV4UlN2MES
7AILN0IY5fb9s0LJ9E0zU/7rg3+WxtpeL22dvDjiyNSQNV6vAgKngCyTnea29uy6+PIoJX3Kn1XH0u
I27S5ZhQl8bL5NTd852BKjIK3eIc3YQe1B6Xs4NSWwEa6F2KAYn/K8oKcvsVbgxx51ODV/EGGkt+U4
NS7M5X01SfirjUHK9HJD19DFEx978DhgisnYwBfC7ktQukYkBwNECs77f8PGs6Yx7jKJTZyjgpLtCH
iCdjgchVEQjHlYrf+Ejcf0Bpjvu4dWQ==
X-Originating-IP: 146.70.133.10
X-MHO-RoutePath: bndhbHNo
X-MHO-User: f4196a05-2064-11ed-bc05-4b4748ac966b
X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information
X-Mail-Handler: DuoCircle Outbound SMTP
Received: from Hackmatack.local (unknown [146.70.133.10])
by outbound2.eu.mailhop.org (Halon) with ESMTPSA
id f4196a05-2064-11ed-bc05-4b4748ac966b;
Sat, 20 Aug 2022 08:49:08 +0000 (UTC)
References: <redmine.issue-5652.20220818194542.3760@plan.io>
<redmine.journal-21591.20220819140239.3760@plan.io>
User-agent: mu4e 1.8.1; emacs 28.1
From: Norm Tovey-Walsh <norm@saxonica.com>
To: Saxonica Developer Community <inbox+saxonica+f38e+saxon@plan.io>
Subject: Re: [Saxon - Support #5652] Questions about Xlink Schema
Date: Sat, 20 Aug 2022 09:42:02 +0100
In-reply-to: <redmine.journal-21591.20220819140239.3760@plan.io>
Message-ID: <m21qtbs3jw.fsf@saxonica.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
micalg=pgp-sha256; protocol="application/pgp-signature"

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Saxonica Developer Community <notifications@plan.io> writes:
> We are currently using Saxon 10.x EE.=20
>
> We've recently replaced the standard URL and Entity resolvers with
> ones based on https://xmlresolver.org because we make use of XML
> Catalogs. We didn't see the issue until we moved to this resolver.

Okay. I=E2=80=99m a little confused about exactly how you have things
configured. You may have found a bug in XML Resolver, but I=E2=80=99ll need=
some
kind of reproducible test case to be sure.

> 1 Saxon contains a standard schema resolver that given the xlink
> namespace uses its own copy and completely ignores our modified one.

Is that true even if you put an entry in the catalog you=E2=80=99re using t=
hat
points to the version you want to use?

> 2 The copy xlink.xsd references xml.xsd -- but does not actually
> supply it

I assume this is related to the fact that, as Michael said, the
semantics of xml.xsd are baked in.

> 3 The URL resolver attempts to resolve xml.xsd -- this is handled by
> XML Resolver

> 4 XML Resolver tries to consult it's cache -- unfortunately the user
> that runs on our production and staging environment does not have
> access to a home directory after startup. So XML Resolver can't access
> ~/.xmlresolver.org/ and it's a cache miss

Are you also using xmlresolverdata.jar? It=E2=80=99s certainly in there.

As of 4.5.0, XML Resolver no longer tries to cache by default.

> 5 XML Resolver attempts to retrieve xml.xsd from w3c.org and this
> stalls
>=20=20
> I can understand the rationale behind caching xml.xsd -- but you are
> actually not doing that. You are caching xlink.xsd -- and we don't
> understand why. Also, this is totally undocumented we had to decompile
> the standard schema resolver to figure out that you were doing that.

The rationale was to avoid stalling requests to www.w3.org.

I=E2=80=99m eager to help resolve this, but I confess, I still don=E2=80=99=
t really
understand precisely how you have things configured. Is it possible to
provide a small test case that demonstrates the problem?

Be seeing you,
norm

=2D-
Norm Tovey-Walsh
Saxonica

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE1ury//rzuvqf7fN/hVWfHhJMAHkFAmMAoAMACgkQhVWfHhJM
AHlpIQ//XRET+hNgQa5Cr9lyDGy8KXs+EkFcyfmc/sdGt9VRWuZp2n3MRlak0vN9
XIIZKMoq5/Dz+fFf5KknLWPsP5oyDpJD0MnvZ9fiFo1Wrm0umzvlARD+p6Ksz9Wk
Tg2oRtCqKrS31qJEpXJGDUHzX4Aydfpra0JEtkOgdH/iXFLaOVpjJalrgBTkc+KP
51UpmzmkoJUynX3m7ApSSHfTZ66A0aWImQpWEDw73XUTQUN4yS1iA3yOIRX2l/BX
K41gwElq2rJJVSWJju74oTIS7U6p5yl24r+aT8r11cSCcGLf4qp38yPmWYiqBqVS
N4sgOYGDKcpwyXt3bcbJMCGP76dMTvvX04NxA7mZS9cikT18SY/JhTRSiZdCHuoe
vXsULCHtTkyOyl54s8uE3/zN4xsp0jWiPztIaDcDXsI9sJ6SggoXm1iNmPa8co4t
WXkW/gjMHWTdWlwjaJ2ga1Tj3sxUAZds9nrrLwXNf1yJULiVHqi/gCNKppdYX89G
Nheqp/3Jd6wuT/LeqlURW5O5ZHSEp+om95zP0tXmyXLfATMRRkxglCHXbaHa/B/e
+Hc/zuUi4hyOTSkXVwsYi+j0VlSA1ibzUBCgYsz46mi3RRjfy6kRbJO+Nk1n3g2c
+LMqJenEDg9sCFJEcY9jahDUE9ZqnPqx3Do5LSui7TYsnyHDl9o=
=EvPB
-----END PGP SIGNATURE-----
--=-=-=--
    (1-1/1)