Martijn van de Rijdt

That's all, I think.

This may be sufficiently covered after implementing https://github.com/opendatakit/xforms-spec/issues/139

* [ ] add a JS script that add the `xforms` css class to all links with textContent starting with "XForms" * [ ] styling for `xforms` class

In Enketo Express, the irrelevant nodes are removed (not just emptied) when the record is saved as final and can no longer be edited. So this is not upon submission...

> So while a form is actively being filled out, irrelevant nodes are not removed, correct? Yes, correct. > So, if the node is not removed, are their values 'blanked'...

Yes, the accidental data loss is a valid concern. I'll try to find the arguments for introducing the 'clear immediately mode' a while back, but we could probably defend both...

I think it make sense to first do 1.0 as that's part of XForms 1.0 and 1.1 and some functions we already use may be deprecated in 3.0. However, maybe...

Thanks for looking into this! I'll check out the references with interest (within a few days ;)). I'm particularly interested in backwards compatibility of XPath 1.0 expressions (XForms) in XPath...

Ah ok. We can perhaps split this issue up into the more exciting little (but :boom:POWER:boom: boosting) improvements. I think these: - starts-with(), ends-with(), contains() => now done in #105...

I'd like to expand on this by also providing a way to add translations to external data as follows: | name | label::English | label::Français | rooms | |------|-------|---|-------| |...