-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove docid
with scope=anchor
#87
Comments
@strogonoff @ronaldtse |
How does "primary docid" look like right now? Why does it have spaces and slashes? |
@andrew2net I believe we were discussing this question with Robert; i.e. ”do we need to maintain all old anchors as is, or can we generate them from docid even if this means they will sometimes differ a bit?” (see https://github.com/ietf-ribose/bibxml-service/issues/206).
Some replacement may be needed, but this can be done by the app that generates XML.
@ronaldtse, primary IDs for RFCs and RFC subseries have spaces (example 1, example 2). Apart from that, I suspect primary (citeable) identifiers of non-IETF documents in And, non-IETF documents in non-IETF Relaton sources often contain slashes (example). |
@strogonoff @ronaldtse @opoudjis in the Relaton model we have a |
|
I feel like we could put anchors in |
|
@andrew2net Interesting:
Maybe this is why the anchor has changed? |
@strogonoff yes, it's definitely so. |
I think the answers have all been answered here. As for:
@strogonoff we can strip off the original anchors on the bibitems sourced from the datatracker -- these are the only ones that provide anchors. |
@strogonoff @ronaldtse can we close this issue? |
@andrew2net I'm still hoping we can get rid of the anchors in the Relaton data. @strogonoff can we? |
Example: https://github.com/ietf-ribose/relaton-data-ids/blob/99b3eadf8840bd841a0044effa87faa4d4e65fce/data/draft-3k1n-6tisch-alice0-00.yaml#L18-L20
Just in case, I think we should first check what Robert further replies in this thread: https://github.com/ietf-ribose/bibxml-service/issues/206#issuecomment-1136058412
cc @ronaldtse
The text was updated successfully, but these errors were encountered: