Did you know ... Search Documentation:
Predicate uri_encoded/3
Availability::- use_module(library(uri)).(can be autoloaded)
Source[det]uri_encoded(+Component, +Value, -Encoded)
[det]uri_encoded(+Component, -Value, +Encoded)
Encoded is the URI encoding for Value. When encoding (Value->Encoded), Component specifies the URI component where the value is used. It is one of query_value, fragment, path or segment. Besides alphanumerical characters, the following characters are passed verbatim (the set is split in logical groups according to RFC3986).
query_value, fragment
"-._~" | "!$’()*,;" | "@" | "/?"
path
"-._~" | "!$&’()*,;=" | "@" | "/"
segment
"-._~" | "!$&’()*,;=" | "@"
Tags are associated to your profile if you are logged in
Tags:
Chris Mungall said (2021-04-27T01:56:35):0 upvotes 0 0 downvotes
Picture of user Chris Mungall.
I am looking for the equivalent to SPARQL ENCODE_FOR_URI. Although both this and uri_encoded/3 seem to implement RFC3986, the behavior seems different in particular, `BIND(ENCODE_FOR_URI('+/') as ?x) yields %2B%2F`. However, no value for Component yields the same. segment pct-encodes the slash but not the plus, query_value pct-encodes the plus but not the slash (the other two options pct-encodes neither).