UML Profile for Telecommunication Services Avatar
  1. OMG Specification

UML Profile for Telecommunication Services — Closed Issues

  • Acronym: TelcoML
  • Issues Count: 8
  • Description: Issues resolved by a task force and approved by Board
Closed All
Issues resolved by a task force and approved by Board

Issues Descriptions

The terms and definitions should not contain terms already defined in OMG context

  • Key: TELCOML-8
  • Legacy Issue Number: 17577
  • Status: closed  
  • Source: France Telecom R&D ( Mariano Belaunde)
  • 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.

  • Reported: TelcoML 1.0b1 — Fri, 14 Sep 2012 04:00 GMT
  • Disposition: Resolved — TelcoML 1.0
  • Disposition Summary:

    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.

  • Updated: Fri, 6 Mar 2015 23:16 GMT

References to OMG specs (like UML) should be updated to refer to the last versions

  • Key: TELCOML-7
  • Legacy Issue Number: 17576
  • Status: closed  
  • Source: France Telecom R&D ( Mariano Belaunde)
  • 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.

  • Reported: TelcoML 1.0b1 — Fri, 14 Sep 2012 04:00 GMT
  • Disposition: Resolved — TelcoML 1.0
  • Disposition Summary:

    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.

  • Updated: Fri, 6 Mar 2015 23:16 GMT

OneAPIs specs (SMS,MMS,Location) in TelcoML need revision

  • Key: TELCOML-6
  • Legacy Issue Number: 17500
  • Status: closed  
  • Source: France Telecom R&D ( Mariano Belaunde)
  • 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.

  • Reported: TelcoML 1.0b1 — Mon, 16 Jul 2012 04:00 GMT
  • Disposition: Resolved — TelcoML 1.0
  • Disposition Summary:

    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”.

  • Updated: Fri, 6 Mar 2015 23:16 GMT

Inconsistent paragraph style for one operation title in section 8.4.2.3.2.

  • Key: TELCOML-5
  • Legacy Issue Number: 17199
  • Status: closed  
  • Source: France Telecom R&D ( Mariano Belaunde)
  • 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).

  • Reported: TelcoML 1.0b1 — Thu, 23 Feb 2012 05:00 GMT
  • Disposition: Resolved — TelcoML 1.0
  • Disposition Summary:

    Since resolution of issue 17500 removes the 8.4.2.3.2 text, this issue becomes obsolete.
    Disposition: See issue 17500 for disposition

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Error in number of datatypes in “8.4.2.1.1 DataTypes”.

  • Key: TELCOML-4
  • Legacy Issue Number: 17198
  • Status: closed  
  • Source: France Telecom R&D ( Mariano Belaunde)
  • 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.

  • Reported: TelcoML 1.0b1 — Thu, 23 Feb 2012 05:00 GMT
  • Disposition: Resolved — TelcoML 1.0
  • Disposition Summary:

    Since resolution of issue 17500 removes the 8.4.2.1.1 text, this issue becomes obsolete.
    Disposition: See issue 17500 for disposition

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Typo error for SMSDeliveryReceiptDescription in 8.4.2.1.1 Data Types

  • Key: TELCOML-3
  • Legacy Issue Number: 17197
  • Status: closed  
  • Source: France Telecom R&D ( Mariano Belaunde)
  • 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)

  • Reported: TelcoML 1.0b1 — Thu, 23 Feb 2012 05:00 GMT
  • Disposition: Resolved — TelcoML 1.0
  • Disposition Summary:

    Since resolution of issue 17500 removes the 8.4.2.1.1 text, this issue becomes obsolete.
    Disposition: See issue 17500 for disposition

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Misplaced “Generic Messaging” title

  • Key: TELCOML-2
  • Legacy Issue Number: 17196
  • Status: closed  
  • Source: France Telecom R&D ( Mariano Belaunde)
  • 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.

  • Reported: TelcoML 1.0b1 — Thu, 23 Feb 2012 05:00 GMT
  • Disposition: Resolved — TelcoML 1.0
  • Disposition Summary:

    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).

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Inclusion of the SES/SMI in the Enabler library

  • Key: TELCOML-1
  • Legacy Issue Number: 17195
  • Status: closed  
  • Source: France Telecom R&D ( Mariano Belaunde)
  • 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).

  • Reported: TelcoML 1.0b1 — Tue, 7 Feb 2012 05:00 GMT
  • Disposition: Resolved — TelcoML 1.0
  • Disposition Summary:

    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).

  • Updated: Fri, 6 Mar 2015 20:58 GMT