DRV STRING - Benutzerbeiträge [de]

Anforderungen

2025-11-10T08:29:35Z

Althoffm:

Auf dieser Seite werden die im Rahmen der Expertenworkshops zu DRV STRING definierten Anforderungen dargestellt. Die Einstellung erfolgt pro Expertenworkshop chronologisch.
 
 
Anforderungen '''MODIFY''' und '''INTERNES BUCHEN''', Expertenworkshop vom 01.02.2024: [[Medium:Anforderungen_Expertenworkshop_01022024.pdf|Anforderungen_Expertenworkshop_01022024.pdf]] 
 
Anforderungen '''Upselling und Cross-Selling''', Expertenworkshop vom 11.04.2024: [[Medium:Anforderungen Expertenworkshop 11042024.pdf|Anforderungen Expertenworkshop 11042024.pdf]] 
 
Anforderungen '''Upselling und Cross-Selling''', Expertenworkshops bis September 2024: [[Medium:Anforderungen Expertenworkshop 06-09 - 2024.pdf|Anforderungen Expertenworkshop 06-09 - 2024.pdf]] 
 
Anforderungen ''''''''Versicherungen und Gruppenreisen''''''', Expertenworkshops bis November 2025: [[Medium:Anforderungen_Expertenworkshops_Versicherungen_und_Gruppenreisen_2025.pdf]]

Anforderungen

2025-11-10T08:29:03Z

Althoffm:

Auf dieser Seite werden die im Rahmen der Expertenworkshops zu DRV STRING definierten Anforderungen dargestellt. Die Einstellung erfolgt pro Expertenworkshop chronologisch.
 
 
Anforderungen '''MODIFY''' und '''INTERNES BUCHEN''', Expertenworkshop vom 01.02.2024: [[Medium:Anforderungen_Expertenworkshop_01022024.pdf|Anforderungen_Expertenworkshop_01022024.pdf]] 
 
Anforderungen '''Upselling und Cross-Selling''', Expertenworkshop vom 11.04.2024: [[Medium:Anforderungen Expertenworkshop 11042024.pdf|Anforderungen Expertenworkshop 11042024.pdf]] 
 
Anforderungen '''Upselling und Cross-Selling''', Expertenworkshops bis September 2024: [[Medium:Anforderungen Expertenworkshop 06-09 - 2024.pdf|Anforderungen Expertenworkshop 06-09 - 2024.pdf]] 
 
Anforderungen '''Versicherungen und Gruppenreisen'', Expertenworkshops bis November 2025: [[Medium:Anforderungen_Expertenworkshops_Versicherungen_und_Gruppenreisen_2025.pdf]]

Datei:Anforderungen Expertenworkshops Versicherungen und Gruppenreisen 2025.pdf

2025-11-10T08:27:33Z

Althoffm:

Anforderungen

2024-12-05T13:27:19Z

Althoffm:

Datei:Anforderungen Expertenworkshop 06-09 - 2024.pdf

2024-12-05T13:26:00Z

Althoffm:

Anforderungen

2024-12-05T13:24:57Z

Althoffm:

Auf dieser Seite werden die im Rahmen der Expertenworkshops zu DRV STRING definierten Anforderungen dargestellt. Die Einstellung erfolgt pro Expertenworkshop chronologisch.
 
 
Anforderungen '''MODIFY''' und '''INTERNES BUCHEN''', Expertenworkshop vom 01.02.2024: [[Medium:Anforderungen_Expertenworkshop_01022024.pdf|Anforderungen_Expertenworkshop_01022024.pdf]] 
 
Anforderungen '''Upselling und Cross-Selling''', Expertenworkshop vom 11.04.2024: [[Medium:Anforderungen Expertenworkshop 11042024.pdf|Anforderungen Expertenworkshop 11042024.pdf]] 
 
Anforderungen '''Upselling und Cross-Selling''', Expertenworkshops bis September 2024: [[Medium:Anforderungen Expertenworkshop 11042024.pdf|Anforderungen Expertenworkshop 11042024.pdf]]

Anforderungen

2024-05-29T08:13:47Z

Althoffm:

Datei:Anforderungen Expertenworkshop 11042024.pdf

2024-05-29T08:12:26Z

Althoffm:

Versicherungen

2024-02-29T15:23:37Z

Althoffm:

Auf dieser Seite werden die im Rahmen der Expertenworkshops zu DRV STRING definierten Anforderungen für den Bereich Reiseversicherungen dargestellt. Die Einstellung erfolgt pro Expertenworkshop chronologisch. Aufgrund der Komplexität des Themas besteht für zum Thema STRING Reiseversicherungen ein eigener Expertenkreis, an dem Versicherungsunternehmen, Reiseveranstalter, Reisevertriebsorganisationen und Softwareanbieter nach vorheriger Anmeldung jederzeit teilnehmen können.
 
Es wurde vereinbart, im ersten Schritt die Produktbereiche '''Versicherungspakete''' sowie - als Einzelversicherungen - die Produkte '''Krankenversicherung, Reiserücktritt und Reiseabbruch''' umzusetzen. Eine Ausweitung auf weitere Produktbereiche kann anschließend erfolgen.
 
 
Anforderungen '''Reiseversicherungen''', Basisdokument: [[Medium:29092020 STRING Versicherung Use Cases.xlsx|29092020 STRING Versicherung Use Cases.xlsx]]

Versicherungen

2024-02-29T15:21:34Z

Althoffm:

Datei:29092020 STRING Versicherung Use Cases.xlsx

2024-02-29T15:20:57Z

Althoffm:

Versicherungen

2024-02-29T15:20:38Z

Althoffm: Die Seite wurde neu angelegt: „Auf dieser Seite werden die im Rahmen der Expertenworkshops zu DRV STRING definierten Anforderungen für den Bereich Reiseversicherungen dargestellt. Die Einst…“

Hauptseite

2024-02-29T15:18:16Z

Althoffm:

[[Datei:DRV-Basislogo WEB-mittel.png]]

'''Herzlich Willkommen bei STRING - STandard Reservation Interface Next Generation'''

Dies ist die offizielle Projektseite des DRV STRING-Projektes. Die nachfolgenden Informationen stehen allen Interessierten zur Verfügung, eine Anmeldung für das Lesen der Informationen ist nicht erforderlich. Wenn Sie sich für eine Mitarbeit an diesem Projekt interessieren und Beiträge auf dieser Website kommentieren möchten, ist vorab eine Registrierung erforderlich (siehe [[Mitarbeit]]).

Die Projektseite ist als Wiki angelegt worden. Hinweise zur Benutzung der zugrunde liegenden Software finden Sie im [//meta.wikimedia.org/wiki/Help:Contents Benutzerhandbuch].

Die übergeordneten Projektinformationen zu Projektziel und –ablauf werden sowohl in Deutsch als auch auf Englisch veröffentlicht. Alle weiteren Dokumente, insbesondere Arbeitsdokumente, werden ausschließlich auf Englisch publiziert.
 
 
<big>'''Eine aktuelle Broschüre zu den Zielen und Mehrwerten von STRING kann unter folgendem Link abgerufen werden:''' [[Medium:STRING DRV final.pdf|STRING DRV final.pdf]]</big> 

== Inhalt ==

* [[DRV_STRING:Über_DRV_STRING | Über DRV STRING]] - Beschreibung des STRING-Projektes (Deutsch/Englisch)
* [http://string.drv.de/mailman/listinfo Öffentliche Mailverteiler] zu STRING
* [[Schemata]] - Die XSD-Schemata, Dokumentation und Diskussion (Englisch)
* [[Releases]] - Übersicht / Download der freigegebenen Versionen (Englisch)
* [[Anforderungen]] - Anforderungen der STRING Experten an die Weiterentwicklung (fortlaufend, Deutsch)
* [[Versicherungen]] - Anforderungen der STRING Experten zur Integration von Reiseversicherungen (über Reiseveranstalter und im direkten Endkundengeschäft) (fortlaufend, Deutsch)
* [[Snapshots]] - Aktueller Entwicklungsstand
* [[Documentation]] - Dokumentation der Schnittstelle, Empfehlungen zur Umsetzung (Deutsch?/Englisch)
* [[Use Cases]] - Anwendungsfälle für die Schnittstelle (Englisch)
* [[Mitarbeit]] - Hinweise zur Mitarbeit, Arbeitsumgebung, Berechtigungskonzept (Englisch)
* [[Abfragen]] - Abfragen zur Ermittlung von Anforderungen seitens der Reiseveranstalter (Deutsch)
* [https://drv-string.atlassian.net/jira/software/c/projects/STRING/issues Ticketsystem] - Unser Ticketsystem ist öffentlich einsehbar (Englisch)
* [[License | Lizenz-Informationen]] für die Schnittstelle (Englisch)
* [[Change Requests]] - Verzeichnis der Change Requests (Englisch)
* [[Library:Bibliothek | Bibliothek]] - Interne Schnittstellen-Bibliothek (Englisch)
* [[Developers Area| Entwicklerbereich]] - Bereich für aktive STRING-Entwickler

'''Welcome to STRING - STandard Reservation Interface Next Generation'''

This is the official project wiki for the DRV STRING project. All information are available to everyone interested in the project, no pre-registration neccessary. If you would like to actively participate in the project and want to be able to comment on articles published on this wiki, please register (please see [[Mitarbeit | Participation]]).

This website is based on wiki software. If you should need further instructions on how to use the software pls see the respective [//meta.wikimedia.org/wiki/Help:Contents manual]. Overall project information, e.g. project objectives and procedures, will be published both in German and in English. All further documents, especially documentations, will only be published in English.

== Content ==

* [[DRV_STRING:Über_DRV_STRING | About DRV STRING]] - Overall describtion of the STRING project
* [http://string.drv.de/mailman/listinfo Public mailing lists] related to STRING
* [[Schemata]] - developed XSD-schemes, documentations und discussion
* [[Releases]] - overview / download of the released versions
* [[Snapshots]] - current state of development
* [[Documentation]] - Interface documentation, recommendations for implementation
* [[Use Cases]] - collection of use cases for the interface
* [[Mitarbeit | Participation]] - Usefull information for those interested to join the project and its working environment
* [https://drv-string.atlassian.net/jira/software/c/projects/STRING/issues Ticketsystem] - Our ticket system has public read access
* [http://string.drv.de/license/ License] terms and conditions
* [[Change Requests]] - List of Change Requests and follow-up information
* [[Library:Bibliothek | Library]] - collection of documentations of relevant interface descriptions for the travel industry
* [[Developers Area]] - Area for active in STRING developers

Mitarbeit

2024-02-29T15:11:32Z

Althoffm:

'''Getting Involved'''

The STRING project is generally open to everyone interested in participating the process of developing a new standard for bookings in the travel industry. Therefore this wiki and its information are open to the public.

The project has several working and decision making levels. The highest institution within this project is the Steering Committee. It consists of the current board members of the users of the DRV data standard and is led by the DRV. Members of the Steering Committee are representatives from the following companies:

* Ameropa
* DER Touristik
* FTI
* Olimar
* Peakwork
* Thomas Cook
* TravelTainment
* Travelport
* TUI

The project is led by the DRV and MC Management Consulting. Amadeus and Bewotec have designated further employees to support this project in order to develop the required XSD-schemes. This project team strongly cooperates with an expert group. Experts are members of the tour operators represented in the Steering Committee.

Nevertheless the project team shares its information with the public and would highly appreciate an industry-wide discussion of the projects intermediate and final results on this platform. Therefore all relevant project information published within this wiki are fully accessable to the public, everyone interested can inform him- or herself about the current status of development.

If you would like to actively accompany the project development and support the project team by discussing published results, pls send a short application request including your name, company, working position and eMail-address to [mailto:registration@string.drv.de registration@string.drv.de]. You will then get access data. Please keep in mind: access will only be provided to individuals, not to overall companies. If needed you can of course have several accounts per company. Please consider: all comments published on this platform will always show the author and authors are fully responsible for the content published with their account. Therefore please handle your access data very carefully. In case of misuse of access the project team has the right to eliminate users from this platform (e.g. use of foul language).

Participation can take place on three different levels:
Level 1: participation via the project wiki, e.g. bei completing questionnaires within the project and by discussing results within the wiki
Level 2: membership within the expert group. This requires at least one dedicated representative of either a tour operator or its it provider, meetings are held every two months approximately.
Level 3: prototyping partner, implementing one or numerous releases within the current project to test the functionality provided. This role can be covered by other representatives of a tour operator or its it provider than the expert group members.

If you would like to gain more information on how to participate pls do not hesitate to contact the head of project, Mr Michael Althoff via eMail: [mailto:Michael.Althoff@mc-gmbh.de Michael.Althoff@mc-gmbh.de]

For more Information please see [[Berechtigungskonzept]].

Anforderungen

2024-02-29T15:10:34Z

Althoffm:

Datei:Anforderungen Expertenworkshop 01022024.pdf

2024-02-29T15:09:37Z

Althoffm:

Anforderungen

2024-02-29T15:08:59Z

Althoffm: Die Seite wurde neu angelegt: „Auf dieser Seite werden die im Rahmen der Expertenworkshops zu DRV STRING definierten Anforderungen dargestellt. Die Einstellung erfolgt pro Expertenworkshop c…“

Auf dieser Seite werden die im Rahmen der Expertenworkshops zu DRV STRING definierten Anforderungen dargestellt. Die Einstellung erfolgt pro Expertenworkshop chronologisch.
 
 
Anforderungen MODIFY und INTERNES BUCHEN, Expertenworkshop vom 01.02.2024, '''Rückmeldung bis spätestens 30.09.2018''': [[Medium:Abfrage Unterkunftssuche Booking.docx|Abfrage Unterkunftssuche Booking.docx]]

Hauptseite

2024-02-29T15:06:09Z

Althoffm:

[[Datei:DRV-Basislogo WEB-mittel.png]]

'''Herzlich Willkommen bei STRING - STandard Reservation Interface Next Generation'''

Dies ist die offizielle Projektseite des DRV STRING-Projektes. Die nachfolgenden Informationen stehen allen Interessierten zur Verfügung, eine Anmeldung für das Lesen der Informationen ist nicht erforderlich. Wenn Sie sich für eine Mitarbeit an diesem Projekt interessieren und Beiträge auf dieser Website kommentieren möchten, ist vorab eine Registrierung erforderlich (siehe [[Mitarbeit]]).

Die Projektseite ist als Wiki angelegt worden. Hinweise zur Benutzung der zugrunde liegenden Software finden Sie im [//meta.wikimedia.org/wiki/Help:Contents Benutzerhandbuch].

Die übergeordneten Projektinformationen zu Projektziel und –ablauf werden sowohl in Deutsch als auch auf Englisch veröffentlicht. Alle weiteren Dokumente, insbesondere Arbeitsdokumente, werden ausschließlich auf Englisch publiziert.
 
 
<big>'''Eine aktuelle Broschüre zu den Zielen und Mehrwerten von STRING kann unter folgendem Link abgerufen werden:''' [[Medium:STRING DRV final.pdf|STRING DRV final.pdf]]</big> 

== Inhalt ==

* [[DRV_STRING:Über_DRV_STRING | Über DRV STRING]] - Beschreibung des STRING-Projektes (Deutsch/Englisch)
* [http://string.drv.de/mailman/listinfo Öffentliche Mailverteiler] zu STRING
* [[Schemata]] - Die XSD-Schemata, Dokumentation und Diskussion (Englisch)
* [[Releases]] - Übersicht / Download der freigegebenen Versionen (Englisch)
* [[Anforderungen]] - Anforderungen der STRING Experten an die Weiterentwicklung (fortlaufend, Deutsch)
* [[Snapshots]] - Aktueller Entwicklungsstand
* [[Documentation]] - Dokumentation der Schnittstelle, Empfehlungen zur Umsetzung (Deutsch?/Englisch)
* [[Use Cases]] - Anwendungsfälle für die Schnittstelle (Englisch)
* [[Mitarbeit]] - Hinweise zur Mitarbeit, Arbeitsumgebung, Berechtigungskonzept (Englisch)
* [[Abfragen]] - Abfragen zur Ermittlung von Anforderungen seitens der Reiseveranstalter (Deutsch)
* [https://drv-string.atlassian.net/jira/software/c/projects/STRING/issues Ticketsystem] - Unser Ticketsystem ist öffentlich einsehbar (Englisch)
* [[License | Lizenz-Informationen]] für die Schnittstelle (Englisch)
* [[Change Requests]] - Verzeichnis der Change Requests (Englisch)
* [[Library:Bibliothek | Bibliothek]] - Interne Schnittstellen-Bibliothek (Englisch)
* [[Developers Area| Entwicklerbereich]] - Bereich für aktive STRING-Entwickler

'''Welcome to STRING - STandard Reservation Interface Next Generation'''

This is the official project wiki for the DRV STRING project. All information are available to everyone interested in the project, no pre-registration neccessary. If you would like to actively participate in the project and want to be able to comment on articles published on this wiki, please register (please see [[Mitarbeit | Participation]]).

This website is based on wiki software. If you should need further instructions on how to use the software pls see the respective [//meta.wikimedia.org/wiki/Help:Contents manual]. Overall project information, e.g. project objectives and procedures, will be published both in German and in English. All further documents, especially documentations, will only be published in English.

== Content ==

* [[DRV_STRING:Über_DRV_STRING | About DRV STRING]] - Overall describtion of the STRING project
* [http://string.drv.de/mailman/listinfo Public mailing lists] related to STRING
* [[Schemata]] - developed XSD-schemes, documentations und discussion
* [[Releases]] - overview / download of the released versions
* [[Snapshots]] - current state of development
* [[Documentation]] - Interface documentation, recommendations for implementation
* [[Use Cases]] - collection of use cases for the interface
* [[Mitarbeit | Participation]] - Usefull information for those interested to join the project and its working environment
* [https://drv-string.atlassian.net/jira/software/c/projects/STRING/issues Ticketsystem] - Our ticket system has public read access
* [http://string.drv.de/license/ License] terms and conditions
* [[Change Requests]] - List of Change Requests and follow-up information
* [[Library:Bibliothek | Library]] - collection of documentations of relevant interface descriptions for the travel industry
* [[Developers Area]] - Area for active in STRING developers

DRV STRING:Impressum

2023-06-19T09:09:45Z

Althoffm:

DRV Deutscher ReiseVerband e. V.
 
Postanschrift: Lietzenburger Straße 99, 10707 Berlin

 
Telefon +49 30 28406 -0
 
Telefax +49 30 28406 -30
 
E-Mail info[at]drv.de

 
Vereinsregister: Amtsgericht Berlin-Charlottenburg
VR 25302 B

Hauptseite

2021-08-06T06:15:05Z

Althoffm: Publikation neue DRV STRING-Broschüre 06082021

[[Datei:DRV-Basislogo WEB-mittel.png]]

'''Herzlich Willkommen bei STRING - STandard Reservation Interface Next Generation'''

Dies ist die offizielle Projektseite des DRV STRING-Projektes. Die nachfolgenden Informationen stehen allen Interessierten zur Verfügung, eine Anmeldung für das Lesen der Informationen ist nicht erforderlich. Wenn Sie sich für eine Mitarbeit an diesem Projekt interessieren und Beiträge auf dieser Website kommentieren möchten, ist vorab eine Registrierung erforderlich (siehe [[Mitarbeit]]).

Die Projektseite ist als Wiki angelegt worden. Hinweise zur Benutzung der zugrunde liegenden Software finden Sie im [//meta.wikimedia.org/wiki/Help:Contents Benutzerhandbuch].

Die übergeordneten Projektinformationen zu Projektziel und –ablauf werden sowohl in Deutsch als auch auf Englisch veröffentlicht. Alle weiteren Dokumente, insbesondere Arbeitsdokumente, werden ausschließlich auf Englisch publiziert.
 
 
<big>'''Eine aktuelle Broschüre zu den Zielen und Mehrwerten von STRING kann unter folgendem Link abgerufen werden:''' [[Medium:STRING DRV final.pdf|STRING DRV final.pdf]]</big> 

== Inhalt ==

* [[DRV_STRING:Über_DRV_STRING | Über DRV STRING]] - Beschreibung des STRING-Projektes (Deutsch/Englisch)
* [http://string.drv.de/mailman/listinfo Öffentliche Mailverteiler] zu STRING
* [[Schemata]] - Die XSD-Schemata, Dokumentation und Diskussion (Englisch)
* [[Releases]] - Übersicht / Download der freigegebenen Versionen (Englisch)
* [[Documentation]] - Dokumentation der Schnittstelle, Empfehlungen zur Umsetzung (Deutsch?/Englisch)
* [[Use Cases]] - Anwendungsfälle für die Schnittstelle (Englisch)
* [[Mitarbeit]] - Hinweise zur Mitarbeit, Arbeitsumgebung, Berechtigungskonzept (Englisch)
* [[Abfragen]] - Abfragen zur Ermittlung von Anforderungen seitens der Reiseveranstalter (Deutsch)
* [http://string.drv.de/jira/browse/STRING Ticketsystem] - Unser Ticketsystem ist öffentlich einsehbar (Englisch)
* [[License | Lizenz-Informationen]] für die Schnittstelle (Englisch)
* [[Change Requests]] - Verzeichnis der Change Requests (Englisch)
* [[Library:Bibliothek | Bibliothek]] - Interne Schnittstellen-Bibliothek (Englisch)
* [[Developers Area| Entwicklerbereich]] - Bereich für aktive STRING-Entwickler

'''Welcome to STRING - STandard Reservation Interface Next Generation'''

This is the official project wiki for the DRV STRING project. All information are available to everyone interested in the project, no pre-registration neccessary. If you would like to actively participate in the project and want to be able to comment on articles published on this wiki, please register (please see [[Mitarbeit | Participation]]).

This website is based on wiki software. If you should need further instructions on how to use the software pls see the respective [//meta.wikimedia.org/wiki/Help:Contents manual]. Overall project information, e.g. project objectives and procedures, will be published both in German and in English. All further documents, especially documentations, will only be published in English.

== Content ==

* [[DRV_STRING:Über_DRV_STRING | About DRV STRING]] - Overall describtion of the STRING project
* [http://string.drv.de/mailman/listinfo Public mailing lists] related to STRING
* [[Schemata]] - developed XSD-schemes, documentations und discussion
* [[Releases]] - overview / download of the released versions
* [[Documentation]] - Interface documentation, recommendations for implementation
* [[Use Cases]] - collection of use cases for the interface
* [[Mitarbeit | Participation]] - Usefull information for those interested to join the project and its working environment
* [http://string.drv.de/jira/browse/STRING Ticketsystem] - Our ticket system has public read access
* [http://string.drv.de/license/ License] terms and conditions
* [[Change Requests]] - List of Change Requests and follow-up information
* [[Library:Bibliothek | Library]] - collection of documentations of relevant interface descriptions for the travel industry
* [[Developers Area]] - Area for active in STRING developers

Datei:STRING DRV final.pdf

2021-08-06T06:13:34Z

Althoffm:

Hauptseite

2021-08-06T06:12:25Z

Althoffm:

[[Datei:DRV-Basislogo WEB-mittel.png]]

'''Herzlich Willkommen bei STRING - STandard Reservation Interface Next Generation'''

Dies ist die offizielle Projektseite des DRV STRING-Projektes. Die nachfolgenden Informationen stehen allen Interessierten zur Verfügung, eine Anmeldung für das Lesen der Informationen ist nicht erforderlich. Wenn Sie sich für eine Mitarbeit an diesem Projekt interessieren und Beiträge auf dieser Website kommentieren möchten, ist vorab eine Registrierung erforderlich (siehe [[Mitarbeit]]).

Die Projektseite ist als Wiki angelegt worden. Hinweise zur Benutzung der zugrunde liegenden Software finden Sie im [//meta.wikimedia.org/wiki/Help:Contents Benutzerhandbuch].

Die übergeordneten Projektinformationen zu Projektziel und –ablauf werden sowohl in Deutsch als auch auf Englisch veröffentlicht. Alle weiteren Dokumente, insbesondere Arbeitsdokumente, werden ausschließlich auf Englisch publiziert.
 
 
Abfrage zu Suchfunktionen im Bereich Unterkünfte innerhalb des Buchungsprozesses, '''Rückmeldung bis spätestens 30.09.2018''': [[Medium:Abfrage Unterkunftssuche Booking.docx|Abfrage Unterkunftssuche Booking.docx]] 

== Inhalt ==

* [[DRV_STRING:Über_DRV_STRING | Über DRV STRING]] - Beschreibung des STRING-Projektes (Deutsch/Englisch)
* [http://string.drv.de/mailman/listinfo Öffentliche Mailverteiler] zu STRING
* [[Schemata]] - Die XSD-Schemata, Dokumentation und Diskussion (Englisch)
* [[Releases]] - Übersicht / Download der freigegebenen Versionen (Englisch)
* [[Documentation]] - Dokumentation der Schnittstelle, Empfehlungen zur Umsetzung (Deutsch?/Englisch)
* [[Use Cases]] - Anwendungsfälle für die Schnittstelle (Englisch)
* [[Mitarbeit]] - Hinweise zur Mitarbeit, Arbeitsumgebung, Berechtigungskonzept (Englisch)
* [[Abfragen]] - Abfragen zur Ermittlung von Anforderungen seitens der Reiseveranstalter (Deutsch)
* [http://string.drv.de/jira/browse/STRING Ticketsystem] - Unser Ticketsystem ist öffentlich einsehbar (Englisch)
* [[License | Lizenz-Informationen]] für die Schnittstelle (Englisch)
* [[Change Requests]] - Verzeichnis der Change Requests (Englisch)
* [[Library:Bibliothek | Bibliothek]] - Interne Schnittstellen-Bibliothek (Englisch)
* [[Developers Area| Entwicklerbereich]] - Bereich für aktive STRING-Entwickler

'''Welcome to STRING - STandard Reservation Interface Next Generation'''

This is the official project wiki for the DRV STRING project. All information are available to everyone interested in the project, no pre-registration neccessary. If you would like to actively participate in the project and want to be able to comment on articles published on this wiki, please register (please see [[Mitarbeit | Participation]]).

This website is based on wiki software. If you should need further instructions on how to use the software pls see the respective [//meta.wikimedia.org/wiki/Help:Contents manual]. Overall project information, e.g. project objectives and procedures, will be published both in German and in English. All further documents, especially documentations, will only be published in English.

== Content ==

* [[DRV_STRING:Über_DRV_STRING | About DRV STRING]] - Overall describtion of the STRING project
* [http://string.drv.de/mailman/listinfo Public mailing lists] related to STRING
* [[Schemata]] - developed XSD-schemes, documentations und discussion
* [[Releases]] - overview / download of the released versions
* [[Documentation]] - Interface documentation, recommendations for implementation
* [[Use Cases]] - collection of use cases for the interface
* [[Mitarbeit | Participation]] - Usefull information for those interested to join the project and its working environment
* [http://string.drv.de/jira/browse/STRING Ticketsystem] - Our ticket system has public read access
* [http://string.drv.de/license/ License] terms and conditions
* [[Change Requests]] - List of Change Requests and follow-up information
* [[Library:Bibliothek | Library]] - collection of documentations of relevant interface descriptions for the travel industry
* [[Developers Area]] - Area for active in STRING developers

Datei:LTA OTA Specification V2.0.1.pdf

2019-12-19T08:29:22Z

Althoffm:

Use Cases

2019-10-21T06:09:55Z

Althoffm:

[[Kategorie:UseCases]]

This is the main page for our collection of use cases.

To add a new one please insert a suitable name and then click ''"Create Use Case"'' to launch a new page for your entry. Then fill in the missing sections of the template.

<createarticle>
type=createarticle
preload=Template:UseCases
buttonlabel=Create Use Case
align=left
default=Please add title
</createarticle>

== Why Use Cases? ==

We aim to create a complete replacement for all transactions which are handled by STADIS and many external extensions today. To do so we have to find out which transactions are needed and what kind of data is exchanged between clients and tour operator systems.

So for a start every action code used today in TOMA-like systems should have at least one assigned use case here (or be deprecated).

The same applies for all proposed extensions of the ''"Anforderungsdefinition"''.

See [[Flight Availability (Gerätevakanz)]] for an example of what we need.

=== Role Definitions ===

- tour operator / airline system

- (supplier for the above)

- CRS / GDS

- client system non-automatic (travel agency)

- client sytem automatic (internet booking engine)

- offer / search system

=== Use Cases by Category ===

==== Flight ====

* [[Flight Availability (Gerätevakanz)]]

*( [[Flugbegriffe]] )

==== Hotel ====
* [[Hotel Availability (Hotelvakanz)]]

* [[Hotel on Request]]

* [[Book an Accommodation]]

==== Package ====

* [[Flight Availability (Gerätevakanz)]]
* [[Package included direct flight, no stops]]
* [[Stops on outbound- and inbound-flight]]

==== RentalCar ====

==== Insurance ====
First Use Case, Booking Request and Booking Response by LTA, 20.05.2019: [[Medium:190522 use case insurance.pdf|190522 use case insurance.pdf]] 
Use Case 1a by LTA, replaces first use case of 20.05.2019, 19.06.2019: [[Medium: 20190619 Use Case 1a travel insurance separate to an existing travel booking.xlsx]] 
REVISED Use Case 1a by LTA, replaces version of 19.06.2019, 24.09.2019: [[Medium: 20190924 Use Case 1a travel insurance separate to an existing travel booking.xlsx]] 
Use Case 1b by LTA, 19.06.2019 (booking of package and insurance via same platform, so that booking data can be transferred to insurance booking after initial package booking: [[Medium:20190619 Use Case 1b Integration into a travel booking.xlsx]] 
Use Case 1c by LTA, 19.06.2019, including additional steps A to C: [[Medium:20190619 Use Case 1c travel insurance without an existing travel booking.xlsx]] 
Protokoll Versicherungsmeeting, 26.07.2019, Berlin: [[Medium:STRING Versicherung 260719.pdf|STRING Versicherung 260719.pdf]] 
* [[Insurance tariffs not total price purchased (Ameropa)]] 

==== Cruise ====
Protokoll Meeting TUI Cruises, 08.08.2019, Hamburg: [[Medium:STRING Cruise 080819.pdf|STRING Cruise 080819.pdf]] 

==== Handling: Booking administration ====

* [[Message Queue]]
* [[Handling-Preferences (Kundenwünsche)]]
* [[One-entry-code for a complete package]]

==== Handling: Payment ====
==== Train ====
In the first step, it should initially be possible to book train journeys within Germany. In the following step also cross-border train journeys.

The display (D, DR etc.) and cancellation (S, SA, SR etc.) actions should be possible.

* [[Train Availability (Bahnauskunft)]]

* [[Book an Train trip]]

* [[Book an Seat only]]

=== Use Cases by Action ===

The STRING interface will not use action codes but request/response pairs. We aim however to support all methods of the old interfaces we're superseding as long as they are not deprecated or applicable.

Several action codes might be linked to the same use case when their functionality will be bundled into the same request/response.

==== Actions for the Display of Examples ====

* B?

==== Vacancies ====
[[Graphical seating plan for the vacancy of tickets]]
* '''G''' [[Flight Availability (Gerätevakanz)]]
* GF
* GK
* GZ
* '''H''' [[Hotel Availability (Hotelvakanz)]]
[[Searching for a hotel using a map]]

[[Show nearby hotels first]]
* HF
* HK
* C
* CF
* CK

==== Actions for the Differentiation of an Offer ====

* HW
* KW
[[Detailed Customer Preferences (Kundenwünsche)]]
* HO
* HU
* MW
* KG/VA

==== Booking Actions ====

* B
[[Book_single_Flight|Book Flight]]

[[Shopping cart functionality]]

[[Using references to search results in Book]]

[[Traveler Name Fields without character limitation]]

[[Check for completeness of data]]

[[Choice of the format of the travel documents]]

[[Upselling function of additional services]]

* BC
[[Display booking-relevant information before booking]]
* BR
* BA
[[Deliver variants of occupancy possibilities]]

[[Deliver board variants]]

[[Calculate senior discount]]
* BK
* BQ
* BW
* BM
* BT
* O
[[Renew options by customer]]
* OC
* OR
* OA
* OQ
* BS
* RF
* PB
* RS
* CM
* ZL
* ZW
* KV
* KS

==== Actions for the Display of a Reservation ====

* D
* DR
* CR

==== Actions for the Modification of a Reservation ====

* F
* FR
* OV
* U
* UR
* UC
* UQ
* S
* SR
* SA
* W

==== Payment Actions ====
[[Later modifications of payment information (credit card)]]
* DI
* DZ
* KU
* KX
* KE

==== Actions for Printing of Vouchers ====

* RA

==== Display of Reservation Lists ====

* V

==== Information ====

* I
* IP
* BI
* DD
* AI
* AG

==== Test Actions ====

* TB
* TD
* TF
* TO
* TS
* TU

==== Service Actions ====

* +/- (Paging)
* ?

=== Use Cases by Reference to Request Document ===

Datei:20190924 Use Case 1a travel insurance separate to an existing travel booking.xlsx

2019-10-21T06:08:45Z

Althoffm:

Use Cases

2019-08-26T09:53:57Z

Althoffm: Protokoll TUI Cruises, 08.08.2019

[[Kategorie:UseCases]]

This is the main page for our collection of use cases.

To add a new one please insert a suitable name and then click ''"Create Use Case"'' to launch a new page for your entry. Then fill in the missing sections of the template.

<createarticle>
type=createarticle
preload=Template:UseCases
buttonlabel=Create Use Case
align=left
default=Please add title
</createarticle>

== Why Use Cases? ==

We aim to create a complete replacement for all transactions which are handled by STADIS and many external extensions today. To do so we have to find out which transactions are needed and what kind of data is exchanged between clients and tour operator systems.

So for a start every action code used today in TOMA-like systems should have at least one assigned use case here (or be deprecated).

The same applies for all proposed extensions of the ''"Anforderungsdefinition"''.

See [[Flight Availability (Gerätevakanz)]] for an example of what we need.

=== Role Definitions ===

- tour operator / airline system

- (supplier for the above)

- CRS / GDS

- client system non-automatic (travel agency)

- client sytem automatic (internet booking engine)

- offer / search system

=== Use Cases by Category ===

==== Flight ====

* [[Flight Availability (Gerätevakanz)]]

*( [[Flugbegriffe]] )

==== Hotel ====
* [[Hotel Availability (Hotelvakanz)]]

* [[Hotel on Request]]

* [[Book an Accommodation]]

==== Package ====

* [[Flight Availability (Gerätevakanz)]]
* [[Package included direct flight, no stops]]
* [[Stops on outbound- and inbound-flight]]

==== RentalCar ====

==== Insurance ====
First Use Case, Booking Request and Booking Response by LTA, 20.05.2019: [[Medium:190522 use case insurance.pdf|190522 use case insurance.pdf]] 
Use Case 1a by LTA, replaces first use case of 20.05.2019, 19.06.2019: [[Medium: 20190619 Use Case 1a travel insurance separate to an existing travel booking.xlsx]] 
Use Case 1b by LTA, 19.06.2019 (booking of package and insurance via same platform, so that booking data can be transferred to insurance booking after initial package booking: [[Medium:20190619 Use Case 1b Integration into a travel booking.xlsx]] 
Use Case 1c by LTA, 19.06.2019, including additional steps A to C: [[Medium:20190619 Use Case 1c travel insurance without an existing travel booking.xlsx]] 
Protokoll Versicherungsmeeting, 26.07.2019, Berlin: [[Medium:STRING Versicherung 260719.pdf|STRING Versicherung 260719.pdf]] 
* [[Insurance tariffs not total price purchased (Ameropa)]] 

==== Cruise ====
Protokoll Meeting TUI Cruises, 08.08.2019, Hamburg: [[Medium:STRING Cruise 080819.pdf|STRING Cruise 080819.pdf]] 

==== Handling: Booking administration ====

* [[Message Queue]]
* [[Handling-Preferences (Kundenwünsche)]]
* [[One-entry-code for a complete package]]

==== Handling: Payment ====
==== Train ====
In the first step, it should initially be possible to book train journeys within Germany. In the following step also cross-border train journeys.

The display (D, DR etc.) and cancellation (S, SA, SR etc.) actions should be possible.

* [[Train Availability (Bahnauskunft)]]

* [[Book an Train trip]]

* [[Book an Seat only]]

=== Use Cases by Action ===

The STRING interface will not use action codes but request/response pairs. We aim however to support all methods of the old interfaces we're superseding as long as they are not deprecated or applicable.

Several action codes might be linked to the same use case when their functionality will be bundled into the same request/response.

==== Actions for the Display of Examples ====

* B?

==== Vacancies ====
[[Graphical seating plan for the vacancy of tickets]]
* '''G''' [[Flight Availability (Gerätevakanz)]]
* GF
* GK
* GZ
* '''H''' [[Hotel Availability (Hotelvakanz)]]
[[Searching for a hotel using a map]]

[[Show nearby hotels first]]
* HF
* HK
* C
* CF
* CK

==== Actions for the Differentiation of an Offer ====

* HW
* KW
[[Detailed Customer Preferences (Kundenwünsche)]]
* HO
* HU
* MW
* KG/VA

==== Booking Actions ====

* B
[[Book_single_Flight|Book Flight]]

[[Shopping cart functionality]]

[[Using references to search results in Book]]

[[Traveler Name Fields without character limitation]]

[[Check for completeness of data]]

[[Choice of the format of the travel documents]]

[[Upselling function of additional services]]

* BC
[[Display booking-relevant information before booking]]
* BR
* BA
[[Deliver variants of occupancy possibilities]]

[[Deliver board variants]]

[[Calculate senior discount]]
* BK
* BQ
* BW
* BM
* BT
* O
[[Renew options by customer]]
* OC
* OR
* OA
* OQ
* BS
* RF
* PB
* RS
* CM
* ZL
* ZW
* KV
* KS

==== Actions for the Display of a Reservation ====

* D
* DR
* CR

==== Actions for the Modification of a Reservation ====

* F
* FR
* OV
* U
* UR
* UC
* UQ
* S
* SR
* SA
* W

==== Payment Actions ====
[[Later modifications of payment information (credit card)]]
* DI
* DZ
* KU
* KX
* KE

==== Actions for Printing of Vouchers ====

* RA

==== Display of Reservation Lists ====

* V

==== Information ====

* I
* IP
* BI
* DD
* AI
* AG

==== Test Actions ====

* TB
* TD
* TF
* TO
* TS
* TU

==== Service Actions ====

* +/- (Paging)
* ?

=== Use Cases by Reference to Request Document ===

Datei:STRING Cruise 080819.pdf

2019-08-26T09:53:23Z

Althoffm:

Use Cases

2019-08-26T09:52:06Z

Althoffm: Protokoll Versicherungsworkshop, 26.07.2019

[[Kategorie:UseCases]]

This is the main page for our collection of use cases.

To add a new one please insert a suitable name and then click ''"Create Use Case"'' to launch a new page for your entry. Then fill in the missing sections of the template.

<createarticle>
type=createarticle
preload=Template:UseCases
buttonlabel=Create Use Case
align=left
default=Please add title
</createarticle>

== Why Use Cases? ==

We aim to create a complete replacement for all transactions which are handled by STADIS and many external extensions today. To do so we have to find out which transactions are needed and what kind of data is exchanged between clients and tour operator systems.

So for a start every action code used today in TOMA-like systems should have at least one assigned use case here (or be deprecated).

The same applies for all proposed extensions of the ''"Anforderungsdefinition"''.

See [[Flight Availability (Gerätevakanz)]] for an example of what we need.

=== Role Definitions ===

- tour operator / airline system

- (supplier for the above)

- CRS / GDS

- client system non-automatic (travel agency)

- client sytem automatic (internet booking engine)

- offer / search system

=== Use Cases by Category ===

==== Flight ====

* [[Flight Availability (Gerätevakanz)]]

*( [[Flugbegriffe]] )

==== Hotel ====
* [[Hotel Availability (Hotelvakanz)]]

* [[Hotel on Request]]

* [[Book an Accommodation]]

==== Package ====

* [[Flight Availability (Gerätevakanz)]]
* [[Package included direct flight, no stops]]
* [[Stops on outbound- and inbound-flight]]

==== RentalCar ====

==== Insurance ====
First Use Case, Booking Request and Booking Response by LTA, 20.05.2019: [[Medium:190522 use case insurance.pdf|190522 use case insurance.pdf]] 
Use Case 1a by LTA, replaces first use case of 20.05.2019, 19.06.2019: [[Medium: 20190619 Use Case 1a travel insurance separate to an existing travel booking.xlsx]] 
Use Case 1b by LTA, 19.06.2019 (booking of package and insurance via same platform, so that booking data can be transferred to insurance booking after initial package booking: [[Medium:20190619 Use Case 1b Integration into a travel booking.xlsx]] 
Use Case 1c by LTA, 19.06.2019, including additional steps A to C: [[Medium:20190619 Use Case 1c travel insurance without an existing travel booking.xlsx]] 
Protokoll Versicherungsmeeting, 26.07.2019, Berlin: [[Medium:STRING Versicherung 260719.pdf|STRING Versicherung 260719.pdf]] 
* [[Insurance tariffs not total price purchased (Ameropa)]] 

==== Cruise ====
==== Handling: Booking administration ====

* [[Message Queue]]
* [[Handling-Preferences (Kundenwünsche)]]
* [[One-entry-code for a complete package]]

==== Handling: Payment ====
==== Train ====
In the first step, it should initially be possible to book train journeys within Germany. In the following step also cross-border train journeys.

The display (D, DR etc.) and cancellation (S, SA, SR etc.) actions should be possible.

* [[Train Availability (Bahnauskunft)]]

* [[Book an Train trip]]

* [[Book an Seat only]]

=== Use Cases by Action ===

The STRING interface will not use action codes but request/response pairs. We aim however to support all methods of the old interfaces we're superseding as long as they are not deprecated or applicable.

Several action codes might be linked to the same use case when their functionality will be bundled into the same request/response.

==== Actions for the Display of Examples ====

* B?

==== Vacancies ====
[[Graphical seating plan for the vacancy of tickets]]
* '''G''' [[Flight Availability (Gerätevakanz)]]
* GF
* GK
* GZ
* '''H''' [[Hotel Availability (Hotelvakanz)]]
[[Searching for a hotel using a map]]

[[Show nearby hotels first]]
* HF
* HK
* C
* CF
* CK

==== Actions for the Differentiation of an Offer ====

* HW
* KW
[[Detailed Customer Preferences (Kundenwünsche)]]
* HO
* HU
* MW
* KG/VA

==== Booking Actions ====

* B
[[Book_single_Flight|Book Flight]]

[[Shopping cart functionality]]

[[Using references to search results in Book]]

[[Traveler Name Fields without character limitation]]

[[Check for completeness of data]]

[[Choice of the format of the travel documents]]

[[Upselling function of additional services]]

* BC
[[Display booking-relevant information before booking]]
* BR
* BA
[[Deliver variants of occupancy possibilities]]

[[Deliver board variants]]

[[Calculate senior discount]]
* BK
* BQ
* BW
* BM
* BT
* O
[[Renew options by customer]]
* OC
* OR
* OA
* OQ
* BS
* RF
* PB
* RS
* CM
* ZL
* ZW
* KV
* KS

==== Actions for the Display of a Reservation ====

* D
* DR
* CR

==== Actions for the Modification of a Reservation ====

* F
* FR
* OV
* U
* UR
* UC
* UQ
* S
* SR
* SA
* W

==== Payment Actions ====
[[Later modifications of payment information (credit card)]]
* DI
* DZ
* KU
* KX
* KE

==== Actions for Printing of Vouchers ====

* RA

==== Display of Reservation Lists ====

* V

==== Information ====

* I
* IP
* BI
* DD
* AI
* AG

==== Test Actions ====

* TB
* TD
* TF
* TO
* TS
* TU

==== Service Actions ====

* +/- (Paging)
* ?

=== Use Cases by Reference to Request Document ===

Use Cases

2019-08-26T09:50:56Z

Althoffm:

[[Kategorie:UseCases]]

This is the main page for our collection of use cases.

To add a new one please insert a suitable name and then click ''"Create Use Case"'' to launch a new page for your entry. Then fill in the missing sections of the template.

<createarticle>
type=createarticle
preload=Template:UseCases
buttonlabel=Create Use Case
align=left
default=Please add title
</createarticle>

== Why Use Cases? ==

We aim to create a complete replacement for all transactions which are handled by STADIS and many external extensions today. To do so we have to find out which transactions are needed and what kind of data is exchanged between clients and tour operator systems.

So for a start every action code used today in TOMA-like systems should have at least one assigned use case here (or be deprecated).

The same applies for all proposed extensions of the ''"Anforderungsdefinition"''.

See [[Flight Availability (Gerätevakanz)]] for an example of what we need.

=== Role Definitions ===

- tour operator / airline system

- (supplier for the above)

- CRS / GDS

- client system non-automatic (travel agency)

- client sytem automatic (internet booking engine)

- offer / search system

=== Use Cases by Category ===

==== Flight ====

* [[Flight Availability (Gerätevakanz)]]

*( [[Flugbegriffe]] )

==== Hotel ====
* [[Hotel Availability (Hotelvakanz)]]

* [[Hotel on Request]]

* [[Book an Accommodation]]

==== Package ====

* [[Flight Availability (Gerätevakanz)]]
* [[Package included direct flight, no stops]]
* [[Stops on outbound- and inbound-flight]]

==== RentalCar ====

==== Insurance ====
First Use Case, Booking Request and Booking Response by LTA, 20.05.2019: [[Medium:190522 use case insurance.pdf|190522 use case insurance.pdf]] 
Use Case 1a by LTA, replaces first use case of 20.05.2019, 19.06.2019: [[Medium: 20190619 Use Case 1a travel insurance separate to an existing travel booking.xlsx]] 
Use Case 1b by LTA, 19.06.2019 (booking of package and insurance via same platform, so that booking data can be transferred to insurance booking after initial package booking: [[Medium:20190619 Use Case 1b Integration into a travel booking.xlsx]] 
Use Case 1c by LTA, 19.06.2019, including additional steps A to C: [[Medium:20190619 Use Case 1c travel insurance without an existing travel booking.xlsx]] 
Protokoll Versicherungsmeeting, 26.07.2019, Berlin: [[Medium:STRING Versicherung 260719.pdf]] 
* [[Insurance tariffs not total price purchased (Ameropa)]] 

==== Cruise ====
==== Handling: Booking administration ====

* [[Message Queue]]
* [[Handling-Preferences (Kundenwünsche)]]
* [[One-entry-code for a complete package]]

==== Handling: Payment ====
==== Train ====
In the first step, it should initially be possible to book train journeys within Germany. In the following step also cross-border train journeys.

The display (D, DR etc.) and cancellation (S, SA, SR etc.) actions should be possible.

* [[Train Availability (Bahnauskunft)]]

* [[Book an Train trip]]

* [[Book an Seat only]]

=== Use Cases by Action ===

The STRING interface will not use action codes but request/response pairs. We aim however to support all methods of the old interfaces we're superseding as long as they are not deprecated or applicable.

Several action codes might be linked to the same use case when their functionality will be bundled into the same request/response.

==== Actions for the Display of Examples ====

* B?

==== Vacancies ====
[[Graphical seating plan for the vacancy of tickets]]
* '''G''' [[Flight Availability (Gerätevakanz)]]
* GF
* GK
* GZ
* '''H''' [[Hotel Availability (Hotelvakanz)]]
[[Searching for a hotel using a map]]

[[Show nearby hotels first]]
* HF
* HK
* C
* CF
* CK

==== Actions for the Differentiation of an Offer ====

* HW
* KW
[[Detailed Customer Preferences (Kundenwünsche)]]
* HO
* HU
* MW
* KG/VA

==== Booking Actions ====

* B
[[Book_single_Flight|Book Flight]]

[[Shopping cart functionality]]

[[Using references to search results in Book]]

[[Traveler Name Fields without character limitation]]

[[Check for completeness of data]]

[[Choice of the format of the travel documents]]

[[Upselling function of additional services]]

* BC
[[Display booking-relevant information before booking]]
* BR
* BA
[[Deliver variants of occupancy possibilities]]

[[Deliver board variants]]

[[Calculate senior discount]]
* BK
* BQ
* BW
* BM
* BT
* O
[[Renew options by customer]]
* OC
* OR
* OA
* OQ
* BS
* RF
* PB
* RS
* CM
* ZL
* ZW
* KV
* KS

==== Actions for the Display of a Reservation ====

* D
* DR
* CR

==== Actions for the Modification of a Reservation ====

* F
* FR
* OV
* U
* UR
* UC
* UQ
* S
* SR
* SA
* W

==== Payment Actions ====
[[Later modifications of payment information (credit card)]]
* DI
* DZ
* KU
* KX
* KE

==== Actions for Printing of Vouchers ====

* RA

==== Display of Reservation Lists ====

* V

==== Information ====

* I
* IP
* BI
* DD
* AI
* AG

==== Test Actions ====

* TB
* TD
* TF
* TO
* TS
* TU

==== Service Actions ====

* +/- (Paging)
* ?

=== Use Cases by Reference to Request Document ===

Datei:STRING Versicherung 260719.pdf

2019-08-26T09:49:39Z

Althoffm:

Use Cases

2019-06-26T05:43:47Z

Althoffm:

[[Kategorie:UseCases]]

This is the main page for our collection of use cases.

To add a new one please insert a suitable name and then click ''"Create Use Case"'' to launch a new page for your entry. Then fill in the missing sections of the template.

<createarticle>
type=createarticle
preload=Template:UseCases
buttonlabel=Create Use Case
align=left
default=Please add title
</createarticle>

== Why Use Cases? ==

We aim to create a complete replacement for all transactions which are handled by STADIS and many external extensions today. To do so we have to find out which transactions are needed and what kind of data is exchanged between clients and tour operator systems.

So for a start every action code used today in TOMA-like systems should have at least one assigned use case here (or be deprecated).

The same applies for all proposed extensions of the ''"Anforderungsdefinition"''.

See [[Flight Availability (Gerätevakanz)]] for an example of what we need.

=== Role Definitions ===

- tour operator / airline system

- (supplier for the above)

- CRS / GDS

- client system non-automatic (travel agency)

- client sytem automatic (internet booking engine)

- offer / search system

=== Use Cases by Category ===

==== Flight ====

* [[Flight Availability (Gerätevakanz)]]

*( [[Flugbegriffe]] )

==== Hotel ====
* [[Hotel Availability (Hotelvakanz)]]

* [[Hotel on Request]]

* [[Book an Accommodation]]

==== Package ====

* [[Flight Availability (Gerätevakanz)]]
* [[Package included direct flight, no stops]]
* [[Stops on outbound- and inbound-flight]]

==== RentalCar ====

==== Insurance ====
First Use Case, Booking Request and Booking Response by LTA, 20.05.2019: [[Medium:190522 use case insurance.pdf|190522 use case insurance.pdf]] 
Use Case 1a by LTA, replaces first use case of 20.05.2019, 19.06.2019: [[Medium: 20190619 Use Case 1a travel insurance separate to an existing travel booking.xlsx]] 
Use Case 1b by LTA, 19.06.2019 (booking of package and insurance via same platform, so that booking data can be transferred to insurance booking after initial package booking: [[Medium:20190619 Use Case 1b Integration into a travel booking.xlsx]] 
Use Case 1c by LTA, 19.06.2019, including additional steps A to C: [[Medium:20190619 Use Case 1c travel insurance without an existing travel booking.xlsx]] 

==== Cruise ====
==== Handling: Booking administration ====

* [[Message Queue]]
* [[Handling-Preferences (Kundenwünsche)]]
* [[One-entry-code for a complete package]]

==== Handling: Payment ====
==== Train ====
In the first step, it should initially be possible to book train journeys within Germany. In the following step also cross-border train journeys.

The display (D, DR etc.) and cancellation (S, SA, SR etc.) actions should be possible.

* [[Train Availability (Bahnauskunft)]]

* [[Book an Train trip]]

* [[Book an Seat only]]

=== Use Cases by Action ===

The STRING interface will not use action codes but request/response pairs. We aim however to support all methods of the old interfaces we're superseding as long as they are not deprecated or applicable.

Several action codes might be linked to the same use case when their functionality will be bundled into the same request/response.

==== Actions for the Display of Examples ====

* B?

==== Vacancies ====
[[Graphical seating plan for the vacancy of tickets]]
* '''G''' [[Flight Availability (Gerätevakanz)]]
* GF
* GK
* GZ
* '''H''' [[Hotel Availability (Hotelvakanz)]]
[[Searching for a hotel using a map]]

[[Show nearby hotels first]]
* HF
* HK
* C
* CF
* CK

==== Actions for the Differentiation of an Offer ====

* HW
* KW
[[Detailed Customer Preferences (Kundenwünsche)]]
* HO
* HU
* MW
* KG/VA

==== Booking Actions ====

* B
[[Book_single_Flight|Book Flight]]

[[Shopping cart functionality]]

[[Using references to search results in Book]]

[[Traveler Name Fields without character limitation]]

[[Check for completeness of data]]

[[Choice of the format of the travel documents]]

[[Upselling function of additional services]]

* BC
[[Display booking-relevant information before booking]]
* BR
* BA
[[Deliver variants of occupancy possibilities]]

[[Deliver board variants]]

[[Calculate senior discount]]
* BK
* BQ
* BW
* BM
* BT
* O
[[Renew options by customer]]
* OC
* OR
* OA
* OQ
* BS
* RF
* PB
* RS
* CM
* ZL
* ZW
* KV
* KS

==== Actions for the Display of a Reservation ====

* D
* DR
* CR

==== Actions for the Modification of a Reservation ====

* F
* FR
* OV
* U
* UR
* UC
* UQ
* S
* SR
* SA
* W

==== Payment Actions ====
[[Later modifications of payment information (credit card)]]
* DI
* DZ
* KU
* KX
* KE

==== Actions for Printing of Vouchers ====

* RA

==== Display of Reservation Lists ====

* V

==== Information ====

* I
* IP
* BI
* DD
* AI
* AG

==== Test Actions ====

* TB
* TD
* TF
* TO
* TS
* TU

==== Service Actions ====

* +/- (Paging)
* ?

=== Use Cases by Reference to Request Document ===

Datei:20190619 Use Case 1c travel insurance without an existing travel booking.xlsx

2019-06-26T05:43:24Z

Althoffm:

Datei:20190619 Use Case 1b Integration into a travel booking.xlsx

2019-06-26T05:41:10Z

Althoffm:

Use Cases

2019-06-26T05:38:21Z

Althoffm:

[[Kategorie:UseCases]]

This is the main page for our collection of use cases.

To add a new one please insert a suitable name and then click ''"Create Use Case"'' to launch a new page for your entry. Then fill in the missing sections of the template.

<createarticle>
type=createarticle
preload=Template:UseCases
buttonlabel=Create Use Case
align=left
default=Please add title
</createarticle>

== Why Use Cases? ==

We aim to create a complete replacement for all transactions which are handled by STADIS and many external extensions today. To do so we have to find out which transactions are needed and what kind of data is exchanged between clients and tour operator systems.

So for a start every action code used today in TOMA-like systems should have at least one assigned use case here (or be deprecated).

The same applies for all proposed extensions of the ''"Anforderungsdefinition"''.

See [[Flight Availability (Gerätevakanz)]] for an example of what we need.

=== Role Definitions ===

- tour operator / airline system

- (supplier for the above)

- CRS / GDS

- client system non-automatic (travel agency)

- client sytem automatic (internet booking engine)

- offer / search system

=== Use Cases by Category ===

==== Flight ====

* [[Flight Availability (Gerätevakanz)]]

*( [[Flugbegriffe]] )

==== Hotel ====
* [[Hotel Availability (Hotelvakanz)]]

* [[Hotel on Request]]

* [[Book an Accommodation]]

==== Package ====

* [[Flight Availability (Gerätevakanz)]]
* [[Package included direct flight, no stops]]
* [[Stops on outbound- and inbound-flight]]

==== RentalCar ====

==== Insurance ====
First Use Case, Booking Request and Booking Response by LTA, 20.05.2019: [[Medium:190522 use case insurance.pdf|190522 use case insurance.pdf]] 
Use Case 1a by LTA, replaces "first use case of 20.05.2019", 19.06.2019: [[Medium: 20190619 Use Case 1a travel insurance separate to an existing travel booking.xlsx]] 
First Use Case, Booking Request and Booking Response by LTA, 20.05.2019: [[Medium:190522 use case insurance.pdf|190522 use case insurance.pdf]] 
First Use Case, Booking Request and Booking Response by LTA, 20.05.2019: [[Medium:190522 use case insurance.pdf|190522 use case insurance.pdf]] 

==== Cruise ====
==== Handling: Booking administration ====

* [[Message Queue]]
* [[Handling-Preferences (Kundenwünsche)]]
* [[One-entry-code for a complete package]]

==== Handling: Payment ====
==== Train ====
In the first step, it should initially be possible to book train journeys within Germany. In the following step also cross-border train journeys.

The display (D, DR etc.) and cancellation (S, SA, SR etc.) actions should be possible.

* [[Train Availability (Bahnauskunft)]]

* [[Book an Train trip]]

* [[Book an Seat only]]

=== Use Cases by Action ===

The STRING interface will not use action codes but request/response pairs. We aim however to support all methods of the old interfaces we're superseding as long as they are not deprecated or applicable.

Several action codes might be linked to the same use case when their functionality will be bundled into the same request/response.

==== Actions for the Display of Examples ====

* B?

==== Vacancies ====
[[Graphical seating plan for the vacancy of tickets]]
* '''G''' [[Flight Availability (Gerätevakanz)]]
* GF
* GK
* GZ
* '''H''' [[Hotel Availability (Hotelvakanz)]]
[[Searching for a hotel using a map]]

[[Show nearby hotels first]]
* HF
* HK
* C
* CF
* CK

==== Actions for the Differentiation of an Offer ====

* HW
* KW
[[Detailed Customer Preferences (Kundenwünsche)]]
* HO
* HU
* MW
* KG/VA

==== Booking Actions ====

* B
[[Book_single_Flight|Book Flight]]

[[Shopping cart functionality]]

[[Using references to search results in Book]]

[[Traveler Name Fields without character limitation]]

[[Check for completeness of data]]

[[Choice of the format of the travel documents]]

[[Upselling function of additional services]]

* BC
[[Display booking-relevant information before booking]]
* BR
* BA
[[Deliver variants of occupancy possibilities]]

[[Deliver board variants]]

[[Calculate senior discount]]
* BK
* BQ
* BW
* BM
* BT
* O
[[Renew options by customer]]
* OC
* OR
* OA
* OQ
* BS
* RF
* PB
* RS
* CM
* ZL
* ZW
* KV
* KS

==== Actions for the Display of a Reservation ====

* D
* DR
* CR

==== Actions for the Modification of a Reservation ====

* F
* FR
* OV
* U
* UR
* UC
* UQ
* S
* SR
* SA
* W

==== Payment Actions ====
[[Later modifications of payment information (credit card)]]
* DI
* DZ
* KU
* KX
* KE

==== Actions for Printing of Vouchers ====

* RA

==== Display of Reservation Lists ====

* V

==== Information ====

* I
* IP
* BI
* DD
* AI
* AG

==== Test Actions ====

* TB
* TD
* TF
* TO
* TS
* TU

==== Service Actions ====

* +/- (Paging)
* ?

=== Use Cases by Reference to Request Document ===

Use Cases

2019-06-26T05:33:30Z

Althoffm:

[[Kategorie:UseCases]]

This is the main page for our collection of use cases.

To add a new one please insert a suitable name and then click ''"Create Use Case"'' to launch a new page for your entry. Then fill in the missing sections of the template.

<createarticle>
type=createarticle
preload=Template:UseCases
buttonlabel=Create Use Case
align=left
default=Please add title
</createarticle>

== Why Use Cases? ==

We aim to create a complete replacement for all transactions which are handled by STADIS and many external extensions today. To do so we have to find out which transactions are needed and what kind of data is exchanged between clients and tour operator systems.

So for a start every action code used today in TOMA-like systems should have at least one assigned use case here (or be deprecated).

The same applies for all proposed extensions of the ''"Anforderungsdefinition"''.

See [[Flight Availability (Gerätevakanz)]] for an example of what we need.

=== Role Definitions ===

- tour operator / airline system

- (supplier for the above)

- CRS / GDS

- client system non-automatic (travel agency)

- client sytem automatic (internet booking engine)

- offer / search system

=== Use Cases by Category ===

==== Flight ====

* [[Flight Availability (Gerätevakanz)]]

*( [[Flugbegriffe]] )

==== Hotel ====
* [[Hotel Availability (Hotelvakanz)]]

* [[Hotel on Request]]

* [[Book an Accommodation]]

==== Package ====

* [[Flight Availability (Gerätevakanz)]]
* [[Package included direct flight, no stops]]
* [[Stops on outbound- and inbound-flight]]

==== RentalCar ====

==== Insurance ====
First Use Case, Booking Request and Booking Response by LTA, 20.05.2019: [[Medium:190522 use case insurance.pdf|190522 use case insurance.pdf]] 
Use Case 1a by LTA, replaces "first use case of 20.05.2019", 19.06.2019: [[Medium:20190619 Use Case 1a travel insurance separate to an existing travel booking.xlsx]] 
First Use Case, Booking Request and Booking Response by LTA, 20.05.2019: [[Medium:190522 use case insurance.pdf|190522 use case insurance.pdf]] 
First Use Case, Booking Request and Booking Response by LTA, 20.05.2019: [[Medium:190522 use case insurance.pdf|190522 use case insurance.pdf]] 

==== Cruise ====
==== Handling: Booking administration ====

* [[Message Queue]]
* [[Handling-Preferences (Kundenwünsche)]]
* [[One-entry-code for a complete package]]

==== Handling: Payment ====
==== Train ====
In the first step, it should initially be possible to book train journeys within Germany. In the following step also cross-border train journeys.

The display (D, DR etc.) and cancellation (S, SA, SR etc.) actions should be possible.

* [[Train Availability (Bahnauskunft)]]

* [[Book an Train trip]]

* [[Book an Seat only]]

=== Use Cases by Action ===

The STRING interface will not use action codes but request/response pairs. We aim however to support all methods of the old interfaces we're superseding as long as they are not deprecated or applicable.

Several action codes might be linked to the same use case when their functionality will be bundled into the same request/response.

==== Actions for the Display of Examples ====

* B?

==== Vacancies ====
[[Graphical seating plan for the vacancy of tickets]]
* '''G''' [[Flight Availability (Gerätevakanz)]]
* GF
* GK
* GZ
* '''H''' [[Hotel Availability (Hotelvakanz)]]
[[Searching for a hotel using a map]]

[[Show nearby hotels first]]
* HF
* HK
* C
* CF
* CK

==== Actions for the Differentiation of an Offer ====

* HW
* KW
[[Detailed Customer Preferences (Kundenwünsche)]]
* HO
* HU
* MW
* KG/VA

==== Booking Actions ====

* B
[[Book_single_Flight|Book Flight]]

[[Shopping cart functionality]]

[[Using references to search results in Book]]

[[Traveler Name Fields without character limitation]]

[[Check for completeness of data]]

[[Choice of the format of the travel documents]]

[[Upselling function of additional services]]

* BC
[[Display booking-relevant information before booking]]
* BR
* BA
[[Deliver variants of occupancy possibilities]]

[[Deliver board variants]]

[[Calculate senior discount]]
* BK
* BQ
* BW
* BM
* BT
* O
[[Renew options by customer]]
* OC
* OR
* OA
* OQ
* BS
* RF
* PB
* RS
* CM
* ZL
* ZW
* KV
* KS

==== Actions for the Display of a Reservation ====

* D
* DR
* CR

==== Actions for the Modification of a Reservation ====

* F
* FR
* OV
* U
* UR
* UC
* UQ
* S
* SR
* SA
* W

==== Payment Actions ====
[[Later modifications of payment information (credit card)]]
* DI
* DZ
* KU
* KX
* KE

==== Actions for Printing of Vouchers ====

* RA

==== Display of Reservation Lists ====

* V

==== Information ====

* I
* IP
* BI
* DD
* AI
* AG

==== Test Actions ====

* TB
* TD
* TF
* TO
* TS
* TU

==== Service Actions ====

* +/- (Paging)
* ?

=== Use Cases by Reference to Request Document ===

Datei:20190619 Use Case 1a travel insurance separate to an existing travel booking.xlsx

2019-06-26T05:32:59Z

Althoffm:

Use Cases

2019-06-03T14:21:42Z

Althoffm: 1. Use Case Versicherungen by LTA

[[Kategorie:UseCases]]

This is the main page for our collection of use cases.

To add a new one please insert a suitable name and then click ''"Create Use Case"'' to launch a new page for your entry. Then fill in the missing sections of the template.

<createarticle>
type=createarticle
preload=Template:UseCases
buttonlabel=Create Use Case
align=left
default=Please add title
</createarticle>

== Why Use Cases? ==

We aim to create a complete replacement for all transactions which are handled by STADIS and many external extensions today. To do so we have to find out which transactions are needed and what kind of data is exchanged between clients and tour operator systems.

So for a start every action code used today in TOMA-like systems should have at least one assigned use case here (or be deprecated).

The same applies for all proposed extensions of the ''"Anforderungsdefinition"''.

See [[Flight Availability (Gerätevakanz)]] for an example of what we need.

=== Role Definitions ===

- tour operator / airline system

- (supplier for the above)

- CRS / GDS

- client system non-automatic (travel agency)

- client sytem automatic (internet booking engine)

- offer / search system

=== Use Cases by Category ===

==== Flight ====

* [[Flight Availability (Gerätevakanz)]]

*( [[Flugbegriffe]] )

==== Hotel ====
* [[Hotel Availability (Hotelvakanz)]]

* [[Hotel on Request]]

* [[Book an Accommodation]]

==== Package ====

* [[Flight Availability (Gerätevakanz)]]
* [[Package included direct flight, no stops]]
* [[Stops on outbound- and inbound-flight]]

==== RentalCar ====

==== Insurance ====
First Use Case, Booking Request and Booking Response by LTA, 20.05.2019: [[Medium:190522 use case insurance.pdf|190522 use case insurance.pdf]] 

==== Cruise ====
==== Handling: Booking administration ====

* [[Message Queue]]
* [[Handling-Preferences (Kundenwünsche)]]
* [[One-entry-code for a complete package]]

==== Handling: Payment ====
==== Train ====
In the first step, it should initially be possible to book train journeys within Germany. In the following step also cross-border train journeys.

The display (D, DR etc.) and cancellation (S, SA, SR etc.) actions should be possible.

* [[Train Availability (Bahnauskunft)]]

* [[Book an Train trip]]

* [[Book an Seat only]]

=== Use Cases by Action ===

The STRING interface will not use action codes but request/response pairs. We aim however to support all methods of the old interfaces we're superseding as long as they are not deprecated or applicable.

Several action codes might be linked to the same use case when their functionality will be bundled into the same request/response.

==== Actions for the Display of Examples ====

* B?

==== Vacancies ====
[[Graphical seating plan for the vacancy of tickets]]
* '''G''' [[Flight Availability (Gerätevakanz)]]
* GF
* GK
* GZ
* '''H''' [[Hotel Availability (Hotelvakanz)]]
[[Searching for a hotel using a map]]

[[Show nearby hotels first]]
* HF
* HK
* C
* CF
* CK

==== Actions for the Differentiation of an Offer ====

* HW
* KW
[[Detailed Customer Preferences (Kundenwünsche)]]
* HO
* HU
* MW
* KG/VA

==== Booking Actions ====

* B
[[Book_single_Flight|Book Flight]]

[[Shopping cart functionality]]

[[Using references to search results in Book]]

[[Traveler Name Fields without character limitation]]

[[Check for completeness of data]]

[[Choice of the format of the travel documents]]

[[Upselling function of additional services]]

* BC
[[Display booking-relevant information before booking]]
* BR
* BA
[[Deliver variants of occupancy possibilities]]

[[Deliver board variants]]

[[Calculate senior discount]]
* BK
* BQ
* BW
* BM
* BT
* O
[[Renew options by customer]]
* OC
* OR
* OA
* OQ
* BS
* RF
* PB
* RS
* CM
* ZL
* ZW
* KV
* KS

==== Actions for the Display of a Reservation ====

* D
* DR
* CR

==== Actions for the Modification of a Reservation ====

* F
* FR
* OV
* U
* UR
* UC
* UQ
* S
* SR
* SA
* W

==== Payment Actions ====
[[Later modifications of payment information (credit card)]]
* DI
* DZ
* KU
* KX
* KE

==== Actions for Printing of Vouchers ====

* RA

==== Display of Reservation Lists ====

* V

==== Information ====

* I
* IP
* BI
* DD
* AI
* AG

==== Test Actions ====

* TB
* TD
* TF
* TO
* TS
* TU

==== Service Actions ====

* +/- (Paging)
* ?

=== Use Cases by Reference to Request Document ===

Datei:190522 use case insurance.pdf

2019-06-03T14:17:26Z

Althoffm:

Abfragen

2018-09-11T09:30:30Z

Althoffm:

Auf dieser Seite werden Abfragen veröffentlicht, bei denen Reiseveranstalter sowie Software-Häuser um Rückmeldungen zu bestehenden Anforderungen gebeten werden. Die Ergebnisse der Abfragen fliessen in die laufende Projektarbeit ein. Bitte beachten Sie die jeweils pro Abfrage angegeben, verbindlichen Endtermine für die Rückmeldung an die Projektleitung bzw. den DRV.
 
 
Abfrage zu Suchfunktionen im Bereich Unterkünfte innerhalb des Buchungsprozesses, '''Rückmeldung bis spätestens 30.09.2018''': [[Medium:Abfrage Unterkunftssuche Booking.docx|Abfrage Unterkunftssuche Booking.docx]]

Abfragen

2018-09-11T09:29:52Z

Althoffm:

Auf dieser Seite werden Abfragen veröffentlicht, bei denen Reiseveranstalter sowie Software-Häuser um Rückmeldungen zu bestehenden Anforderungen gebeten werden. Die Ergebnisse der Abfragen fliessen in die laufende Projektarbeit ein. Bitte beachten Sie die jeweils pro Abfrage angegeben, verbindlichen Endtermine für die Rückmeldung an die Projektleitung bzw. den DRV.
 
 
Abfrage zu Suchfunktionen im Bereich Unterkünfte innerhalb des Buchungsprozesses, Rückmeldung bis spätestens 30.09.2018: [[Medium:Abfrage Unterkunftssuche Booking.docx|Abfrage Unterkunftssuche Booking.docx]]

Datei:Abfrage Unterkunftssuche Booking.docx

2018-09-11T09:29:33Z

Althoffm:

Abfragen

2018-09-11T09:25:33Z

Althoffm: Die Seite wurde neu angelegt: „Auf dieser Seite werden Abfragen veröffentlicht, bei denen Reiseveranstalter sowie Software-Häuser um Rückmeldungen zu bestehenden Anforderungen gebeten wer…“

Hauptseite

2018-09-11T09:24:21Z

Althoffm:

[[Datei:DRV-Basislogo WEB-mittel.png]]

'''Herzlich Willkommen bei STRING - STandard Reservation Interface Next Generation'''

Dies ist die offizielle Projektseite des DRV STRING-Projektes. Die nachfolgenden Informationen stehen allen Interessierten zur Verfügung, eine Anmeldung für das Lesen der Informationen ist nicht erforderlich. Wenn Sie sich für eine Mitarbeit an diesem Projekt interessieren und Beiträge auf dieser Website kommentieren möchten, ist vorab eine Registrierung erforderlich (siehe [[Mitarbeit]]).

Die Projektseite ist als Wiki angelegt worden. Hinweise zur Benutzung der zugrunde liegenden Software finden Sie im [//meta.wikimedia.org/wiki/Help:Contents Benutzerhandbuch].

Die übergeordneten Projektinformationen zu Projektziel und –ablauf werden sowohl in Deutsch als auch auf Englisch veröffentlicht. Alle weiteren Dokumente, insbesondere Arbeitsdokumente, werden ausschließlich auf Englisch publiziert.

== Inhalt ==

* [[DRV_STRING:Über_DRV_STRING | Über DRV STRING]] - Beschreibung des STRING-Projektes (Deutsch/Englisch)
* [http://string.drv.de/mailman/listinfo Öffentliche Mailverteiler] zu STRING
* [[Schemata]] - Die XSD-Schemata, Dokumentation und Diskussion (Englisch)
* [[Releases]] - Übersicht / Download der freigegebenen Versionen (Englisch)
* [[Documentation]] - Dokumentation der Schnittstelle, Empfehlungen zur Umsetzung (Deutsch?/Englisch)
* [[Use Cases]] - Anwendungsfälle für die Schnittstelle (Englisch)
* [[Mitarbeit]] - Hinweise zur Mitarbeit, Arbeitsumgebung, Berechtigungskonzept (Englisch)
* [[Abfragen]] - Abfragen zur Ermittlung von Anforderungen seitens der Reiseveranstalter (Deutsch)
* [http://string.drv.de/jira/browse/STRING Ticketsystem] - Unser Ticketsystem ist öffentlich einsehbar (Englisch)
* [[License | Lizenz-Informationen]] für die Schnittstelle (Englisch)
* [[Change Requests]] - Verzeichnis der Change Requests (Englisch)
* [[Library:Bibliothek | Bibliothek]] - Interne Schnittstellen-Bibliothek (Englisch)

'''Welcome to STRING - STandard Reservation Interface Next Generation'''

This is the official project wiki for the DRV STRING project. All information are available to everyone interested in the project, no pre-registration neccessary. If you would like to actively participate in the project and want to be able to comment on articles published on this wiki, please register (please see [[Mitarbeit | Participation]]).

This website is based on wiki software. If you should need further instructions on how to use the software pls see the respective [//meta.wikimedia.org/wiki/Help:Contents manual]. Overall project information, e.g. project objectives and procedures, will be published both in German and in English. All further documents, especially documentations, will only be published in English.

== Content ==

* [[DRV_STRING:Über_DRV_STRING | About DRV STRING]] - Overall describtion of the STRING project
* [http://string.drv.de/mailman/listinfo Public mailing lists] related to STRING
* [[Schemata]] - developed XSD-schemes, documentations und discussion
* [[Releases]] - overview / download of the released versions
* [[Documentation]] - Interface documentation, recommendations for implementation
* [[Use Cases]] - collection of use cases for the interface
* [[Mitarbeit | Participation]] - Usefull information for those interested to join the project and its working environment
* [http://string.drv.de/jira/browse/STRING Ticketsystem] - Our ticket system has public read access
* [http://string.drv.de/license/ License] terms and conditions
* [[Change Requests]] - List of Change Requests and follow-up information
* [[Library:Bibliothek | Library]] - collection of documentations of relevant interface describtions for the travel industry

Mitarbeit

2018-09-03T07:00:46Z

Althoffm:

'''Getting Involved'''

The STRING project is generally open to everyone interested in participating the process of developing a new standard for bookings in the travel industry. Therefore this wiki and its information are open to the public.

The project has several working and decision making levels. The highest institution within this project is the Steering Committee. It consists of the current board members of the users of the DRV data standard and is led by the DRV. Members of the Steering Committee are representatives from the following companies:

* Ameropa
* DER Touristik
* FTI
* Olimar
* Peakwork
* Thomas Cook
* TravelTainment
* Travelport
* TUI

The project is led by the DRV and MC Management Consulting. Amadeus, Bewotec and traffics have designated further employees to support this project in order to develop the required XSD-schemes. This project team strongly cooperates with an expert group. Experts are members of the tour operators represented in the Steering Committee.

Nevertheless the project team shares its information with the public and would highly appreciate an industry-wide discussion of the projects intermediate and final results on this platform. Therefore all relevant project information published within this wiki are fully accessable to the public, everyone interested can inform him- or herself about the current status of development.

If you would like to actively accompany the project development and support the project team by discussing published results, pls send a short application request including your name, company, working position and eMail-address to [mailto:registration@string.drv.de registration@string.drv.de]. You will then get access data. Please keep in mind: access will only be provided to individuals, not to overall companies. If needed you can of course have several accounts per company. Please consider: all comments published on this platform will always show the author and authors are fully responsible for the content published with their account. Therefore please handle your access data very carefully. In case of misuse of access the project team has the right to eliminate users from this platform (e.g. use of foul language).

Participation can take place on three different levels:
Level 1: participation via the project wiki, e.g. bei completing questionnaires within the project and by discussing results within the wiki
Level 2: membership within the expert group. This requires at least one dedicated representative of either a tour operator or its it provider, meetings are held every two months approximately.
Level 3: prototyping partner, implementing one or numerous releases within the current project to test the functionality provided. This role can be covered by other representatives of a tour operator or its it provider than the expert group members.

If you would like to gain more information on how to participate pls do not hesitate to contact the head of project, Mr Michael Althoff via eMail: [mailto:Michael.Althoff@mc-gmbh.de Michael.Althoff@mc-gmbh.de]

For more Information please see [[Berechtigungskonzept]].

Releases

2017-09-21T14:48:05Z

Althoffm:

Releases

2017-05-16T12:34:07Z

Althoffm:

== Development Releases ==

* [[Release 0.1]] - first common release containing unmerged collections of flight / accomodation elements

* [[Release 0.2]] - second release containing merges of 0.1

* [[Release 0.3]] - third release

* [[Release 0.4]] - fourth release
Ergebnisse 4. Expertenworkshop zu Release 0.4, 31. März 2017: [[Medium:Ergebnisse Expertenworkshop 310317.pdf|Ergebnisse Expertenworkshop 310317.pdf]] 

* [[Release 0.5]] - fifth release containing a first attempt at a WSDL
Ergebnisse 5. Expertenworkshop zu Release 0.5, 10. Mai 2017: [[Medium:Ergebnisse Expertenworkshop 100517.pdf|Ergebnisse Expertenworkshop 100517.pdf]] 

Erhebung zu ausgewählten Anforderungen zur Vorbereitung von Release 0.7:
* Für touristische Buchungen erforderliche Zusatzfunktionen im Bereich Flug: [[Medium:Abfrage Flugfunktionen final.pdf|Abfrage Flugfunktionen final.pdf]]
* Verwendung von Kunden- und Zahlkarten mit/ohne Preisrelevanz: [[Medium:Abfrage Kunden und Zahlungskarten final.pdf|Abfrage Kunden und Zahlungskarten final.pdf]]

== Production Releases ==

A first limited production release is planned for the third quarter of 2017.

Releases

2017-05-16T12:33:40Z

Althoffm: Einstellung Erhebungsbögen Flugfunktionen und Zahl-/Kundenkarten

== Development Releases ==

* [[Release 0.1]] - first common release containing unmerged collections of flight / accomodation elements

* [[Release 0.2]] - second release containing merges of 0.1

* [[Release 0.3]] - third release

* [[Release 0.4]] - fourth release
Ergebnisse 4. Expertenworkshop zu Release 0.4, 31. März 2017: [[Medium:Ergebnisse Expertenworkshop 310317.pdf|Ergebnisse Expertenworkshop 310317.pdf]] 

* [[Release 0.5]] - fifth release containing a first attempt at a WSDL
Ergebnisse 5. Expertenworkshop zu Release 0.5, 10. Mai 2017: [[Medium:Ergebnisse Expertenworkshop 100517.pdf|Ergebnisse Expertenworkshop 100517.pdf]] 

Erhebung zu ausgewählten Anforderungen zur Vorbereitung von Release 0.7:
* Für touristische Buchungen erforderliche Zusatzfunktionen im Bereich Flug: [[Medium:AAbfrage Flugfunktionen final.pdf|Abfrage Flugfunktionen final.pdf]]
* Verwendung von Kunden- und Zahlkarten mit/ohne Preisrelevanz: [[Medium:Abfrage Kunden und Zahlungskarten final.pdf|Abfrage Kunden und Zahlungskarten final.pdf]]

== Production Releases ==

A first limited production release is planned for the third quarter of 2017.

Datei:Abfrage Flugfunktionen final.pdf

2017-05-16T12:32:59Z

Althoffm:

Datei:Abfrage Kunden und Zahlungskarten final.pdf

2017-05-16T12:32:21Z

Althoffm: