xforms-spec icon indicating copy to clipboard operation
xforms-spec copied to clipboard

The XForms-derived specification used in the ODK ecosystem. If you are interested in building a tool that is compliant with the forms rendered by ODK tools, this is the place to start. ✨⚒✨

Results 48 xforms-spec issues
Sort by recently updated
recently updated
newest added

As described at https://www.w3.org/TR/2003/REC-xforms-20031014/slice8.html#ui-selectMany: > Note that the datatype bound to this form control may include a non-enumerated value space, e.g., xsd:string, or a union of a enumeration and a...

To add or refer to`` action to add defaults with the odk-new-repeat (and odk-instance-first-load) events. Perhaps `jr:template` can be removed entirely as it has become obsolete (once pyxform no longer...

without giving the impression that it is exclusively a body element https://opendatakit.github.io/xforms-spec/#body-elements

Now that we have a way to [add external XML data](https://opendatakit.github.io/xforms-spec/#secondary-instances---external), I'd like to propose to extend this by adding a way to add external CSV data. This proposal aims...

See the sample manifest at https://opendatakit.github.io/xforms-spec/encryption and issue filed with Central at https://github.com/opendatakit/central/issues/114.

Not immediately clear to me if this done after calculations or before (but may be overlooking).

Everyone's favorite function, `jr:choice-name`, seems to be documented with arguments flipped. It should be `jr:choice-name(node node, string value)` I believe. Validate and Collect agree with that.

We've been having some conversations about `trigger` with the Collect community: opendatakit/collect#908 The punchline is that we're not sure why `trigger` was used to represent boolean values. Does anyone know?...

needs discussion

https://opendatakit.github.io/xforms-spec/client-audit-logs says "`node`: for events that refer to a specific node, the XPath path of that node". Add something like "In the case of repeats, position predicates are always included...

Our spec implies that `ref `and `nodeset` can be used interchangeably in the `` and just recommends to use nodeset for `` and `` elements. I think this is not...