Issues for Mailing list of the TelcoML 1.0 Finalization Task Force

To comment on any of these issues, send email to telcoml-ftf@omg.org. (Please include the issue number in the Subject: header, thusly: [Issue ###].) To submit a new issue, send email to issues@omg.org.

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Issue 17195: Inclusion of the SES/SMI in the Enabler library
Issue 17196: Misplaced “Generic Messaging” title
Issue 17197: Typo error for SMSDeliveryReceiptDescription in 8.4.2.1.1 Data Types
Issue 17198: Error in number of datatypes in “8.4.2.1.1 DataTypes”.
Issue 17199: Inconsistent paragraph style for one operation title in section 8.4.2.3.2.
Issue 17500: OneAPIs specs (SMS,MMS,Location) in TelcoML need revision
Issue 17576: References to OMG specs (like UML) should be updated to refer to the last versions
Issue 17577: The terms and definitions should not contain terms already defined in OMG context

Issue 17195: Inclusion of the SES/SMI in the Enabler library (telcoml-ftf)

Click here for this issue's archive.
Source: France Telecom R&D (Mr. Mariano Belaunde, mariano.belaunde(at)orange.com)
Nature: Uncategorized Issue
Severity:
Summary:

In the beta spec the SES/SMI interface is provided in an annex waiting for update

from TMF SES team.

If such update is provided the final TelcoML v1.0 should incorporate this interface

within an additional Section  within the telcoML library (should be section 8.11).

Resolution: Remove the Annex A SES/SMI annex from the Core TelcoML document since SES/SMI will be part of a separated extension document named “Service Management TelcoML Extension”. This implies updating some text in the actual core document (such as references to the annex).
Revised Text: (1) Remove the SES/SMI Annex (2) In Section 7.2, within TM Forum bullet replace “The Software Enabled Services (SES) Management Interface (SMI) - which is actually in draft state - will be considered for integration in future releases of the TelcoML library. Annex A provides a temporary non-normative SoaML representation of this API.” By “The Software Enabled Services (SES) Management Interface (SMI) defines simple operations to manage service configuration and service execution. This interface will extend the TelcoML library (publication to be done in a separated document).” (3) Add two new accompanying documents for the TelcoML specification: These are the document named “SES Management TelcoML Extension” (with doc reference: ptc/2012-07-22) and “XMI for SES Management TelcoML Extension” (with doc reference: ptc/2012-07-23)
Actions taken:
February 7, 2012: received issue
January 7, 2013: closed issue

Discussion:

Issue 17196: Misplaced “Generic Messaging” title (telcoml-ftf)

Click here for this issue's archive.
Source: France Telecom R&D (Mr. Mariano Belaunde, mariano.belaunde(at)orange.com)
Nature: Uncategorized Issue
Severity: Minor
Summary:

In the beta spec (ptc-12-01-02) the title “8.3.1  Generic Messaging” is misplaced.

It should be at the same level than the others interfaces, that is to say at level 2

instead of level 3.

Resolution: The three first sub-titles Introduction, Convention and Package Structure are actually at the same level than the titles for individual enablers and the specific “Generic Messaging” enabler title is misplaced as sub-section. This was a formatting error introduced accidentally when creating the beta version in Framemaker. In fact the introductory text contains the convention and package structure text and the sub clause numbering only starts with the first interface (“Generic Messaging” should be the first subtitle).
Revised Text: Replace the introductory text from “8 TelcoML Enabler Library” to “8.3.1 Generic messaging” by the following content: ------------------ START -------------- 8 TelcoML Enabler Library This clause is normative, with the exception of some sub-sections explicitly marked as non normative. The TelcoML Enabler library defines a set of predefined service interfaces to facilitate the definition of composite services accessing well-known telecommunication facilities (called enablers) usually provided by telecom operators. These service definitions are provided in a sufficient technology agnostic way to enable independence in respect to the enabler provider and to the usage of a specific implementation technology. Whenever possible the service interfaces defined here are reformulations in UML of pre-existing enablers defined in telecom-oriented standardization bodies and implemented by telecom operators. Conventions: Each enabler is described using at least two sub-clauses: The "Overview" gives a short explanation of the purpose of the enabler. - An optional "Context" provides additional information that may be of interest to understand the design of the interface. If present, this is non normative. - The "Interface Definitions" gives the list of interfaces defined for the enabler. For each service interface, there is a specific section, containing: - The "Data Types" lists the data types in graphical form and with additional textual explanations. - The "Operations" provides the details on each service operation: - firstly a header providing in short the semantics of the operation, - secondly the complete signature (with all multiplicities), - then, if useful for the comprehension, an additional explanation of the purpose of the operation, - finally three sections: parameters, outputs and exceptions Package Structure: Technically the TelcoML Enabler Library is defined by a UML Package containing a list of sub-packages corresponding to each sub clause ("Generic Messaging" and so on). The SoaML profile applies to this package. The ServiceInterface stereotype used in the enabler library is the stereotype defined by SoaML.
Actions taken:
February 23, 2012: received issue
January 7, 2013: closed issue

Issue 17197: Typo error for SMSDeliveryReceiptDescription in 8.4.2.1.1 Data Types (telcoml-ftf)

Click here for this issue's archive.
Source: France Telecom R&D (Mr. Mariano Belaunde, mariano.belaunde(at)orange.com)
Nature: Uncategorized Issue
Severity: Minor
Summary:

In section 8.4.2.1.1 Data Types, “SMSDeliveryReceiptDescription”  should be 

in “SMSDeliveryReceiptSubscription” (two occurrences of text).

Similar problem exists in Section 8.5.2.1.1 Data Types:  

“MMSDeliveryReceiptDescription”  should be 

 “MMSDeliveryReceiptSubscription” (two occurrences of text)

Resolution: Since resolution of issue 17500 removes the 8.4.2.1.1 text, this issue becomes obsolete. Disposition: See issue 17500 for disposition
Revised Text:
Actions taken:
February 23, 2012: received issue
January 7, 2013: closed issue

Issue 17198: Error in number of datatypes in “8.4.2.1.1 DataTypes”. (telcoml-ftf)

Click here for this issue's archive.
Source: France Telecom R&D (Mr. Mariano Belaunde, mariano.belaunde(at)orange.com)
Nature: Uncategorized Issue
Severity: Minor
Summary:

It is said “The specification of the SMS interface involves the definition of seven data types

and one enumeration:”. However in fact there are 6 datatypes and 1 enumeration.

The same happens in 8.5.2.1.1 Data Types: There are 7 datatypes, not 8.

Issue 17199: Inconsistent paragraph style for one operation title in section 8.4.2.3.2. (telcoml-ftf)

Click here for this issue's archive.
Source: France Telecom R&D (Mr. Mariano Belaunde, mariano.belaunde(at)orange.com)
Nature: Uncategorized Issue
Severity: Minor
Summary:

The paragraph style used for operation “Receiving the notification of arrival of messages

for a client application” should be the same than for other operations titles in the spec

(italic and bold).

Resolution: Since resolution of issue 17500 removes the 8.4.2.3.2 text, this issue becomes obsolete. Disposition: See issue 17500 for disposition
Revised Text:
Actions taken:
February 23, 2012: received issue
January 7, 2013: closed issue

Issue 17500: OneAPIs specs (SMS,MMS,Location) in TelcoML need revision (telcoml-ftf)

Click here for this issue's archive.
Source: France Telecom R&D (Mr. Mariano Belaunde, mariano.belaunde(at)orange.com)
Nature: Revision
Severity:
Summary:

The GSMA consortium has published new versions of SMS, MMS and Location APIs.

Hence the UML versions of these APIs in the draft TelcoML spec need be revised and possible

moved from the core document for maintenance reasons.

Resolution: In line with discussions conclusion on how to maintain TelcoML interface definitions that are reformulations of specifications developed by other standardization bodies (in our case GSMA and TMF), we agreed to remove these specifications from the core specification. In the case of GSMA APIs the three clauses regarding SMS, MMS and Location interfaces are hence removed. In future TelcoML releases (provided GSMA and OMG sign a copyright agreement) these three interfaces (and possible new ones from the OneAPI family) will be re-incoprporated in a separated specification document “OneAPI TelcoML Extension”.
Revised Text: (1) Remove chapters 8.4 SMS, 8.5 MMS and 8.7 Location. (2) At the end of clause 7, remove the two sentences : “An exception is the SES SMI interface which fits in the BSS part. The Composition Service Profile (Section 9) fits in the first category since its purpose is the specification of executable composite services.” (3) At the end of clause 7, replace paragraph: “Note: In future releases of this specification other kind of interfaces could be incorporated, like the OneAPI Billing interface as well as additional interfaces coming from OneAPI v2.0 (like user data management).” By: “In future releases of this specification other kind of interfaces could be incorporated, like interfaces for billing and for user data management which fits in the BSS category depicted in Figure 1.” (4) In introductory text of Section 8 replace the sentence: “Whenever possible the service interfaces defined here are reformulations in UML of pre-existing enablers defined in telecom-oriented standardization bodies and implemented by telecom operators.” By “The TelcoML enabler library presented in this document contains a limited set of interfaces serving as the starting foundation for the library. Extensions to this library will be typically defined in separated documents, especially to provide reformulations in TelcoML of pre-existing enabler interfaces defined by other standardization bodies.” (5) In 7.2 Section, OMA bullet, replace: “Some of them have been reformulated as UML interfaces and integrated to TelcoML library.” By “In the future some of these interfaces could be reformulated in TelcoML formalism and integrated as extensions to the normative TelcoML library” (6) In 7.2 Section, GSMA bullet, replace: “One APIs are reformulated in terms of UML and integrated in TelecoML” By: The SMS, MMS and Location interfaces are good candidates for a future integration as extensions to the normative TelcoML library.
Actions taken:
July 16, 2012: received issue
January 7, 2013: closed issue

Issue 17576: References to OMG specs (like UML) should be updated to refer to the last versions (telcoml-ftf)

Click here for this issue's archive.
Source: France Telecom R&D (Mr. Mariano Belaunde, mariano.belaunde(at)orange.com)
Nature: Uncategorized Issue
Severity: Significant
Summary:

The actual references to OMG specs like UML do not refer to the last versions of

the specs.

This need to be corrected, especially for consistency with the provided XMI files.

Resolution: Making the replacement for UML and other specs in the core TelcoML spec and in the extension doc. Note: The extension doc (ptc/12-07-22) was introduced by resolution of 17195 in 2nd ballot.
Revised Text: (1) Replace the content of Section 3 “Normative references” of the TelcoML specification by the text below delimited by the –start- and –end—delimiters. -- START ------ The following normative documents contain provisions which, through reference in this text, constitute provisions of this specification. For dated references, subsequent amendments to, or revisions of, any of these publications do not apply. List of normative references 1. Object Constraint Language (OCL) v2.3.1, OMG document number formal/2012-05-09. 2. Service oriented architecture Modeling Language (SoaML) v1.0, OMG document number formal/2012-05-01. 3. UML v2.4.1 Superstructure (UML), OMG document number formal/2012-05-07. 4. Action Language for Foundational UML (ALF), OMG document number ptc/2010-10-05. 5. Meta Object Facility (MOF) Core v2.4.1, OMG document number formal/2011-08-07. 6. MOF/XMI Mapping v2.4.1, OMG document number formal/2011-08-09. Normative parts of TelcoML The following is included as part of this specification: - XMI for TelcoML Library, OMG document number ptc/2012-09-21. - XMI for TelcoML Composition Profile, OMG document number ptc/2012-09-22. -- END ------- (2) Replace the content of Section 3 “Normative references” of the “SES Management TelcoML Extension” document (ptc/12-07-22) by the text below delimited by the –start- and –end—delimiters. -- START ------ The following normative documents contain provisions which, through reference in this text, constitute provisions of this specification. For dated references, subsequent amendments to, or revisions of, any of these publications do not apply. List of normative references 1. Object Constraint Language (OCL) v2.3.1, OMG document number formal/2012-05-09. 2. Service oriented architecture Modeling Language (SoaML) v1.0, OMG document number formal/2012-05-01. 3. UML v2.4.1 Superstructure (UML), OMG document number formal/2012-05-07. 4. Action Language for Foundational UML (ALF), OMG document number ptc/2010-10-05. 5. Meta Object Facility (MOF) Core v2.4.1, OMG document number formal/2011-08-07. 6. MOF/XMI Mapping v2.4.1, OMG document number formal/2011-08-09. Normative parts of TelcoML The following is included as part of this specification: - XMI for SES Management Library Extension ptc/2012-09-24. -- END -------
Actions taken:
September 14, 2012: received issue
January 7, 2013: closed issue

Issue 17577: The terms and definitions should not contain terms already defined in OMG context (telcoml-ftf)

Click here for this issue's archive.
Source: France Telecom R&D (Mr. Mariano Belaunde, mariano.belaunde(at)orange.com)
Nature: Revision
Severity: Significant
Summary:

The terms of definitions chapters contains terms that are already know to OMG community and

that are not specifically defined in telcoML. These do not need to appear in the section.

Resolution: Removing these references in the core document and in the extension doc. Instead we put the sentence “This specification does not introduce specific definitions and terms”. Notice that the “OneAPI” term is not anymore essential to the spec since the three OneAPI interfaces have been suppressed. Note: The extension doc was introduced by resolution of 17195 in 2nd ballot.
Revised Text: (1) Replace all the content of Section 4 “Definitions and Terms” of the TelcoML specification by the sentence : This specification does not introduce specific definitions and terms. (2) Replace all the content of Section 4 “Definitions and Terms” of the “SES Management TelcoML Extension” document (ptc/12-07-22) by the following sentence:. This specification does not introduce specific definitions and terms
Actions taken:
September 14, 2012: receivd issue
January 7, 2013: closed issue