Hello,
I am working in a project that aims for validating open data by an open
standard defined in an XML Schema[1]. The document size varies from 13kB -
2GB[2]. The basic problem I face is key constraint validation, defined as
key, keyref and unique combinations. The special case here is tha
Hi Nick,
Thanks for your reply. It does have a noticeable impact, while having
compiled libxml2-git yesterday, I oversaw it.
With the single constraint file;
libxml2-2.9.10
User time (seconds): 90.81
Elapsed (wall clock) time (h:mm:ss or m:ss): 1:31.60
libxml2-git
User time (seconds): 49.57
Hi Liam,
On Wednesday, January 6, 2021 2:35:53 AM CET, Liam R E Quin wrote:
Could you do this instead using schematron?
Would you have an example how to do a key identity constraint with
schematron? I am happy to benchmark it.
--
Stefan
___
xml ma
Dear Nick,
This is great news, thanks Google for acknowledging the importance of
maintaining core open source products. Your previous improvements on XSD
validation made a great difference, but from my prototype in Python (LXML)
I assume that multithreaded constraint validation and a more effi
Hi Nick,
On Wednesday, January 12, 2022 3:49:07 PM CET, Nick Wellnhofer wrote:
I didn't make any performance improvements to the XSD code
personally. You're probably seeing improvements from the
following commit which wasn't authored by me:
https://gitlab.gnome.org/GNOME/libxml2/-/commit/
Hi,
Would a patch be accepted that would create an option to disable identity
constraints at runtime? Use case: only syntactically validate a file.
--
Stefan
___
xml mailing list, project page http://xmlsoft.org/
xml@gnome.org
https://mail.gnome.org
On Wednesday, February 9, 2022 1:25:41 PM CET, Nick Wellnhofer wrote:
I'm always reluctant to add new features, especially if it
sounds like it only solves a problem for a single user. Do you
want to disable checking of identity constraints for performance
reasons or is there another use case?
