Anton Strogonoff

As of now, the discrepancies are: > * [IANA](https://raw.githubusercontent.com/ietf-tools/relaton-data-iana/main/data/bgp-extended-communities_arp-nd-extended-community-flags.yaml): > > ``` > contributor -> 0 -> organization -> abbreviation > str type expected (type=type_error.str) # fixed > ``` >...

A couple of notes: - Reindex delay is the same for all data sources (https://bib.ietf.org/static/docs/howto/auto-reindex-sources.html) - The delay, if any, is configured in environment variables (Kesara may know the value,...

> Another URL that is causing above error: `http://bib.ietf.org/public/rfc/bibxml-ids/reference.i-d.draft-harkins-pkex-02.xml` This URL contains `i-d` in lowercase, the logic assumes `I-D`. This could be changed, of course🤔

> The ID is definitely invalid, it is likely to should have been `moss-named-ports-01`. @strogonoff what should we do with this? It looks like the path was not given correctly....

What I’m going to do for now is avoid canonical URLs of the form `/type/IETF/RFCXXXX` in both API and GUI, and rather provide an endpoint a la `/get-citation-by-docid?type=IETF&id=RFCXXXX`, which would...

I think we’re talking on different layers of abstraction. As a web resource, we provide some entities (citation or bibitem, doesn’t matter in this context), and we want to have...

Related: https://github.com/relaton/relaton-data-w3c/issues/2

> If we can synchronise the PubID and the DOI as done in NIST PubID, would you be happier? I’ll start from the end: there is no such thing as...

This will remain open for now. For reasons described above (possible lack of a singular canonical identifier), the service doesn’t offer reliable canonical URLs for bibliographic items, purposefully supporting querying...

> > the service doesn’t offer reliable canonical URLs for bibliographic items > > For the stable PubIDs, we are able to offer canonical URLs, right? Well, we don’t have...