Added references to feature files

testing/SPEC-CONFORMANCE.md

@@ -7,7 +7,7 @@ The conformance requirements for EBU-TT Part 3 derive from the specification its
 |ID|Section|Statement|Feature file path and Scenario name|
 |---|---|---|---|---|
 | | **Tech3370**| | |
-| R1|2.2|When presenting a sequence of documents, at each moment in time exactly zero or one document shall be active.| |
+| R1|2.2|When presenting a sequence of documents, at each moment in time exactly zero or one document shall be active.|`/bdd/features/timing/resolved_times.feature`|
 | R2|2.2 |If no document is active, or if a document with no content is active, no content shall be displayed. | |
 | R3|2.2 |Sequences shall be considered distinct if they have had processing applied, even if the result of that processing is no change other than a known difference in state, for example if the processing has checked the spelling of the text content.| |
 | R4|2.2 |Every distinct sequence shall have a unique sequence identifier.| |
@@ -19,9 +19,9 @@ The conformance requirements for EBU-TT Part 3 derive from the specification its
 |R10|2.2 |Every document in a sequence shall be valid and self-contained.| |
 |R11|2.2 |Every document in a sequence shall have an identical timing model as defined by using the same values for the `ttp:timeBase` and `ttp:clockMode` attributes. ~~(Note issue to add `frameRate`, `frameRateMultiplier` and `dropMode` to this attribute set)~~ SMPTE Deprecated.|`bdd/features/validation/sequence\_identical\_timing\_model.feature` `(Not) compatible document`|
 |R12|2.2 |A passive node shall NOT modify input sequences and shall only emit sequences that are identical (including the sequence numbers) to the input sequence(s)| |
-|R13|2.2 |At any moment in the presentation of a sequence by a node exactly zero or one document shall be temporally active.| |
-|R14|2.3.1|At any single moment in time during the presentation of a sequence either zero documents or one document shall be active.| |
-|R15|2.3.1 |The period during which a document is active begins at the document resolved begin time and ends at the document resolved end time.| |
+|R13|2.2 |At any moment in the presentation of a sequence by a node exactly zero or one document shall be temporally active.|`/bdd/features/timing/resolved_times.feature`|
+|R14|2.3.1|At any single moment in time during the presentation of a sequence either zero documents or one document shall be active.|`/bdd/features/timing/resolved_times.feature`|
+|R15|2.3.1 |The period during which a document is active begins at the document resolved begin time and ends at the document resolved end time.|`/bdd/features/timing/resolved_times.feature`|
 |R16|2.3.1.1|The document resolved begin time shall be the later of (a) the document availability time, (b) the earliest computed begin time in the document and (c) any externally specified document activation begin time, such as the beginning of sequence presentation.|`bdd/features/timing/resolved\_times.feature`|
 |R17|2.3.1.2|The document resolved end time shall be the earlier of (a) the earliest document resolved begin time of all available documents in the sequence with a greater sequence number, (b) the document resolved begin time plus the value of the `dur` attribute, if and only if the `dur` attribute is present, (c) the latest computed end time in the document and (d) any externally specified document deactivation time, such as the end of sequence presentation.|`bdd/features/timing/resolved\_times.feature`|
 |R18|2.3.1.3|When no document is active a presentation processor shall NOT render any content.| |