DRV STRING - Benutzerbeiträge [de]

CommonService

2018-06-27T13:53:49Z

Sandk: /* Overview */

== Overview ==
The Common Service is a superstructure defining the mostly shared elements of any service. Specific services like the AccommodationService only extend this structure to add specific information for their case. This basic structure is separated into a Request version and a Response version. Each of them only contain the Attributes and Elements suitable for the specified direction. As, for example, it is essential to send the state for a service in the response of a BookingResponse, it is not supposed (or even harmful) to use it in the BookingRequest.

The concept of separate attributes for Request Services and Response Services is inherited by all other service implementations.

[[Datei:CommonServiceRequestType.png|mini|links|Request Type]]
[[Datei:CommonServiceResponseType.PNG|mini|rechts|Response Type]]

=== Basic Attributes ===
The minimal set of Information needed to describe a service is its Code, the StartDate and its EndDate. These fields are mandatory for every request containing a service.
The response adds another manydatory field, which is: State.

=== Optional Attributes ===
To extend the information capable to be transported by the protocol, each service contains a set of optional Elements and Attributes.
Please note, that these fields might be expected by the communication partner, even if specified as optional by STRING Protocol.

{| class="wikitable sortable"
|-
! Attribute!! Values / Explanation
|-
| '''@Identifier'''|| This is a unique identifier within one message, which can be used to reference on a concrete room
|-
| '''@Type'''|| Specific ServiceType
|-
| '''AssignedTraveller'''|| A List of traveller Ids to describe who is assigned to this service
|-
| '''Quantity'''|| The quantity of equal services described by this service element.
|-
| '''Attributes'''|| A List of Attributes describing the Service. Each attribute is defined by a code and its source plus optional descriptive Texts.
|-
| '''PackageReference'''|| In case the Service belongs to a package, the identifier can be set here
|-
| '''CustomerRequests''' (Request only)|| A List of texts holding customer specific request information
|-
| '''AdditionalInfos''' (Response only)|| Element to send additional information separated into: - GeneralInformation, - CancellationPolicies and - ModificationPolicies
|}

CommonService

2018-06-27T13:32:09Z

Sandk: /* Overview */

== Overview ==
The Common Service is a superstructure defining the mostly shared elements of any service. Specific services like the AccommodationService only extend this structure to add specific information for their case. This basic structure is separated into a Request version and a Response version. Each of them only contain the Attributes and Elements suitable for the specified direction. As, for example, it is essential to send the state for a service in the response of a BookingResponse, it is not supposed (or even harmful) to use it in the BookingRequest.

The concept of separate attributes for Request Services and Response Services is inherited by all other service implementations.

[[Datei:CommonServiceRequestType.png|mini|links|Request Type]]
[[Datei:CommonServiceResponseType.PNG|mini|rechts|Response Type]]

=== Basic Attributes ===
The minimal set of Information needed to describe a service is its Code, the StartDate and its EndDate. These fields are mandatory for every request containing a service.
The response adds another manydatory field, which is: State.

=== Optional Attributes ===
To extend the information capable to be transported by the protocol, each service contains a set of optional Elements and Attributes.
Please note, that these fields might be expected by the communication partner, even if specified as optional by STRING Protocol.

{| class="wikitable sortable"
|-
! Attribute!! Values / Explanation
|-
| '''@Identifier'''|| This is a unique identifier within one message, which can be used to reference on a concrete room
|-
| '''@Type'''|| Specific ServiceType
|-
| '''AssignedTraveller'''|| A List of traveller Ids to describe who is assigned to this service
|-
| '''Quantity'''|| The quantity of equal services described by this service element.
|-
| '''Attributes'''|| A List of Attributes describing the Service. Each attribute is defined by a code and its source plus optional descriptive Texts.
|-
| '''PackageReference'''|| In case the Service belongs to a package, the identifier can be set here
|-
| '''CustomerRequests''' (Request only)|| A List of texts holding customer specific request information
|-
| '''AdditionalInfos''' (Response only)|| Element to send additional information separated into: GeneralInformation, CancellationPolicies ans ModificationPolicies
|}

CommonService

2018-06-27T12:59:47Z

Sandk: /* Overview */

== Overview ==
The Common Service is a superstructure defining the mostly shared elements of any service. Specific services like the AccommodationService only extend this structure to add specific information for their case. This basic structure is separated into a Request version and a Response version. Each of them only contain the Attributes and Elements suitable for the specified direction. As, for example, it is essential to send the state for a service in the response of a BookingResponse, it is not supposed (or even harmful) to use it in the BookingRequest.

The concept of separate attributes for Request Services and Response Services is inherited by all other service implementations.

[[Datei:CommonServiceRequestType.png|mini|links|Request Type]]
[[Datei:CommonServiceResponseType.PNG|mini|rechts]]

=== Basic Attributes ===
The minimal set of Information needed to describe a service is its Code, the StartDate and its EndDate. These fields are mandatory for every request containing a service.
The response adds another manydatory field, which is: State.

=== Optional Attributes ===
To extend the information capable to be transported by the protocol, each service contains a set of optional Elements and Attributes.
Please note, that these fields might be expected by the communication partner, even if specified as optional by STRING Protocol.

{| class="wikitable sortable"
|-
! Attribute!! Values / Explanation
|-
| '''@Identifier'''|| This is a unique identifier within one message, which can be used to reference on a concrete room
|-
| '''@Type'''|| Specific ServiceType
|-
| '''AssignedTraveller'''|| A List of traveller Ids to describe who is assigned to this service
|-
| '''Quantity'''|| The quantity of equal services described by this service element.
|-
| '''Attributes'''|| A List of Attributes describing the Service. Each attribute is defined by a code and its source plus optional descriptive Texts.
|-
| '''PackageReference'''|| In case the Service belongs to a package, the identifier can be set here
|-
| '''CustomerRequests''' (Request only)|| A List of texts holding customer specific request information
|-
| '''AdditionalInfos''' (Response only)|| Element to send additional information separated into: GeneralInformation, CancellationPolicies ans ModificationPolicies
|}

CommonService

2018-06-27T12:58:23Z

Sandk: /* Overview */

== Overview ==
The Common Service is a superstructure defining the mostly shared elements of any service. Specific services like the AccommodationService only extend this structure to add specific information for their case. This basic structure is separated into a Request version and a Response version. Each of them only contain the Attributes and Elements suitable for the specified direction. As, for example, it is essential to send the state for a service in the response of a BookingResponse, it is not supposed (or even harmful) to use it in the BookingRequest.

The concept of separate attributes for Request Services and Response Services is inherited by all other service implementations.

[[Datei:CommonServiceRequestType.png|mini|links|Request Type]]
[[Datei:CommonServiceResponseType.png|mini|rechts|Response Type]]

=== Basic Attributes ===
The minimal set of Information needed to describe a service is its Code, the StartDate and its EndDate. These fields are mandatory for every request containing a service.
The response adds another manydatory field, which is: State.

=== Optional Attributes ===
To extend the information capable to be transported by the protocol, each service contains a set of optional Elements and Attributes.
Please note, that these fields might be expected by the communication partner, even if specified as optional by STRING Protocol.

{| class="wikitable sortable"
|-
! Attribute!! Values / Explanation
|-
| '''@Identifier'''|| This is a unique identifier within one message, which can be used to reference on a concrete room
|-
| '''@Type'''|| Specific ServiceType
|-
| '''AssignedTraveller'''|| A List of traveller Ids to describe who is assigned to this service
|-
| '''Quantity'''|| The quantity of equal services described by this service element.
|-
| '''Attributes'''|| A List of Attributes describing the Service. Each attribute is defined by a code and its source plus optional descriptive Texts.
|-
| '''PackageReference'''|| In case the Service belongs to a package, the identifier can be set here
|-
| '''CustomerRequests''' (Request only)|| A List of texts holding customer specific request information
|-
| '''AdditionalInfos''' (Response only)|| Element to send additional information separated into: GeneralInformation, CancellationPolicies ans ModificationPolicies
|}

Datei:CommonServiceResponseType.PNG

2018-06-27T12:57:56Z

Sandk: Sandk lud eine neue Version von Datei:CommonServiceResponseType.PNG hoch

CommonService

2018-06-27T12:57:34Z

Sandk:

== Overview ==
The Common Service is a superstructure defining the mostly shared elements of any service. Specific services like the AccommodationService only extend this structure to add specific information for their case. This basic structure is separated into a Request version and a Response version. Each of them only contain the Attributes and Elements suitable for the specified direction. As, for example, it is essential to send the state for a service in the response of a BookingResponse, it is not supposed (or even harmful) to use it in the BookingRequest.

The concept of separate attributes for Request Services and Response Services is inherited by all other service implementations.

[[Datei:CommonServiceRequestType.png|mini|links|Request Type]]
[[Datei:CommonServiceResponseType|mini|rechts|Response Type]]

=== Basic Attributes ===
The minimal set of Information needed to describe a service is its Code, the StartDate and its EndDate. These fields are mandatory for every request containing a service.
The response adds another manydatory field, which is: State.

=== Optional Attributes ===
To extend the information capable to be transported by the protocol, each service contains a set of optional Elements and Attributes.
Please note, that these fields might be expected by the communication partner, even if specified as optional by STRING Protocol.

{| class="wikitable sortable"
|-
! Attribute!! Values / Explanation
|-
| '''@Identifier'''|| This is a unique identifier within one message, which can be used to reference on a concrete room
|-
| '''@Type'''|| Specific ServiceType
|-
| '''AssignedTraveller'''|| A List of traveller Ids to describe who is assigned to this service
|-
| '''Quantity'''|| The quantity of equal services described by this service element.
|-
| '''Attributes'''|| A List of Attributes describing the Service. Each attribute is defined by a code and its source plus optional descriptive Texts.
|-
| '''PackageReference'''|| In case the Service belongs to a package, the identifier can be set here
|-
| '''CustomerRequests''' (Request only)|| A List of texts holding customer specific request information
|-
| '''AdditionalInfos''' (Response only)|| Element to send additional information separated into: GeneralInformation, CancellationPolicies ans ModificationPolicies
|}

CommonService

2018-06-27T12:57:08Z

Sandk:

== Overview ==
The Common Service is a superstructure defining the mostly shared elements of any service. Specific services like the AccommodationService only extend this structure to add specific information for their case. This basic structure is separated into a Request version and a Response version. Each of them only contain the Attributes and Elements suitable for the specified direction. As, for example, it is essential to send the state for a service in the response of a BookingResponse, it is not supposed (or even harmful) to use it in the BookingRequest.

The concept of separate attributes for Request Services and Response Services is inherited by all other service implementations.

[[Datei:CommonServiceRequestType.png|mini|links|Request Type]]
[[Datei:CommonServiceResponseType.png|mini|rechts|Response Type]]

=== Basic Attributes ===
The minimal set of Information needed to describe a service is its Code, the StartDate and its EndDate. These fields are mandatory for every request containing a service.
The response adds another manydatory field, which is: State.

=== Optional Attributes ===
To extend the information capable to be transported by the protocol, each service contains a set of optional Elements and Attributes.
Please note, that these fields might be expected by the communication partner, even if specified as optional by STRING Protocol.

{| class="wikitable sortable"
|-
! Attribute!! Values / Explanation
|-
| '''@Identifier'''|| This is a unique identifier within one message, which can be used to reference on a concrete room
|-
| '''@Type'''|| Specific ServiceType
|-
| '''AssignedTraveller'''|| A List of traveller Ids to describe who is assigned to this service
|-
| '''Quantity'''|| The quantity of equal services described by this service element.
|-
| '''Attributes'''|| A List of Attributes describing the Service. Each attribute is defined by a code and its source plus optional descriptive Texts.
|-
| '''PackageReference'''|| In case the Service belongs to a package, the identifier can be set here
|-
| '''CustomerRequests''' (Request only)|| A List of texts holding customer specific request information
|-
| '''AdditionalInfos''' (Response only)|| Element to send additional information separated into: GeneralInformation, CancellationPolicies ans ModificationPolicies
|}

CommonService

2018-06-27T12:56:27Z

Sandk:

== Overview ==
The Common Service is a superstructure defining the mostly shared elements of any service. Specific services like the AccommodationService only extend this structure to add specific information for their case. This basic structure is separated into a Request version and a Response version. Each of them only contain the Attributes and Elements suitable for the specified direction. As, for example, it is essential to send the state for a service in the response of a BookingResponse, it is not supposed (or even harmful) to use it in the BookingRequest.

The concept of separate attributes for Request Services and Response Services is inherited by all other service implementations.

[[Datei:CommonServiceRequestType.png|mini|links|Request Type]]
[[Datei:CommonServiceResponseType.png|mini|rechts<Response Type]]

=== Basic Attributes ===
The minimal set of Information needed to describe a service is its Code, the StartDate and its EndDate. These fields are mandatory for every request containing a service.
The response adds another manydatory field, which is: State.

=== Optional Attributes ===
To extend the information capable to be transported by the protocol, each service contains a set of optional Elements and Attributes.
Please note, that these fields might be expected by the communication partner, even if specified as optional by STRING Protocol.

{| class="wikitable sortable"
|-
! Attribute!! Values / Explanation
|-
| '''@Identifier'''|| This is a unique identifier within one message, which can be used to reference on a concrete room
|-
| '''@Type'''|| Specific ServiceType
|-
| '''AssignedTraveller'''|| A List of traveller Ids to describe who is assigned to this service
|-
| '''Quantity'''|| The quantity of equal services described by this service element.
|-
| '''Attributes'''|| A List of Attributes describing the Service. Each attribute is defined by a code and its source plus optional descriptive Texts.
|-
| '''PackageReference'''|| In case the Service belongs to a package, the identifier can be set here
|-
| '''CustomerRequests''' (Request only)|| A List of texts holding customer specific request information
|-
| '''AdditionalInfos''' (Response only)|| Element to send additional information separated into: GeneralInformation, CancellationPolicies ans ModificationPolicies
|}

Datei:CommonServiceRequestType.png

2018-06-27T12:50:22Z

Sandk:

2018-06-27T06:09:02Z

Sandk: /* Available top-level attributes */

== Overview ==
Accommodation Services extend the CommonService to carry accommodation 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. Accommodation specific information are held using a List of room 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">
<Accommodation>

...

<Rooms>
<Room>
<Identifier>01</Identifier>
<AssignedTraveller>
<Identifier>01</Identifier>
<Identifier>02</Identifier>
</AssignedTraveller>
<RoomCode>
<Code>DS</Code>
</RoomCode>
<Board>
<Code>BF</Code>
</Board>
<CustomerRequests>
<Description>
<Text>Superior Doppelzimmer mit Frühstück</Text>
</Description>
</CustomerRequests>
</Room>
</Rooms>
</Accommodation>
</syntaxhighlight>
[http://string.drv.de/downloads/releases/release-0.9.2/examples/Booking/UC01rq.xml Full File]

In case of a Request the structure is also capable of holding service related customerRequests for a desired CheckIn/Out time.

==== Available Room-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 payment
|-
| '''@AssignedTraveller'''|| A list of traveller Ids, representing the traveller assigned to this specific room
|-
| '''@RoomCode'''|| The room category code identifying this specific class of room
|-
| '''@Board'''|| The code representing the assigned mealplan for that room
|-
| '''@CustomerRequests'''|| A List of texts holding customer specific request information
|}

=== Response Element ===
The Response on the other hand is meant to represent the view of the TourOperator on the request. In case of CheckIn/out Times the values are either reflected in meaning of confirmation or correction. The Response also carries more specific information about the requested accommodation service like LocationDetails or a Stay element to inform about charged nights and CheckIn/Out Times.

<syntaxhighlight lang="xml">
<Accommodation>

...

<LocationDetails>
<GeoLocation>
<Longitude>2.314477</Longitude>
<Latitude>48.87173</Latitude>
</GeoLocation>
<Contact>
<Mail>reservations.lebristolparis@oetkercollection.com</Mail>
<Phone>+33 153 43 43 00</Phone>
<URL>http://www.lebristolparis.com/eng/home</URL>
</Contact>
<Address>
<AddressLines>
<AddressLine>Le Bristol Paris</AddressLine>
</AddressLines>
<Street>Rue du Faubourg Saint HonorÃ©</Street>
<Additional>08. Arrondissement - Champs Ã‰lysÃ©es</Additional>
<HouseNumber>112</HouseNumber>
<ZIPCode>75008</ZIPCode>
<City>Paris</City>
<Country>
<Name>Frankreich</Name>
<CountryCode>FR</CountryCode>
</Country>
</Address>
<Regions>
<Region>
<Code>FR-IDF</Code>
<Description>
<Text>Ille de France</Text>
</Description>
</Region>
</Regions>
</LocationDetails>
<Rooms>
<Room>
<Identifier>01</Identifier>
<AssignedTraveller>
<Identifier>01</Identifier>
<Identifier>02</Identifier>
</AssignedTraveller>
<RoomCode>
<Code>DS</Code>
<Description>
<Text>Doppelzimmer Superior</Text>
</Description>
<Description>
<Text>Zimmer größer als der Durchschnitt in Paris: 40 m², mit großem Doppelbett</Text>
</Description>
</RoomCode>
<Board>
<Code>BF</Code>
</Board>
<State>OK</State>
</Room>
</Rooms>
<Stay>
<ChargedNights>7</ChargedNights>
<CheckInOut/>
</Stay>
</Accommodation>
</syntaxhighlight>
[http://string.drv.de/downloads/releases/release-0.9.2/examples/Booking/UC01rs.xml Full File]

=== Room Element ===
A Room-Element, as the name suggests, represents a physical room in the accommodation facility. Each room has an (optional) List of assigned travellers, which can be used to directly assign the travellers to a specific room.

It is represented by a RoomCode Element holding code and description of the room category. Specific attributes of the room (like room facilities). In addition to that, it holds the selected board 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 room, board or included extras.
<syntaxhighlight lang="xml">
<Room>
<Identifier>01</Identifier>
<AssignedTraveller>
<Identifier>01</Identifier>
<Identifier>02</Identifier>
</AssignedTraveller>
<RoomCode>
<Code>DS</Code>
<Attributes>
<Attribute>
<Code>SAFE</Code>
<Description>Safe</Description>
<AttributeSource>Touroperator</AttributeSource>
</Attribute>
<Attribute>
<Code>DESK</Code>
<Description>Schreibtisch</Description>
<AttributeSource>Touroperator</AttributeSource>
</Attribute>
</Attributes>
<Description>
<Text>Doppelzimmer Superior</Text>
</Description>
<Description>
<Text>Zimmer größer als der Durchschnitt in Paris: 40 m², mit großem Doppelbett</Text>
</Description>
</RoomCode>
<Board>
<Code>BF</Code>
<Description>
<Text>Frühstück</Text>
</Description>
</Board>
<IncludedExtras>
<IncludedExtra>
<ExtraCode>
<Code>WIFI</Code>
<Description>Kostenfreies WLAN auf allen Zimmern</Description>
</ExtraCode>
</IncludedExtra>
</IncludedExtras>
<State>OK</State>
</Room>
</syntaxhighlight>

Accommodation

2018-06-27T06:08:21Z

Sandk: /* Request element */

== Overview ==
Accommodation Services extend the CommonService to carry accommodation 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. Accommodation specific information are held using a List of room 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">
<Accommodation>

...

<Rooms>
<Room>
<Identifier>01</Identifier>
<AssignedTraveller>
<Identifier>01</Identifier>
<Identifier>02</Identifier>
</AssignedTraveller>
<RoomCode>
<Code>DS</Code>
</RoomCode>
<Board>
<Code>BF</Code>
</Board>
<CustomerRequests>
<Description>
<Text>Superior Doppelzimmer mit Frühstück</Text>
</Description>
</CustomerRequests>
</Room>
</Rooms>
</Accommodation>
</syntaxhighlight>
[http://string.drv.de/downloads/releases/release-0.9.2/examples/Booking/UC01rq.xml Full File]

In case of a Request the structure is also capable of holding service related customerRequests for a desired CheckIn/Out time.

==== Available top-level 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 payment
|-
| '''@AssignedTraveller'''|| A list of traveller Ids, representing the traveller assigned to this specific room
|-
| '''@RoomCode'''|| The room category code identifying this specific class of room
|-
| '''@Board'''|| The code representing the assigned mealplan for that room
|-
| '''@CustomerRequests'''|| A List of texts holding customer specific request information
|}

=== Response Element ===
The Response on the other hand is meant to represent the view of the TourOperator on the request. In case of CheckIn/out Times the values are either reflected in meaning of confirmation or correction. The Response also carries more specific information about the requested accommodation service like LocationDetails or a Stay element to inform about charged nights and CheckIn/Out Times.

<syntaxhighlight lang="xml">
<Accommodation>

...

<LocationDetails>
<GeoLocation>
<Longitude>2.314477</Longitude>
<Latitude>48.87173</Latitude>
</GeoLocation>
<Contact>
<Mail>reservations.lebristolparis@oetkercollection.com</Mail>
<Phone>+33 153 43 43 00</Phone>
<URL>http://www.lebristolparis.com/eng/home</URL>
</Contact>
<Address>
<AddressLines>
<AddressLine>Le Bristol Paris</AddressLine>
</AddressLines>
<Street>Rue du Faubourg Saint HonorÃ©</Street>
<Additional>08. Arrondissement - Champs Ã‰lysÃ©es</Additional>
<HouseNumber>112</HouseNumber>
<ZIPCode>75008</ZIPCode>
<City>Paris</City>
<Country>
<Name>Frankreich</Name>
<CountryCode>FR</CountryCode>
</Country>
</Address>
<Regions>
<Region>
<Code>FR-IDF</Code>
<Description>
<Text>Ille de France</Text>
</Description>
</Region>
</Regions>
</LocationDetails>
<Rooms>
<Room>
<Identifier>01</Identifier>
<AssignedTraveller>
<Identifier>01</Identifier>
<Identifier>02</Identifier>
</AssignedTraveller>
<RoomCode>
<Code>DS</Code>
<Description>
<Text>Doppelzimmer Superior</Text>
</Description>
<Description>
<Text>Zimmer größer als der Durchschnitt in Paris: 40 m², mit großem Doppelbett</Text>
</Description>
</RoomCode>
<Board>
<Code>BF</Code>
</Board>
<State>OK</State>
</Room>
</Rooms>
<Stay>
<ChargedNights>7</ChargedNights>
<CheckInOut/>
</Stay>
</Accommodation>
</syntaxhighlight>
[http://string.drv.de/downloads/releases/release-0.9.2/examples/Booking/UC01rs.xml Full File]

=== Room Element ===
A Room-Element, as the name suggests, represents a physical room in the accommodation facility. Each room has an (optional) List of assigned travellers, which can be used to directly assign the travellers to a specific room.

It is represented by a RoomCode Element holding code and description of the room category. Specific attributes of the room (like room facilities). In addition to that, it holds the selected board 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 room, board or included extras.
<syntaxhighlight lang="xml">
<Room>
<Identifier>01</Identifier>
<AssignedTraveller>
<Identifier>01</Identifier>
<Identifier>02</Identifier>
</AssignedTraveller>
<RoomCode>
<Code>DS</Code>
<Attributes>
<Attribute>
<Code>SAFE</Code>
<Description>Safe</Description>
<AttributeSource>Touroperator</AttributeSource>
</Attribute>
<Attribute>
<Code>DESK</Code>
<Description>Schreibtisch</Description>
<AttributeSource>Touroperator</AttributeSource>
</Attribute>
</Attributes>
<Description>
<Text>Doppelzimmer Superior</Text>
</Description>
<Description>
<Text>Zimmer größer als der Durchschnitt in Paris: 40 m², mit großem Doppelbett</Text>
</Description>
</RoomCode>
<Board>
<Code>BF</Code>
<Description>
<Text>Frühstück</Text>
</Description>
</Board>
<IncludedExtras>
<IncludedExtra>
<ExtraCode>
<Code>WIFI</Code>
<Description>Kostenfreies WLAN auf allen Zimmern</Description>
</ExtraCode>
</IncludedExtra>
</IncludedExtras>
<State>OK</State>
</Room>
</syntaxhighlight>

Accommodation

2018-06-11T11:00:34Z

Sandk:

Accommodation

2018-06-11T09:45:21Z

Sandk: Added Room ELement

== Overview ==
Accommodation Services extend the CommonService to carry accommodation 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. Accommodation specific information are held using a List of room 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">
<Accommodation>

...

<Rooms>
<Room>
<Identifier>01</Identifier>
<AssignedTraveller>
<Identifier>01</Identifier>
<Identifier>02</Identifier>
</AssignedTraveller>
<RoomCode>
<Code>DS</Code>
</RoomCode>
<Board>
<Code>BF</Code>
</Board>
<CustomerRequests>
<Description>
<Text>Superior Doppelzimmer mit Frühstück</Text>
</Description>
</CustomerRequests>
</Room>
</Rooms>
</Accommodation>
</syntaxhighlight>
[http://string.drv.de/downloads/releases/release-0.9.2/examples/Booking/UC01rq.xml Full File]

In case of a Request the structure is also capable of holding service related customerRequests for a desired CheckIn/Out time.

=== Response Element ===
The Response on the other hand is meant to represent the view of the TourOperator on the request. In case of CheckIn/out Times the values are either reflected in meaning of confirmation or correction. The Response also carries more specific information about the requested accommodation service like LocationDetails or a Stay element to inform about charged nights and CheckIn/Out Times.

<syntaxhighlight lang="xml">
<Accommodation>

...

<LocationDetails>
<GeoLocation>
<Longitude>2.314477</Longitude>
<Latitude>48.87173</Latitude>
</GeoLocation>
<Contact>
<Mail>reservations.lebristolparis@oetkercollection.com</Mail>
<Phone>+33 153 43 43 00</Phone>
<URL>http://www.lebristolparis.com/eng/home</URL>
</Contact>
<Address>
<AddressLines>
<AddressLine>Le Bristol Paris</AddressLine>
</AddressLines>
<Street>Rue du Faubourg Saint HonorÃ©</Street>
<Additional>08. Arrondissement - Champs Ã‰lysÃ©es</Additional>
<HouseNumber>112</HouseNumber>
<ZIPCode>75008</ZIPCode>
<City>Paris</City>
<Country>
<Name>Frankreich</Name>
<CountryCode>FR</CountryCode>
</Country>
</Address>
<Regions>
<Region>
<Code>FR-IDF</Code>
<Description>
<Text>Ille de France</Text>
</Description>
</Region>
</Regions>
</LocationDetails>
<Rooms>
<Room>
<Identifier>01</Identifier>
<AssignedTraveller>
<Identifier>01</Identifier>
<Identifier>02</Identifier>
</AssignedTraveller>
<RoomCode>
<Code>DS</Code>
<Description>
<Text>Doppelzimmer Superior</Text>
</Description>
<Description>
<Text>Zimmer größer als der Durchschnitt in Paris: 40 m², mit großem Doppelbett</Text>
</Description>
</RoomCode>
<Board>
<Code>BF</Code>
</Board>
<State>OK</State>
</Room>
</Rooms>
<Stay>
<ChargedNights>7</ChargedNights>
<CheckInOut/>
</Stay>
</Accommodation>
</syntaxhighlight>
[http://string.drv.de/downloads/releases/release-0.9.2/examples/Booking/UC01rs.xml Full File]

=== Room Element ===
A Room-Element, as the name suggests, represents a physical room in the accommodation facility. Each room has an (optional) List of assigned travellers, which can be used to directly assign the travellers to a specific room.

It is represented by a RoomCode Element holding code and description of the room category. Specific attributes of the room (like room facilities). In addition to that, it holds the selected board 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 room, board or included extras.
<syntaxhighlight lang="xml">
<v0:Room>
<v0:Identifier>01</v0:Identifier>
<v0:AssignedTraveller>
<v0:Identifier>01</v0:Identifier>
<v0:Identifier>02</v0:Identifier>
</v0:AssignedTraveller>
<v0:RoomCode>
<v0:Code>DS</v0:Code>
<v0:Attributes>
<v0:Attribute>
<v0:Code>SAFE</v0:Code>
<v0:Description>Safe</v0:Description>
<v0:AttributeSource>Touroperator</v0:AttributeSource>
</v0:Attribute>
<v0:Attribute>
<v0:Code>DESK</v0:Code>
<v0:Description>Schreibtisch</v0:Description>
<v0:AttributeSource>Touroperator</v0:AttributeSource>
</v0:Attribute>
</v0:Attributes>
<v0:Description>
<v0:Text>Doppelzimmer Superior</v0:Text>
</v0:Description>
<v0:Description>
<v0:Text>Zimmer größer als der Durchschnitt in Paris: 40 m², mit großem Doppelbett</v0:Text>
</v0:Description>
</v0:RoomCode>
<v0:Board>
<v0:Code>BF</v0:Code>
<v0:Description>
<v0:Text>Frühstück</v0:Text>
</v0:Description>
</v0:Board>
<v0:IncludedExtras>
<v0:IncludedExtra>
<v0:ExtraCode>
<v0:Code>WIFI</v0:Code>
<v0:Description>Kostenfreies WLAN auf allen Zimmern</v0:Description>
</v0:ExtraCode>
</v0:IncludedExtra>
</v0:IncludedExtras>
<v0:State>OK</v0:State>
</v0:Room>
</syntaxhighlight>

Accommodation

2018-05-25T10:55:17Z

Sandk:

Accommodation

2018-05-25T10:05:11Z

Sandk:

2016-11-23T14:59:36Z

Sandk: /* Response Data */

[[Kategorie:UseCases]]

== Use Case: ''Book single flight'' ==

''Book single flight''

'''Module:''' Flight

== Description ==
It has to be possible to book various types of flights with or without an other service (like hotel). Possible flight types are: 
 
- Oneway flight 
A one directional flight that may have multiple Segments combined to one Leg. 
(for Example: VIE -> FRA -> NYC) 
 
- Roundtrip flight 
A bidirectional flight that has a defined outgoing Leg and a defined return Leg where each Leg may consist of multiple Segments. 
The origin of the Outgoing flight is equal to the Destination of the Return flight. 
The destination of the Outgoing flight is equal to the Origin of the Return flight. 
(For example: Outgoing: VIE -> FRA -> NYC; Return: NYC -> CDG -> VIE) 
 
- (Double) Openjaw flights 
Is a roundtrip flight, where outgoing leg and return leg belong together but one or both of the following statements are true: 
The origin of the outgoing flight is not equal to the destination of the return flight. 
The destination of the return flight is not equal to the origin of the return flight. 
 
- Stopover flights 
Is a set of one or more Legs, each Leg consists of multiple Segments. 
The Travellers want to stay for more than one night at a location between origin and destination of the Leg. 
For example: 
 
Outgoing Leg (with Stopover): VIE -> NYC 
01.04.2017 VIE -> FRA 
04.04.2017 FRA -> NYC 
 
Return Leg (without Stopover): NYC -> VIE 
28.04.2017 NYC -> CDG 
29.04.2017 CDG -> VIE 

== Request Data ==
A defined Structure that represents the logical structure of the described flights giving access to the main attributes of each Leg and Segment like: 
- Origin 
- Destination 
- Departure (Date + Time) 
- Arrival (Date + Time) 
- Reference to a Search Result 
- Direction (Outgoing / Return) 
- Assigned Traveller 
Especially it is important to have a reference representing the relationship between Outgoing Leg and its Incoming Leg

== Response Data ==
A reflection of the request structure extended by relevant (optional) data for each Leg and Segment like: 
- Price (amount and currency) 
- Booking State

Book single Flight

2016-11-23T14:57:47Z

Sandk: Die Seite wurde neu angelegt: „ Kategorie:UseCases == Use Case: ''Book single flight'' == ''Book single flight'' '''Module:''' Flight == Description == It has to be possible to book…“

[[Kategorie:UseCases]]

== Use Case: ''Book single flight'' ==

''Book single flight''

'''Module:''' Flight

== Description ==
It has to be possible to book various types of flights with or without an other service (like hotel). Possible flight types are: 
 
- Oneway flight 
A one directional flight that may have multiple Segments combined to one Leg. 
(for Example: VIE -> FRA -> NYC) 
 
- Roundtrip flight 
A bidirectional flight that has a defined outgoing Leg and a defined return Leg where each Leg may consist of multiple Segments. 
The origin of the Outgoing flight is equal to the Destination of the Return flight. 
The destination of the Outgoing flight is equal to the Origin of the Return flight. 
(For example: Outgoing: VIE -> FRA -> NYC; Return: NYC -> CDG -> VIE) 
 
- (Double) Openjaw flights 
Is a roundtrip flight, where outgoing leg and return leg belong together but one or both of the following statements are true: 
The origin of the outgoing flight is not equal to the destination of the return flight. 
The destination of the return flight is not equal to the origin of the return flight. 
 
- Stopover flights 
Is a set of one or more Legs, each Leg consists of multiple Segments. 
The Travellers want to stay for more than one night at a location between origin and destination of the Leg. 
For example: 
 
Outgoing Leg (with Stopover): VIE -> NYC 
01.04.2017 VIE -> FRA 
04.04.2017 FRA -> NYC 
 
Return Leg (without Stopover): NYC -> VIE 
28.04.2017 NYC -> CDG 
29.04.2017 CDG -> VIE 

== Request Data ==
A defined Structure that represents the logical structure of the described flights giving access to the main attributes of each Leg and Segment like: 
- Origin 
- Destination 
- Departure (Date + Time) 
- Arrival (Date + Time) 
- Reference to a Search Result 
- Direction (Outgoing / Return) 
- Assigned Traveller 
Especially it is important to have a reference representing the relationship between Outgoing Leg and its Incoming Leg

== Response Data ==
A reflection of the request structure extended by relevant data like: 
- Price (amount and currency) 
- Booking State