- removed outdated wiki (moved to separate repo)

## Agenda

|       |                      Topic                      |                           Speaker                            |                          Materials                           |

| :---: | :---------------------------------------------: | :----------------------------------------------------------: | :----------------------------------------------------------: |

| 14:00 |                    Welcoming                    |              Andreas Urlich, TDL Steering Group              |                                                              |

| 14:15 |          Introduction/Tutorial to TDL           |        Philip Makedonski, TDL Open Source Leadership         | [Slides](https://tdl.etsi.org/uploads/TDL_Workshop_2018_PM.pdf) |

| 14:45 | Presentation of TOP and current available tools |          Martti Kaarik, TDL Open Source Leadership           |                                                              |

| 15:15 |                      BREAK                      |                                                              |                                                              |

| 15:30 |        Current usage inside/outside ETSI        |                                                              |                                                              |

| 15:35 |             Usage of TDL in MTS TST             |              Axel Rennoch, MTS-TST WG Chairman               |    [Slides](https://tdl.etsi.org/uploads/TDL4TST_AR.pdf)     |

| 15:45 |        Usage of TDL in ETSI CTI projects        | Sebastian Mueller, ETSI Center for Testing and Interoperability | [Slides](https://tdl.etsi.org/uploads/UPDATE_TDL_TO_USAGE_SM.ppt) |

| 16:00 | Needs for the community for future development  |                                                              |                                                              |

| 16:45 |               Wrap up/Next steps                |                                                              |                                                              |

## Notes

1. Welcoming from Andreas Ulrich

1. Round table of presentations

   - In the room: Philip, Martti, Dirk, Axel, André, Sascha, Yens, Alexander Kaiser, Sebastian, Alex, Michele

   - Remote: Finn, Bostjan, Andreas, Gary, Eric, Jan

2. Overview on TDL and Latest from standardization (Philip)

3. Q&A

   - Jan: Open Source project, is there a grammar available?

     - Philip: The implementation is based on Xtext, it is published in the repository. Also there is a BNF grammar in the Annex of the Metamodel Standards

     - Martti: The Xtext grammar is for the informative textual grammar but what is normatively specified is the Meta Model

4. TOP Tooling (Martti)

   - Installation information are available at https://labs.etsi.org/rep/top/ide

5. Q&A

   - Andreas: We do have full implementation of the language and is available to everyone via the links pasted in the chat and 

6. Discussion on applications of TDL:

   - The results from the Survey on TDL were presented

   - Andreas: is there a need for participants on UML integration?

     - No comments provided

### Open discussion on TDL and TOP

#### Discussion on TDL language

- Andreas: Reported experiences focus on TDL-TO. Have you - TDL-TO users- tried other approaches? How does it relate?

  - Axel: I used Tplan in the past. Feels quite similar.

  - Jens: In our application domain we did not have an internal testing framework for SW. 

- Philip: Quite a lot of interest in TDL-TO but not much interest in TDL. Could you elaborate on why is that so? TDL too big? Too foreign? TDL-TO more familiar?

  - Axel: Coming from INT work, the methodology is composed by TPs and TTCN3 code. TP languages seem lightweight and are complementary to TTCN3. 

  - Sebastian:We do see the use of TDL as somehow overlapping with TTCN3. We could not see advantages of TDL over TTNC3. ETSI CTI will keep evaluating TDL and maybe Interoperaility Testing could be a valuable application.

  - Andreas: I think there are abstract TDL features which are handy, we may need to focus more on the translation features of TDL to TTCN3

- Philip: The implementation of tools translating from TDL to TTCN3 is still in the pipe and we do not have detailed plans at the moment. The level and quality of expertise required is not easy to meet. 

- Andreas: Looking back at the results from the Survey, there seems to be the need to provide translation to more than just TTCN3, therefore some flexibility in the mapping may be needed.

- Philip: The intention of the TDL to TTCN3 was to show the way on the possibility to translate into executable languages. May be the case to extend documentation (e.g. on the wiki) on the goal and methodology to enable third parties to develop their own translators.

- Andreas: Important to support the community and the request for the users.

- Philip: The users are invited to share their experiences/materials on the wiki.

- Michele: My proposal Use the bugzilla as much as possible so that to keep any feedback

- Andres: Better documentation should be provided on the wiki/website

- Dirk: Maybe a Forum can be easier and enable search engines to track information (as it is done in TTCN3)

- Reported issues:

  - Group element could not be used

  - defining constants (#14)

  - issue11 - Configuration connection cannot be resolved 

  - issue10 - Group does not work (references to the domain elements not found) 

  - issue12 - NOT keyword required 

  - issue13 - WORD conversion 

  - issue14 - how to define a constant? entity keyword not required containing semi colons; use meaningful tabulation Test Config : make the gate /PDU declaration optional mix of upper and lower case. why?

#### Discussion on TDL language

- Reported issues:

  - no distinction among literals/content and package definition references (event, entity, pics)

  - Possible way to include comments into word export (e.g. under final condition)

  - Configuration connection not resolver (#11)

  - Group does not work (#10)

  - NOT keyword (#12)

  - (#13)

  - entity keyword not required

  - Q: containing semi colons ; use meaningful tabulation

    - A: needs to be further evaluated

  - test config: make the gate / PDU declaration optional

  - mix of upper and lower case. why?

- Michele: Important to lower the barrier for developers and allow the possiblity to host/link other tools/projects. Is there anybody interested in developing TDL tools?

- Philip: As said before, the level of expertise required is a difficulty to onboard contributors

- Andreas: Better documentation on the website could help.

- Andreas: What are the expectations/intentions from newcomers? (participants who are not TDL users).

#### Providing more documentation

- Advertise a link to the TP created in MTS TST should be referenced on TDL website

- TDL team is asked to provide examples as well

 No newline at end of file

The TOP project has been created to grow a community around TDL the test description language. The language is specified by ETSI Methods for Testing and Specification committe (TC MTS) as an independent, extensible testing language.

You can find more information about ETSI (European Telecommunication Standards Institute) at [www.etsi.org](http://www.etsi.org/) and the information and work program of TC MTS [here](https://portal.etsi.org/tb.aspx?tbid=97&SubTB=97).

The governing rules are decided within TC MTS itself.

## TOP Governing groups

### Project lead (PL)

This is a small group of people from from TC MTS and ETSI CTI that deals with:

* Providing project timeline and roadmap,

* Ensuring IP compliance of code base,

* Deciding on TOP roles assignement.

### Steering Group (SG)

TOP Steering Group is formed by the people in the TDL Steering Group. Its tasks:

* To coordinate TOP's technical activities

* To provide guidelines for future development

* To resolve conflicts at technical level

* To guarantee neutrality from contributors

### Advisory group (AG)

The Advisory Group for TOP is ETSI TC MTS itself. Decisions regarding TOP are taken at MTS meetings, held usually every 3 months. The advisory groups goals are:

* To set the policies of the project

* To make administrative decisions

* To coordinate marketing efforts

Find out [how to participate in TC MTS](mailto:membership@etsi.org).

## Roles

### User

* Browse and download code base.

* Join the mailing list or forum, access to wiki

### Contributor

Same as user plus:

* Create a new issue / bug report

* Provide bug fixes as code patches

* Create new feature requests

* Provide code and tests for new features

* Contribute to the TOP wiki

Anybody is welcome to contribute code and ideas to the TOP project.

Find out [how to contribute](How-to-contribute).

### Committer 

Same as contributor plus:

* Consolidate code changes

* Ensure software quality and validate bug fixes

* Manage new versions and branches

## Access Rights

The following rules are used to assign access rights to the TOP Group and Projects on the ETSI Labs Gitlab server, for both members of Testing Task Forces assigned to develop the project, and to volunteers who have signed the Contributors License Agreement:

- TTF Leader and MTS Chair get Maintainer level rights to the whole TDL Open Source group, for as long as they are in these roles. 

- Individuals or representatives of an organisation which has signed a Contributor License Agreement get Developer level access to the TOP IDE group.

- Members of a current TTF get Developer access at TDL Open Source group level. They also get assigned Developer access to their specific TTF project. This level of access can be upgraded to Maintainer (for the TTF or for the group) if required - TTF leader to decide. 

- Members of a closed TTF retain their Developer access to that TTF project but lose it for all other groups, unless they've signed the CLA or are on another active TTF. 

# Welcome to TOP - TDL Open source Project!

The TDL Open Source Project (TOP) fosters the shared development and testing of contributed tools to manage TDL files, generate documentation and code.

The project is an initiative of ETSI TC MTS – the ETSI committee that standardizes methods for testing and specification. 

[Subscribe here](https://tdl.etsi.org/index.php/contact) to the TDL public mailing list to keep in touch with TDL community, receive news and find support on the TDL public mailing list.

## Quick links

<big>

<table style="width:100%">

<tr>

<td>

**Discover the project**

* [[Governance | Governance]]

* [[Legal framework]]

* [[Learn about TDL]] 

</td>

<td>

**Users**

* [[Installation]]

* [[Usage]]

</td>

<td>

**Developers**

* [[How to contribute]]

</td>

</tr>

</table>

</big>

## Meetings

[[1st TDL Open Source Meeting]] 

## Software

### TDL Open Source Implementation

To accelerate the adoption of TDL, TC MTS has commissioned an open source implementation of TDL in order to lower the barrier to entry for both users and tool vendors in getting started with using TDL. The open source implementation comprises graphical and textual editors, validation facilities, as well as a UML profile for TDL to enable the application of TDL in UML-based working environments.  It will be made available later in 2017 as an ETSI open source software project accessible from the TDL website and enabling contributions from the community.

The open source implementation is based on the Eclipse XText toolset to provide a set of Java libraries and Eclipse plugins to support development of TDL specifications.

### How to contribute  

Are you a test designer, a test developer or a tool vendor? Your contribution is most welcome! Active contributions to the TDL standardisation require an ETSI membership. Any interested company can find how to become an ETSI member here. 

The TOP source base is openly accessible. Its usage is governed by the Eclipse Public License (EPLv1). A source code contribution to TOP (merge request) requires adhering to EPLv1 and signing a Contributor Agreement between the developer and ETSI TC MTS beforehand. Find out more about TOP governance on the Governance wiki page.

Find out more information on how to contribute here.

## Are you a test designer, a test developer or a tool vendor? 

**Your contribution is most welcome!** 

Active contributions to the TDL standardisation require an ETSI membership. 

Any interested company can find how to become an ETSI member [here](http://www.etsi.org/membership/apply). 

## The TOP source base is openly accessible

Its usage is governed by the Eclipse Public License (EPLv1). A source code contribution to TOP (merge request) requires adhering to EPLv1 and signing a Contributor Agreement between the developer and ETSI TC MTS beforehand.

* Find out more about TOP governance on the [Governance wiki page](Governance). 

* Find out more information on how to contribute here.

* Find out more information on how to set up a development environment in the [Readme](https://labs.etsi.org/rep/top/ide).