Hi Sue, Thank you for the teachables inside your message! I really appreciate them (but will need some time to fully ingest them). On the remaining comment: > You have still missed the following editorial issues in -20: > #19 –2.2.3. sdfAction, paragraph 1, unclear > > > Old text: > > /The sdfAction group contains declarations of Actions, model > > affordances that, when triggered, have more effect than just reading, > > updating, or observing Thing state, often resulting in some outward > > physical effect (which, itself, cannot be modeled in SDF). / > > > Maybe my comment was unclear, so let me suggest a change: > > New text: / > The sdfAction group contains declarations of Actions and model > affordances that, when triggered, have more effect than just reading, > updating, or observing Thing state. These Actions and model > Affordances often resulting in some outward physical effect > (which, itself, cannot be modeled in SDF). / Oh, I now see how this indeed was unclear. Here is what we were trying to say: »The `sdfAction` group contains declarations of Actions, which model affordances that, when triggered, have more effect than just reading, updating, or observing Thing state. Actions often result in some outward physical effect (which, itself, cannot be modeled in SDF). From a programmer's perspective, they might be considered to be roughly analogous to method calls.« Now: https://github.com/ietf-wg-asdf/SDF/pull/174 (and likely to be part of a -21.) Grüße, Carsten -- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
