You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?)
The text was updated successfully, but these errors were encountered:
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
"3.11.6 Messages with embedded links" has:
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?)The text was updated successfully, but these errors were encountered: