ITU-T M 3030-2002 Telecommunications Markup Language (tML) Framework Series M TMN and Network Maintenance International Transmission Systems Telephone Circuits Telegraphy Facsimile.pdf

1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T M.3030TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (08/2002) SERIES M: TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS Telecommunications management network Telecommunicatio

2、ns Markup Language (tML) framework ITU-T Recommendation M.3030 ITU-T M-SERIES RECOMMENDATIONS TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS Introduction and general principles of maintenance and maintenance organization

3、 M.10M.299 International transmission systems M.300M.559 International telephone circuits M.560M.759 Common channel signalling systems M.760M.799 International telegraph systems and phototelegraph transmission M.800M.899 International leased group and supergroup links M.900M.999 International leased

4、 circuits M.1000M.1099 Mobile telecommunication systems and services M.1100M.1199 International public telephone network M.1200M.1299 International data transmission systems M.1300M.1399 Designations and information exchange M.1400M.1999 International transport network M.2000M.2999 Telecommunication

5、s management network M.3000M.3599 Integrated services digital networks M.3600M.3999 Common channel signalling systems M.4000M.4999 For further details, please refer to the list of ITU-T Recommendations. ITU-T Rec. M.3030 (08/2002) i ITU-T Recommendation M.3030 Telecommunications Markup Language (tML

6、) framework Summary This Recommendation is a framework containing rules, guidelines, and objectives for developing telecommunications industry standard telecommunications Markup Language (tML) schemas for operations, administration, maintenance and provisioning (OAM Use of common vocabulary structur

7、e; Use of namespaces; Mapping from existing standards to tML; Specification of metadata used. The scope of this Recommendation does not specify the following items because trading partners specify these items through negotiation: Business Process Scenario; Implementation Infrastructure Profile-Speci

8、fication of any particular communications protocol profile (including provisions for reliability, availability and survivability, or RAS), and provisions for security, privacy, and non-repudiation; Data and Vocabulary content. _ 1Other uses of the term t-m-l exist today, and shouldnt be confused wit

9、h telecommunications Markup Language (tML). tML distinguishes itself from other uses of the term with a lower case “t“. Two examples of other TMLs are: 1) Tutorial Markup Language (TML), an interchange format designed to separate the semantic content of a question from its screen layout or formattin

10、g (TML has been specified using SGML); and 2) Telephony Markup Language (TML), a proprietary framework for applying the Web for distributed Computer Telephony and messaging applications. 2 ITU-T Rec. M.3030 (08/2002) M.3030_F01Data users of this Recommendation are therefore encouraged to investigate

11、 the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of

12、 a Recommendation. 2.1 ITU-T Recommendations 1 ITU-T Recommendation M.3010 (2000), Principles for a telecommunications management network. ITU-T Rec. M.3030 (08/2002) 3 2 ITU-T Recommendation M.3013 (2000), Considerations for a telecommunications management network. 2.2 ISO Standards 3 ISO/IEC 10646

13、-1:2000, Information technology Universal Multiple-Octet Coded Character Set (UCS) Part 1: Architecture and Basic Multilingual Plane. 4a ISO/IEC 11179-3:1994, Information technology Specification and standardization of data elements Part 3: Basic attributes of data elements. 4b ISO/IEC 11179-5:1995,

14、 Information technology Specification and standardization of data elements Part 5: Naming and identification principles for data elements. 2.3 World Wide Web Consortium (W3C) Recommendations 5 eXtensible Markup Language (XML) 1.0 (Second Edition), 6 October 2000. 6 XML Schema Part 1: Structures, 2 M

15、ay 2001. 7 XML Schema Part 2: Datatypes, 2 May 2001. 8 Namespaces in XML, 14 January 1999. 2.4 IETF Specifications 9 IETF RFC 2141 (1997), URN Syntax. 10 IETF RFC 2396 (1998), Uniform Resource Identifiers (URI): Generic Syntax. 2.5 Object Management Group Specifications 11 Unified Modeling Language

16、Specification, Version 1.4, September 2001. 2.6 Committee T1 Standards (Sponsored by ATIS, Alliance for Telecommunications Industry Solutions) 12 T1.227-2000 OAM a property of an element; attributes can be viewed as metadata for the element because they can pass information about an element. Compose

17、d structurally as name=value pair, where name is the name of the attribute and value is the value of the attribute. 3.1.2 character: An atomic unit of text as specified by ISO/IEC 10646; a single alpha, numeric, or punctuation mark, as defined by ISO/IEC 10646. 3.1.3 character data: All text charact

18、ers that are not markup characters. 3.1.4 content model: All data between the start tag and end tag of an element that affects the structure of the element in the instance document. This could be attributes or other elements within an element. (This term is not used). 4 ITU-T Rec. M.3030 (08/2002) 3

19、.1.5 context: A designation or description of the application environment or discipline in which a name is applied or from which it originates (ISO/IEC 11179-3). 3.1.6 data dictionary: A collection of metadata about the data objects or items in a data model including such characteristics as name, se

20、mantic meaning, relationships, and type of data. 3.1.7 data element: A unit of data for which the definition, identification, representation, and permissible values are specified by means of a set of attributes (ISO/IEC 11179-3). 3.1.8 default namespace: A namespace with an empty prefix. A default n

21、amespace is considered to apply to the element where it is declared (if that element has no namespace prefix), and to all elements with no prefix within the content of that element. If the URI reference in a default namespace declaration is empty, then unprefixed elements in the scope of the declara

22、tion are not considered to be in any namespace. 3.1.9 delimiter: A special character that marks the beginning and end of a string or text field. 3.1.10 document: A class of data object; may be the text of a printed document, a set of database records. 3.1.11 document element: The root element of an

23、instance document. There is exactly one element, called the root, or document element, no part of which appears in the content of any other element. 3.1.12 element: A logical data structure within an XML document; start tags and end tags define the beginning and end of an element. Each XML document

24、contains one or more elements, the boundaries of which are either delimited by start-tags and end-tags, or, for empty elements, by an empty-element tag. Each element has a type, identified by a case-sensitive name, sometimes called its “generic identifier“ (GI), and may have a set of attribute speci

25、fications. Each attribute specification has a name and a value. 3.1.13 element declaration: Associating a name with a type. (This term is only within the definition of local element declaration, which is not used). 3.1.14 element type: The name that appears in a start-, end- or empty-tag. In the fol

26、lowing example there are three elements but only two element types: Jo Anne Stephen An element type has element content when elements of that type must contain only child elements, optionally separated by white space. 3.1.15 empty element: Elements that do not have content. An empty-tag follows the

27、syntax: or . 3.1.16 end tag: The end of every element that begins with a start-tag must be marked by an end-tag containing a name that echoes the elements type as given in the start-tag. It is assumed that an XML processor is doing its work on behalf of another module, called the application. 3.1.17

28、 entity: A virtual storage unit of no fixed value, identified by a name; often a separate file, but may be a string or even a database record. 3.1.18 eXtensible Markup Language (XML): By construction, XML documents are conforming SGML documents; a W3C Recommendation; an application profile or restri

29、cted form of the Standard Generalized Markup Language (SGML). By construction, XML documents are conforming SGML documents. The XML subset of SGML has been specifically designed to function on the Web. While HTMLs tags are predefined, XML allows tags to be defined by the developer of the page. Thus,

30、 XML-defined Web pages can function like database records. ITU-T Rec. M.3030 (08/2002) 5 3.1.19 generic identifier (GI): The name of an element “type“. Sometimes the term “tag name“ is used to refer to a GI. 3.1.20 global element (and attribute) declarations: Global elements, and global attributes,

31、are created by declarations that appear as the children of the schema element. Once declared, a global element or a global attribute can be referenced in one or more other declarations. 3.1.21 HyperText Markup Language (HTML): A system of coding information from a wide range of domains (e.g. text, g

32、raphics, database query results) for display by World Wide Web browsers. Certain special codes, called tags, are embedded in the document so that the browser can be told how to render the information. 3.1.22 import: Defines incorporation of type declarations from another schema. The import mechanism

33、 is used in an XML Schema to allow definitions and declarations contained in other schemas under different namespaces to be referenced in the document. If a developer references schema fragments or modules from another namespace, then the import mechanism must be used. If the developer references fr

34、agments or modules from the same namespace, then the include mechanism must be used. 3.1.23 include: Defines incorporation of another schema into the existing namespace. An entity is included when its replacement text is retrieved and processed, in place of the reference itself, as though it were pa

35、rt of the document at the location the reference was recognized. XML Schemas can be included in other XML Schemas. Such included schema documents must either a) have the same target namespace as the ing schema document; or b) no target namespace at all, in which case the d schema document is convert

36、ed to the ing schema documents target namespace. 3.1.24 local element declarations: Local element declarations are nested further inside a schema structure and are not direct children of the root schema element (This term is not used). 3.1.25 local name: A local name is the local part of a qualified

37、 name. This is called the local part in namespaces in XML. 3.1.26 lower camel case: Lower Camel Case is a capitalization pattern where the first letter is lowercase, but after that all words are capitalized and no separators are used. thisIsAnExample. 3.1.27 markup: Markup takes the form of start-ta

38、gs, end-tags, empty-element tags, entity references, character references, comments, CDATA section delimiters, document type declarations, processing instructions, XML declarations, text declarations, and any white space that is at the top level of the document entity. 3.1.28 metadata: Data that des

39、cribes other data. 3.1.29 meta-language: A language that describes other languages. SGML and XML are considered meta-languages because they define markup languages such as tML. (This term is not used). 3.1.30 name: A token beginning with a letter or one of a few punctuation characters, and continuin

40、g with letters, digits, hyphens, underscores, colons, or full stops, together known as name characters. 3.1.31 namespace: A conceptual collection of unique names identified by a URI or a URN reference IETF RFC 2396; used in XML documents as element types and attribute names. Namespaces are used in X

41、ML to qualify names in order to separate them from other names. NOTE A URI has a similar format to a URL. It is not always possible to resolve a URI to find an instance of an XML schema. 3.1.32 namespace prefix: A string that associates an element or attribute name with a namespace URI in XML. 6 ITU

42、-T Rec. M.3030 (08/2002) 3.1.33 namespace root: The standard part of any tML Namespace: e.g. urn:int.itu/tML. 3.1.34 namespace URI: A URI that identifies an XML namespace. Strictly speaking, this actually is a namespace URI reference. This is called the namespace name in W3C document Namespaces in X

43、ML. 3.1.35 object class term: A component of the name of a data element that represents the logical data grouping (in a logical data model) to which it belongs; e.g. “employee.“ (This term is not used). 3.1.36 parent element: An element containing other elements; the elements contained within the pa

44、rent element are known as child elements. (This term is not used). 3.1.37 qualified name: The name of an element or attribute defined as the concatenation of a local name (as defined in this specification), optionally preceded by a namespace prefix and colon character. 3.1.38 registry: In the contex

45、t of this Recommendation, the location of metadata about a repository. A registry is provided for users who want to locate schemas, owners of schemas, and other information stored in a repository. 3.1.39 repository: One or more globally distributed locations used to store schemas, names and location

46、s of schema owners, UML models, and other data and constructs needed to facilitate interoperable exchanges of information between entities. 3.1.40 root element: One element that contains all other elements of the document; the root element may be the document element. 3.1.41 schema: A set of schema

47、components. A collection (vocabulary) of type definitions and element declarations whose names belong to a particular namespace called a target namespace. A schema defines the allowable contents of a class of XML documents. The purpose of a schema is to define and describe a class of XML instance do

48、cuments by using these constructs to constrain and document the meaning, usage and relationships of their constituent parts: datatypes, elements and their content, attributes and their values, entities and their contents, and notations. A class of documents refers to all possible permutations of str

49、ucture in instance documents that will still conform to the rules of the schema. 3.1.42 schema components: The generic term for the building blocks that comprise the abstract data model of the schema. There are 13 kinds of schema components defined: named components (Simple type definitions, Complex type definitions, Attribute declarations, Element declarations, attribute group definitions, identity-constraint definitions, model group definitions, notation declarations, annotations), and un-named co