Published at https://getodk.github.io/xforms-spec/
Install Jekyll (Windows users, see here) and bundler.
Afterwards, to install all dependencies for this repo:
bundle install
When editing use jekyll serve or bundle exec jekyll serve to build, start up a webserver and automatically rebuild on http://localhost:4000/xforms-spec/.
Pull requests are welcome for any agreed-upon issues! Propose a specification addition or change or join the live conversation in the xforms-spec channel of the ODK Slack.
This specification is not a fixed document and is regularly extended with new features. Occassionally, poor earlier choices are removed, and behavior is clarified or corrected. To propose a small correction or clarification, just open an issue here. For a more significant change in the XForms specification, the following approach should be used:
- Post a proposal in the ODK Forum (e.g. under the
Developmentcategory and tagged withspec-proposalandodk-xforms). If you have a proposed XForm (and/or XLSForm) syntax, please include it. - If the ODK community is interested and a syntax candidate emerges, there will be a vote according to the ODK Voting Rules.
- Once the extension is approved any relevant issues will be created in this repo, in pyxform and in the XLSForm documentation and the implementation can go ahead.
If you propose a specification addition that does not make it through the approval process (e.g. because it is considered to be for a too-specific use case), the recommended way to add it to your own application is to use your own custom namespace for any new elements or attributes. This will avoid conflicts with any future features in the ODK XForms Specification (or the W3C XForms specification). If in the future, the situation changes and ODK would like to adopt the feature after all, the common practise would be to include it using your namespace.