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

Is any escaping of URIs within "3.11.6 Messages with embedded links" needed? #657

Open
davidmalcolm opened this issue Aug 19, 2024 · 2 comments

Comments

@davidmalcolm
Copy link

"3.11.6 Messages with embedded links" has:

link destination = ? Any valid URI ?;
embedded link = "[", link text, "](", link destination, ")";

My reading of the spec if that no escaping is needed/done on the link destination, and thus it is implicitly required that URIs do not contain ) so that a consumer can detect where the link destination ends.

Am I correct? Is this lack of ) guaranteed by RFC 3896, an additional constraint in SARIF, or is some kind of matching of ( and ) pairs assumed for SARIF consumers? (and is that guaranteed by RFC 3896?)

@davidmalcolm davidmalcolm changed the title Escaping of URIs within "3.11.6 Messages with embedded links" Is any escaping of URIs within "3.11.6 Messages with embedded links" needed? Aug 19, 2024
@sthagen
Copy link
Contributor

sthagen commented Aug 30, 2024

Interesting question, thank you. I added the question and to be discussed labels, as I think the TC should consider this question.

@davidmalcolm
Copy link
Author

"On RFC 3896: I don’t believe lack of ) is guaranteed. e.g., https://en.wikipedia.org/wiki/Parenthesis_(disambiguation)"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants