Data descriptive labels and field names MUST match the "Guide to Field Names" (...fix the Guide if necessary)

[jpotvin]

In https://xalgo-rm-components-sample-application.netlify.app/editor we have Input: Contexts Jurisdictions Country Jurisdiction Sub-Country Jurisdiction

But in https://xalgo-system.herokuapp.com/apps/rm/editor/353f82b7-c52d-4539-bade-872f54ca4512 we have Input: Contexts Data Sources Jurisdiction Sub-Jurisdiction

In the Guide to Field Names I specified the following use-friendly questions: WHERE AND WHEN THIS RULE IS ASSERTED TO BE "IN EFFECT" What is the country jurisdiction of the organization or person declaring this to be a rule? What is the state/province/territory/region jurisdiction (one level below the 'country') of the organization or person declaring this to be a rule?

... and the fieldnames would be called: INPUT.CONTEXT
jurisdictions.country jurisdictions.subcountry

• I indended for those short questions to be the labels for each field (rather like filling in an income tax form).
• I did not intend for the concatenated fieldnames themselves to be used for communication with the end-user Author.
• The Guide to Field Names needs to be implemented exactly as it is the thoroughly-considered core data structure. If it contains a problem it needs to be fixed. We cannot have any mismatch between the (latest) Guide to Field Names and the implemented data names and prompts.

[jpotvin]

Also "Name & Description" shows up in an odd place before the "Start Date". (The label "Name & Description" should be removed from there.) And "End Date" is mis-labelled as "Start Date" Where does the text "Standard Role Name" come from?

...all in all, non-conforance to the Guide to Field Names makes the logic of the form hard to use.

[millenniallglyphs]

I made some changes for today, but we should come back to this + determine a strategy for managing all the labels, hints, heuristics, etc.