Name Changes #85
thesimmermon
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Is it possible to change the names of any of the fields in this specification? I know we were in a hurry to get this out the door before and that we were going to clean it up in the next version, but since we are much past that point, perhaps we can revisit this topic? For instance, the "broadcast" flag does not mean broadcast and causes confusion to implementers. This flag actually means if it is true, do not broadcast. If it is false, broadcast, and if it is omitted, -- broadcast?.
There are other places where we might make some small name changes or ensure consistent naming throughout the data objects that will ease understanding.
And, if we want to stretch a little, we could talk about the use of HTTP verbs. We use PUT in places where it should be a POST and GET that could be a POST in places.
The original thought was to publish this to exactly match OPCP so that we could just say everyone was migrated. However, I recommend that we take a moment to decide as a group if we are just documenting the OPCP protocol or trying to build something more resilient that will work as a standard.
And I know this is late in the game. I haven't chimed in on this topic because when I joined these decision were already made. But, we are now 2 years later and since we are still in draft mode, maybe it would be a good time to build the right thing.
Beta Was this translation helpful? Give feedback.
All reactions