Hi Éric, thank you for these comments.
I’m currently collecting updates into https://github.com/cabo/ace-aif until the ID submission opens again. > On 2022-03-08, at 09:45, Éric Vyncke via Datatracker <[email protected]> wrote: > > Éric Vyncke has entered the following ballot position for > draft-ietf-ace-aif-06: No Objection > […] > > # COMMENTS > > I like when "internet of things" is used without its "IoT" acronym ;) > > ## Abstract > > In "This specification provides a generic information model and format" should > this rather be "This specification provides a generic information and a data > models" ? It actually goes down one more level, from the data model level to the (representation) format. In the interest of brevity, we mention only the top and bottom end. > ## Section 2 > > Suggestion: to avoid the reader to stop wondering at figure 1, please > introduce > "Toid" and "Tperm" before the figure 1. Fixed in https://github.com/cabo/ace-aif/commit/5889c92 > ## Section 2.3 > > I took me several reading and parsing of this section to understand the need > and the specification of "dynamic-GET". May I suggest a rewrite about: the > issue that this section wants to address, be specific that this doc define > "dynamic methods" (not defined anywhere else) ? See also Rob's comment. Fixes to Rob’s comment are in https://github.com/cabo/ace-aif/commit/d7748f3 The motivation is already in 2.2. The title and first sentence says "With Dynamic Resource Creation”, so that should be enough of positioning. I hope that the fixes to Rob’s comment make this section easier to understand. If there are any “dynamic methods” in the text, please point me to them — the methods are still the same, but the permission bits say that they refer to applying these methods on the “dynamic resources”, not on the resource mentioned in the Toid field. > ## Section 3 > > In the first paragraph, should the plural form be used for 'information model' > ? As two of them are defined before. The specializations are for the generic information model, not necessarily for the specific variant information models given. (For instance, MQTT has their own specialization in Section 2.3 of draft-ietf-ace-mqtt-tls-profile-15.txt.) The section then goes on to discuss “our” variants. Grüße, Carsten _______________________________________________ Ace mailing list [email protected] https://www.ietf.org/mailman/listinfo/ace
