merge relevant improvements from commcare spec about xforms-spec HOT 3 CLOSED

What's the high level differences here?

On Tue, Aug 25, 2015 at 10:21 AM, Martijn van de Rijdt <
[email protected]> wrote:

https://github.com/dimagi/xform-spec

—
Reply to this email directly or view it on GitHub
#33.

from xforms-spec.

I was referring to just lots of edits and additions that apply to ODK as well.

Major differences of CommCare with ODK are:

• external data (CommCare similar to Enketo => <instance src="jr://somesrc"/>)
• actions
• meta data
• more comprehensive XPath predicate support (I think)
• more native XPath functions
• fewer custom XPath functions
• more namespace usage (and probably better support for this)
• no geotrace and geoshape datatypes
• not sure: external applications

from xforms-spec.

Todo:

• orx:version instead of version acceptable?
• xsd:string, xsd:integer etc acceptable?
• make sure all 'badges' are removed
• section on external app has reference - may need another writer if different from CommCare.
• depending on prev point, check with bind data type 'intent' is correct
• check if function double() is supported
• check if abs(), ceiling(), floor(), log(), uppercase(), contains(), starts-with(), ends-with(), translate(), replace() are not supported (assumed they were not but they are in CommCare)
• check if uuid() description is correct (probably is not!)
• property() description

from xforms-spec.