This is a clean review so the last one most likely still applies. * From my review of the group comm document. There needs to be an easy way to talk about a single entry in the array of all permissions. Some times you only want to ask for one thing and not deal with permissions for any other Toid. Perhaps also define an AIF-Generic-One<>
* Section 3 - I think you might want to highlight that the first bullet implies that once a Toid is found, then there is no need to continue searching. The array allows this because it is an ordered list. Optional to toss the authorization set if a duplicate Toid is found. (And no, I don't want to switch to a map.) * Section 3 - the previous statement is correct for this data model. Should it be a requirement for all data models encoded with this? (I think yes) * Section 3 - I am happy that you are pushing the JSON encoding as a text string!!! * Section 2.1 - I think it would be better to use one of the URI naming parts than using local-part as the identifier assigned here. My problem is that local-part is a term I associate with email addresses. Perhaps "path-query" with or without a leading uri would be a better name. * Section 2.2 - Some of the implementations might be avoided by making a single operation into a series of steps which can then be checked. Thus "opening an unlocked door" becomes two steps "unlock a door" and "open a door" with different permissions set for each. * Section ?? - We should probably say something about the use of "0" for permissions in this model. Is this legal and means nothing else? Jim _______________________________________________ Ace mailing list Ace@ietf.org https://www.ietf.org/mailman/listinfo/ace
