|
39 | 39 | Organization {#organization} |
40 | 40 | ============================ |
41 | 41 |
|
42 | | -This registry maintains a mapping between codec strings and registration |
| 42 | +This registry maintains a mapping between <a>codec strings</a> and registration |
43 | 43 | specifications as described below. |
44 | 44 |
|
45 | 45 | Registration Entry Requirements {#registration-entry-requirements} |
46 | 46 | ================================================================== |
47 | 47 |
|
48 | | -1. Each entry must include a unique codec string, a common name string, and a |
| 48 | +1. Each entry must include a unique <a>codec string</a>, a common name string, and a |
49 | 49 | link to the codec's specification. |
50 | | -2. The codec string must be crafted as follows: |
51 | | - 1. If the codec string contains a fixed prefix with variable suffix values, |
| 50 | +2. The <a>codec string</a> must be crafted as follows: |
| 51 | + 1. If the <a>codec string</a> contains a fixed prefix with variable suffix values, |
52 | 52 | the suffix must be represented by an asterisk and the registration's |
53 | 53 | public specification must describe how to fully qualify the variable |
54 | 54 | portion of the string. |
|
79 | 79 | The registry editors will review and merge the pull request. |
80 | 80 | 6. Existing entries cannot be deleted or deprecated. They may be changed after |
81 | 81 | being published through the same process as candidate entries. Possible |
82 | | - changes include expansion of the codec string to better qualify the codec, |
| 82 | + changes include expansion of the <a>codec string</a> to better qualify the codec, |
83 | 83 | adjustments to the codec name string, and modification of the link to the |
84 | 84 | codec's specification. |
85 | 85 |
|
|
0 commit comments