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

refactor/question: Representation of metadata::Entry #449

Open
duesee opened this issue Feb 15, 2024 · 0 comments
Open

refactor/question: Representation of metadata::Entry #449

duesee opened this issue Feb 15, 2024 · 0 comments
Labels
chore Reduction of technical debt enhancement New feature or request question Further information is requested

Comments

@duesee
Copy link
Owner

duesee commented Feb 15, 2024

Currently, an Entry is basically an AString. However, the RFC has more to say in prose about entries.

  • Each annotation is an entry that has a hierarchical name, with each component of the name separated by a slash ("/"). An entry name MUST NOT contain two consecutive "/" characters and MUST NOT end with a "/" character.
  • Entry names MUST NOT contain asterisk ("*") or percent ("%") characters and MUST NOT contain non-ASCII characters or characters with octet values in the range 0x00 to 0x19.
  • Entry names are case-insensitive.
  • All entries MUST have either "/shared" or "/private" as a prefix. Entry names MUST be specified in a Standards Track or IESG-approved Experimental RFC, or fall under the vendor namespace (i.e., use /shared/vendor/ or /private/vendor/ as the prefix).
@duesee duesee added enhancement New feature or request question Further information is requested chore Reduction of technical debt labels Feb 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Reduction of technical debt enhancement New feature or request question Further information is requested
Projects
Status: No status
Development

No branches or pull requests

1 participant