Thank you again for responding with some further details and for making those references.
It just seems a little odd to me because we have a 'replace' operation for the purpose of replacing property values. When using the add operation, passing visibility and the response being successful, it almost seems like a new visibility property is added even though it is only being replaced.
If that is the agreed upon standard, "if the member already exists, it is replaced by the specified value" for the add operation, then I guess I can be okay with it, but I just want to make sure that this is the standard that is used throughout. Can we get some other folks' input on this to make sure everyone is on the same page and okay with the way this works?
Thank you again for responding with some further details and for making those references.
It just seems a little odd to me because we have a 'replace' operation for the purpose of replacing property values. When using the add operation, passing visibility and the response being successful, it almost seems like a new visibility property is added even though it is only being replaced.
If that is the agreed upon standard, "if the member already exists, it is replaced by the specified value" for the add operation, then I guess I can be okay with it, but I just want to make sure that this is the standard that is used throughout. Can we get some other folks' input on this to make sure everyone is on the same page and okay with the way this works?
Thank you again!