The Abstract Test Suite (ATS) defined by this I-ETS complies with the international standards on conformance testing (ISO 9646-1 [4]@ ISO 9646-2 [5]@ ISO 9646-3 [6] and ISO 9646-5 [7]). Results of the joint EWOS/ETSI Project Team No.5 on Open Systems Interconnection (OSI) conformance testing in Europe Project are also taken into account. The ATS defined by this I-ETS is applicable to Videotex terminals which make use of the Syntax-based Videotex (SBV) protocol as defined by draft prETS 300 223 [2] or ETS 300 079 [3]). NOTE 1: At the time of producing this I-ETS@ ETS 300 079 [3] contains both the SBV protocol definition and the use of that protocol over an ISDN DTE/DTE connection. In case of an ETS 300 079[3] based terminal@ tests for layers other than layer 7 are outside the scope of this ETS. The chosen test method for this ATS ensures that all SBV terminals can be tested without any additional requirement other than those resulting from the protocol standard itself. NOTE 2: The scope of testing is currently restricted to protocol testing where protocol is understood in the way described in IS 7498 [16]. Extension of the scope might require other test methods. (see also subclause 5.1 and (informative) Annex K) These cases are fully specified for those situations in which an SBV terminal acts as a Terminal Function (TF) (cf. subclause 6.2 of draft prETS 300 233 [2] r ETS 300 079 [3]). NOTE 3: This situation@ in which the SBV terminal acts as a Terminal Function@ covers the following cases : when the communication is established by the terminal itself (without having the reverse_role_assignmetn parameter present in the Establish PDU)@ or when the terminal is called by an SBV service or another SBV terminal with this parameter present. For those situations in which an SBV terminal behaves like an Access Function (AF) (cf. subclause 6.2 of draft prETS 300 223 [2] or ETS 300 079[3])@ only the test purposes are given by this I-ETS. NOTE 4: This situation occurs when a called SBV terminal accepts an incoming Establish request@ on which the reverse_role_assignment parameter is not present. This is generally used in case of terminal-to-terminal communication.