What is the full syntax for an INFO URI?
<< The INFO URI syntax is fully conformant with the generic URI syntax defined in RFC 3986. This specification uses the Augmented Backus-Naur Form (ABNF) notation of RFC 4234 to define the URI. The following core ABNF productions are used by this specification as defined by Appendix B.1 of RFC 4234: ALPHA, DIGIT, HEXDIG. The INFO URI syntax is presented in two parts. Part A contains productions specific to the INFO URI scheme: info-URI = info-scheme ":" info-identifier [ "#" fragment ] info-scheme = "info" info-identifier = namespace "/" identifier namespace = scheme identifier = *( pchar / "/" ) Part B contains generic productions from RFC 3986 which are repeated here both for completeness and for reference. scheme = ALPHA *( ALPHA / DIGIT / "+" / "-" / "." ) pchar = unreserved / pct-encoded / sub-delims / ":" / "@" fragment = *( pchar / "/" / "?" ) unreserved = ALPHA / DIGIT / "-" / "." / "_" / "~" pct-encoded = "%" HEXDIG HEXDIG sub-delims = "!
<< The INFO URI syntax is fully conformant with the generic URI syntax defined in RFC 3986. This specification uses the Augmented Backus-Naur Form (ABNF) notation of RFC 4234 to define the URI. The following core ABNF productions are used by this specification as defined by Appendix B.1 of RFC 4234: ALPHA, DIGIT, HEXDIG. The INFO URI syntax is presented in two parts. Part A contains productions specific to the INFO URI scheme: info-URI = info-scheme ":" info-identifier [ "#" fragment ] info-scheme = "info" info-identifier = namespace "/" identifier namespace = scheme identifier = *( pchar / "/" ) Part B contains generic productions from RFC 3986 which are repeated here both for completeness and for reference.
