In the examples that follow, keys with values that are null or an empty sequence are elided for editorial clarity. String literals that include an ampersand character are written as string templates (for example `Barnes&Noble`) to ensure that the examples work in both XPath and XQuery. |
| Expression: | parse-uri("http://qt4cg.org/specifications/xpath-functions-40/Overview.html#parse-uri") |
|---|
| Result: | {
"authority": "qt4cg.org",
"fragment": "parse-uri",
"hierarchical": true(),
"host": "qt4cg.org",
"path": "/specifications/xpath-functions-40/Overview.html",
"path-segments": ("", "specifications", "xpath-functions-40", "Overview.html"),
"scheme": "http",
"uri": "http://qt4cg.org/specifications/xpath-functions-40/Overview.html#parse-uri"
} |
|---|
| Expression: | parse-uri("http://www.ietf.org/rfc/rfc2396.txt") |
|---|
| Result: | {
"authority": "www.ietf.org",
"hierarchical": true(),
"absolute": true(),
"host": "www.ietf.org",
"path": "/rfc/rfc2396.txt",
"path-segments": ("", "rfc", "rfc2396.txt"),
"scheme": "http",
"uri": "http://www.ietf.org/rfc/rfc2396.txt"
} |
|---|
| Expression: | parse-uri("https://example.com/path/to/file") |
|---|
| Result: | {
"authority": "example.com",
"path": "/path/to/file",
"scheme": "https",
"path-segments": ("", "path", "to", "file"),
"host": "example.com",
"hierarchical": true(),
"absolute": true(),
"uri": "https://example.com/path/to/file"
} |
|---|
| Expression: | parse-uri(
`https://example.com:8080/path?s=%22hello world%22&sort=relevance`
) |
|---|
| Result: | {
"authority": "example.com:8080",
"hierarchical": true(),
"absolute": true(),
"host": "example.com",
"path": "/path",
"path-segments": ("", "path"),
"port": "8080",
"query": `s=%22hello world%22&sort=relevance`,
"query-parameters": {
"s": """hello world""",
"sort": "relevance"
},
"scheme": "https",
"uri": `https://example.com:8080/path?s=%22hello world%22&sort=relevance`
} |
|---|
| Expression: | parse-uri("https://user@example.com/path/to/file") |
|---|
| Result: | {
"authority": "user@example.com",
"hierarchical": true(),
"absolute": true(),
"host": "example.com",
"path": "/path/to/file",
"path-segments": ("", "path", "to", "file"),
"scheme": "https",
"uri": "https://user@example.com/path/to/file",
"userinfo": "user"
} |
|---|
| Expression: | parse-uri("ftp://ftp.is.co.za/rfc/rfc1808.txt") |
|---|
| Result: | {
"authority": "ftp.is.co.za",
"hierarchical": true(),
"absolute": true(),
"host": "ftp.is.co.za",
"path": "/rfc/rfc1808.txt",
"path-segments": ("", "rfc", "rfc1808.txt"),
"scheme": "ftp",
"uri": "ftp://ftp.is.co.za/rfc/rfc1808.txt"
} |
|---|
| Expression: | parse-uri("file:////uncname/path/to/file") |
|---|
| Result: | {
"filepath": "/uncname/path/to/file",
"hierarchical": true(),
"absolute": true(),
"path": "/uncname/path/to/file",
"path-segments": ("", "uncname", "path", "to", "file"),
"scheme": "file",
"uri": "file:////uncname/path/to/file"
} |
|---|
| Expression: | parse-uri("file:///c:/path/to/file") |
|---|
| Result: | {
"filepath": "c:/path/to/file",
"hierarchical": true(),
"absolute": true(),
"path": "/c:/path/to/file",
"path-segments": ("", "c:", "path", "to", "file"),
"scheme": "file",
"uri": "file:///c:/path/to/file"
} |
|---|
| Expression: | parse-uri("file:/C:/Program%20Files/test.jar") |
|---|
| Result: | {
"filepath": "C:/Program Files/test.jar",
"hierarchical": true(),
"absolute": true(),
"path": "/C:/Program%20Files/test.jar",
"path-segments": ("", "C:", "Program Files", "test.jar"),
"scheme": "file",
"uri": "file:/C:/Program%20Files/test.jar"
} |
|---|
| Expression: | parse-uri("file:\\c:\path\to\file") |
|---|
| Result: | {
"filepath": "c:/path/to/file",
"hierarchical": true(),
"absolute": true(),
"path": "/c:/path/to/file",
"path-segments": ("", "c:", "path", "to", "file"),
"scheme": "file",
"uri": "file:\\c:\path\to\file"
} |
|---|
| Expression: | parse-uri("file:\c:\path\to\file") |
|---|
| Result: | {
"filepath": "c:/path/to/file",
"hierarchical": true(),
"absolute": true(),
"path": "/c:/path/to/file",
"path-segments": ("", "c:", "path", "to", "file"),
"scheme": "file",
"uri": "file:\c:\path\to\file"
} |
|---|
| Expression: | parse-uri("c:\path\to\file") |
|---|
| Result: | {
"filepath": "c:/path/to/file",
"hierarchical": true(),
"path": "/c:/path/to/file",
"path-segments": ("", "c:", "path", "to", "file"),
"scheme": "file",
"uri": "c:\path\to\file"
} |
|---|
| Expression: | parse-uri("/path/to/file") |
|---|
| Result: | {
"filepath": "/path/to/file",
"hierarchical": true(),
"path": "/path/to/file",
"path-segments": ("", "path", "to", "file"),
"uri": "/path/to/file"
} |
|---|
| Expression: | |
|---|
| Result: | {
"fragment": "testing",
"uri": "#testing"
} |
|---|
| Expression: | |
|---|
| Result: | {
"query": "q=1",
"query-parameters":{
"q": "1"
},
"uri": "?q=1"
} |
|---|
| Expression: | parse-uri("ldap://[2001:db8::7]/c=GB?objectClass?one") |
|---|
| Result: | {
"authority": "[2001:db8::7]",
"hierarchical": true(),
"absolute": true(),
"host": "[2001:db8::7]",
"path": "/c=GB",
"path-segments": ("", "c=GB"),
"query": "objectClass?one",
"query-parameters":{
"": "objectClass?one"
},
"scheme": "ldap",
"uri": "ldap://[2001:db8::7]/c=GB?objectClass?one"
} |
|---|
| Expression: | parse-uri("mailto:John.Doe@example.com") |
|---|
| Result: | {
"hierarchical": false(),
"path": "John.Doe@example.com",
"path-segments": "John.Doe@example.com",
"scheme": "mailto",
"uri": "mailto:John.Doe@example.com"
} |
|---|
| Expression: | parse-uri("news:comp.infosystems.www.servers.unix") |
|---|
| Result: | {
"hierarchical": false(),
"path": "comp.infosystems.www.servers.unix",
"path-segments": "comp.infosystems.www.servers.unix",
"scheme": "news",
"uri": "news:comp.infosystems.www.servers.unix"
} |
|---|
| Expression: | parse-uri("tel:+1-816-555-1212") |
|---|
| Result: | {
"hierarchical": false(),
"path": "+1-816-555-1212",
"path-segments": " 1-816-555-1212",
"scheme": "tel",
"uri": "tel:+1-816-555-1212"
} |
|---|
| Expression: | parse-uri("telnet://192.0.2.16:80/") |
|---|
| Result: | {
"authority": "192.0.2.16:80",
"hierarchical": true(),
"absolute": true(),
"host": "192.0.2.16",
"path": "/",
"path-segments": ("", ""),
"port": "80",
"scheme": "telnet",
"uri": "telnet://192.0.2.16:80/"
} |
|---|
| Expression: | parse-uri("urn:oasis:names:specification:docbook:dtd:xml:4.1.2") |
|---|
| Result: | {
"hierarchical": false(),
"path": "oasis:names:specification:docbook:dtd:xml:4.1.2",
"path-segments": "oasis:names:specification:docbook:dtd:xml:4.1.2",
"scheme": "urn",
"uri": "urn:oasis:names:specification:docbook:dtd:xml:4.1.2"
} |
|---|
| Expression: | parse-uri("tag:textalign.net,2015:ns") |
|---|
| Result: | {
"hierarchical": false(),
"path": "textalign.net,2015:ns",
"path-segments": "textalign.net,2015:ns",
"scheme": "tag",
"uri": "tag:textalign.net,2015:ns"
} |
|---|
| Expression: | parse-uri("tag:jan@example.com,1999-01-31:my-uri") |
|---|
| Result: | {
"hierarchical": false(),
"path": "jan@example.com,1999-01-31:my-uri",
"path-segments": "jan@example.com,1999-01-31:my-uri",
"scheme": "tag",
"uri": "tag:jan@example.com,1999-01-31:my-uri"
} |
|---|
This example uses the algorithm described above, not an algorithm that is specifically aware of the jar: scheme. |
| Expression: | parse-uri("jar:file:/C:/Program%20Files/test.jar!/foo/bar") |
|---|
| Result: | {
"hierarchical": false(),
"path": "file:/C:/Program%20Files/test.jar!/foo/bar",
"path-segments": ("file:", "C:", "Program Files", "test.jar!", "foo", "bar"),
"scheme": "jar",
"uri": "jar:file:/C:/Program%20Files/test.jar!/foo/bar"
} |
|---|
This example demonstrates that parsing the URI treats non-URI characters in lexical IRIs as “unreserved characters”. The rationale for this is given in the description of fn:resolve-uri. |
| Expression: | parse-uri("http://www.example.org/Dürst") |
|---|
| Result: | {
"authority": "www.example.org",
"hierarchical": true(),
"absolute": true(),
"host": "www.example.org",
"path": "/Dürst",
"path-segments": ("", "Dürst"),
"scheme": "http",
"uri": "http://www.example.org/Dürst"
} |
|---|
This example demonstrates the use of | instead of : in a Windows path. |
| Expression: | parse-uri("c|/path/to/file") |
|---|
| Result: | {
"filepath": "c:/path/to/file",
"hierarchical": true(),
"path": "/c:/path/to/file",
"path-segments": ("", "c:", "path", "to", "file"),
"scheme": "file",
"uri": "c|/path/to/file"
} |
|---|
This example demonstrates the use of | instead of : in a Windows path with an explicit file: scheme. |
| Expression: | parse-uri("file://c|/path/to/file") |
|---|
| Result: | {
"filepath": "c:/path/to/file",
"hierarchical": true(),
"absolute": true(),
"path": "/c:/path/to/file",
"path-segments": ("", "c:", "path", "to", "file"),
"scheme": "file",
"uri": "file://c|/path/to/file"
} |
|---|