[EXT] Re: Re: [xsde-users] xs:date , xs:datetime validation

[Yegnaram, Shrikant]

Hi Boris,



Thanks for the explanation and the fixes provided.



Can you explain more on what you mean by below :

I think it should apply cleanly to XSD/e 3.2.0 if you would like to give it a try (you will need to apply it and rebuilt the libxsde runtime). Alternatively, if you would like, I can apply it to 3.2.0 and make the affected files available.



First option would be for us to pick up the files from git and recompile libxsde runtime and test.

Second option, are you saying, you would make a new XSD/e product release and package the updated files with the release?





Thanks,

Shrikant Yegnaram

CLS Classification: Confidential Information

This email was classified by Yegnaram, Shrikant on Tuesday, March 28, 2023 3:07:39 PM

CLS is committed to protecting and safeguarding your personal data. Our privacy notice<https://www.cls-group.com/privacy> provides you with information about how we process and protect your personal data. We aim to ensure direct marketing is reasonable, proportionate and of relevance to you. However, if you no longer want to receive direct marketing from us please email dpo at cls-services.com<mailto:dpo at cls-services.com>.



-----Original Message-----
From: Boris Kolpackov <boris at codesynthesis.com>
Sent: Monday, March 20, 2023 8:46 AM
To: Yegnaram, Shrikant <SYegnaram at cls-bank.com>
Cc: xsde-users at codesynthesis.com; Ramanathan, Murali <mramanathan at cls-bank.com>; Parthasarathy, Madhusoodan <mparthasarathy at cls-bank.com>
Subject: [EXT] Re: Re: [xsde-users] xs:date , xs:datetime validation



<div align=left><table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 align=left><tr><td width=100% style='width:100%;border-top:solid #E32719 3.0pt;border-left:none;border-bottom:solid #E32719 3.0pt;border-right:none;padding:0in 0in 0in 0in;background:#E1E73C;'><p class=MsoNormal align=left style='text-align:left'><b><span style='font-family:"Arial",sans-serif;color:#CF4520'>Be careful with this message: </span></b><span style='font-family:"Arial",sans-serif;color:#C00000'></span><span style='font-family:"Arial",sans-serif;color:#002855'>it has been sent from an <b>external</b> email address. <br>Do not open attachments or click links from unknown senders or unexpected email.</span></p></td></tr></table></div>

Yegnaram, Shrikant <SYegnaram at cls-bank.com<mailto:SYegnaram at cls-bank.com>> writes:



> Yes we have enabled parser/serializer validation



Thanks for the confirmation.



I dug a bit deeper into this and it appears that the constraint you have quoted is from the XML Schema 1.1 specification while XSD/e only aims to conform to XML Schema 1.0 (even more precisely, it only aims to conform for validation to a subset of it; see [1][2]). And looking at the XML Schema 1.0 specification, there is no such constraint (but there is a general statement to the effect that the date shall be valid). This is the reason why we don't have tighter validation for these types.



However, the constraint in the XML Schema 1.1 is quite sensible and is not too expensive to implement (neither with regards to footprint nor performance). So I went ahead and implemented it (as well as a similar constraint for gMonthDay). You can find the patch here:



https://git.codesynthesis.com/cgit/xsde/xsde/commit/?id=387d98b80d9f383c4c7708a42444472cb89dd42b



I think it should apply cleanly to XSD/e 3.2.0 if you would like to give it a try (you will need to apply it and rebuilt the libxsde runtime). Alternatively, if you would like, I can apply it to 3.2.0 and make the affected files available.



[1] https://codesynthesis.com/projects/xsde/documentation/cxx/parser/guide/#A

[2] https://codesynthesis.com/projects/xsde/documentation/cxx/serializer/guide/#A
************************************************************************************************************************************************************************
WARNING: This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this e-mail.
Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.

E-mails are not encrypted and cannot be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender 
therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of this e-mail transmission. If verification is required, please request a hard copy version.

CLS is committed to protecting and safeguarding your personal data. Our privacy notice (https://www.cls-group.com/privacy) provides you with information about how we process and protect your personal data.
We aim to ensure direct marketing is reasonable, proportionate and of relevance to you. However, if you no longer want to receive direct marketing from us please email dpo at cls-services.com