RFC 7950 does not explicitly state whether two different revisions of a module can be published with the same date.
There is an example of an OpenConfig YANG module that has published multiple revisions with the same revision date, and the OpenConfig proponents state that RFC 7950 does not disallow this.
Note - this issue was discussed in the context of YANG versioning, with the question as to whether the YANG Module versioning draft should explicitly require revision dates to be unique, but amongst the authors the thought was that this is out of scope and it would be more appropriate for this to be clarified via an update to RFC 7950.
Either way, it seems like it would be useful if the next revision of YANG is explicit on this.
RFC 7950 does not explicitly state whether two different revisions of a module can be published with the same date.
There is an example of an OpenConfig YANG module that has published multiple revisions with the same revision date, and the OpenConfig proponents state that RFC 7950 does not disallow this.
Note - this issue was discussed in the context of YANG versioning, with the question as to whether the YANG Module versioning draft should explicitly require revision dates to be unique, but amongst the authors the thought was that this is out of scope and it would be more appropriate for this to be clarified via an update to RFC 7950.
Either way, it seems like it would be useful if the next revision of YANG is explicit on this.