|Frequently Asked Questions|
- How does Nux relate to Saxon?
Nux wraps Saxon via a XOM-friendly API, hiding most of Saxon's substantial complexity and
making it accessible via a convenient, powerful and efficient API.
In general, Saxon (and by its virtue, Nux) implements the latest and greatest XQuery specs.
Nux supports XQuery in the same way that Saxon does.
If Saxon supports XQuery feature XYZ, then Nux automatically inherits that feature as well,
with the very same semantics.
For example, Saxon and Nux implement XQuery's full axis feature,
i.e., support all 12 XPath axes (except the namespace axis which has been deprecated by the W3C).
In particular, anything that can be done with the Saxon API can be done with the Nux API.
Like Saxon-B, Nux XQuery is not schema aware, unlike the commercial Saxon SA version.
Nux contributed its Saxon-XOM bridge back to the Saxon codebase.
- What about support for database integration and the
XQJ will be very useful, but it is still immature, in flux and mostly without real implementations. Once XQJ stabilizes, and implementations of it become available,
we will also support plugging in any XQJ implementation via a factory interface.
But that day doesn't seem close yet.
- Where does the project name stem from?
No, it's not an akronym.
For anthropologists: The Goddess Nux (Night) was one of the four original primeval Greek deities,
who were the first entities to be formed out of Chaos, her siblings being
Eros (Love), Gaea (Earth) and Erebos (Darkness).
Nux vomica also refers to a tree native to the East Indies, as well as its nut-like seeds.
In homeopathy, it is one of the most commonly prescribed remedies.
- I'd like to help. How can I contribute?
Your contributions are most welcome, be they suggestions for improvement,
problem reports, bug fixes, patches, or anything else.
In particular, a comprehensive suite of JUnit test cases in your area of interest
would be a very useful addition.