I am working on a custom actuator profile (cap) and could use some assistance in wording.
We use the work 'optional' in two different contexts.
One use of 'optional' is whether a particular command component is required to be implemented by the receiver and another use is whether a particular command component is required to be sent on the wire by the producer.
An example of the former would be an actuator that did not implement the optional argument 'start_time' (ie it just executed the command when received and did not have the ability to delay the command to start at a future time).
An example of the latter would be an actuator that did implement 'delay command until a future time' but had a default start_time='now' so it is ok to leave the start_time off the command.
Do we have a convention on how to word stuff like this? I'm trying to say the cap removes the options from the slpf profile but it doesn't - it only removes the first kind (ie it does implement start_time) but the kind are still optional (ie you don't have to put start_time on the wire).
Duncan Sparrell
sFractal Consulting LLC
iPhone, iTypo, iApologize