Pack URI

Table 1. H–15. Pack URI conformance requirements

ID

Rule

Reference

Package Implementer

Format Designer

Format Producer

Format Consumer

M7.1

The authority component contains an embedded URI that points to a package. The package implementer shall create an embedded URI that meets the requirements defined in RFC 3986 for a valid URI.

B.1

×

M7.2

The optional path component identifies a particular part within the package. The package implementer shall only create path components that conform to the part naming rules. When the path component is missing, the resource identified by the pack URI is the package as a whole.

B.1

×

M7.3

The package implementer shall consider pack URIs equivalent if:

The scheme components are octet-by-octet identical after they are both converted to lowercase; and

The URIs, decoded as described in §B.2 from the authority components are equivalent (the equivalency rules by scheme, as per RFC 3986); and

The path components are equivalent when compared as case-insensitive ASCII strings.

B.4

×

M7.4

The package implementer shall not create an authority component with an unescaped colon (:) character.

B.1

×

Table 2. H–16. Pack URI optional requirements

ID

Rule

Reference

Package Implementer

Format Designer

Format Producer

Format Consumer

O7.1

Consumer applications, based on the obsolete URI specification RFC 2396, might tolerate the presence of an unescaped colon character in an authority component.

B.1

×