Skip to content
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

Can <annotation be used by authors or is it claimed by bibxml? #360

Open
1 task done
cabo opened this issue Jul 29, 2023 · 4 comments
Open
1 task done

Can <annotation be used by authors or is it claimed by bibxml? #360

cabo opened this issue Jul 29, 2023 · 4 comments
Labels
enhancement New feature or request

Comments

@cabo
Copy link

cabo commented Jul 29, 2023

Description

Annotations could be content of the referencing document or they could be used by bibxml.
Are they?

Code of Conduct

@cabo cabo added the enhancement New feature or request label Jul 29, 2023
@TonyLHansen
Copy link

can you give an example?

@cabo
Copy link
Author

cabo commented Aug 2, 2023

As a document author, maybe I want to add an annotation to a referencec such as that the referenced document was superseded by another document, possibly by another SDO (say, was OASIS and is now ISO). But if there are annotations from the bibxml, these might clash. So I was wondering whether bibxml ever emits annotations or I'm free to hand that tool to the document authors.

@TonyLHansen
Copy link

AFAIK, none of the bibxml references have ever had annotations within them.

@cabo
Copy link
Author

cabo commented Mar 5, 2024

The current code in kramdown-rfc simply appends annotations to any incoming bibxml.
The conflict I was envisioning doesn't exist, because one can have zero or more annotations in a reference.
Still, it would be nice to document invariants such as "the bibxml service does not output annotation elements" if they exist.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants