@faassen Very nice! Thank you!

As an aside, I started to write a crate to implement XSD datatypes XPath/XQuery functions and operators for my SPARQL implementation, it might be handy: https://docs.rs/oxsdatatypes

@Tpt
Oh that might be interesting, especially the datetime parsing logic is too heavy in Xee right now. Though there are a lot of XPath conformance tests to pass for operations on this stuff.

I see you also have your own decimal implementation. Oh and my integer is arbitrarily large via ibig.

I have endless casting rules too but that could be layered over this stuff.

@faassen Yes, having both my interger and decimal as fixed size makes the storage layer much easier (no arbitrary size).

On testing, the SPARQL testsuite is not covering much built-in types and functions, the XPath testsuite is much more careful on this so I am not sure how correct my implementation is.

@Tpt
rust_decimal is also not arbitrary size. It sounds like the context for your library leads to different choices than mine.

It still strikes me as interesting to attempt to share stuff, perhaps offer different backends for the various data types, though that would mean quite a bit of engineering and right now your lib has almost no deps, an attractive property.

As a first step maybe I will just steal your date-time related parsers first so I can get rid of my overwrought implementation.