Strip from this dataset all documents that have more complete equivalents in other datasets. (I don’t suggest to delete them from any underlying XML source; just make sure they don’t get into relaton-data-misc. I don’t know the best way of doing this, perhaps by filtering out certain filenames in the GHA workflow?) This would mean 1) old xml2rfc paths still work (via bibxml-data-archive fallback) and 2) GUI shows a newer version. I suspect there are no downsides.
Iff removed document corresponds to a legacy path (that is, a path that exists in bibxml-data-archive), we can additionally map that legacy path so that they don’t fallback and return more complete data.
Case in point:
IEEE 802.1QBV_2015.Proposed plan
Strip from this dataset all documents that have more complete equivalents in other datasets. (I don’t suggest to delete them from any underlying XML source; just make sure they don’t get into relaton-data-misc. I don’t know the best way of doing this, perhaps by filtering out certain filenames in the GHA workflow?) This would mean 1) old xml2rfc paths still work (via bibxml-data-archive fallback) and 2) GUI shows a newer version. I suspect there are no downsides.
Iff removed document corresponds to a legacy path (that is, a path that exists in bibxml-data-archive), we can additionally map that legacy path so that they don’t fallback and return more complete data.
Asking for comments @ronaldtse and @andrew2net.