Operation Level Tags must be unique, Fix For Issue 1727

[r-sreesaran]

Operation Level Tags must be unique, Fix For Issue 1727

[r-sreesaran]

@MikeRalphson i have added the changes in 3.1.0 md, have i missed anything else ?.

[MikeRalphson]

@r-sreesaran No, that LGTM. Unfortunately we ran out of time on the last TSC call to discuss open PRs but we will get to it ASAP.

[earth2marsh]

Rather than being so strict as to potentially break existing specs, could we add guidance like, "Duplicate tags MAY be considered an authoring mistake"?

[handrews]

@MikeRalphson

Rather than being so strict as to potentially break existing specs, could we add guidance like, "Duplicate tags MAY be considered an authoring mistake"?

I'm fond of "The behavior of X is undefined" 😛

[r-sreesaran]

@earth2marsh considering the fact it will break existing code changes, this may be the only way forward.

[earth2marsh]

Based on my rationale in #1727 , I'm inclined to close this issue without merging, though I would also like to recognize the author's contribution to the process--thank you!

[lornajane]

Closing as I don't see a consensus to accept/merge this. I'll second the acknowledgement of the contribution though! Thanks!