DICOM PS3.3 2021d - Information Object Definitions

C.24.2.4 Relative URI Reference Within Encapsulated Document (Current)
Prev | C.24.2 Encapsulated Document Module | Next

#### C.24.2.4 Relative URI Reference Within Encapsulated Document

The relative URI reference within encapsulated document value shall be encoded as a relative URI reference [RFC3986], with the following restrictions:

- The base path (URI) to which the reference is relative is the location where the referencing file would hypothetically be written, were it to be unencapsulated and written to a file, such that the set of related encapsulated documents share the same base path.

- The path shall not begin with a slash or two slashes.

- The path shall not refer to a higher level in the file system hierarchy (i.e., use of ".." is not permitted).

- File name extensions corresponding to executable file types (exe, dll, etc.) are not permitted.

- Embedded white space is not permitted.

The following are examples of valid relative URI references:

- "matlist.mtl"

- "materials/matlist.mtl"

- "./materials/matlist.mtl"

The following are examples of invalid relative URI references:

- "file:///matlist.mtl" (not a relative reference)

- "/matlist.mtl" (initial slash not permitted)

- "//matlist.mtl" (initial slashes not permitted)

- "c:/matlist.mtl" (not a relative reference)

- "../matlist.mtl" (".." not permitted)

- "mat list.mtl" (embedded spaces not permitted)

- "materials\matlist.mtl" (backslash not permitted)

Prev | Up | Next
C.24.2.3 Security Considerations for Encapsulated Documents (Informative) | Home | C.25 Real World Value Mapping Modules

DICOM PS3.3 2021d - Information Object Definitions