Re: Re: Possible Bug: Xerces 2.12.1 for XML Validation with XSD 1.1 Schema under Java - Plain Text

--00000000000075e54305ae128824
Content-Type: text/plain; charset="UTF-8"

Hi John,

On Fri, Aug 28, 2020 at 1:47 PM JOHN Morris <[email protected]> wrote:

> I'm not sure what was happening before to give us those discrepancies
> between our respective results though. Did you try comparing the files you
> were using for the validations before with the new (but, from my point of
> view, the same) files from the Jira case?
>

I've not been able to do, detailed comparison between the files posted by
you within this mail thread and those attached on the Jira issue. I'd
assume that they're same as claimed by you. But fetching your files from
the Jira issue attachment, gives me same results that you've got (and I
don't get same results by copying file contents from within the mail
thread). For the purpose of making a possible fix to implementation as per
the issue that we're discussing here, I'd suggest that we use the file
attachment that you've provided within the Jira issue.

I also suggest that, if you may reduce as much as possible the XML input
file contents and also possibly remove most of the comments from the XSD
document (and reattach the modified files on the Jira issue) that would be
still ok for validation and replicates the same bug, I guess that'd be more
easy for any Xerces-J developer to investigate the issue & possibly make a
fix.


> What can I expect to happen next? Is there some process where one of the
> Xerces-J Developers (assuming that you are not already one of those) will
> pick up this case? If so, how long does that process typically take, in
> your experience?
>

As per my knowledge, the issue would be picked up (for analysis & a
possible fix) by any Xerces-J developer depending who has available time
(the Xerces-J developers are volunteers).


> I wonder whether it would help my case, if you could add your supporting
> information, that you had succeeded in replicating the problem, to the Jira
> case itself?
>

I've made few comments on the Xerces-J Jira issue you've posted, some time
ago.



-- 
Regards,
Mukul Gandhi

--00000000000075e54305ae128824
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div>Hi John,</div><br><div class=3D"gmai=
l_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Aug 28, 2020 at 1:47=
 PM JOHN Morris &lt;<a href=3D"mailto:[email protected]">j.morris13@n=
tlworld.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">I&#39;m not sure what was happening before to give us those disc=
repancies between our respective results though. Did you try comparing the =
files you were using for the validations before with the new (but, from my =
point of view, the same) files from the Jira case?<br></blockquote><div><br=
></div><div>I&#39;ve not been able to do, detailed comparison between the f=
iles posted by you within this mail thread and those attached on the Jira i=
ssue. I&#39;d assume that they&#39;re same as claimed by you. But fetching =
your files from the Jira issue attachment, gives me same results that you&#=
39;ve got (and I don&#39;t get same results by copying file contents from w=
ithin the mail thread). For the purpose of making a possible fix to impleme=
ntation as per the issue that we&#39;re discussing here, I&#39;d suggest th=
at we use the file attachment that you&#39;ve provided within the Jira issu=
e.</div><div><br></div><div>I also suggest that, if you may reduce as much =
as possible the XML input file contents and also possibly remove most of th=
e comments from the XSD document (and reattach the modified files on the Ji=
ra issue) that would be still ok for validation and replicates the same bug=
, I guess that&#39;d be more easy for any Xerces-J developer to investigate=
 the issue &amp; possibly make a fix.</div><div>=C2=A0</div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex">
What can I expect to happen next? Is there some process where one of the Xe=
rces-J Developers (assuming that you are not already one of those) will pic=
k up this case? If so, how long does that process typically take, in your e=
xperience?<br></blockquote><div><br></div><div>As per my knowledge, the iss=
ue would be picked up (for analysis &amp; a possible fix) by any Xerces-J d=
eveloper depending who has available time (the Xerces-J developers are volu=
nteers).</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left=
:1ex">
I wonder whether it would help my case, if you could add your supporting in=
formation, that you had succeeded in replicating the problem, to the Jira c=
ase itself?<br></blockquote><div><br></div><div>I&#39;ve made few comments =
on the Xerces-J Jira issue you&#39;ve posted, some time ago.</div><div>=C2=
=A0</div></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr" cla=
ss=3D"gmail_signature"><div dir=3D"ltr"><div>Regards,<br>Mukul Gandhi<br></=
div></div></div></div></div>

--00000000000075e54305ae128824--