You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jena.apache.org by an...@apache.org on 2022/05/16 13:18:19 UTC
[jena] branch main updated: Update file URL (RFC 8089) and URN (RFC 8141)
This is an automated email from the ASF dual-hosted git repository.
andy pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/jena.git
The following commit(s) were added to refs/heads/main by this push:
new bf66e87e50 Update file URL (RFC 8089) and URN (RFC 8141)
new d73862568a Merge pull request #1312 from afs/file-url
bf66e87e50 is described below
commit bf66e87e50367544dc6388e4ab461aca8d4306c4
Author: Andy Seaborne <an...@apache.org>
AuthorDate: Sun May 15 22:15:52 2022 +0100
Update file URL (RFC 8089) and URN (RFC 8141)
URN changes move java changes into violations.xml
---
jena-iri/NotesAFS.txt | 7 +
.../java/org/apache/jena/iri/ViolationCodes.java | 273 ++++++---------------
.../xml/org/apache/jena/iri/impl/violations.xml | 79 ++----
3 files changed, 107 insertions(+), 252 deletions(-)
diff --git a/jena-iri/NotesAFS.txt b/jena-iri/NotesAFS.txt
index 1b0f2a3f5c..9c25ffc8e4 100644
--- a/jena-iri/NotesAFS.txt
+++ b/jena-iri/NotesAFS.txt
@@ -1,3 +1,10 @@
+==
+Changes for 8089 (file URL)
+violations.xml
+==
+Changes for 8141 (URN)
+violations.xml
+
===
Changes for RFC 1123 sec 2.1
violations.xml: comment out IP_V4_HAS_FOUR_COMPONENTS
diff --git a/jena-iri/src/main/java/org/apache/jena/iri/ViolationCodes.java b/jena-iri/src/main/java/org/apache/jena/iri/ViolationCodes.java
index 701bdd00c5..0801d009ff 100644
--- a/jena-iri/src/main/java/org/apache/jena/iri/ViolationCodes.java
+++ b/jena-iri/src/main/java/org/apache/jena/iri/ViolationCodes.java
@@ -547,12 +547,10 @@ group = alpha *[ alpha | digit | "-" | "." | "+" | "_" ]
<dt><a name="ref-file">[file]</a>
- RFC 1738
+ RFC 8089
</dt>
- <dd><a href="http://www.apps.ietf.org/rfc/rfc1738.html#sec-3.10">
- Host-specific file names
- (section 3.10)
- </a>
+ <dd><a href="http://www.ietf.org/rfc/rfc8089.txt">
+ Host-specific file names</a>
</dd>
<dd>
@@ -562,27 +560,24 @@ group = alpha *[ alpha | digit | "-" | "." | "+" | "_" ]
<dt>
See
- <a href="http://www.apps.ietf.org/rfc/rfc1738.html#sec-5">section 5<a>
+ <a href="http://www.ietf.org/rfc/rfc8089.txt">here<a>
</dt>
<dd>
<pre>
-fileurl = "file://" [ host | "localhost" ] "/" fpath
-</pre>
+ file-URI = file-scheme ":" file-hier-part
+ file-scheme = "file"
- <pre>
-fpath = fsegment *[ "/" fsegment ]
-fsegment = *[ uchar | "?" | ":" | "@" | "&" | "=" ]
-</pre>
+ file-hier-part = ( "//" auth-path )
+ / local-path
+ auth-path = [ file-auth ] path-absolute
- <pre>
-safe = "$" | "-" | "_" | "." | "+"
-extra = "!" | "*" | "'" | "(" | ")" | ","
-escape = "%" hex hex
-unreserved = alpha | digit | safe | extra
-uchar = unreserved | escape
+ local-path = path-absolute
+
+ file-auth = "localhost"
+ / host
</pre>
@@ -606,18 +601,6 @@ uchar = unreserved | escape
The AUTHORITY component is required.<br />
- The PATHQUERY component:
- <ul>
- <li>
- is required to match the regular expression: [^;~]*
- </li>
- <li>
- may use ~; as sub-delimiters, and care must
- be taken when percent escaping or unescaping these delimiters to not disrupt
- the scheme specific syntax.
- </li>
- </ul>
-
<br/>
The following are examples of well-formed IRIs using this scheme:
<ul>
@@ -640,10 +623,6 @@ uchar = unreserved | escape
<li><<code>file://example.org</code>></li>
- <li><<code>file://foo/bar;t</code>></li>
-
- <li><<code>file://foo/~jjc</code>></li>
-
</ul>
</dd>
@@ -731,19 +710,6 @@ uchar = unreserved | escape
</pre>
- </dd>
-
- <dt>
- See
- <a href="http://www.apps.ietf.org/rfc/rfc2141.html#sec-2.3.2">section 2.3.2<a>
- </dt>
- <dd>
-RFC 1630 [2] reserves the characters "/", "?", and "#" for particular purposes.
-The URN-WG has not yet debated the applicability and precise semantics of those
-purposes as applied to URNs. Therefore, these characters are RESERVED for future
-developments. Namespace developers SHOULD NOT use these characters in unencoded form,
-but rather use the appropriate %-encoding for each character.
-
</dd>
</dl>
@@ -752,21 +718,15 @@ but rather use the appropriate %-encoding for each character.
<dd>
The AUTHORITY component must be omitted.<br />
- The QUERY component must be omitted.<br />
-
The PATH component is required.<br />
- The PATH component:
- <ul>
- <li>
- is required to match the regular expression: (?![uU][rR][nN]:)[a-zA-Z0-9][-a-zA-Z0-9]{1,31}:.*
- </li>
- <li>
- may use /~ as sub-delimiters, and care must
- be taken when percent escaping or unescaping these delimiters to not disrupt
- the scheme specific syntax.
- </li>
- </ul>
+ The PATH component
+ is required to match the regular expression: (?![uU][rR][nN]:)[a-zA-Z0-9][-a-zA-Z0-9]{1,31}:.+
+ <br/>
+
+ The QUERY component
+ is required to match the regular expression: [+=].*
+ <br/>
<br/>TODO: case of NIS<br/>TODO:
registry of URNs, implement something of the NSS with Namespace specific rules.
<br/>TODO:
@@ -780,6 +740,8 @@ In addition, octet 0 (0 hex) should NEVER be used, in either unencoded or %-enco
<li><<code>urn:x-hp:foo\u00E9</code>></li>
+ <li><<code>urn:nss:a/b/c</code>></li>
+
<li><<code>urn:urn-1:foo</code>></li>
</ul>
@@ -788,16 +750,12 @@ In addition, octet 0 (0 hex) should NEVER be used, in either unencoded or %-enco
The following are examples of ill-formed IRIs using this scheme:
<ul>
- <li><<code>urn:x-hp:foo/bar</code>></li>
-
<li><<code>urn:urn:foo</code>></li>
<li><<code>urn://foo</code>></li>
<li><<code>urn:foo:bar?query</code>></li>
- <li><<code>urn:foo:ff~</code>></li>
-
</ul>
</dd>
@@ -1775,18 +1733,14 @@ This class is not part of the API.
);
- // Updated for RFC 8089
spec =
new SchemeSpecification(
"file",
-// "1738",
-// "http://www.apps.ietf.org/rfc/rfc1738.html#sec-3.10",
-// "Host-specific file names",
-// "3.10",
"8089",
- "https://tools.ietf.org/html/rfc8089",
- "The \"file\" URI Scheme",
+ "http://www.ietf.org/rfc/rfc8089.txt",
+ "Host-specific file names",
"",
+
new String[]{
"file://user@example.org/foo/bar",
@@ -1797,10 +1751,6 @@ This class is not part of the API.
"file://example.org",
-// "file://foo/bar;t",
-//
-// "file://foo/~jjc",
-
},
new String[]{
@@ -1815,42 +1765,41 @@ This class is not part of the API.
spec
.addDefinition(
- "https://tools.ietf.org/html/rfc8089", "", "");
-// //"http://www.apps.ietf.org/rfc/rfc1738.html#sec-5",
-// ""+
-// "\n"+
-// "fileurl = \"file://\" [ host | \"localhost\" ] \"/\" fpath\n"+
-// ""+
-// "\n"+
-// "fpath = fsegment *[ \"/\" fsegment ]\n"+
-// "fsegment = *[ uchar | \"?\" | \":\" | \"@\" | \"&\" | \"=\" ]\n"+
-// ""+
-// "\n"+
-// "safe = \"$\" | \"-\" | \"_\" | \".\" | \"+\"\n"+
-// "extra = \"!\" | \"*\" | \"'\" | \"(\" | \")\" | \",\"\n"+
-// "escape = \"%\" hex hex\n"+
-// "unreserved = alpha | digit | safe | extra\n"+
-// "uchar = unreserved | escape\n"+
-// "",
-// ""+
-// "</p><pre>\n"+
-// "fileurl = \"file://\" [ host | \"localhost\" ] \"/\" fpath\n"+
-// "</pre>"+
-// "<p>"+
-// "</p><pre>\n"+
-// "fpath = fsegment *[ \"/\" fsegment ]\n"+
-// "fsegment = *[ uchar | \"?\" | \":\" | \"@\" | \"&\" | \"=\" ]\n"+
-// "</pre>"+
-// "<p>"+
-// "</p><pre>\n"+
-// "safe = \"$\" | \"-\" | \"_\" | \".\" | \"+\"\n"+
-// "extra = \"!\" | \"*\" | \"'\" | \"(\" | \")\" | \",\"\n"+
-// "escape = \"%\" hex hex\n"+
-// "unreserved = alpha | digit | safe | extra\n"+
-// "uchar = unreserved | escape\n"+
-// "</pre>"+
-// "<p>"
-// );
+ "http://www.ietf.org/rfc/rfc8089.txt",
+ ""+
+ "\n"+
+ " file-URI = file-scheme \":\" file-hier-part\n"+
+ "\n"+
+ " file-scheme = \"file\"\n"+
+ "\n"+
+ " file-hier-part = ( \"//\" auth-path )\n"+
+ " / local-path\n"+
+ "\n"+
+ " auth-path = [ file-auth ] path-absolute\n"+
+ "\n"+
+ " local-path = path-absolute\n"+
+ "\n"+
+ " file-auth = \"localhost\"\n"+
+ " / host\n"+
+ "",
+ ""+
+ "</p><pre>\n"+
+ " file-URI = file-scheme \":\" file-hier-part\n"+
+ "\n"+
+ " file-scheme = \"file\"\n"+
+ "\n"+
+ " file-hier-part = ( \"//\" auth-path )\n"+
+ " / local-path\n"+
+ "\n"+
+ " auth-path = [ file-auth ] path-absolute\n"+
+ "\n"+
+ " local-path = path-absolute\n"+
+ "\n"+
+ " file-auth = \"localhost\"\n"+
+ " / host\n"+
+ "</pre>"+
+ "<p>"
+ );
spec.setDNS(true);
@@ -1870,10 +1819,6 @@ This class is not part of the API.
IRIComponents.AUTHORITY
);
- spec.setPattern(PATHQUERY, "[^;~]*" );
-
- spec.setReserved(PATHQUERY,"~;");
-
spec =
new SchemeSpecification(
"prospero",
@@ -2342,7 +2287,6 @@ This class is not part of the API.
);
- // See also https://tools.ietf.org/html/rfc8141
spec =
new SchemeSpecification(
"urn",
@@ -2353,16 +2297,11 @@ This class is not part of the API.
new String[]{
-// Legal by 8141
-// "urn:x-hp:foo/bar",
-
"urn:urn:foo",
"urn://foo",
"urn:foo:bar?query",
-// Legal by 8141
-// "urn:foo:ff~",
},
@@ -2370,10 +2309,9 @@ This class is not part of the API.
"urn:x-hp:foo\u00E9",
- "urn:urn-1:foo",
-
- "urn:urn-1:a/b/c"
+ "urn:nss:a/b/c",
+ "urn:urn-1:foo",
}
);
@@ -2445,37 +2383,19 @@ This class is not part of the API.
"<p>"
);
- spec
- .addDefinition(
- "http://www.apps.ietf.org/rfc/rfc2141.html#sec-2.3.2",
- "RFC 1630 [2] reserves the characters \"/\", \"?\", and \"#\" for particular purposes. The URN-WG has not yet debated the applicability and precise semantics of those purposes as applied to URNs. Therefore, these characters are RESERVED for future developments. Namespace developers SHOULD NOT use these characters in unencoded form, but rather use the appropriate %-encoding for each character.",
- "RFC 1630 [2] reserves the characters \"/\", \"?\", and \"#\" for particular purposes. The URN-WG has not yet debated the applicability and precise semantics of those purposes as applied to URNs. Therefore, these characters are RESERVED for future developments. Namespace developers SHOULD NOT use these characters in unencoded form, but rather use the appropriate %-encoding for each character."
- );
-
spec.prohibit(
IRIComponents.AUTHORITY
);
- // As of RFC 8141 revision of 2141, query, in the form of ?q+ and ?q= are allowed.
- // See the pattern below.
-// spec.prohibit(
-// IRIComponents.QUERY
-// );
-
spec.require(
IRIComponents.PATH
);
- spec.setPattern(QUERY, "[+=].*");
-
spec.setPattern(PATH,
- // RFC 2141 -
- //"(?![uU][rR][nN]:)[a-zA-Z0-9][-a-zA-Z0-9]{1,31}:[^/~]+"
- // RFC 8141 revision of 2141 - JENA-1647
- "(?![uU][rR][nN]:)[a-zA-Z0-9][-a-zA-Z0-9]{0,30}[a-zA-Z0-9]:.+"
- );
+ "(?![uU][rR][nN]:)[a-zA-Z0-9][-a-zA-Z0-9]{1,31}:.+" );
- spec.setReserved(PATH,"/~");
+ spec.setPattern(QUERY,
+ "[+=].*" );
spec =
new SchemeSpecification(
@@ -3041,8 +2961,7 @@ This class is not part of the API.
"http://example.org/fo<o",
- // & before ? (so in the PATH) is acceptable by RFC 3986 (general URI) and RFC 7230 (http URI scheme)
-// "http://example.org/fo>o",
+ "http://example.org/fo>o",
"http://example.org/fo\"o",
@@ -4572,9 +4491,7 @@ This class is not part of the API.
"http://xn--andr--ep-.example.org/",
- // Was longer, but breaks at Java19.
- // Still way over the DNS name limits (255 bytes, 63 bytes a label).
- "http://xn.example.\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u333 [...]
+ "http://xn.example.\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u333 [...]
},
@@ -5303,31 +5220,13 @@ This class is not part of the API.
new FromSpec_scheme(
"file",
PATH,
- "http://www.apps.ietf.org/rfc/rfc1738.html#sec-5",
- ""+
- "\n"+
- "fileurl = \"file://\" [ host | \"localhost\" ] \"/\" fpath\n"+
- "",
- "<p>"+
- "</p><pre>\n"+
- "fileurl = \"file://\" [ host | \"localhost\" ] \"/\" fpath\n"+
- "</pre>"+
- "<p></p>"
+ "http://www.ietf.org/rfc/rfc8089.txt"
),
new FromSpec_scheme(
"file",
AUTHORITY,
- "http://www.apps.ietf.org/rfc/rfc1738.html#sec-5",
- ""+
- "\n"+
- "fileurl = \"file://\" [ host | \"localhost\" ] \"/\" fpath\n"+
- "",
- "<p>"+
- "</p><pre>\n"+
- "fileurl = \"file://\" [ host | \"localhost\" ] \"/\" fpath\n"+
- "</pre>"+
- "<p></p>"
+ "http://www.ietf.org/rfc/rfc8089.txt"
),
new FromSpec_scheme(
@@ -5446,31 +5345,13 @@ This class is not part of the API.
new FromSpec_scheme(
"file",
USER,
- "http://www.apps.ietf.org/rfc/rfc1738.html#sec-5",
- ""+
- "\n"+
- "fileurl = \"file://\" [ host | \"localhost\" ] \"/\" fpath\n"+
- "",
- "<p>"+
- "</p><pre>\n"+
- "fileurl = \"file://\" [ host | \"localhost\" ] \"/\" fpath\n"+
- "</pre>"+
- "<p></p>"
+ "http://www.ietf.org/rfc/rfc8089.txt"
),
new FromSpec_scheme(
"file",
PORT,
- "http://www.apps.ietf.org/rfc/rfc1738.html#sec-5",
- ""+
- "\n"+
- "fileurl = \"file://\" [ host | \"localhost\" ] \"/\" fpath\n"+
- "",
- "<p>"+
- "</p><pre>\n"+
- "fileurl = \"file://\" [ host | \"localhost\" ] \"/\" fpath\n"+
- "</pre>"+
- "<p></p>"
+ "http://www.ietf.org/rfc/rfc8089.txt"
),
new FromSpec_scheme(
@@ -5503,12 +5384,6 @@ This class is not part of the API.
"<p></p>"
),
- new FromSpec_scheme(
- "urn",
- QUERY,
- "http://www.apps.ietf.org/rfc/rfc2141.html#sec-2.3.2"
- ),
-
},
new String[]{
@@ -5808,7 +5683,7 @@ This class is not part of the API.
<li><<code>http://example.org/fo<o</code>></li>
- <li><<code>http://example.org/fo>o</code>></li>
+ <li><<code>http://example.org/fo>o</code>></li>
<li><<code>http://example.org/fo"o</code>></li>
@@ -7066,7 +6941,7 @@ URI producers should provide these registered names in the IDNA encoding, rather
<li><<code>http://xn--andr--ep-.example.org/</code>></li>
- <li><<code>http://xn.example.\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u333 [...]
+ <li><<code>http://xn.example.\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u3333\u333 [...]
</ul>
@@ -7525,8 +7400,6 @@ For instance, the "foo" tree would allow creation of scheme names of the form: "
/**The character code is not assigned in the version of Unicode implemented here.
- Check validity of code, consider updating your copy of icu4j.jar.
-
<p>This violates the following specifications:
<a href="#ref-Unicode">[Unicode]</a>, <a href="#ref-IRI">[IRI]</a>.
</p>
diff --git a/jena-iri/src/main/xml/org/apache/jena/iri/impl/violations.xml b/jena-iri/src/main/xml/org/apache/jena/iri/impl/violations.xml
index 58f88dac7c..d05a897c2f 100644
--- a/jena-iri/src/main/xml/org/apache/jena/iri/impl/violations.xml
+++ b/jena-iri/src/main/xml/org/apache/jena/iri/impl/violations.xml
@@ -239,50 +239,36 @@ group = alpha *[ alpha | digit | "-" | "." | "+" | "_" ]
<scheme id="wais" type="scheme" rfc="4156">
<name>Wide Area Information Servers</name>
</scheme>
-<scheme id="file" type="scheme" rfc="1738" section="3.10">
+<!-- Was RFC 1738, now updated for RFC 8089 -->
+<scheme id="file" type="scheme" rfc="8089">
<name>Host-specific file names</name>
-
- <defn section="5">
-<pre>
-fileurl = "file://" [ host | "localhost" ] "/" fpath
-</pre>
+<defn>
<pre>
-fpath = fsegment *[ "/" fsegment ]
-fsegment = *[ uchar | "?" | ":" | "@" | "&amp;" | "=" ]
-</pre>
-<pre>
-safe = "$" | "-" | "_" | "." | "+"
-extra = "!" | "*" | "'" | "(" | ")" | ","
-escape = "%" hex hex
-unreserved = alpha | digit | safe | extra
-uchar = unreserved | escape
+ file-URI = file-scheme ":" file-hier-part
+
+ file-scheme = "file"
+
+ file-hier-part = ( "//" auth-path )
+ / local-path
+
+ auth-path = [ file-auth ] path-absolute
+
+ local-path = path-absolute
+
+ file-auth = "localhost"
+ / host
</pre>
</defn>
<complete/>
<dns/>
- <prohibit component="USER" section="5"><text>
-<pre>
-fileurl = "file://" [ host | "localhost" ] "/" fpath
-</pre></text></prohibit>
- <prohibit component="PORT" section="5"><text>
-<pre>
-fileurl = "file://" [ host | "localhost" ] "/" fpath
-</pre></text></prohibit>
- <require component="PATH" section="5"><text>
-<pre>
-fileurl = "file://" [ host | "localhost" ] "/" fpath
-</pre></text></require>
- <require component="AUTHORITY" section="5"><text>
-<pre>
-fileurl = "file://" [ host | "localhost" ] "/" fpath
-</pre></text></require>
- <pattern component="PATHQUERY" reserved="~;" >[^;~]*</pattern>
+ <prohibit component="USER"/>
+ <prohibit component="PORT"/>
+ <require component="PATH"/>
+ <require component="AUTHORITY"/>
<bad>file://user@example.org/foo/bar</bad>
<bad>file://eg:4029/foo/bar</bad>
<bad>file:/foo/bar</bad>
<bad>file://example.org</bad>
- <bad>file://foo/bar;t</bad>
- <bad>file://foo/~jjc</bad>
<good>file:///foo/b</good>
<good>file:///foo/b?ar/yuk</good>
</scheme>
@@ -365,6 +351,7 @@ fileurl = "file://" [ host | "localhost" ] "/" fpath
<scheme id="xmlrpc.beeps" type="scheme" rfc="3529">
<name>xmlrpc.beeps</name>
</scheme>
+<!-- RFC 2141, updated for RFC 8141 -->
<scheme id="urn" type="scheme" rfc="2141">
<name>Uniform Resource Names</name>
<defn section="2">
@@ -394,13 +381,6 @@ fileurl = "file://" [ host | "localhost" ] "/" fpath
":" | "=" | "@" | ";" | "$" |
"_" | "!" | "*" | "'"
</pre>
-</defn>
-<defn section="2.3.2">
-RFC 1630 [2] reserves the characters "/", "?", and "#" for particular purposes.
-The URN-WG has not yet debated the applicability and precise semantics of those
-purposes as applied to URNs. Therefore, these characters are RESERVED for future
-developments. Namespace developers SHOULD NOT use these characters in unencoded form,
-but rather use the appropriate %-encoding for each character.
</defn>
<prohibit component="AUTHORITY">
<text section="2">
@@ -414,23 +394,20 @@ but rather use the appropriate %-encoding for each character.
</pre>
</text></prohibit>
- <prohibit component="QUERY" section="2.3.2"/>
<require component="PATH">
<text section="2">
<pre>
<URN&gt; ::= "urn:" <NID&gt; ":" <NSS&gt;
</pre>
</text></require>
-
- <pattern component="PATH" reserved="/~">(?![uU][rR][nN]:)[a-zA-Z0-9][-a-zA-Z0-9]{1,31}:.*</pattern>
- <pattern compoentent="QUERY">[+=].*</pattern>
- <good>urn:x-hp:foo<unicode>00E9</unicode></good>
- <bad>urn:x-hp:foo/bar</bad>
+ <pattern component="PATH">(?![uU][rR][nN]:)[a-zA-Z0-9][-a-zA-Z0-9]{1,31}:.+</pattern>
+ <pattern component="QUERY">[+=].*</pattern>
+ <good>urn:x-hp:foo<unicode>00E9</unicode></good>
+ <good>urn:nss:a/b/c</good>
<bad>urn:urn:foo</bad>
<good>urn:urn-1:foo</good>
<bad>urn://foo</bad>
<bad>urn:foo:bar?query</bad>
- <bad>urn:foo:ff~</bad>
<todo>case of NIS</todo>
<todo>
registry of URNs, implement something of the NSS with Namespace specific rules.
@@ -625,7 +602,7 @@ In addition, octet 0 (0 hex) should NEVER be used, in either unencoded or %-enco
<also ref="URI" fragment="page-49"/>
<bad>http://example.org/fo|o</bad>
<bad>http://example.org/fo<o</bad>
- <bad>http://example.org/fo&gt;o</bad>
+ <bad>http://example.org/fo>o</bad>
<bad>http://example.org/fo"o</bad>
<bad>http://example.org/fo`o</bad>
</violation>
@@ -1655,9 +1632,7 @@ For instance, the "foo" tree would allow creation of scheme names of the form: "
<violation>
<name>UNASSIGNED_UNICODE_CHARACTER</name>
<minting/>
- <description>The character code is not assigned in the version of Unicode implemented here.
- Check validity of code, consider updating your copy of icu4j.jar.
- </description>
+ <description>The character code is not assigned in the version of Unicode implemented here.</description>
<also ref="Unicode"/>
<also ref="IRI"/>
</violation>