DRV STRING - Benutzerbeiträge [de]

Release 4.0.1

2025-02-05T13:01:48Z

Bachemj: Die Seite wurde neu angelegt: „This is a release for production use in cruise operator systems. == Downloads == * Archive: [http://string.drv.de/downloads/releases/string-release-4.0.1.zip…“

This is a release for production use in cruise operator systems.

== Downloads ==

* Archive: [http://string.drv.de/downloads/releases/string-release-4.0.1.zip string-release-4.0.1.zip]

* Files: [http://string.drv.de/downloads/releases/release-4.0.1/ Release 4.0.1]

== Notes ==
* type change for the StringBookingList/Booking element

Releases

2025-02-05T13:00:10Z

Bachemj:

== 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

* [[Release 0.5]] - fifth release containing a first attempt at a WSDL

* [[Release 0.6]] - sixth release, confirmation / error handling

* [[Release 0.7]] - seventh release, payment added

* [[Release 0.8]] - eigth release (alterations and amendments to Rel. 0.7; final version for publication to steering committee)

* [[Release 0.9]] - series of release candidates in preparation for 1.0

== Production Releases ==

* [[Release 1.0]] - first "limited production" release as base for showcases and prototypes

* [[Release 1.1]] - the "Mallorca" release with lots of fixes necessary for actual implementation

* [[Release 1.1.1]] - the "Mallorca" release with v1 namespace

* [[Release 1.1.2]] - maintenance release for the implementation test branch

* [[Release 2.0.0]] - the "Cruise" release ready for production in cruise related systems

* [[Release 3.0.0]] - [...]

* [[Release 4.0.0]] - [...]

* [[Release 4.0.1]] - small fixes for BookingList

Release 4.0.0

2024-08-08T12:15:31Z

This is a release for production use in cruise operator systems.

== Downloads ==

* Archive: [http://string.drv.de/downloads/releases/string-release-4.0.0.zip string-release-4.0.0.zip]

* Files: [http://string.drv.de/downloads/releases/release-4.0.0/ Release 4.0.0]

== Notes ==

Releases

2024-08-08T12:14:32Z

Bachemj: Release 4

Release 3.0.0

2023-10-30T15:54:15Z

Bachemj: 3

This is a release for production use in cruise operator systems.

== Downloads ==

* Archive: [http://string.drv.de/downloads/releases/string-release-3.0.0.zip string-release-3.0.0.zip]

* Files: [http://string.drv.de/downloads/releases/release-3.0.0/ Release 3.0.0]

== Notes ==

Releases

2023-10-30T15:53:37Z

Bachemj: 3

Hauptseite

2023-02-24T02:57:40Z

Bachemj:

[[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)
* [[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

Hauptseite

2023-02-24T02:54:02Z

Bachemj: Link zu Jira geändert

[[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)
* [[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/boards/2 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/boards/2 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

Snapshots

2022-11-09T16:38:05Z

Bachemj: Die Seite wurde neu angelegt: „[http://string.drv.de/downloads/snapshots/ The snapshot area] collects development archives created for each revision / commit on a daily basis. Use at your ow…“

[http://string.drv.de/downloads/snapshots/ The snapshot area] collects development archives created for each revision / commit on a daily basis. Use at your own risk.

Hauptseite

2022-11-09T16:36:25Z

Bachemj: Snapshots section

[[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)
* [[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)
* [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
* [[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
* [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

Release 2.0.0

2021-04-01T08:55:35Z

This is a release for production use in cruise operator systems.

== Downloads ==

* Archive: [http://string.drv.de/downloads/releases/string-release-2.0.0.zip string-release-2.0.0.zip]

* Files: [http://string.drv.de/downloads/releases/release-2.0.0/ Release 2.0.0]

== Notes ==

No joke.

Releases

2021-04-01T08:53:37Z

Bachemj:

Release 1.1.2

2020-02-04T15:39:38Z

Bachemj: Die Seite wurde neu angelegt: „This is a maintenance release for the implementation test branch. == Downloads == * Archive: [http://string.drv.de/downloads/releases/string-release-1.1.2.zi…“

This is a maintenance release for the implementation test branch.

== Downloads ==

* Archive: [http://string.drv.de/downloads/releases/string-release-1.1.2.zip string-release-1.1.2.zip]

* Files: [http://string.drv.de/downloads/releases/release-1.1.2/ Release 1.1.2]

== Notes ==

We still consider this a development release for testing purposes but encourage implementation to get feedback for production in v2.

Releases

2020-02-04T15:38:21Z

Bachemj: /* Production Releases */

Releases

2020-02-04T15:38:00Z

Bachemj: 1.1.2

== 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

* [[Release 0.5]] - fifth release containing a first attempt at a WSDL

* [[Release 0.6]] - sixth release, confirmation / error handling

* [[Release 0.7]] - seventh release, payment added

* [[Release 0.8]] - eigth release (alterations and amendments to Rel. 0.7; final version for publication to steering committee)

* [[Release 0.9]] - series of release candidates in preparation for 1.0

== Production Releases ==

* [[Release 1.0]] - first "limited production" release as base for showcases and prototypes

* [[Release 1.1]] - the "Mallorca" release with lots of fixes necessary for actual implementation

* [[Release 1.1.1]] - the "Mallorca" release with v1 namespace

* [[Release 1.1.1]] - maintenance release for the implementation test branch

Datei:Drvws xsd-1.11.0.zip

2020-01-16T14:17:58Z

Bachemj: DRV-Abfragelogik 1.11

DRV-Abfragelogik 1.11

Datei:DRV-Abfrageschnittstelle Realisierung 2019-10-23 DE.pdf

2020-01-16T14:16:50Z

Bachemj: Doku DRV-Abfragelogik

Doku DRV-Abfragelogik

Datei:OTA LTA.WSDL.zip

2020-01-03T11:37:11Z

Bachemj: LTA / OTA WSDL

LTA / OTA WSDL

Datei:LTA OTA Specification V2.0.1.pdf

2020-01-03T11:33:36Z

Bachemj: Bachemj lud eine neue Version von Datei:LTA OTA Specification V2.0.1.pdf hoch

Releases

2019-12-19T12:45:07Z

Bachemj:

Releases

2019-12-19T12:43:08Z

Bachemj:

== 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

* [[Release 0.5]] - fifth release containing a first attempt at a WSDL

* [[Release 0.6]] - sixth release, confirmation / error handling

* [[Release 0.7]] - seventh release, payment added

* [[Release 0.8]] - eigth release (alterations and amendments to Rel. 0.7; final version for publication to steering committee)

* [[Release 0.9]] - series of release candidates in preparation for 1.0

== Production Releases ==

* [[Release 1.0.0]] - first "limited production" release as base for showcases and prototypes

* [[Release 1.1.0]] - the "Mallorca" release with lots of fixes necessary for actual implementation

* [[Release 1.1.1]] - the "Mallorca" release with v1 namespace

OTA-based workflow

2019-12-19T11:13:46Z

Bachemj: Die Seite wurde neu angelegt: „tbd“

tbd

Insurance

2019-12-19T11:13:24Z

Bachemj: Die Seite wurde neu angelegt: „Current OTA-based workflow“

[[OTA-based workflow|Current OTA-based workflow]]

Documentation

2019-12-19T11:11:50Z

Bachemj:

Documentation main page

* [[Introduction]]

== Central concepts ==

* [[Message Containers and Versioning]]
* [[Authentication]]
* [[Agency System]]
* [[Message Handling]]
* [[Error Messages]]
* [[General Workflows]]
* [[Configuration]]
* [[External Collection of value keys, status codes etc.]]
* [[Use of Identifiers]]

== Queries by category ==

* [[Flights]]
* [[CommonService]]
* [[Accommodation]]
* [[Rental Car]]
* [[Cruise]]
* [[Packages]]
* [[Transfer]]
* [[Insurance]]

== Common topics ==

* [[Price Handling]]
* [[Payment Handling]]

* [[Glossar and Abbreviations]]

* [[XSD Documentation]]

Releases

2019-10-29T14:00:54Z

Bachemj:

Release 1.1.1

2019-10-29T14:00:21Z

Bachemj: Die Seite wurde neu angelegt: „This is the "Mallorca" release of STRING. It contains changes deemed necessary for actual implementation of v1. == Downloads == * Archive: [http://string.drv…“

This is the "Mallorca" release of STRING. It contains changes deemed necessary for actual implementation of v1.

== Downloads ==

* Archive: [http://string.drv.de/downloads/releases/string-release-1.1.1.zip string-release-1.1.1.zip]

* Files: [http://string.drv.de/downloads/releases/release-1.1.1/ Release 1.1.1]

== Notes ==

We still consider this a development release for testing purposes but encourage implementation to get feedback for production in v2.

The namespace of the versioned part has been renamed to v1.

Release 1.1

2019-10-29T13:59:22Z

Bachemj: namespace

This is the "Mallorca" release of STRING. It contains changes deemed necessary for actual implementation of v1.

== Downloads ==

* Archive: [http://string.drv.de/downloads/releases/string-release-1.1.0.zip string-release-1.1.0.zip]

* Files: [http://string.drv.de/downloads/releases/release-1.1.0/ Release 1.1]

== Notes ==

We still consider this a development release for testing purposes but encourage implementation to get feedback for production in v2.

This release has been superseded by 1.1.1 with a fixed namespace.

Release 1.1

2019-10-25T09:03:39Z

This is the "Mallorca" release of STRING. It contains changes deemed necessary for actual implementation of v1.

== Downloads ==

* Archive: [http://string.drv.de/downloads/releases/string-release-1.1.0.zip string-release-1.1.0.zip]

* Files: [http://string.drv.de/downloads/releases/release-1.1.0/ Release 1.1]

== Notes ==

We still consider this a development release for testing purposes but encourage implementation to get feedback for production in v2.

Releases

2019-10-25T09:00:44Z

Bachemj:

External Collection of value keys, status codes etc.

2019-10-18T12:19:21Z

Bachemj:

STRING will avoid to define possible values for elements in enumerations inside the schema files as this leads to validation violations when new values are added within the same version. We decided to collect these values in a central place on the project server alongside the schema definitions where they will be updated as needed.

The rules regarding these definitions are:

* You are supposed to use only values defined by STRING but you are not enforced to do so.
* You should detect unknown values and fail gracefully. Depending on the environment this could mean to just ignore it or to produce a meaningfull error message.
* If you need a new value (that is: you use a value in a communication between two partners already and think it should go into the common definition) please feel free to propose it to the STRING board ''(TODO: add link to documentation about this process)''.

[http://string.drv.de/message/ Messages] and [http://string.drv.de/enum/ Enums] are kept on a public webserver and may be included into automatic build processes.

=== Categories of STRING codes and messages ===

==== Value Keys for Configuration Response ====

{| class="wikitable sortable"
|-
! Key !! Description
|-
| max_travellers || maximum number of travellers in a transaction / booking
|-
| max_services || maximum number of services in a transaction / booking
|-
| [...] || [...]
|}

==== Credit Card Codes ====

{| class="wikitable sortable"
|-
! Key !! Description
|-
| MA || Mastercard (we use only one code of the different ones in circulation)
|-
| VI || Visa
|-
| AX || American Express
|-
| DI || Diner's Club
|-
| [...] || [...]
|}

==== [...] ====

External Collection of value keys, status codes etc.

2019-10-17T11:43:56Z

Bachemj:

STRING will avoid to define possible values for elements in enumerations inside the schema files as this leads to validation violations when new values are added within the same version. We decided to collect these values in a central place on the project server alongside the schema definitions where they will be updated as needed.

The rules regarding these definitions are:

* You are supposed to use only values defined by STRING but you are not enforced to do so.
* You should detect unknown values and fail gracefully. Depending on the environment this could mean to just ignore it or to produce a meaningfull error message.
* If you need a new value (that is: you use a value in a communication between two partners already and think it should go into the common definition) please feel free to propose it to the STRING board ''(TODO: add link to documentation about this process)''.

[http://string.drv.de/message/ Messages] and [http://string.drv.de/enum/ Enums] are kept on a public webserver and may be included into automatic build processes.

=== Categories of STRING codes and messages ===

==== Value Keys for Configuration Response ====

{| class="wikitable sortable"
|-
! Key !! Description
|-
| max_travellers || maximum number of travellers in a transaction / booking
|-
| max_services || maximum number of services in a transaction / booking
|-
| [...] || [...]
|}

==== Credit Card Codes ====

{| class="wikitable sortable"
|-
! Key !! Description
|-
| MA || Mastercard (we use only one code of the different ones in circulation)
|-
| VI || Visa
|-
| AM || American Express
|-
| DI || Diner's Club
|-
| [...] || [...]
|}

==== [...] ====

Error Messages

2019-10-17T10:09:00Z

Bachemj:

Error messages can be sent on three different levels.

== Errors in StringMessage ==

Errors on the outer level include cases like unavailable operators or invalid content. They are not version-specific.

<syntaxhighlight lang="xml">include example here</syntaxhighlight>

== Errors in Content/Payload ==

Errors related to valid requests might be handled "inline" in the matching response if the operator is able to create a response, otherwise an ErrorResponse may be used (<GeneralErrorType> in StringError.xsd).

<syntaxhighlight lang="xml">include example here</syntaxhighlight>

== Errors in Responses ==

The response types have their own error fields for informational messages and non-fatal errors. See the documentation of the [[Documentation|queries by category]].

<syntaxhighlight lang="xml">include example here</syntaxhighlight>

== Standard Error Messages ==

STRING defines a set of standard error messages and matching codes. They are not stored in the XSD schemata but on the STRING web server: [http://string.drv.de/message/ http://string.drv.de/message/errors_$LANG.csv]. We will supply at least English and German versions of these files; other languages might follow later.

Error Messages

2019-10-17T10:03:06Z

Bachemj:

Error Messages

2019-10-17T09:55:42Z

Bachemj:

Error messages can be sent on three different levels.

== Errors in StringMessage ==

Errors on the outer level include cases like unavailable operators or invalid content. They are not version-specific.

== Errors in Content/Payload ==

Errors related to valid requests might be handled "inline" in the matching response if the operator is able to create a response, otherwise an ErrorResponse may be used (<GeneralErrorType> in StringError.xsd).

== Errors in Responses ==

The response types have their own error fields for informational messages and non-fatal errors. See the documentation of the [[Documentation|queries by category]].

Error Messages

2019-10-17T09:54:57Z

Bachemj:

Error messages can be sent on three different levels.

== Errors in StringMessage ==

Errors on the outer level include cases like unavailable operators or invalid content. They are not version-specific.

== Errors in Content/Payload ==

Errors related to valid requests might be handled "inline" in the matching response if the operator is able to create a response, otherwise an ErrorResponse may be used (<GeneralErrorType> in StringError.xsd).

== Errors in Responses ==

The response types have their own error fields for informational messages and non-fatal errors. See the documentation of the [[Documentation|request/response types]].

Message Handling

2019-10-16T10:15:51Z

Bachemj:

The STRING message framework consists of an outer layer (StringMessage) and [[Versioning|version-specific payload messages]]. Most messages are [[Request/Response Pairs|pairs of requests and responses with defined workflows]].

== The StringMessage ==

The outer <StringMessage> contains the operator and agency data to route the message to the operator system and authenticate it as a valid request. [[Authentication|We don't require a specific form of authentication]] as it is implementation-dependent and might be handled on a higher level. The RoutingHeader will get the necessary operator information to identify the target system.

== The Payload Messages ==

The actual request message goes in the Content node. You have to make sure it is valid for a [[Message Containers and Versioning|version the operator supports]]. The standard content type is "application/xml" but systems might support other types (e.g. compression, encryption) in the future.

For the choice of the first request type in a session refer to the [[Request/Response Pairs|table of message pairs]]. Not all types might be supported by all operators.

== Error Messages ==

If the request message doesn't match the stated version, is incorrect in any other way or if there is some other kind of generic error (f.i. in the transport) you will get a [[Error Messages|generic error message]].

== Client Workflow ==

=== Preparation ===

These steps should be handled by the client system on a regular basis:

# Check the supported versions in the operator system and choose the highest common one (weekly?)
# Get the configuration data from the operator (daily)

=== Transaction ===

# Create <StringMessage> and set <RoutingHeader>, <AuthHeader> as required by the GDS system used
# create entry message in the format of the version chosen, set the marshalled message as Content (payload)
# Send the complete message to the GDS or directly to the operator endpoint as applicable

== GDS workflow ==

# Check if the client is allowed to use the system and the operator, optionally check for the correct GDS agency
# Check the RoutingHeader information and choose the matching operator endpoint to pass on the message

STRING is designed in a way that the GDS doesn't '''have''' to look at the Payload. Of course there may be reasons to do so anyway (e.g. statistics).

== Operator Workflow ==

# Get the <StringMessage> from the client / GDS
# Optionally check authentication
# Check the GDS agency and map it to the internal one
# Check if the stated version is supported and pass on the message to the matching adapter

STRING doesn't define the way how the <Payload> is processed. Systems may decide to pass on the whole message or just the <Payload> accompanied by the operator agency.

Error Messages

2019-10-16T10:15:19Z

Bachemj: Die Seite wurde neu angelegt: „To be defined“

To be defined

Documentation

2019-10-16T10:13:56Z

Bachemj:

Documentation main page

* [[Introduction]]

== Central concepts ==

* [[Message Containers and Versioning]]
* [[Authentication]]
* [[Agency System]]
* [[Message Handling]]
* [[Error Messages]]
* [[General Workflows]]
* [[Configuration]]
* [[External Collection of value keys, status codes etc.]]
* [[Use of Identifiers]]

== Queries by category ==

* [[Flights]]
* [[CommonService]]
* [[Accommodation]]
* [[Rental Car]]
* [[Cruise]]
* [[Packages]]
* [[Transfer]]

== Common topics ==

* [[Price Handling]]
* [[Payment Handling]]

* [[Glossar and Abbreviations]]

* [[XSD Documentation]]

Message Handling

2019-10-16T10:12:51Z

Bachemj:

The STRING message framework consists of an outer layer (StringMessage) and [[Versioning|version-specific payload messages]]. Most messages are [[Request/Response Pairs|pairs of requests and responses with defined workflows]].

== The StringMessage ==

The outer <StringMessage> contains the operator and agency data to route the message to the operator system and authenticate it as a valid request. [[Authentication|We don't require a specific form of authentication]] as it is implementation-dependent and might be handled on a higher level. The RoutingHeader will get the necessary operator information to identify the target system.

== The Payload Messages ==

The actual request message goes in the Content node. You have to make sure it is valid for a [[Message Containers and Versioning|version the operator supports]]. The standard content type is "application/xml" but systems might support other types (e.g. compression, encryption) in the future.

For the choice of the first request type in a session refer to the [[Request/Response Pairs|table of message pairs]]. Not all types might be supported by all operators.

== Error Messages ==

If the request message doesn't match the stated version, is incorrect in any other way or if there is some other kind of generic error (f.i. in the transport) you will get a [[Error messages|generic error message]].

== Client Workflow ==

=== Preparation ===

These steps should be handled by the client system on a regular basis:

# Check the supported versions in the operator system and choose the highest common one (weekly?)
# Get the configuration data from the operator (daily)

=== Transaction ===

# Create <StringMessage> and set <RoutingHeader>, <AuthHeader> as required by the GDS system used
# create entry message in the format of the version chosen, set the marshalled message as Content (payload)
# Send the complete message to the GDS or directly to the operator endpoint as applicable

== GDS workflow ==

# Check if the client is allowed to use the system and the operator, optionally check for the correct GDS agency
# Check the RoutingHeader information and choose the matching operator endpoint to pass on the message

STRING is designed in a way that the GDS doesn't '''have''' to look at the Payload. Of course there may be reasons to do so anyway (e.g. statistics).

== Operator Workflow ==

# Get the <StringMessage> from the client / GDS
# Optionally check authentication
# Check the GDS agency and map it to the internal one
# Check if the stated version is supported and pass on the message to the matching adapter

STRING doesn't define the way how the <Payload> is processed. Systems may decide to pass on the whole message or just the <Payload> accompanied by the operator agency.

Message Handling

2019-10-16T09:42:57Z

Bachemj:

The STRING message framework consists of an outer layer (StringMessage) and [[Versioning|version-specific payload messages]]. Most messages are [[Request/Response Pairs|pairs of requests and responses with defined workflows]].

== The StringMessage ==

The outer StringMessage contains the operator and agency data to route the message to the operator system and authenticate it as a valid request. [[Authentication|We don't require a specific form of authentication]] as it is implementation-dependent and might be handled on a higher level. The RoutingHeader will get the necessary operator information to identify the target system.

== The Payload Messages ==

The actual request message goes in the Content node. You have to make sure it is valid for a [[Message Containers and Versioning|version the operator supports]]. The standard content type is "application/xml" but systems might support other types (e.g. compression, encryption) in the future.

For the choice of the first request type in a session refer to the [[Request/Response Pairs|table of message pairs]]. Not all types might be supported by all operators.

== Error Messages ==

If the request message doesn't match the stated version, is incorrect in any other way or if there is some other kind of generic error (f.i. in the transport) you will get a [[Error messages|generic error message]].

== Client Workflow ==

=== Preparation ===

These steps should be handled by the client system on a regular basis:

# Check the supported versions in the operator system and choose the highest common one (weekly?)
# Get the configuration data from the operator (daily)

=== Transaction ===

# Create StringMessage and set RoutingHeader, AuthHeader as required by the GDS system used
# create entry message in the format of the version chosen, set the marshalled message as Content (payload)
# Send the complete message to the GDS or directly to the operator endpoint as applicable

== GDS workflow ==

== Operator Workflow ==

Developers Area

2019-10-16T09:16:32Z

Bachemj:

=== TODOs for the upcoming "Developer Camp" ===

* Create proof of concept application with STRING.
** Amadeus creates frontend (Martin)
** DaVinci / Phoenix Unlimited run as backends
* Create consistent style guide and apply to schemas
* Discuss authorization for STRING
** Built-in and/or HTTP based (e.g. OAuth2,...)
** Describe best/preferred practices
* Create external lists in for non trivial enums
** Reference and document in schema
** Make downloadable from wiki
* Documentation
** Further completion of in-schema documentation
** Further completion of wiki documentation
** Reference wiki documentation in schema where applicable
** Describe different architectural models when working with envelopes and payloads.
** Desribe standard workflow template
* Model and document ConfigurationRequest and ConfigurationResponse
* Discuss payment models
* Create table or graph of possible request-response sequences
* generic error messages
* Simulate/Test workflow for cruises (Desktop Test)
* Create JIRA backlog for the tasks that cannot be completed

Message Handling

2019-10-16T08:27:04Z

Bachemj: work in progress

Agency System

2019-10-16T07:48:20Z

Bachemj:

The agency system maps external agencies (GDS agency) to internal ones in a n-1 relation as GDS agencies of several GDS are pointing to the same operator agency.

The GDS agency is set in the StringMessage on top level as it is a routing-dependent information. The operator system will likely do the mapping to the internal agency before extracting the payload message and has to pass it along with the payload processing. The AgencyId in the payload is unverified by the GDS and should be set by the operator only.

Message Handling

2019-10-15T15:54:11Z

Bachemj: Die Seite wurde neu angelegt: „The STRING message framework consists of an outer layer (StringMessage) and version-specific payload messages. Most messages are Request/Respo…“

Documentation

2019-10-15T15:47:44Z

Bachemj:

Documentation main page

* [[Introduction]]

== Central concepts ==

* [[Message Containers and Versioning]]
* [[Authentication]]
* [[Agency System]]
* [[Message Handling]]
* [[General Workflows]]
* [[Configuration]]
* [[External Collection of value keys, status codes etc.]]
* [[Use of Identifiers]]

== Queries by category ==

* [[Flights]]
* [[CommonService]]
* [[Accommodation]]
* [[Rental Car]]
* [[Cruise]]
* [[Packages]]
* [[Transfer]]

== Common topics ==

* [[Price Handling]]
* [[Payment Handling]]

* [[Glossar and Abbreviations]]

* [[XSD Documentation]]