ACTION Steven to dig out previous discussions on MIPs on controls and evaluate effect of MIPs on controls

This was the first time I used the new XForms Minutes app in anger, but I'm 
very glad I made it, because it made the task of finding previous stuff 
very much easier.

Alain's orginal message: 
https://lists.w3.org/Archives/Public/public-xformsusers/2019Apr/0046

Discussion:
https://www.w3.org/2019/05/08-forms-minutes.html#item06
ACTION-2255 on Erik: 
https://lists.w3.org/Archives/Public/public-xformsusers/2019Jun/0005

This led to ACTION 2259 - Steven to spec
and apparently I dropped the ball on that, when somehow it got left off an 
agenda and never put back.

So let me try and repair that mistake.


Model Item Properties on controls

The MIPS are type, constraint, relevant, required, readonly, calculate, 
whitespace
as well as label, help, hint, alert which are already allowed on controls
and p3ptype which is deprecated.

In the following all elements and attributes that are deprecated have been 
ignored.

Calculate and whitespace are special in that they are not allowed to be 
applied more than once to a node. The others are as long as they don't 
clash.

Let's take them one by one:

type
Looks OK, as long as the types aren't incompatible. All have to be 'true', 
i.e. match.

constraint
Similarly; would just add another constraint. All have to be true.

relevant
We had already agreed to do this, and it is already possible using a filter 
on the ref. All have to be true.

required
Would add another requirement option. Only one has to be true for it to 
apply.

readonly
We had already agreed to do this. One has to be true.

calculate
It has always low-key annoyed me that we have @calculate and @value, but  
the difference is that @calculate affects the @ref, and @value replaces it.

Combination of calculates are not allowed. We might have to investigate to 
what extent calculate and value clash, but I expect they don't, because if 
you have @value, you don't have @ref, and vice versa.

Calculate makes the value readonly.

 <output value="x+1"/>
 <output ref="x" calculate=".+1"/>

the latter would update x, and make it readonly at this point.

whitespace
Combination not allowed.

@value

@value produces a string, @mediatype specifies how to interpret it

@value is carried by

   label hint help alert
   output
   output/mediatype (deprecated)
   select[1]/item
   select[1]/itemset

@mediatype is carried by
   label hint help alert
   output

(submission which is not a control, also has @value and @relevant
   submission/header has @value)
   
Actions that carry @value
   
   setvalue
   param
   property

Received on Friday, 12 April 2024 13:23:14 UTC