ETSI ES 203 119-3-2016 Methods for Testing and Specification(MTS) The Test Description Language (TDL) Part 3 Exchange Format (V1 2 1)《试验和规范方法(MTS) 试验描述语言(TDL) 第3部分 交换格式(V1 2 1)》.pdf

1、 ETSI ES 203 119-3 V1.2.1 (2016-09) Methods for Testing and Specification(MTS); The Test Description Language (TDL); Part 3: Exchange Format ETSI STANDARD ETSI ETSI ES 203 119-3 V1.2.1 (2016-09)2Reference RES/MTS-203119-3v1.2.1 Keywords language, MBT, methodology, testing, TSS Essential, or potentia

2、lly Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No gu

3、arantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This ETSI Standard (ES) has been produced by ETSI Technical Committee Methods for Testing

4、and Specification (MTS). The present document is part 3 of a multi-part deliverable. Full details of the entire series can be found in part 1 1. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are

5、 to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI ES 203 119-3 V1.2.1 (2016-09)51 Scope The present document specifies the

6、 exchange format of the Test Description Language (TDL) in the form of an XML Schema derived from the TDL meta-model 1. The intended use of the present document is to serve as the specification of the format used for exchange of model instances and tool interoperability between TDL-compliant tools.

7、2 References 2.1 Normative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (includ

8、ing any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term v

9、alidity. The following referenced documents are necessary for the application of the present document. 1 ETSI ES 203 119-1 (V1.3.1): “Methods for Testing and Specification (MTS); The Test Description Language (TDL); Part 1: Abstract Syntax and Associated Semantics“. 2 OMG: “OMG Meta Object FacilityT

10、M(MOF) Core Specification“, Version 2.4.2, formal/2014-04-03. NOTE: Available at http:/www.omg.org/spec/MOF/2.4.2/. 3 OMG: “OMG XML Metadata InterchangeTM(XMI) Specification“, Version 2.4.2, formal/2014-04-04. NOTE: Available at http:/www.omg.org/spec/XMI/2.4.2/. 4 W3C Recommendation 26 November 200

11、8: “Extensible Markup Language (XML) 1.0 (Fifth Edition)“. NOTE: Available at http:/www.w3.org/TR/REC-xml/. 5 Recommendation ITU-T X.667: “Information technology - Procedures for the operation of object identifier registration authorities: Generation of universally unique identifiers and their use i

12、n object identifiers“. 2.2 Informative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference docu

13、ment (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user

14、 with regard to a particular subject area. Not applicable. ETSI ETSI ES 203 119-3 V1.2.1 (2016-09)63 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: TDL XMI document: XMI document that represents the serialization of

15、a TDL model TDL XMI Schema: XMI Schema that describes valid TDL XMI documents XMI document: XML document that represents the serialization of a MOF model XMI Schema: XML Schema definition that describes valid XMI documents 3.2 Abbreviations For the purposes of the present document, the following abb

16、reviations apply: EBNF Extended Backus-Naur Form MOF Meta-Object Facility TDL Test Description Language URI Uniform Resource Identifier UUID Universal Unique Identifier XMI XML Metadata Interchange XML eXtensible Markup LanguageXSD XML Schema Definition 4 Basic principles 4.1 Introduction XMI is the

17、 serialization format for persistence and interchange of TDL models. XMI stands for XML Metadata Interchange and describes a unified way to serialize, persist, exchange and de-serialize MOF-based models 2. The XMI specification 3 describes both production rules to create an XMI Schema and an XMI doc

18、ument for a MOF model. The present document describes the production rules for both a TDL XMI Schema according to the TDL meta-model definition and TDL XMI documents for the serialization of TDL models. A TDL XMI Schema is useful to validate whether a TDL XMI document complies with the serialization

19、 rules specified in the present document. A complete validation of the represented TDL model cannot be performed solely with the TDL XMI Schema due to additional semantics introduced by MOF and XMI compared to XML Schema. Validation of TDL XMI documents shall be done in a two-step approach: Lexical

20、(syntactical) validation based on the TDL XMI Schema: This validation step assures that XMI documents abide by the serialization rules for TDL models as described by the present document. Semantical validation based on the TDL meta-model definition: While deserializing TDL XMI documents, the modelli

21、ng tool shall perform semantics checks based on the specification of the TDL meta-model and the additional XMI information. The lexical validation is optional, since it only serves the purpose of syntactically assuring that a TDL XMI document is valid in terms of structure. Semantical validation is

22、always required to ensure that the XMI document is a valid serialization of a TDL model. Due to the nature of the lexical validation, it is possible to produce valid TDL XMI documents with respect to the TDL XMI Schema but invalid TDL XMI documents with respect to the TDL meta-model specification. E

23、TSI ETSI ES 203 119-3 V1.2.1 (2016-09)74.2 Document Structure The present document defines the exchange format for TDL model instances by means of a TDL XMI schema. The document is structured as follows: Clause 5 “TDL XMI Schema“ describes the rules that are applied for the production of a valid TDL

24、 XMI Schema according to TDL meta-model. Clause 6 “TDL XMI Document Serialization“ describes the production rules that shall be applied when serializing TDL models. This clause contains a number of examples to comprehensibly illustrate the serialization of various TDL elements. Annex A specifies the

25、 canonical TDL XMI Schema based on the current TDL meta-model specification 1. 4.3 Notational Conventions For the scope of the present document, the following notational conventions apply: Elements from the TDL meta-model or MOF model or XMI model are typeset in italic, e.g. the property is Optional

26、 of Member has the default value false. Elements from XML or XML Schema are typeset in the monospaced font Courier, e.g. the complexType declaration. 4.4 Conformance TDL XMI documents shall be valid and well formed as defined by the XML recommendation 4. TDL XMI documents shall be syntactically vali

27、d according the TDL XMI Schema described in the present document. TDL XMI documents shall be semantically valid according the TDL meta-model specification. 5 TDL XMI Schema 5.1 TDL XMI Schema Production Rules 5.1.1 Overview The TDL XMI Schema production rules refine the general XMI Schema derivation

28、 rules 3. The TDL XMI Schema production rules unify the way in which TDL XMI documents shall be represented. Since XMI is more expressive than XML Schema in some parts which are relevant for MOF-based models, the following rules clarify how a TDL XMI Schema copes with the higher expressiveness of XM

29、I compared to XML Schema: Multiple inheritance: Multiple inheritance is not required for the TDL XMI Schema. Identification: Element identification is based on the XMI attribute ID as specified in the XMI specification 3. The value of an elements ID shall be derived according to the algorithm for ge

30、nerating universally unique identifier (UUID) specified in Recommendation ITU-T X.667 5. Differences: TDL XMI Schema does not support the XMI elements Difference, Add, Replace, Delete. Bidirectionality: Bidirectional associations (i.e. association ends that have an opposite association end that can

31、be directly navigated from each other) are resolved into two associations. The TDL XMI Schema described in the present document should not be used for the generation of the MOF-based TDL meta-model. ETSI ETSI ES 203 119-3 V1.2.1 (2016-09)8The structure of the TDL XMI Schema document complies with th

32、e XMI specification and contains the following concepts: An XML version processing instruction with an encoding character set information, e.g. . Any other valid XML processing instructions. An XML schema element, i.e. the root of the XML Schema document. An import XML element for the XMI namespace.

33、 Any other valid import XML elements to other referenced XML Schema documents. Declarations of concepts for the TDL meta-model. 5.1.2 TDL metaclass Element The TDL XMI Schema element (root element of the TDL XMI Schema definition) has to comply with the following rules: The namespace declaration of

34、XML Schema shall be present and set to xsd=“http:/www.w3.org/2001/XMLSchema“ The namespace declaration of XMI shall be present and set to xmi=“http:/www.omg.org/spec/XMI/20100901“ The namespace declaration of the TDL meta-model shall be present and set to tdl=“http:/www.etsi.org/spec/TDL/1.3.1“ The

35、target namespace declaration shall be the same as the namespace declaration for the TDL meta-model 5.1.3 Import statements For the definition of import statements, the following rules shall be applied: An import of the fixed declarations that are mandatory for every XMI schema shall be given as firs

36、t import statement after the XMI Schema element. These declarations are in the namespace http:/www.omg.org/spec/XMI/20100901. For further information about the fixed declarations of the XMI schema element, please refer to the XMI specification 3, clause “XMI Document and Schema Design Principles“. I

37、mport elements for other XML Schema documents are allowed as long as they do not contradict with the concepts provided by the TDL meta-model or rules specified for the TDL XMI Schema document. 5.1.4 Representation of the TDL meta-model The declaration of the concepts contained in the TDL meta-model

38、shall comply with the following rules: Metaclasses are represented as a combination of the XML Schema elements complexType and element where complexType specifies the metaclass structure and element its concrete use in a certain situation. The use of element is required for expressing containment re

39、lationships. Abstract metaclasses are represented similar to concrete metaclasses, but with abstract=“true“ set in the complexType declaration. Enumerations are represented as XML Schema simpleType elements. A restriction is used with base set to XML Schema xsd:NCName. ETSI ETSI ES 203 119-3 V1.2.1

40、(2016-09)9 Metaclass properties in general represent properties that are typed by MOF primitive types (e.g. String, Integer, etc.), TDL enumerations, or TDL metaclasses. They are either represented as an XML Schema element or attribute, depending on the multiplicity of the metaclass property, the ty

41、pe of the metaclass property, and whether the type of property is contained within in the same XMI file as the property or not. In either case, the name shall be set to the propertys name. The type shall be set to the XML Schema type declaration corresponding to the propertys type. Metaclass propert

42、ies that refer to metaclasses in a different XMI file are always serialized as nested elements. These properties are represented as XML schema elements element. Such an element declaration is embedded in a choice model group with minOccurs=“0“ and maxOccurs=“unbounded“ attributes within the complexT

43、ype declaration representing the containing metaclass of the property. Metaclass properties of simple type represent properties that are typed by MOF primitive types (e.g. String, Integer etc.) or TDL enumerations. They are represented either as an XML Schema element or attribute, depending on the m

44、ultiplicity of the metaclass property. The MOF primitive type to XML Schema simple type mapping is defined as follows: - MOF:String - xsd:string - MOF:Integer - xsd:integer - MOF:Boolean - xsd:Boolean - MOF:Real - xsd:decimal Metaclass properties of simple type with an upper bound of 1 are represent

45、ed as attribute elements of the complexType declaration representing the propertys containing metaclass. If the lower value of the metaclass property is 1 (i.e. the property value is mandatory), the attributes attribute use=“required“ shall be set. Metaclass properties of simple type with an upper b

46、ound greater than 1 are represented as element elements. Such element declarations are embedded in a choice model group with minOccurs=“0“ and maxOccurs=“unbounded“ attributes within the complexType declaration representing the containing metaclass of the property. Mixed use of both an attribute and

47、 an element elements for the same metaclass property is not permitted. Metaclass properties of metaclass type composing metaclasses represent properties of a TDL metaclass that are typed by another TDL metaclass with compositional relationship among those metaclasses. These properties are represente

48、d as XML schema element elements. Such element declarations are embedded in a choice model group with minOccurs=“0“ and maxOccurs=“unbounded“ attributes within the complexType declaration representing the containing metaclass of the property. Metaclass properties of metaclass type referencing metacl

49、asses represent properties of a metaclass that are typed by another TDL metaclass with a non-compositional relationship among those metaclasses. These properties are represented as XML Schema attribute elements, or element elements if the referenced metaclass is contained in a different XMI file. The type attribute shall be set to xsd:string in case of attribute elements, and to the complexType declaration in case of element elements. Referencing attributes that represent collec