]>

fakedme@gmail.com https://soniex2.autistic.space/

wit Internet Engineering Task Force This document describes a format for embedding a URI inside a URI, as part of a URI scheme's syntax definition.

Introduction Sometimes, it is useful to encode application-specific metadata as part of a URI. Traditionally, URIs provide very little support for application-specific metadata: defines URI fragments, but they are specified by "the media type of [the resource]", not the application. In practice, some applications have alternatively made use of fragments for application-specific metadata, in conflict with its intended usage. This document defines a generic syntax for encoding application-specific metadata in a URI.

Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

The Meta-URI Syntax An URI scheme describes a meta-URI if the scheme's syntax conforms to the syntax described here in Augmented BNF , borrrowing various terms from . As per , the meta-URI scheme MAY require support for specific embedded schemes, but SHOULD NOT restrict the allowed embedded schemes.

Fragment Handling The fragment identifier, if any, is not part of the embedded URI, but instead applies to the whole Meta-URI, as per . While the URI-reference term used above includes the fragment identifier, this approach merely enables future updates to to also apply to this document automatically.

IANA Considerations This document has no IANA considerations.

Security Considerations It is up to the scheme authors to evaluate any security implications of using this syntax.

Interoperability Considerations IPv6 literals cannot be encoded in the embedded URI, as square brackets ("[" and "]") are not allowed in the query element. A future update to may change this.

Encoding considerations No encoding considerations are known at this time.

References Normative References Informative References

Acknowledgements Some of the ABNF rules in this document were adapted from .