Menu
▾
▴
[aaf-commits] AAF/Utilities/AAFAnalyzer/Doc EditProtocolTests_Assumptions_and_Issues.txt,1.14,1.15 assumptions_and_issues_in_context.txt,1.13,1.14
|
From: Andrew K. <aja...@us...> - 2005-12-14 22:02:42
|
Update of /cvsroot/aaf/AAF/Utilities/AAFAnalyzer/Doc In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv1300/Doc Modified Files: EditProtocolTests_Assumptions_and_Issues.txt assumptions_and_issues_in_context.txt Log Message: Categorized Issues - Fixed spelling/formatting Index: EditProtocolTests_Assumptions_and_Issues.txt =================================================================== RCS file: /cvsroot/aaf/AAF/Utilities/AAFAnalyzer/Doc/EditProtocolTests_Assumptions_and_Issues.txt,v retrieving revision 1.14 retrieving revision 1.15 diff -C2 -d -r1.14 -r1.15 *** EditProtocolTests_Assumptions_and_Issues.txt 14 Dec 2005 17:25:59 -0000 1.14 --- EditProtocolTests_Assumptions_and_Issues.txt 14 Dec 2005 22:02:31 -0000 1.15 *************** *** 6,9 **** --- 6,10 ---- available, REQ_EP_063 is being used to specify an invalid reference from a file source. + (Requirements Elaboration) 2. REQ_EP_063 only deals with references to import, tape and film sources, not *************** *** 12,15 **** --- 13,17 ---- REQ_EP_063 is being used to specify that a reference from a file source to another file source is valid. + (Requirements Elaboration) 3. REQ_EP_064 states "if a file source does not have one of the above sources, *************** *** 19,22 **** --- 21,25 ---- being interpreted as an if and only if, therefore, a file source may have a(n) file/import/tape/file source as well as a recording source. + (Assumption Validation) 4. The Edit Protocol does not specify what types of references an import *************** *** 27,30 **** --- 30,34 ---- requirement is available, REQ_EP_076 is being used to specify an invalid reference from an import source. + (Requirements Elaboration) 5. The Edit Protocol does not specify what type of references a tape source is *************** *** 34,37 **** --- 38,42 ---- more appropriate requirement is available, REQ_EP_083 is being used to specify an invalid reference from a tape source. + (Requirements Elaboration) 6. The Edit Protocol does not specify what type of references a film source is *************** *** 39,42 **** --- 44,48 ---- requirements will appear to have passed if a film source is not the end of the derivation chain. + (Requirements Elaboration) 7. Currently a test will fail if a CompositionMob does not have a UsageCode *************** *** 46,49 **** --- 52,56 ---- A possible solution is to fail the requirement that specifies acceptable references out of the "current node." + (Assumption Validation - Requiremetns Elaboration) 8. Currently a test will fail if a CompositionMob or a MasterMob has an *************** *** 53,56 **** --- 60,64 ---- pass. A possible solution is to fail the requirement that specifies acceptable references out of the "current node." + (Assumption Validation - Requiremetns Elaboration) 9. Currently a test will fail if a SourceMob has no descriptor. However, the *************** *** 59,62 **** --- 67,71 ---- possible solution is to fail the requirement that specifies acceptable references out of the "current node." + (Assumption Validation - Requiremetns Elaboration) 10. Currently a test will fail if a SourceMob has an "invalid" descriptor (ie. *************** *** 65,68 **** --- 74,78 ---- requirements will appear to pass. A possible solution is to fail the requirement that specifies acceptable references out of the "current node." + (Assumption Validation - Requiremetns Elaboration) 11. Currently a test will fail if a SourceClip does not have a SourceReference *************** *** 71,74 **** --- 81,85 ---- all requirements will appear to pass. A possible solution is to fail the requirement that specifies acceptable references out of the "current node." + (Assumption Validation - Requiremetns Elaboration) 12. Tests will currently fail if the first "node" in the derivation chain is *************** *** 81,84 **** --- 92,96 ---- will be considered as the first "node" in a derivation chain. Unreferenced SourceMobs, MasterMobs and SourceClips will never be tested. + (Assumption Validation - Requiremetns Elaboration) 13. REQ_EP_026, REQ_EP_031, REQ_EP_036 and REQ_EP_045 state that top-level, *************** *** 89,92 **** --- 101,105 ---- these compositions is the end of a chain, the test will fail, however, all requirements will appear to pass. + (Assumption Validation - Requiremetns Elaboration) 14. As was discussed in the conference call on September 26, 2005, REQ_EP_031 *************** *** 96,99 **** --- 109,113 ---- therefore, REQ_EP_031 is used to specify a valid reference from one lower-level composition to another. + (Requirements Elaboration) 15. As was discussed during the conference call on September 26, 2005, the *************** *** 101,104 **** --- 115,119 ---- derivation chain. Until further information is avaliable, the test will assume that it is valid for a clip to be the end of the derivation chain. + (Requirements Elaboration) 16. Requirements REQ_EP_025, REQ_EP_030, DEF_EP_034, DEF_EP_043, DEF_EP_049, *************** *** 112,177 **** CompositionMob with Mob::UsageCode property equal to Usage_AdjustedClip". These requirements can not be tested. 17. REQ_EP_013, REQ_EP_014 and REQ_EP_039 are all classified as file requirements but they seem dependant on an importing or exporting application. 18. REQ_EP_023 and REQ_EP_097 are optional ("MAY") requirements. There is no way they can present a warning or a failure - they are not currently being tested. 19. REQ_EP_028 does not specify if physical track numbers may be repeated. Until further information is avaliable, it is assumed that they can not be repeated. 20. REQ_EP_028 does not specify if reserved physical track numbers are legal values. Until further information is avaliable, it is assumed that they are illegal. 21. REQ_EP_028 does not specify if physical track numbers outside the range 1-6 are legal. Until further information is avaliable, it is assumed that they are illegal. 22. REQ_EP_082 does not specify if physical track numbers may be repeated. Until further information is avaliable, it is assumed that they can not be repeated. 23. REQ_EP_082 does not specify if reserved physical track numbers are legal values. Until further information is avaliable, it is assumed that they are illegal. 24. REQ_EP_082 does not specify if physical track numbers outside the range 1-12 are legal. Until further information is avaliable, it is assumed that they are illegal. 25. REQ_EP_087 does not specify if physical track numbers may be repeated. Until further information is avaliable, it is assumed that they can not be repeated. 26. REQ_EP_087 does not specify if physical track numbers outside the range 1-3 are legal. Until further information is avaliable, it is assumed that they are illegal. 27. Timecode track is not defined. It is assumed to be a MobSlot where IsTimecodeType is true. 28. Edgecode track is not defined. It is assumed to be a MobSlot where IsEdgecodeType is true. ! 29. The legal layout of a derivation chain is not specified in test, only in the diagram. 30. REQ_EP_037 states each essence track of a sub-clip composition shall contain exactly one SourceClip - what about sequences of one SourceClip? Currently, sequences are not accepted. 31. REQ_EP_046 states each essence track of an adjusted-clip composition shall contain exactly one OperationGroup - what about sequence of one OperationGroup? Currently sequences are not accepted. 32. What does REQ_EP_056 mean? ! 33. Essence track is not defined. It is assumed to be a MobSlot that has an ! Sound or Picture DataDefinition. 34. REQ_EP_091 states that the edit rate of an essence track must be equivalent --- 127,210 ---- CompositionMob with Mob::UsageCode property equal to Usage_AdjustedClip". These requirements can not be tested. + (Requirements Change) 17. REQ_EP_013, REQ_EP_014 and REQ_EP_039 are all classified as file requirements but they seem dependant on an importing or exporting application. + (XML Change) 18. REQ_EP_023 and REQ_EP_097 are optional ("MAY") requirements. There is no way they can present a warning or a failure - they are not currently being tested. + (Open Question - How do we treat "MAY" requirements) 19. REQ_EP_028 does not specify if physical track numbers may be repeated. Until further information is avaliable, it is assumed that they can not be repeated. + (Assumption Validation - Requiremetns Elaboration) 20. REQ_EP_028 does not specify if reserved physical track numbers are legal values. Until further information is avaliable, it is assumed that they are illegal. + (Assumption Validation - Requiremetns Elaboration) 21. REQ_EP_028 does not specify if physical track numbers outside the range 1-6 are legal. Until further information is avaliable, it is assumed that they are illegal. + (Assumption Validation - Requiremetns Elaboration) 22. REQ_EP_082 does not specify if physical track numbers may be repeated. Until further information is avaliable, it is assumed that they can not be repeated. + (Assumption Validation - Requiremetns Elaboration) 23. REQ_EP_082 does not specify if reserved physical track numbers are legal values. Until further information is avaliable, it is assumed that they are illegal. + (Assumption Validation - Requiremetns Elaboration) 24. REQ_EP_082 does not specify if physical track numbers outside the range 1-12 are legal. Until further information is avaliable, it is assumed that they are illegal. + (Assumption Validation - Requiremetns Elaboration) 25. REQ_EP_087 does not specify if physical track numbers may be repeated. Until further information is avaliable, it is assumed that they can not be repeated. + (Assumption Validation - Requiremetns Elaboration) 26. REQ_EP_087 does not specify if physical track numbers outside the range 1-3 are legal. Until further information is avaliable, it is assumed that they are illegal. + (Assumption Validation - Requiremetns Elaboration) 27. Timecode track is not defined. It is assumed to be a MobSlot where IsTimecodeType is true. + (Assumption Validation - Requiremetns Elaboration) 28. Edgecode track is not defined. It is assumed to be a MobSlot where IsEdgecodeType is true. + (Assumption Validation - Requiremetns Elaboration) ! 29. The legal layout of a derivation chain is not specified in text, only in the diagram. + (Requirements Elaboration) 30. REQ_EP_037 states each essence track of a sub-clip composition shall contain exactly one SourceClip - what about sequences of one SourceClip? Currently, sequences are not accepted. + (Assumption Validation - Requiremetns Elaboration) 31. REQ_EP_046 states each essence track of an adjusted-clip composition shall contain exactly one OperationGroup - what about sequence of one OperationGroup? Currently sequences are not accepted. + (Assumption Validation - Requiremetns Elaboration) 32. What does REQ_EP_056 mean? + (Requirements Clarification) ! 33. Essence track is not defined. It is assumed to be a MobSlot where ! IsSoundKind() or IsPictureKind() returns true. ! (Assumption Validation - Requiremetns Elaboration) 34. REQ_EP_091 states that the edit rate of an essence track must be equivalent *************** *** 180,183 **** --- 213,217 ---- a Sound or Picture DataDefinition. How should REQ_EP_091 treat StaticMobSlots? + (Assumption Validation - Requiremetns Elaboration) 35. REQ_EP_061 and REQ_EP_075 require that URIs comply with RFC 2396 and also *************** *** 186,193 **** --- 220,229 ---- conform with RFC 1738 should the test fail? What if in order to comform to RFC 1738 it can not comply with RFC 2396. + (Requirements Clarification) 36. REQ_EP_061 and REQ_EP_075 require that if a NetworkLocator contains a "relative URI, the base URI should be determined from the URI of the AAF file itself." What exactly does this mean? + (Requirements Clarification) 37. REQ_EP_059 says that essence associated with a file SourceMob shall be *************** *** 198,201 **** --- 234,238 ---- assume the only legal values are kAAFContainerDef_External and kAAFContainerDef_AAF. + (Assumption Validation - Requiremetns Elaboration) 38. REQ_EP_060 states there should be a Locator specifying the location of the *************** *** 206,209 **** --- 243,247 ---- or External is not specified), that the test is currently being implemented to accept two differnt locators that will meet these requeirements. + (Assumption Validation - Requiremetns Elaboration) 39. The URI validator that is currently being used does not accept wide *************** *** 211,214 **** --- 249,253 ---- a different URI validator is found, these problems will exist when validating URIs. + (Library Needed) 40. REQ_EP_060 tests if a file exists at the location pointed to by the locator. *************** *** 216,219 **** --- 255,259 ---- Once a URI tool that deals with relative URIs, this can be modified to to allow the path to be absolute or relative. + (Library Needed) 41. The words "valid name" are used throughout the Edit Protocol, but what makes *************** *** 221,224 **** --- 261,265 ---- it is assumed that a name is valid if an AAF Object has a name property that has been set. + (Assumption Validation - Requiremetns Elaboration) 42. REQ_EP_099 and REQ_EP_100 state that the edit rates of audio tracks must *************** *** 230,233 **** --- 271,275 ---- do not have edit rates. Until more information is avaliable, all StaticMobSlots will cause test failures. + (Assumption Validation - Requiremetns Elaboration) 43. The term zero-valued SourceClip object is not defined. For the purpose of *************** *** 235,246 **** --- 277,291 ---- { {0,0,0,0,0,0,0,0,0,0,0,0}, 0, 0, 0, 0, { 0, 0, 0, {0,0,0,0,0,0,0,0} } } = 00000000000000000000000000000000-00000000-0000-0000-0000000000000000. + (Assumption Validation - Requiremetns Elaboration) 44. The term essence track is not defined. For the purpose of this test (REQ_EP_050, REQ_EP_072), it is aussumed to be any SourceClip object along the derivation chain. + (Assumption Validation - Requiremetns Elaboration) 45. How do you acuratley check that a file exists (ie. it is insufficient to check if the file can be open using an ifstream) in a platform independant fashion? + (Coding Needed) 46. REQ_EP_161 can not easily be regression tested as there does not appear to *************** *** 248,251 **** --- 293,297 ---- its initialize method. The initialize method will provide the DefinitionObject with a valid name. + (Regression Test Issue) 47. There is no requirement that specifies when it is legal to end the *************** *** 253,256 **** --- 299,303 ---- detected based upon the diagram in section 6.1. A failure will be reported, but, not requirements will be shown as failing. + (Assumption Validation - Requiremetns Elaboration) 48. Effects are being classified solely based upon their AUIDs, not the rest *************** *** 258,261 **** --- 305,309 ---- states the AUID can only be used for effects matching the definitions specified in section 12. + (Requirements Elaboration) 49. Section 12 uses the phrases "within a Transition object" and "not within *************** *** 263,266 **** --- 311,315 ---- that the direct parent must or must not be a Transition object, however, it is ok if an ancestor higher than a parent is a Transition object. + (Assumption Validation - Requiremetns Elaboration) 50. The URI validator currently being used is libURI *************** *** 268,271 **** --- 317,321 ---- Until a better validator is avaliable, this test will be registered but not run. + (Library Needed) 51. REQ_EP_187 does not specify if the Speed Ratio parameter should be constant *************** *** 273,282 **** --- 323,335 ---- for there to be a ratio value of zero. Tests will fail if it is not constant. + (Assumption Validation - Requiremetns Elaboration) 52. It is assumed that REQ_EP_187 applies only to Speed Ratio Parameters that belong to Video Speed Control effects. + (Assumption Validation - Requiremetns Elaboration) 53. There is no easy way to regression test Speed Ratio parameters for REQ_EP_187. + (Regression Test Issue) 54. Currently, if a test fails or issues a warning, traversal down the current *************** *** 286,310 **** mobs/clips are in the correct place), however, in other cases, it is should be possible to continue testing (ie. any non-structural test). Switching ! the tests to continue along the chain should not effect the regression tests unless noted within the XML files. 55. It is assumed that REQ_EP_131 means that a Primary Timecode mob slot can only have one Timecode object (ie. No sequences and it can not be the child of another segment). 56. REQ_EP_131 refers to Primary Timecode Tracks in Lower-Level compositions. Primary Timecode Tracks are only defined for Top-Level Compositions and Tape Sources. It is assumed that the definition is consistent. 57. REQ_EP_136 says the slots in an Auxiliary SourceMob may be timeline, event ! or static. May implies that this is optional, so any time of slot is legal. If this is not correct, the requirement should be written with a shall in place of the may. 58. Auxiliary SourceMobs are defined in section 9.1.1 and requirements specify what data they can include. However, they do not fit anywhere in the ! derivation chain. This may be correct, but, if it is not, the derivation test will fail when an Auxiliary SourceMob is encountered in the derivation chain. 59. REQ_EP_149 and REQ_EP_150 prevent CommentMarkers from being used in places --- 339,368 ---- mobs/clips are in the correct place), however, in other cases, it is should be possible to continue testing (ie. any non-structural test). Switching ! the tests to continue along the chain should not effect the regression tests unless noted within the XML files. + (Analyzer Structure Issue) 55. It is assumed that REQ_EP_131 means that a Primary Timecode mob slot can only have one Timecode object (ie. No sequences and it can not be the child of another segment). + (Assumption Validation - Requiremetns Elaboration) 56. REQ_EP_131 refers to Primary Timecode Tracks in Lower-Level compositions. Primary Timecode Tracks are only defined for Top-Level Compositions and Tape Sources. It is assumed that the definition is consistent. + (Assumption Validation - Requiremetns Elaboration) 57. REQ_EP_136 says the slots in an Auxiliary SourceMob may be timeline, event ! or static. May implies that this is optional, so any type of slot is legal. If this is not correct, the requirement should be written with a shall in place of the may. + (Requirement Clarification) 58. Auxiliary SourceMobs are defined in section 9.1.1 and requirements specify what data they can include. However, they do not fit anywhere in the ! derivation chain. This may be correct, but, if it is, the derivation test will fail when an Auxiliary SourceMob is encountered in the derivation chain. + (Requirement Clarification) 59. REQ_EP_149 and REQ_EP_150 prevent CommentMarkers from being used in places *************** *** 312,329 **** --- 370,392 ---- refers to the base class and any subclass other than DescriptiveMarker and its subclasses. + (Assumption Validation - Requiremetns Elaboration) 60. REQ_EP_149 referes to annotations not associated with a specific essence track. It is assumed that an annotation is associated with the MobSlot that the component with the annotation is contained within. + (Assumption Validation - Requiremetns Elaboration) 61. It is assumed that for data definition values to be consistent in REQ_EP_162, AxDataDef::IsDataDefOf() must return true. + (Assumption Validation - Requiremetns Elaboration) 62. For REQ_EP_162 it is assumed that a warning should be presented if there is an OperationDefinition in the AAF file that is not referenced. + (Assumption Validation - Requiremetns Elaboration) 63. It is not possible to save an AAF file with an unreferenced OperationDefinition so the warn condition of REQ_EP_162 can not be regression tested. + (Regression Test Issue) 64. When testing REQ_EP_248 and REQ_EP_249 it is assumed that the parent of a *************** *** 331,338 **** --- 394,403 ---- this appears to be a valid assumption, however, should the specification change, the requirements may need to change. + (Assumption Validation - Requiremetns Elaboration) 65. When REQ_EP_248 and REQ_EP_249 state that segments must be specified from the begining/to the end of a Transition, it is assumed that this means the length of the segment must be at least as long as the transition. + (Assumption Validation - Requiremetns Elaboration) 66. REQ_EP_248 and REQ_EP_249 cannot be accuratley regression tested as the *************** *** 342,359 **** --- 407,429 ---- b) Transitions or Segments with no length. c) A Transition with no outgoing segment. + (Regression Test Issue) 67. The conditions tested by REQ_EP_248 are a subset of the conditions tested by REQ_EP_249. REQ_EP_248 is not necessary since when it fails, an identical failure of REQ_EP_249 will be produced. + (Requirements Overlap) 68. REQ_EP_248 and REQ_EP_249 are requirements for Two-Parameter Mono Audio Dissolve effects. There should probably be an analogous requirement for Single Parameter Mono Audio Dissolve effects. + (Missing Requirements) 69. It is assumed that sub-classes of ConstantValue and VaryingValue are legal for REQ_EP_174, but any other sub-class of Parameter is illegal. + (Assumption Validation - Requiremetns Elaboration) 70. There is no easy way to regression test REQ_EP_174 with the current testing framework. + (Regression Test Issue) 71. When building the test graph, it is assumed that properties with a Record *************** *** 367,372 **** --- 437,444 ---- used in this way and if this assumption is incorrect, the AAF Analyzer will throw an exception and terminate before analyzing the file. + (Assumption Validation) 72. Should REQ_EP_012, REQ_EP_062 and REQ_EP_160 be FILE requirements? + (XML Change) 73. Currently, error messages attempt to indicate which object in an AAF file *************** *** 377,387 **** --- 449,462 ---- is added, or the -dump functionality is extended, the node id could be very useful in identifying the problem object. + (Analyzer Enhancement) 74. REQ_EP_110 referes to mono and multi-channel sound Data Definitions that do not exist. It is assumed that these refer to sound descriptors with 1 or more than one channels respectively. + (Assumption Validation - Requiremetns Elaboration) 75. It is assumed that REQ_EP_110 means SoundDescriptors with multiple channels cannot occur in the derivation chain after a Composition or MasterMob. + (Assumption Validation - Requiremetns Elaboration) 76. There is not much to be tested for REQ_EP_108. Currently it is being used *************** *** 389,404 **** TimelineMobSlot::MarkOut properties are present and that the MarkOut point does not occur before the MarkIn point. 77. For REQ_EP_218 it is assumed that the 2nd input to an OpetaionGroup for an Alpha with Video Key Effect must be a Source References to a file SourceMob ! with an RGBADescriptor or a CDCIDescriptor. 78. For REQ_EP_219 it is assumed that the 2nd input to an OpetaionGroup for an Alpha with Video Key Effect must be a Source References to a file SourceMob with a DigitalImageDescriptor. 79. For REQ_EP_223 it is assumed that the 3rd input to an OpetaionGroup for a Separate-Alpha Key Effect must be a Source References to a file SourceMob ! with an RGBADescriptor or a CDCIDescriptor. 80. For REQ_EP_223 it is assumed that the 3rd input to an OpetaionGroup for an --- 464,483 ---- TimelineMobSlot::MarkOut properties are present and that the MarkOut point does not occur before the MarkIn point. + (Assumption Validation - Requiremetns Elaboration) 77. For REQ_EP_218 it is assumed that the 2nd input to an OpetaionGroup for an Alpha with Video Key Effect must be a Source References to a file SourceMob ! with an RGBADescriptor or a CDCIDescriptor. ! (Assumption Validation - Requiremetns Elaboration) 78. For REQ_EP_219 it is assumed that the 2nd input to an OpetaionGroup for an Alpha with Video Key Effect must be a Source References to a file SourceMob with a DigitalImageDescriptor. + (Assumption Validation - Requiremetns Elaboration) 79. For REQ_EP_223 it is assumed that the 3rd input to an OpetaionGroup for a Separate-Alpha Key Effect must be a Source References to a file SourceMob ! with an RGBADescriptor or a CDCIDescriptor. ! (Assumption Validation - Requiremetns Elaboration) 80. For REQ_EP_223 it is assumed that the 3rd input to an OpetaionGroup for an *************** *** 409,464 **** by the essence descriptor. Until clarification is provided, this will not be tested. 82. In REQ_EP_223, it is not known how to test if the alpha channel is indicated by the essence descriptor or how to find the luminance calue of the essence. Until clarification is provided, this will not be tested. 83. REQ_EP_150 states CommentMarkers shall be placed only in EventMobSlots. It is assumed that this means, the component with the CommentMarker (or the CommentMarker) must be contained within an EventMobSlot. 84. What should be tested for REQ_EP_111? 85. REQ_EP_112, REQ_EP_113, REQ_EP_114 and REQ_EP_115 refer to multi-channel tracks and mono tracks. Tracks do not have channels, this needs to be clarified. 86. REQ_EP_110 and REQ_EP_112 refer to multi-channel sound Data Definitions. This Data Definition does not exist and must be clarified. 87. What should be tested for REQ_EP_116? 88. Should there be any requirements about the StillFrame property for REQ_EP_121? 89. For DEF_EP_129 should TimecodeStream12M objects be validated? 90. REQ_EP_138 is confusing because nothing has to be done to comply with the Edit Protocol. The requirement is the same as the general AAF Object Specification requirement but applied to an auxiliary file. 91. Should REQ_EP_143 be tested? 92. Is there a representation of a nested group other than the one in REQ_EP_172 that should be rejected? 93. For REQ_EP_178, how is it checked that inputs are VH normalized to the first video input. Also, where can it be stated to do otherwise? ! 94. Tracks/MobSlots do not have data definitions. What types of objects can ! legaly have these definitions? 95. REQ_EP_163 and REQ_EP_164 are redundant as they only fail when more specific versions of the requirement fail. 96. Under the current regression testing system there is no way to save an AAF file as anything other than version 1.1, so the warn condition of REQ_EP_163 is not tested, nor are all of the pass conditions. 97. There are 4 ways the derivation chain test can fail that are not associated with requirements. 98. Should StaticMobSlots be allowed in derivation chains, if so, what do they mean? 99. Currently, references from TimelineMobSlots to TimelineMobSlots and --- 488,561 ---- by the essence descriptor. Until clarification is provided, this will not be tested. + (Requirements Elaboration) 82. In REQ_EP_223, it is not known how to test if the alpha channel is indicated by the essence descriptor or how to find the luminance calue of the essence. Until clarification is provided, this will not be tested. + (Requirements Elaboration) 83. REQ_EP_150 states CommentMarkers shall be placed only in EventMobSlots. It is assumed that this means, the component with the CommentMarker (or the CommentMarker) must be contained within an EventMobSlot. + (Assumption Validation - Requiremetns Elaboration) 84. What should be tested for REQ_EP_111? + (Requirement Clarification) 85. REQ_EP_112, REQ_EP_113, REQ_EP_114 and REQ_EP_115 refer to multi-channel tracks and mono tracks. Tracks do not have channels, this needs to be clarified. + (Requirement Clarification) 86. REQ_EP_110 and REQ_EP_112 refer to multi-channel sound Data Definitions. This Data Definition does not exist and must be clarified. + (Requirement Clarification) 87. What should be tested for REQ_EP_116? + (Requirement Clarification) 88. Should there be any requirements about the StillFrame property for REQ_EP_121? + (Missing Requirement) 89. For DEF_EP_129 should TimecodeStream12M objects be validated? + (Requirement Elaboration) 90. REQ_EP_138 is confusing because nothing has to be done to comply with the Edit Protocol. The requirement is the same as the general AAF Object Specification requirement but applied to an auxiliary file. + (Unnecessary Requirement) 91. Should REQ_EP_143 be tested? + (Requirement Clarification) 92. Is there a representation of a nested group other than the one in REQ_EP_172 that should be rejected? + (Requirement Elaboration) 93. For REQ_EP_178, how is it checked that inputs are VH normalized to the first video input. Also, where can it be stated to do otherwise? + (Requirement Elaboration) ! 94. For REQ_EP_148 Tracks/MobSlots do not have data definitions. What types of ! objects can legaly have these definitions? ! (Requirement Clarification) 95. REQ_EP_163 and REQ_EP_164 are redundant as they only fail when more specific versions of the requirement fail. + (Redundant Requirements) 96. Under the current regression testing system there is no way to save an AAF file as anything other than version 1.1, so the warn condition of REQ_EP_163 is not tested, nor are all of the pass conditions. + (Regression Test Issue) 97. There are 4 ways the derivation chain test can fail that are not associated with requirements. + (Missing Requirements) 98. Should StaticMobSlots be allowed in derivation chains, if so, what do they mean? + (Requirements Elaboration) 99. Currently, references from TimelineMobSlots to TimelineMobSlots and *************** *** 503,506 **** --- 600,604 ---- implemented visit AAFComponentReference Edges, so changes will not effect the currently implemented test set. + (Analyzer Structure - SDK Issues) 100. In the AAF SDK, when a Component is added to a Sequence, the Length of the *************** *** 509,511 **** Sequence is not updated. It is probably true that when the length of any Component is updated, its parent Sequence's Length property is not updated. ! This may be known and intended, but, it may not. \ No newline at end of file --- 607,610 ---- Sequence is not updated. It is probably true that when the length of any Component is updated, its parent Sequence's Length property is not updated. ! This may be known and intended, but, it may not. ! (SDK Issues) \ No newline at end of file Index: assumptions_and_issues_in_context.txt =================================================================== RCS file: /cvsroot/aaf/AAF/Utilities/AAFAnalyzer/Doc/assumptions_and_issues_in_context.txt,v retrieving revision 1.13 retrieving revision 1.14 diff -C2 -d -r1.13 -r1.14 *** assumptions_and_issues_in_context.txt 14 Dec 2005 20:59:22 -0000 1.13 --- assumptions_and_issues_in_context.txt 14 Dec 2005 22:02:31 -0000 1.14 *************** *** 55,60 **** NONE Issues: ! 33. Essence track is not defined. It is assumed to be a MobSlot that has a ! Sound or Picture DataDefinition. 42. REQ_EP_099 and REQ_EP_100 state that the edit rates of audio tracks must --- 55,60 ---- NONE Issues: ! 33. Essence track is not defined. It is assumed to be a MobSlot where ! IsSoundKind() or IsPictureKind() returns true. 42. REQ_EP_099 and REQ_EP_100 state that the edit rates of audio tracks must *************** *** 62,66 **** or equal to the sample rate respectively. Currently, it is assumed that an audio track is a mob slot where IsSoundKind() is true that contains a ! File Source mob and a video track is a mob slot where IsPictureKind() is true that contains a File Source mob. This includes StaticMobSlots, which do not have edit rates. Until more information is avaliable, all --- 62,66 ---- or equal to the sample rate respectively. Currently, it is assumed that an audio track is a mob slot where IsSoundKind() is true that contains a ! File Source mob and a video track is a mob slot where IsPictureKind() is true that contains a File Source mob. This includes StaticMobSlots, which do not have edit rates. Until more information is avaliable, all *************** *** 284,288 **** assume that it is valid for a clip to be the end of the derivation chain. ! 29. The legal layout of a derivation chain is not specified in test, only in the diagram. --- 284,288 ---- assume that it is valid for a clip to be the end of the derivation chain. ! 29. The legal layout of a derivation chain is not specified in text, only in the diagram. *************** *** 305,309 **** 58. Auxiliary SourceMobs are defined in section 9.1.1 and requirements specify what data they can include. However, they do not fit anywhere in the ! derivation chain. This may be correct, but, if it is not, the derivation test will fail when an Auxiliary SourceMob is encountered in the derivation chain. --- 305,309 ---- 58. Auxiliary SourceMobs are defined in section 9.1.1 and requirements specify what data they can include. However, they do not fit anywhere in the ! derivation chain. This may be correct, but, if it is, the derivation test will fail when an Auxiliary SourceMob is encountered in the derivation chain. *************** *** 505,509 **** 57. REQ_EP_136 says the slots in an Auxiliary SourceMob may be timeline, event ! or static. May implies that this is optional, so any time of slot is legal. If this is not correct, the requirement should be written with a shall in place of the may. --- 505,509 ---- 57. REQ_EP_136 says the slots in an Auxiliary SourceMob may be timeline, event ! or static. May implies that this is optional, so any type of slot is legal. If this is not correct, the requirement should be written with a shall in place of the may. *************** *** 932,936 **** 79. For REQ_EP_223 it is assumed that the 3rd input to an OpetaionGroup for a Separate-Alpha Key Effect must be a Source References to a file SourceMob ! with an RGBADescriptor or a CDCIDescriptor. 80. For REQ_EP_223 it is assumed that the 3rd input to an OpetaionGroup for an --- 932,936 ---- 79. For REQ_EP_223 it is assumed that the 3rd input to an OpetaionGroup for a Separate-Alpha Key Effect must be a Source References to a file SourceMob ! with an RGBADescriptor or a CDCIDescriptor. 80. For REQ_EP_223 it is assumed that the 3rd input to an OpetaionGroup for an *************** *** 989,994 **** KLVDataDefinition with the same AUID in the dictionary. Issues: ! 33. Essence track is not defined. It is assumed to be a MobSlot that has a ! Sound or Picture DataDefinition. 59. REQ_EP_149 and REQ_EP_150 prevent CommentMarkers from being used in places --- 989,994 ---- KLVDataDefinition with the same AUID in the dictionary. Issues: ! 33. Essence track is not defined. It is assumed to be a MobSlot where ! IsSoundKind() or IsPictureKind() returns true. 59. REQ_EP_149 and REQ_EP_150 prevent CommentMarkers from being used in places *************** *** 1386,1391 **** DataDef_DescriptiveMetadata. Issue: ! 94. Tracks/MobSlots do not have data definitions. What types of objects can ! legaly have these definitions? Requirements: --- 1386,1391 ---- DataDef_DescriptiveMetadata. Issue: ! 94. For REQ_EP_148 Tracks/MobSlots do not have data definitions. What types of ! objects can legaly have these definitions? Requirements: |