DRV STRING - Benutzerbeiträge [de]

Release 4.0.0

2024-08-08T12:45:29Z

Freitagm:

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 ==
* Support for insurance-Services and insurance search
* Support for airport search
* Support for flight seat information
* Support for booking modifications (full and partial)

Release 4.0.0

2024-08-08T12:45:06Z

Freitagm:

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 ==
- Support for insurance-Services and insurance search
- Support for airport search
- Support for flight seat information
- Support for booking modifications (full and partial)

Cruise

2019-10-16T10:45:46Z

Freitagm: small change

== Overview ==
Cruise services extend the CommonService to carry cruise specific information.
The main element holds basic service information to give a brief overview about the main characteristics which are fully inherited by the CommonService Element. Cruise specific information are held using a List of categories elements and a list of transfer elements.

Available attributes slightly differ for the given direction of the message (Request/Response).

=== Request element ===
<syntaxhighlight lang="xml">
<Service>
<Details xsi:type="CruiseRequestType" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

...

<Categories>
<CruiseCategory>
<Identifier>01</Identifier>
<AssignedTraveller>
<Identifier>01</Identifier>
<Identifier>02</Identifier>
</AssignedTraveller>
<CruiseCategoryCode>
<Code>INAW2V</Code>
</CruiseCategoryCode>
<CustomerRequests>
<Description>
<Text>Veganes Essen</Text>
</Description>
</CustomerRequests>
<CabinDetails>
<CabinDetail>
<AssignedTraveller>
<Identifier>01</Identifier>
<Identifier>02</Identifier>
</AssignedTraveller>
<Cabin>
<Number>10058</Number>
</Cabin>
</CabinDetail>
</CabinDetails>
</CruiseCategory>
</Categories>
</Details>
</Service>
</syntaxhighlight>

=== Response Element ===
The Response on the other hand is meant to represent the view of the TourOperator on the request. The Response also carries more specific information about the requested cruise service like detailed route information.

<syntaxhighlight lang="xml">
<Service>
<Details xsi:type="CruiseResponseType" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

...

<Categories>
<CruiseCategory>
<Identifier>01</Identifier>
<AssignedTraveller>
<Identifier>01</Identifier>
<Identifier>02</Identifier>
</AssignedTraveller>
<CruiseCategoryCode>
<Code>INAW2V</Code>
<Description>
<Text>Innenkabine Kategorie A</Text>
</Description>
</CruiseCategoryCode>
<CabinDetails>
<CabinDetail>
<Identifier>10058</Identifier>
<AssignedTraveller>
<Identifier>01</Identifier>
<Identifier>02</Identifier>
</AssignedTraveller>
<Attributes>
<Attribute>
<Code>2 Betten, zusammen oder trennbar</Code>
<AttributeSource>Touroperator</AttributeSource>
</Attribute>
<Attribute>
<Code>Bereich 4</Code>
<AttributeSource>Touroperator</AttributeSource>
</Attribute>
<Attribute>
<Code>Bett quer zur Fahrtrichtung</Code>
<AttributeSource>Touroperator</AttributeSource>
</Attribute>
</Attributes>
<Cabin>
<Number>10058</Number>
<Deck>Deck 10 - Perle</Deck>
</Cabin>
</CabinDetail>
</CabinDetails>
<State>OK</State>
</CruiseCategory>
</Categories>
<RouteDetails>
<RouteDetail>
<Date>2020-01-31</Date>
<ArrivalTime>T07:00Z</ArrivalTime>
<DepartureTime>T22:00Z</DepartureTime>
<Harbour>
<LanguageCode>DE</LanguageCode>
<Text>La Romana</Text>
</Harbour>
</RouteDetail>
<RouteDetail>
<Date>2020-02-01</Date>
<Harbour>
<LanguageCode>DE</LanguageCode>
<Text>Seetag</Text>
</Harbour>
</RouteDetail>
<RouteDetail>
<Date>2020-02-02</Date>
<ArrivalTime>T07:30Z</ArrivalTime>
<DepartureTime>T19:00Z</DepartureTime>
<Harbour>
<LanguageCode>DE</LanguageCode>
<Text>Fort-de-France</Text>
</Harbour>
</RouteDetail>
</RouteDetails>
</Details>
</Service>
</syntaxhighlight>

=== CruiseCategory Element ===
A CruiseCategory-Element, as the name suggests, represents a guarantee or real category on theacruise facility. Each category has an (optional) List of assigned travellers, which can be used to directly assign the travellers to a specific category.

It is represented by a CruiseCategoryCode Element holding code and description of the category. Specific attributes of the category (like facilities). In addition to that, it holds the selected cabins and a List of included extra services, all represented by a code and a description.
Whereas the code in these elements is intended to be used mainly in a technical manner and the description to be used for presentation, the description is an optional element. If not set, the code has to be used to describe category or included extras.
<syntaxhighlight lang="xml">
<CruiseCategory>
<Identifier>01</Identifier>
<AssignedTraveller>
<Identifier>01</Identifier>
<Identifier>02</Identifier>
</AssignedTraveller>
<CruiseCategoryCode>
<Code>DS</Code>
<Description>
<LanguageCode>DE</LanguageCode>
<Text>Innenkabine Kategorie A</Text>
</Description>
</CruiseCategoryCode>
<Attributes>
<Attribute>
<Code>SAFE</Code>
<Description>Safe</Description>
<AttributeSource>Touroperator</AttributeSource>
</Attribute>
<Attribute>
<Code>DESK</Code>
<Description>Schreibtisch</Description>
<AttributeSource>Touroperator</AttributeSource>
</Attribute>
</Attributes>
<IncludedExtras>
<IncludedExtra>
<ExtraCode>
<Code>WIFI</Code>
<Description>Kostenfreies WLAN/Description>
</ExtraCode>
</IncludedExtra>
</IncludedExtras>
<State>OK</State>
</CruiseCategory>
</syntaxhighlight>

==== Available CruiseCategory-Element attributes ====

{| class="wikitable sortable"
|-
! Attribute!! Values / Explanation
|-
| '''@Identifier'''|| This is a unique identifier within one message, which can be used to reference on a concrete category
|-
| '''AssignedTraveller'''|| A list of traveller Ids, representing the traveller assigned to this specific category
|-
| '''CruiseCategoryCode'''|| The category code identifying this specific class of cruise. Can be enriched by textual desriptions of the category.
|-
| '''CruiseCategoryCode/Attributes'''|| A list of special attributes of the category structured in a @Code, a @Description (for display purposes) and the @AttributeSource indicating the source/type of that attribute code
|-
| '''CustomerRequests''' (Request only)|| A List of texts holding customer specific request information
|-
| '''IncludedExtras'''|| A List of extras included for that category
|}

Cruise

2019-10-16T10:44:26Z

Freitagm: first definition

== Overview ==
Cruise services extend the CommonService to carry cruise specific information.
The main element holds basic service information to give a brief overview about the main characteristics which are fully inherited by the CommonService Element. Cruise specific information are held using a List of categories elements and a list of transfer elements.

Available attributes slightly differ for the given direction of the message (Request/Response).

=== Request element ===
<syntaxhighlight lang="xml">
<Service>
<Details xsi:type="CruiseRequestType" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

...

<Categories>
<CruiseCategory>
<Identifier>01</Identifier>
<AssignedTraveller>
<Identifier>01</Identifier>
<Identifier>02</Identifier>
</AssignedTraveller>
<CruiseCategoryCode>
<Code>INAW2V</Code>
</CruiseCategoryCode>
<CustomerRequests>
<Description>
<Text>Veganes Essen</Text>
</Description>
</CustomerRequests>
<CabinDetails>
<CabinDetail>
<AssignedTraveller>
<Identifier>01</Identifier>
<Identifier>02</Identifier>
</AssignedTraveller>
<Cabin>
<Number>10058</Number>
</Cabin>
</CabinDetail>
</CabinDetails>
</CruiseCategory>
</Categories>
</Details>
</Service>
</syntaxhighlight>

=== Response Element ===
The Response on the other hand is meant to represent the view of the TourOperator on the request. The Response also carries more specific information about the requested cruise service like detailed route information.

<syntaxhighlight lang="xml">
<Service>
<Details xsi:type="CruiseResponseType" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

...

<Categories>
<CruiseCategory>
<Identifier>01</Identifier>
<AssignedTraveller>
<Identifier>01</Identifier>
<Identifier>02</Identifier>
</AssignedTraveller>
<CruiseCategoryCode>
<Code>INAW2V</Code>
<Description>
<Text>Innenkabine Kategorie A</Text>
</Description>
</CruiseCategoryCode>
<CabinDetails>
<CabinDetail>
<Identifier>10058</Identifier>
<AssignedTraveller>
<Identifier>01</Identifier>
<Identifier>02</Identifier>
</AssignedTraveller>
<Attributes>
<Attribute>
<Code>2 Betten, zusammen oder trennbar</Code>
<AttributeSource>Touroperator</AttributeSource>
</Attribute>
<Attribute>
<Code>Bereich 4</Code>
<AttributeSource>Touroperator</AttributeSource>
</Attribute>
<Attribute>
<Code>Bett quer zur Fahrtrichtung</Code>
<AttributeSource>Touroperator</AttributeSource>
</Attribute>
</Attributes>
<Cabin>
<Number>10058</Number>
<Deck>Deck 10 - Perle</Deck>
</Cabin>
</CabinDetail>
</CabinDetails>
<State>OK</State>
</CruiseCategory>
</Categories>
<RouteDetails>
<RouteDetail>
<Date>2020-01-31</Date>
<ArrivalTime>T07:00Z</ArrivalTime>
<DepartureTime>T22:00Z</DepartureTime>
<Harbour>
<LanguageCode>DE</LanguageCode>
<Text>La Romana</Text>
</Harbour>
</RouteDetail>
<RouteDetail>
<Date>2020-02-01</Date>
<Harbour>
<LanguageCode>DE</LanguageCode>
<Text>Seetag</Text>
</Harbour>
</RouteDetail>
<RouteDetail>
<Date>2020-02-02</Date>
<ArrivalTime>T07:30Z</ArrivalTime>
<DepartureTime>T19:00Z</DepartureTime>
<Harbour>
<LanguageCode>DE</LanguageCode>
<Text>Fort-de-France</Text>
</Harbour>
</RouteDetail>
</RouteDetails>
</Details>
</Service>
</syntaxhighlight>

=== Room Element ===
A CruiseCategory-Element, as the name suggests, represents a guarantee or real category on theacruise facility. Each category has an (optional) List of assigned travellers, which can be used to directly assign the travellers to a specific category.

It is represented by a CruiseCategoryCode Element holding code and description of the category. Specific attributes of the category (like facilities). In addition to that, it holds the selected cabins and a List of included extra services, all represented by a code and a description.
Whereas the code in these elements is intended to be used mainly in a technical manner and the description to be used for presentation, the description is an optional element. If not set, the code has to be used to describe category or included extras.
<syntaxhighlight lang="xml">
<CruiseCategory>
<Identifier>01</Identifier>
<AssignedTraveller>
<Identifier>01</Identifier>
<Identifier>02</Identifier>
</AssignedTraveller>
<CruiseCategoryCode>
<Code>DS</Code>
<Description>
<LanguageCode>DE</LanguageCode>
<Text>Innenkabine Kategorie A</Text>
</Description>
</CruiseCategoryCode>
<Attributes>
<Attribute>
<Code>SAFE</Code>
<Description>Safe</Description>
<AttributeSource>Touroperator</AttributeSource>
</Attribute>
<Attribute>
<Code>DESK</Code>
<Description>Schreibtisch</Description>
<AttributeSource>Touroperator</AttributeSource>
</Attribute>
</Attributes>
<IncludedExtras>
<IncludedExtra>
<ExtraCode>
<Code>WIFI</Code>
<Description>Kostenfreies WLAN/Description>
</ExtraCode>
</IncludedExtra>
</IncludedExtras>
<State>OK</State>
</CruiseCategory>
</syntaxhighlight>

==== Available CruiseCategory-Element attributes ====

{| class="wikitable sortable"
|-
! Attribute!! Values / Explanation
|-
| '''@Identifier'''|| This is a unique identifier within one message, which can be used to reference on a concrete category
|-
| '''AssignedTraveller'''|| A list of traveller Ids, representing the traveller assigned to this specific category
|-
| '''CruiseCategoryCode'''|| The category code identifying this specific class of cruise. Can be enriched by textual desriptions of the room.
|-
| '''CruiseCategoryCode/Attributes'''|| A list of special attributes of the category structured in a @Code, a @Description (for display purposes) and the @AttributeSource indicating the source/type of that attribute code
|-
| '''CustomerRequests''' (Request only)|| A List of texts holding customer specific request information
|-
| '''IncludedExtras'''|| A List of extras included for that category
|}

Flights

2018-05-25T10:20:49Z

Freitagm: next flight examples

Each flight service is divided in three different type of levels which can be used to describe a flight routing.

Those levels are:

Flight: This flight level describes a single or a combination of sales routes for a flight service (e.g. One-Way or Return) and should be seen as a container for flight segments.

Segment: The flight segment is a single purchasable sales route offered by the touroperator. Therefore the flight segment should be identifiable by an according touroperator product code.

Leg: The leg level is used to deliver flight routing details (e.g. flight times, airports) belonging to a certain flight segment. A single flight leg is not offered as a separate bookable service by the touroperator.

Depending on the touroperator the same offered flight services might be sold in different ways. If the touroperator wants to distribute a combination of a feeder and a long haul flight this combination might be represented as a flight with two legs (and optionally one leg) in case that the feeder and the long haul flight can be selected and booked separately. If the same combination is offered by the touroperator while those two components are mandatory and are only bookable in this certain combination the touroperator might deliver one segment with two legs.

Examples:

1) Return-Flight with segments but without leg details
<syntaxhighlight lang="xml">
<FlightRequest>
<Segments>
<Segment Type="F" Identifier="SEGMENT 01">
<StartDate>2018-05-25</StartDate>
<EndDate>2018-05-25</EndDate>
<Quantity>1</Quantity>
<AssignedTraveller>
<Identifier>01</Identifier>
</AssignedTraveller>
<Product>
<Code>CGN PMI</Code>
</Product>
<DepartureAirport>
<IataCode>CGN</IataCode>
</DepartureAirport>
<ArrivalAirport>
<IataCode>PMI</IataCode>
</ArrivalAirport>
<Carrier>
<OperatingCarrier>
<IataCode>LH</IataCode>
</OperatingCarrier>
</Carrier>
<Classes>
<FlightClass>
<Identifier>CLASS 01</Identifier>
<CabinClass>Economy</CabinClass>
<State>OK</State>
<AssignedTraveller>
<Identifier>01</Identifier>
</AssignedTraveller>
</FlightClass>
</Classes>
</Segment>
<Segment Type="F" Identifier="SEGMENT 02">
<StartDate>2018-06-01</StartDate>
<EndDate>2018-06-01</EndDate>
<Quantity>1</Quantity>
<AssignedTraveller>
<Identifier>01</Identifier>
</AssignedTraveller>
<Product>
<Code>PMI CGN</Code>
</Product>
<DepartureAirport>
<IataCode>PMI</IataCode>
</DepartureAirport>
<ArrivalAirport>
<IataCode>CGN</IataCode>
</ArrivalAirport>
<Carrier>
<OperatingCarrier>
<IataCode>LH</IataCode>
</OperatingCarrier>
</Carrier>
<Classes>
<FlightClass>
<Identifier>CLASS 02</Identifier>
<CabinClass>Economy</CabinClass>
<State>OK</State>
<AssignedTraveller>
<Identifier>01</Identifier>
</AssignedTraveller>
</FlightClass>
</Classes>
</Segment>
</Segments>
</syntaxhighlight>

2) One-Way-Flight with two legs

<syntaxhighlight lang="xml">
<FlightRequest>
<Segments>
<Segment Type="F" Identifier="SEGMENT 01">
<StartDate>2018-05-25</StartDate>
<EndDate>2018-05-25</EndDate>
<Quantity>1</Quantity>
<AssignedTraveller>
<Identifier>01</Identifier>
</AssignedTraveller>
<Product>
<Code>CGN PMI</Code>
</Product>
<Legs>
<Leg>
<Identifier>LEG CGN FRA 01</Identifier>
<DepartureDate>2018-05-25</DepartureDate>
<ArrivalDate>2018-05-25</ArrivalDate>
<FlightNumber>LH123</FlightNumber>
<State>OK</State>
<AssignedTraveller>
<Identifier>01</Identifier>
</AssignedTraveller>
<DepartureAirport>
<IataCode>CGN</IataCode>
</DepartureAirport>
<ArrivalAirport>
<IataCode>FRA</IataCode>
</ArrivalAirport>
<Carrier>
<OperatingCarrier>
<IataCode>LH</IataCode>
</OperatingCarrier>
</Carrier>
<Class>
<CabinClass>Economy</CabinClass>
<ClassCode>
<Code>Y</Code>
</ClassCode>
</Class>
</Leg>
<Leg>
<Identifier>LEG FRA PMI 01</Identifier>
<DepartureDate>2018-05-25</DepartureDate>
<ArrivalDate>2018-05-25</ArrivalDate>
<FlightNumber>LH123</FlightNumber>
<State>OK</State>
<AssignedTraveller>
<Identifier>01</Identifier>
</AssignedTraveller>
<DepartureAirport>
<IataCode>FRA</IataCode>
</DepartureAirport>
<ArrivalAirport>
<IataCode>PMI</IataCode>
</ArrivalAirport>
<Carrier>
<OperatingCarrier>
<IataCode>LH</IataCode>
</OperatingCarrier>
</Carrier>
<Class>
<CabinClass>Business</CabinClass>
<ClassCode>
<Code>Y</Code>
</ClassCode>
</Class>
</Leg>
</Legs>
<DepartureAirport>
<IataCode>CGN</IataCode>
</DepartureAirport>
<ArrivalAirport>
<IataCode>PMI</IataCode>
</ArrivalAirport>
<Carrier>
<OperatingCarrier>
<IataCode>LH</IataCode>
</OperatingCarrier>
</Carrier>
<Classes>
<FlightClass>
<Identifier>CLASS 01</Identifier>
<CabinClass>Economy</CabinClass>
<State>OK</State>
<AssignedTraveller>
<Identifier>01</Identifier>
</AssignedTraveller>
</FlightClass>
</Classes>
</Segment>
</Segments>
</syntaxhighlight>

3) Return-Flight with feeder flight on the outbound site while the touroperator offers the feeder as a separate bookable service

4) Return-Flight with feeder flight on the outbound site while the touroperator offers the feeder as a non-bookable service

Flights

2018-05-25T10:03:47Z

Freitagm: First draft for flight

Each flight service is divided in three different kind of levels.

Those levels are:

Flight: This flight level describes a combination of sales route for a flight service (e.g. One-Way or Return) and is a container for one or more flight segments.

Segment: The flight segment is a single purchasable sales route offered by the touroperator. Therefore the flight segment should be identifiable by an according touroperator product code.

Leg: The leg level is used to deliver flight routing details (e.g. flight times, airports) belonging to a certain flight segment. A single flight leg is not offered as a separate bookable service by the touroperator.

Examples:

1) Return-Flight
<syntaxhighlight lang="xml">
<FlightRequest>
<Segments>
<Segment Type="F" Identifier="SEGMENT 01">
<StartDate>2018-05-25</StartDate>
<EndDate>2018-05-25</EndDate>
<Quantity>1</Quantity>
<AssignedTraveller>
<Identifier>01</Identifier>
</AssignedTraveller>
<Product>
<Code>CGN PMI</Code>
</Product>
<DepartureAirport>
<IataCode>CGN</IataCode>
</DepartureAirport>
<ArrivalAirport>
<IataCode>PMI</IataCode>
</ArrivalAirport>
<Carrier>
<OperatingCarrier>
<IataCode>LH</IataCode>
</OperatingCarrier>
</Carrier>
<Classes>
<FlightClass>
<Identifier>CLASS 01</Identifier>
<CabinClass>Economy</CabinClass>
<State>OK</State>
<AssignedTraveller>
<Identifier>01</Identifier>
</AssignedTraveller>
</FlightClass>
</Classes>
</Segment>
<Segment Type="F" Identifier="SEGMENT 02">
<StartDate>2018-06-01</StartDate>
<EndDate>2018-06-01</EndDate>
<Quantity>1</Quantity>
<AssignedTraveller>
<Identifier>01</Identifier>
</AssignedTraveller>
<Product>
<Code>PMI CGN</Code>
</Product>
<DepartureAirport>
<IataCode>PMI</IataCode>
</DepartureAirport>
<ArrivalAirport>
<IataCode>CGN</IataCode>
</ArrivalAirport>
<Carrier>
<OperatingCarrier>
<IataCode>LH</IataCode>
</OperatingCarrier>
</Carrier>
<Classes>
<FlightClass>
<Identifier>CLASS 02</Identifier>
<CabinClass>Economy</CabinClass>
<State>OK</State>
<AssignedTraveller>
<Identifier>01</Identifier>
</AssignedTraveller>
</FlightClass>
</Classes>
</Segment>
</Segments>
</syntaxhighlight>

2) One-Flight

3) Return-Flight with feeder flight on the outbound site while the touroperator offers the feeder as a separate bookable service

4) Return-Flight with feeder flight on the outbound site while the touroperator offers the feeder as a non-bookable service

Versioning

2017-08-09T13:49:44Z

Freitagm: Die Seite wurde neu angelegt: „- Aufbau der Nachrichten mit einer stabilen Hülle und einem volatilen Container <xml> <version>1.3</version> <data> … </data> </xml> - Im Rahmen wird…“

- Aufbau der Nachrichten mit einer stabilen Hülle und einem volatilen Container
<xml>
<version>1.3</version>
<data>
…
</data>
</xml>

- Im Rahmen wird der Container und eine Versionsinformation mitgesendet
- Es findet ein Version-Handshake zwischen Sender und Empfänger statt. Beide tauschen die Information über die unterstützten Versionen aus und einigen sich auf eine gemeinsam unterstützte Version (für eine Session muss diese Version stabil gehalten werden)
Diese unterstützen Versionsinformationen werden über einen separaten Request-/Response ausgetauscht.
- Die Major-Versionsnummer in der Hülle wird nur bei Breaking-Changes (Syntaktisch oder Semantisch) hochgezählt. Die Minor-Versionsnummer kann bei jeder Änderung (z.B. neue Felder) hochgezählt werden, muss aber innerhalb des Major-Releases abwärtskompatibel sein.
- Die Major-Versionsnummer könnte Bestandteil des Namespaces des inneren Container-Schemas sein
- Neue Nachrichtentypen könnten an der Versionnummer hängen und so geprüft werden oder aber einfach bei der Verarbeitung durch die empfangene Stelle eine Fehlermeldung auslösen

Schemata

2016-09-23T14:00:08Z

Freitagm:

Hier bekommt dann jeder Komplex seine eigene Unterseite.

string-carrental-types.xsd
string-carrental.xsd

string-common-types.xsd

string-cruise-types.xsd
string-cruise.xsd

string-flight-types.xsd
string-flight.xsd

string-hotel-types.xsd
string-hotel.xsd

string-package.xsd

string-configuration.xsd

string.xsd

[[Datei:DRV Typen.png|200px|thumb|left|High-Level Übersicht der Leistungstypenstruktur]]

Datei:DRV Typen.png

2016-09-23T13:58:56Z

Freitagm: High-Level Übersicht der Leistungstypenstruktur

High-Level Übersicht der Leistungstypenstruktur

Schemata

2016-09-23T13:56:55Z

Freitagm:

Hier bekommt dann jeder Komplex seine eigene Unterseite.

string-carrental-types.xsd
string-carrental.xsd

string-common-types.xsd

string-cruise-types.xsd
string-cruise.xsd

string-flight-types.xsd
string-flight.xsd

string-hotel-types.xsd
string-hotel.xsd

string-package.xsd

string-configuration.xsd

string.xsd

[[Datei:DRV Typen.pdf|200px|thumb|left|High-Level Übersicht der Leistungstypenstruktur]]

Schemata

2016-09-23T13:55:49Z

Freitagm:

Schemata

2016-09-23T13:55:22Z

Freitagm:

Hier bekommt dann jeder Komplex seine eigene Unterseite.

string-carrental-types.xsd
string-carrental.xsd

string-common-types.xsd

string-cruise-types.xsd
string-cruise.xsd

string-flight-types.xsd
string-flight.xsd

string-hotel-types.xsd
string-hotel.xsd

string-package.xsd

string-configuration.xsd

string.xsd

[[Datei:Datei.png|200px|thumb|left|High-Level Übersicht der Leistungstypenstruktur]]

Datei:DRV Typen.pdf

2016-09-23T13:54:38Z

Freitagm: High-Level Übersicht der Leistungstypenstruktur

High-Level Übersicht der Leistungstypenstruktur