Liaison Statement: Proposal to address Telecom issues and requirements on W3C standards (ws-addressing, soap, … ws-resource Access) Source




Дата канвертавання27.04.2016
Памер18.77 Kb.
Liaison Statement: Proposal to address Telecom issues and requirements on W3C standards (WS-Addressing, SOAP, … WS-Resource Access)
Source: OASIS SOA-TEL TC, OASIS Telecom Member Section Steering Committee (TMS SC)

To: W3C
Contact Persons

Enrico Ronco, Telecom Italia, enrico.ronco@telecomitalia.it


Abbie Barbir abarbir@live.ca

Paul Knight paul.the.knight@gmail.com

1. Liaison statement introduction

OASIS SOA-TEL TC and TMS SC want to introduce themselves to W3C, and describe their activities, which are conducted within the OASIS Telecom Member Section.


2. Overview of Telecom Member Section and SOA-Tel Technical Committee objectives

2.1 OASIS Telecom Member Section (TMS)

The TMS is committed to bring the full advantages of SOA to the telecommunications industry. Its objective is twofold:



  • to promote, host and coordinate affiliated Technical Committees (TCs) to profile and/or enhance existing SOA and Web Service specifications in order to make them fit-for-purpose for telecommunications scenarios. Adoption and marketing activities related to the OASIS TMS objective are also within its scope;

  • to coordinate with other Technical Committees within OASIS or Working Groups within different SDOs so that such TCs or WGs can profile and/or enhance existing SOA and Web Service specifications in order to make them fit-for-purpose for telecommunications scenarios.

The TMS supports the process of gathering requirements, developing specifications, coordinating the work of its affiliated Technical Committees, and provide the governance structure to accept and manage funds to serve its work. As standards in this area mature, the Member Section may also support adoption and implementation efforts including development of test cases, testing procedures, and interoperability testing and demonstrations.

Refer to http://www.oasis-telecom.org/ for information on the OASIS Telecom Member Section.

2.2 OASIS SOA-Tel TC

This TC was chartered to identify gaps in standards coverage for using Service Oriented Architecture (SOA) techniques in a telecom environment, particularly for Telecom operators/providers, and to specify requirements for addressing such gaps. Refer to http://www.oasis-open.org/committees/soa-tel for information on SOA-TEL TC.

The SOA-TEL TC is within the OASIS Telecom Member Section.

One of the reasons that determined the formation of the SOA-TEL TC is that applicability of IT-based SOA techniques is much more complex in the Telecom world, where services and network features are often tightly coupled and vertically integrated.



  • Tight coupling tends to limit the ability of Telecom operators to develop new composite services that span heterogeneous telecommunications networks.

  • Vertical integration reduces visibility and access to services management functions making difficult the automation of operations and business processes across stacks or organizations.

Telecom providers/operators want to rapidly create and deploy new services that leverage their infrastructure and give them the ability to generate new revenue streams. Telecom providers/operators need to leverage their infrastructure to better compete in a Web 2.0 environment and service-oriented IT world. Current SOA technologies were designed mostly for IT use cases, and it is feared that they may not be able to support the requirements of Telecom use cases.

Within this general context, the activities in SOA-TEL have focused on identifying gaps and on generating requirements to identify how existing standards can help Telecom providers/operators better compete in this new environment.

SOA-Tel has delivered the following documents:


    1. Telecom SOA Use Cases and Issues Version 1 – Approved as “Committee Specification” on March 8, 2010.

    2. Telecom SOA Requirements Version 1 – Approved as “Committee Draft” on February 23, 2010, on which Public Evaluation has started and will terminate on May 18th. Comments on this document can be sent at http://lists.oasis-open.org/archives/tc-announce/201003/msg00015.html.

2.3. SOA-TEL issues and requirements related to W3C standards

The “Telecom SOA Use Cases and Issues” document by SOA-TEL contains 3 use cases (and related technical issues) related to possible technical issues on SOA standards specified in W3C specifications. Conversely also the “Telecom SOA Requirements document” contains specific Requirements related to the abovementioned issues.

The topics managed within the issues are


  1. issue on Transaction Endpoints Specification, related to W3C WS-Addressing recommendation;

  2. issue on OASIS WS-Notification specification, which itself is based on W3C WS-Addressing recommendation; this issue may be resolved within the W3C WS-Resource Access specification;

  3. issue on SOAP, related to W3C SOAP (v.1.2) Recommendation.

OASIS SOA-TEL TC believes that such 3 cases can be of interest and competence of W3C WGs. The above mentioned issues are related to a common theme, which can be identified as “Intermediaries Handling”.

Each Issue in the “Use Cases and Issues” document is presented with subsections “Scenario/Context”, “Use Case”, and “Perceived Technical Issue”.

For each Issue in the “Use Cases and Issues” document one or more Requirements are provided in the “Requirements” document. Each requirement in the latter document is described with subsections “Identification of Use Case Text”, “Requirement(s)”, “Description” and “Solution proposal”.

Each “Solution proposal” section is provided by SOA-TEL as a possible solution to the specific problem addressed by the requirement, and by no means is to be considered as mandatory, as other possible options which are not represented could be identified.

Both “Use Cases and Issues” and “Requirements” documents are attached to this Liaison Statement in their most recently approved version.

Within OASIS SOA-TEL it is known that W3C WS-Addressing WG (owner of WS-Addressing) and XML Protocol WG (owner of SOAP) are closed, but some other WGs within W3C (such as WS-Resource Access or others) may be interested in analyzing and possibly addressing the three issues contained in this LS proposal.



3. Actions

OASIS SOA-TEL TC and TMS SC want to propose to W3C to consider and analyze topics listed in Section 3 (as 1, 2, 3) in this Liaison Statement (refer to Sections 3 “Issues on Addressing and Notification” and 4 “Issues on communications protocols” in the “Use Cases and Issues” document and to Section 2 “Requirements on Intermediaries Handling” in the “Requirements” document).

Should topics presented be recognized as real issues some W3C active WGs, SOA-TEL and TMS SC ask if it is possible for such WGs to identify valid technical solutions to address such issues and to update and enhance the existing affected W3C specifications accordingly.

In order to facilitate and start this process, delegates within SOA-TEL TC would be keen to participate to one or more W3C WG meetings (teleconferences) to present the 3 above mentioned issues.

Next meetings (teleconferences) within SOA-TEL will be on May 11th and June 8th 2010 (at 10 AM ET). Meetings within the TMS SC occur the first Wednesday (e.g. May 5th, 2010) of each month at 10 AM ET.

Thanks and kind regards,



Enrico Ronco on behalf of OASIS SOA-TEL TC.

Abbie Barbir, Paul Knight on behalf of OASIS TMS SC.


База данных защищена авторским правом ©shkola.of.by 2016
звярнуцца да адміністрацыі

    Галоўная старонка