Anton Strogonoff

Currently, the following legacy path pattern works (demo instance pending deployment) /public/rfc/{legacy dataset}/reference.{ref}.xml Tested with external DOI (bibxml7) and static NIST (bibxml-nist). Where: - _legacy dataset_ is a key from...

Example NIST legacy path (#22) on demo instance: http://34.229.41.119:8000/public/rfc/bibxml-nist/reference.NIST_FIPS_8-6.xml

The rest of datasets are lacking data (see issues in https://github.com/ietf-ribose/bibxml-indexer/). _All paths patterns are supported_ via one shared legacy path pattern, as described above. Will be closing all relevant...

W3C data has arrived, example path on demo instance: http://34.229.41.119:8000/public/rfc/bibxml4/reference.WD-SWBP-SKOS-CORE-GUIDE-20051102.xml

@ronaldtse > * Implemented legacy pattern : http://34.229.41.119:8000/public/rfc/bibxml4/reference.WD-xslt20-20050915.xml (not working) Source document does not exist in https://github.com/ietf-ribose/bibxml-data-w3c/tree/main/data (in fact, there is no document at all with date 20050915). If it...

This path pattern now works: http://34.229.41.119:8000/public/rfc/bibxml4/reference.W3C.WD-SWBP-SKOS-CORE-GUIDE-20051102.xml Configuration allows to specify arbitrary prefix for legacy datasets, example: https://github.com/ietf-ribose/bibxml-service/blob/main/bibxml/settings.py#L124

New way of handling xml2rfc-style paths was implemented in https://github.com/ietf-ribose/bibxml-service/commit/905b0867ef9f47d593844a123a283c947fa56e7e, https://github.com/ietf-ribose/bibxml-service/commit/9915e1197cae0c4160e390d39a8d0d446a8dca47 and is deployed as `v2022.1.28_1`. Additionally, now legacy XML is generated the same way as with `format=bibxml` new API...

- Entire overage of xml2rfc data is not yet guaranteed. - Some docs are missing in our data sources. - Some XML filenames in theory may not resolve to our...

@ronaldtse It’s not completely done yet, because some paths are missing in the archive and I want to do something about it. The GUI for checking xml2rfc path resolution may...

Working on it in https://github.com/ietf-ribose/bibxml-service/commit/d5661e87c88130b201d27844f7a2143eaeab9562.