1、 ETSI ES 203 119-3 V1.3.1 (2018-05) Methods for Testing and Specification (MTS); The Test Description Language (TDL); Part 3: Exchange Format ETSI STANDARD ETSI ETSI ES 203 119-3 V1.3.1 (2018-05)2 Reference RES/MTS-203119-3v1.3.1 Keywords language, MBT, methodology, testing, TSS Essential, or potent
2、ially 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
3、guarantee 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. Trademarks The present document may include trademarks and/or tradenames which are asserted and/o
4、r registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of
5、 products, services or organizations associated with those trademarks. Foreword This ETSI Standard (ES) has been produced by ETSI Technical Committee Methods for Testing and Specification (MTS). The present document is part 3 of a multi-part deliverable. Full details of the entire series can be foun
6、d 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 to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ a
7、nd “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI ES 203 119-3 V1.3.1 (2018-05)5 1 Scope The present document specifies the exchange format of the Test Description Language (TDL) in the form of an XML Schema derived from the TDL meta-model 1. The inten
8、ded 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. NOTE: OMG, UML, OCL and UTP are the trademarks of OMG (Object Management Group). This information is given for the convenience of
9、 users of the present document and does not constitute an endorsement by ETSI of the products named. 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 cit
10、ed version applies. For non-specific references, the latest version of the referenced document (including 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
11、included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. 1 ETSI ES 203 119-1 (V1.4.1): “Methods for Testing and Specification (MTS); The Test Descriptio
12、n Language (TDL); Part 1: Abstract Syntax and Associated Semantics“. 2 OMG: “OMG Meta Object FacilityTM (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, forma
13、l/2014-04-04. NOTE: Available at http:/www.omg.org/spec/XMI/2.4.2/. 4 W3C Recommendation 26 November 2008: “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
14、object identifier registration authorities: Generation of universally unique identifiers and their use in 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 reference
15、s, only the cited version applies. For non-specific references, the latest version of the referenced document (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 re
16、ferenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. ETSI ETSI ES 203 119-3 V1.3.1 (2018-05)6 Not applicable. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the f
17、ollowing terms and definitions apply: TDL XMI document: XMI document that represents the serialization of 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 d
18、escribes valid XMI documents 3.2 Abbreviations For the purposes of the present document, the following abbreviations 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 Intercha
19、nge XML eXtensible Markup LanguageXSD XML Schema Definition 4 Basic principles 4.1 Introduction XMI is the 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-base
20、d models 2. The XMI specification 3 describes both production rules to create an XMI Schema and an XMI document 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
21、 models. A TDL XMI Schema is useful to validate whether a TDL XMI document complies with the serialization 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
22、XMI compared to XML Schema. Validation of TDL XMI documents shall be done in a two-step approach: Lexical (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. Semant
23、ical validation based on the TDL meta-model definition: While deserializing TDL XMI documents, the modelling 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 o
24、f syntactically assuring that a TDL XMI document is valid in terms of structure. Semantical validation is 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 respe
25、ct to the TDL XMI Schema but invalid TDL XMI documents with respect to the TDL meta-model specification. ETSI ETSI ES 203 119-3 V1.3.1 (2018-05)7 4.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 a
26、s follows: Clause 5 “TDL XMI Schema“ describes the rules that are applied for the production of a valid TDL 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 numbe
27、r of examples to comprehensibly illustrate the serialization of various TDL elements. Annex A specifies the 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: Elem
28、ents from the TDL meta-model or MOF model or XMI model are typeset in italic, e.g. the property is Optional 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
29、valid and well formed as defined by the XML recommendation 4. TDL XMI documents shall be syntactically valid 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 P
30、roduction Rules 5.1.1 Overview The TDL XMI Schema production rules refine the general XMI Schema derivation 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 MO
31、F-based models, the following rules clarify how a TDL XMI Schema copes with the higher expressiveness of XMI 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
32、 in the XMI specification 3. The value of an elements ID shall be derived according to the algorithm for generating 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. Bidirect
33、ionality: Bidirectional associations (i.e. association ends that have an opposite association end that can 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-m
34、odel. ETSI ETSI ES 203 119-3 V1.3.1 (2018-05)8 The structure of the TDL XMI Schema document complies with the 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. A
35、n XML schema element, i.e. the root of the XML Schema document. An import XML element for the XMI namespace. 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 ele
36、ment of the TDL XMI Schema definition) has to comply with the following rules: The namespace declaration of 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/XMI“ The namespace declaration
37、of the TDL meta-model shall be present and set to tdl=“http:/www.etsi.org/spec/TDL/1.4.1“ The 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 i
38、mport of the fixed declarations that are mandatory for every XMI schema shall be given as first import statement after the XMI Schema element. These declarations are in the namespace http:/www.omg.org/spec/XMI/20131001. For further information about the fixed declarations of the XMI schema element,
39、please refer to the XMI specification 3, clause “XMI Document and Schema Design Principles“. Import 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 Represe
40、ntation of the TDL meta-model The declaration of the concepts contained in the TDL meta-model 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 con
41、crete use in a certain situation. The use of element is required for expressing containment relationships. 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
42、. A restriction is used with base set to XML Schema xsd:NCName. ETSI ETSI ES 203 119-3 V1.3.1 (2018-05)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 XM
43、L Schema element or attribute, depending on the multiplicity of the metaclass property, the type 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
44、 set to the XML Schema type declaration corresponding to the propertys type. Metaclass properties 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
45、choice model group with minOccurs=“0“ and maxOccurs=“unbounded“ attributes within the complexType 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 enume
46、rations. They are represented either as an XML Schema element or attribute, depending on the multiplicity 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
47、:Real - xsd:decimal Metaclass properties of simple type with an upper bound of 1 are represented 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 attribu
48、tes attribute use=“required“ shall be set. Metaclass properties of simple type with an upper bound 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 declara
49、tion representing the containing metaclass of the property. Mixed use of both an attribute and 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 represented as XML schema element elements. Such element declarations are embedded in a choice m
