SMPTE AG 29

Administrative Guideline

Persistent URIs for documents Document Library — URL Spec (Persistent URIs)

Draft - Thu Feb 27 2025 ~~22:02:09~~ 22:02:06 GMT+0000 (Coordinated Universal Time)

Copyright © 2025 , Society of Motion Picture and Television Engineers . All rights reserved. No part of this material may be reproduced, by any means whatsoever, without the prior written permission of the Society of Motion Picture and Television Engineers.

Warning: This document is an unpublished work under development and shall not be referred to as a SMPTE Standard, Recommended Practice, or Engineering Guideline. It is distributed for review and comment; distribution does not constitute publication. Recipients of this document are strongly encouraged to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation.

Table of contents 🔗

Foreword
Introduction
1 Scope
2 Conformance
3 Normative references
4 Terms and definitions
5 General
6 Most recent version of a document
7 Most recent publication version of a document
8 All documents
9 All versions of a document
10 All documents with the same root number
11 Specific version of a document
12 Package of a specific version of a document

Foreword 🔗

~~SMPTE (the~~ The Society of Motion Picture and Television ~~Engineers)~~ Engineers (SMPTE) is an internationally-recognized standards developing organization. Headquartered and incorporated in the United States of America, SMPTE has members in over 80 countries on six continents. SMPTE’s Engineering Documents, including Standards, Recommended Practices, and Engineering Guidelines, are prepared by SMPTE’s Technology Committees. Participation in these Committees is open to all with a bona fide interest in their work. SMPTE cooperates closely with other standards-developing organizations, including ISO, IEC and ITU. SMPTE Engineering Documents are drafted in accordance with the rules given in its Standards Operations Manual. For more information, please visit www.smpte.org .

This Standards Administrative Guideline forms an adjunct to the use and interpretation of the SMPTE Standards Operations Manual. In the event of a conflict, the Operations Manual shall prevail.

Introduction 🔗

This document specifies URIs for documents developed by the SMPTE Standards Community. The URIs are intended to:

persistently identify documents; and
retrieve documents over the Internet.

As illustrated in Table 1 , URIs are defined for specific versions of documents as well as related collections of documents.

Table 1 –⁠ Sample URIs
URI	Standards document(s) identified by the URI
`https://pub.smpte.org/doc/st429-2/20230716-cd/`	Committee Draft of SMPTE ST 429-2 approved on July 16, 2023
`https://pub.smpte.org/doc/st429-2/20230110-wd/`	Working Draft of SMPTE ST 429-2 approved on January 10, 2023
`https://pub.smpte.org/doc/st429-2/20130116-am1-pub/`	Amendment 1:2013 to SMPTE ST 429-2:2011 approved on January 16, 2013
`https://pub.smpte.org/doc/st429-2/`	List of all versions of SMPTE ST 429-2
`https://pub.smpte.org/doc/429/`	List of all the documents with the root number 429
`https://pub.smpte.org/doc/`	List of all documents
`https://pub.smpte.org/pub/st429-2/`	Most recent publication version of SMPTE ST 429-2
`https://pub.smpte.org/latest/st429-2/`	Most recent version of SMPTE ST 429-2, which is not necessarily at publication stage
`https://pub.smpte.org/package/st429-2/20230110-wd/`	Working Draft of SMPTE ST 429-2 approved on January 10, 2023, as a single ZIP file

The URIs can also used to retrieve the resource itself: an HTTPS GET request to the URI will return the one or more documents identified by the URI. For example, a GET request to https://pub.smpte.org/doc/ returns an HTML document that contains the list of all available document.

2 Conformance 🔗

Normative text is text that describes elements of the design that are indispensable or contains the conformance language keywords: "shall", "should", or "may". Informative text is text that is potentially helpful to the user, but not indispensable, and can be removed, changed, or added editorially without affecting interoperability. Informative text does not contain any conformance keywords. All text in this document is, by default, normative, except: the Introduction, any section explicitly labeled as "Informative" or individual paragraphs that start with "Note:" The following keywords ~~"shall" and "shall not" indicate requirements strictly to be followed~~ have a specific meaning in ~~order to conform to~~ the ~~document~~ context of this document:

shall and shall not express a requirement from which no deviation is ~~permitted. The keywords, "should"~~ permitted;
should and ~~"should not" indicate that, among several possibilities, one is recommended as particularly suitable,~~ should not express a strong recommendation without necessarily mentioning or excluding others; or that a certain course of action is preferred but not necessarily required; or that (in the negative form) a certain possibility or course of action is deprecated but not prohibited. The keywords "may" other choices;
may expresses explicit liberty (or opportunity) to do something;
Note and ~~"need not" indicate courses of action permissible within the limits of the document. The keyword "reserved"~~ informative indicates ~~a provision~~ that the associated prose is not ~~defined at this time, shall not be used, and may be defined in the future. The keyword "forbidden" indicates "reserved"~~ indispensable, and ~~in addition indicates that the provision will never~~ can be ~~defined in the future. Unless otherwise specified, the order of precedence of~~ removed, changed, or added editorially without affecting the ~~types of normative information in this document shall be as follows: Normative prose shall be~~ scope, or the ~~authoritative definition; Tables shall be next; then formal languages; then figures; and then any other language forms.~~ document's usage.

3 Normative references 🔗

The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.

HTML Standard , Living Standard. url: https://html.spec.whatwg.org/multipage/
IETF RFC 7405 , Case-Sensitive String Support in ABNF. url: https://datatracker.ietf.org/doc/html/rfc7405
IETF RFC 3986 , Uniform Resource Identifier (URI): Generic Syntax. url: https://www.rfc-editor.org/rfc/rfc3986

5 General 🔗

5.1 URI 🔗

URI syntax is specified using the grammar specified at IETF RFC 7405 .

Trailing slashes are significant in URIs.

EXAMPLE 1 —⁠ The URI https://pub.smpte.org/doc/st428-12/latest/ is not equivalent to the URI https://pub.smpte.org/doc/st428-12/latest.

The path component of a URI is case-sensitive.

EXAMPLE 2 —⁠ The URI https://pub.smpte.org/doc/st428-12/latest/ is not equivalent to the URI https://pub.smpte.org/doc/st428-12/LATEST/.

Unless specified otherwise, an HTTPS GET request to a URI shall offer to return an HTML document ( text/html ) and may offer return other media types.

Unless specified otherwise, if a URI resolves to a specific version of a document and the main element of the version is only available as a PDF document, then the HTML document embeds the PDF document.

5.2 HTML 🔗

HTML documents shall conform to HTML Standard .

5.3 Publication prefix 🔗

The following prefix string is used by URI definitions:

prefix
=
"https://pub.smpte.org"

6 Most recent version of a document 🔗

The latest-version URI resolves to the most recent version of the standard document whose short name is document-short-name.

latest-version
=
prefix
%s"/latest/"
document-short-name
"/"

EXAMPLE —⁠ https://pub.smpte.org/latest/st429-2/

7 Most recent publication version of a document 🔗

The latest-pub URI resolves to the most recent publication version of the standard document whose short name is document-short-name.

latest-pub
=
prefix
%s"/pub/"
document-short-name
"/"

EXAMPLE —⁠ https://pub.smpte.org/pub/st429-2/

9 All versions of a document 🔗

The all-versions URI resolves to a resource that lists all versions of the standard document whose short name is document-short-name.

all-versions
=
prefix
%s"/doc/"
document-short-name
"/"

EXAMPLE —⁠ https://pub.smpte.org/doc/st429-2/

10 All documents with the same root number 🔗

The all-parts URI resolves to a resource that lists all documents whose root number is root-number.

all-parts
=
prefix
%s"/doc/"
root-number
"/"

EXAMPLE —⁠ https://pub.smpte.org/doc/429/

11 Specific version of a document 🔗

The specific-version URI resolves to the specific version version-short-name of the document whose short name is document-short-name.

specific-version
=
prefix
%s"/doc/"
document-short-name
"/"
version-short-name
"/"

EXAMPLE —⁠ https://pub.smpte.org/doc/st429-2/20230716-cd/

12 Package of a specific version of a document 🔗

The specific-version-package URI resolves to a single archive file that contains all files that comprise the specific version version-short-name of the document whose short name is document-short-name.

specific-version-package
=
prefix
%s"/package/"
document-short-name
"/"
version-short-name
"/"

EXAMPLE —⁠ https://pub.smpte.org/package/st429-2/20230716-cd/

An HTTPS GET request to the specific-version-package URI shall offer to return an ZIP archive document ( application/zip ) and may offer return other media types.