| Submitter
Information |
| Q |
1 |
Organization
Name |
|
|
Please enter your company name. |
| A |
1 |
|
| Q |
2 |
Contact
Information |
|
|
Please enter the name of the author of this
conformance statement
questionnaire. |
| A |
2 |
|
| Product Information |
|
Note
to submitter: The information provided in this section must match
the name and version information provided on the registration form when
registering this product for certification. Please refer to section 3
of
the Guide to HTNG Certification.
|
| Q |
3 |
Product
Name |
|
|
Please enter the name of the product for which this
application is being
made. |
| A |
3 |
|
| Q |
4 |
Product
Version/Identifier |
|
|
Please enter the version number (or other
identifier) of the product for which this
application is being made. |
| A |
4 |
|
| Scope of
Certification |
| Q |
5 |
Roles |
|
|
The Product Specification requires conformance to
the Framework 2.0 Specification
and, optionally, the Single Guest Itinerary Specification. Please
indicate to which specifications the product conform. |
| A |
5 |
| HTNG Framework 2.0 Specification (mandatory) |
YES/NO |
| HTNG Single Guest Itinerary Specification
(optional) |
YES/NO |
|
| Framework
2.0 Conformance (mandatory) |
| Q |
6 |
Identify
the Web Services that utilize
Framework 2.0 |
|
|
Please identify each Web service supported. The
first four services correspond to
published HTNG Specifications. The fifth entry allows for proprietary
services to be referenced.
Interoperability may be demonstrated by providing one of the following
- The name of other
companies with whom you have successfully interoperated
- A test report from
internal testing. These can be either a URL on your own website or as inline text in the
Supporting
Document Table below.
- Other evidence of a
successful implementation.
At least one web service must be implemented.
|
| A |
6 |
| Web
Services Implemented |
Web Service Name
|
Interoperable Vendors, Test Report URL, or
Supporting Document Number (see table
below) |
| HTNG Single Guest Itinerary Version 1.01 |
YES/NO |
|
| HTNG Property/Distribution Usage Profile -
Reservations Version 1.0.4 |
YES/NO |
|
| HTNG Property/Distribution Usage Profile -
Availability Version 1.0.2 |
YES/NO |
|
| HTNG Property/Distribution Usage Profile - Rates
Version 1.0.3 |
YES/NO |
|
| Proprietary System(s) |
YES/NO |
|
|
| Q |
7 |
Details of Proprietary
Systems |
|
|
Please
provide a summary description of
proprietary systems identified in A6.
Add rows to the table as required. |
| A |
7 |
| System
Name |
Version Number |
Summary of System Details |
Contact Name |
Date of Implementation |
|
|
|
|
|
|
| Q |
8 |
Supporting Documents |
|
|
The
Product Specification defines six possible
supporting documents which provide evidence of conformance. Four of
these are mandatory and denoted by shading. The Published API
Specification should be used to reference the published HTNG
specification that is supported. These documents may be provided
either as a URL to an external site or as inline text in the Supporting Document Table
below.
Replicate this table for each of Web Service supported. |
| A |
8 |
| <insert Web
Service name> |
| Documentation
Provided |
Mandatory/
Optional |
HTNG
Specification Reference, URL, or Supporting Document Number (see table
below) |
| WSDL |
Mandatory |
|
| Schemas
externally referenced in WSDL |
Mandatory |
|
| SOAP
Packet Trace |
Mandatory |
|
| Published
API Specification |
Mandatory for HTNG defined Web Services |
|
| Write-up on WS Security
Implementation |
Optional |
|
| Write-up on WS Addressing
Implementation |
Optional |
|
|
| Q |
9 |
Communication
Style |
|
|
Indicate
which communication methods the
product supports. At least one communication style must be supported.
The Asynchronous style is not defined in this version of the
Product Specification.. |
| A |
9 |
| Communication Style |
| Synchronous |
YES/NO |
| Asynchronous |
Not
applicable in this version of the Product Specification |
|
| Single
Guest Itinerary Conformance
(optional) |
| Q |
10 |
Roles |
| |
|
Please
check all roles that the product will
certify as in the Single Guest Itinerary Web Services. At least one
role must be supported. |
| A |
10 |
| Role |
| Activity Reservation System |
YES/NO |
| Accommodation Reservation
System |
YES/NO |
| Posting System |
YES/NO |
| Folio System |
YES/NO |
| Customer Profile System |
YES/NO |
| Itinerary Consolidation System |
YES/NO |
| Itinerary Display System |
YES/NO |
|
| Q |
11 |
Activity Reservation System Role |
| |
|
If
the product performs the role of an Activity
Reservation System please indicate which functions and messages are
supported. Shaded cells indicate mandatory functionality. Black
cells are not applicable. |
| A |
11 |
| Function/Message
Description |
Function/Message Name |
Mandatory/
Optional |
Can provide these web service functions |
Can initiate these
messages |
| Lookup Activities for matching
guests |
ActivityLookup |
Mandatory |
YES/NO |
|
| Create Activity |
CreateActivity |
Mandatory |
|
YES/NO |
| Update Activity |
UpdateActivity |
Mandatory |
|
YES/NO |
| Cancel Activity |
CancelActivity |
Mandatory |
|
YES/NO |
| List Activities for a specific
guest |
FetchActivities |
Mandatory |
YES/NO |
|
| Lookup Matching Guest Profiles |
ProfileLookup |
Mandatory |
YES/NO |
YES/NO |
| Fetch detailed information for
a specific guest profile |
FetchProfile |
Mandatory |
YES/NO |
YES/NO |
| Create new profile |
NewProfile |
Optional |
YES/NO |
YES/NO |
| Modify existing profile |
UpdateProfile |
Mandatory |
YES/NO |
YES/NO |
| Notify when appointment time
is outside of stay dates |
OutOfScopeNotification |
Mandatory |
YES/NO |
|
| Notification of status change |
GuestStatusNotification |
Mandatory |
YES/NO |
|
| Link new profile ID to another
system |
Subscription |
Mandatory |
YES/NO |
YES/NO |
| Lookup matching reservations |
ReservationLookup |
Optional |
|
YES/NO |
| Fetch specific reservation
details |
FetchReservation |
Optional |
|
YES/NO |
| Notify of guest location |
LocationNotification |
Optional |
|
YES/NO |
| Send guest message |
GuestMessage |
Optional |
|
YES/NO |
|
| Q |
12 |
Accommodation Reservation System |
| |
|
If
the product performs the role of an
Accommodation Reservation System please indicate which functions and
messages are supported. Shaded cells indicate mandatory
functionality. Black cells are not applicable. |
| A |
12 |
| Function/Message
Description |
Function/Message Name |
Mandatory/
Optional |
Can provide these web service functions |
Can initiate these
messages |
| Notify when reservation stay
date range with scheduled appointment is moved outside of appointment
date |
OutOfScopeNotification |
Mandatory |
|
YES/NO |
| Notification of status change |
GuestStatusNotification |
Mandatory |
|
YES/NO |
| Lookup matching reservations |
ReservationLookup |
Mandatory |
YES/NO |
|
| Fetch specific reservation
details |
FetchReservation |
Mandatory |
YES/NO |
|
| Notify of guest location |
LocationNotification |
Mandatory |
YES/NO |
|
| Send guest message |
GuestMessage |
Mandatory |
YES/NO |
|
|
| Q |
13 |
Posting System |
| |
|
If
the product performs the role of an Posting
System please indicate which functions and messages are supported.
Shaded cells indicate mandatory functionality. Black cells are
not applicable. |
| A |
13 |
| Function/Message
Description |
Function/Message Name |
Mandatory/
Optional |
Can provide these web
service functions |
Can initiate these
messages |
| Post charge |
PostPayment |
Mandatory |
|
YES/NO |
|
| Q |
14 |
Folio System |
| |
|
If
the product performs the role of an Folio
System please indicate which functions and messages are supported.
Shaded cells indicate mandatory functionality. Black cells are
not applicable. |
| A |
14 |
| Function/Message Description |
Function/Message Name |
Mandatory/
Optional |
Can provide these web
service functions |
Can initiate these messages |
| Post charge for related activity |
PostPayment |
Mandatory |
YES/NO |
|
|
| Q |
15 |
Customer Profile System |
| |
|
If
the product performs the role of an Customer
Profile System please indicate which functions and messages are
supported. Shaded cells indicate mandatory functionality. Black
cells are not applicable. |
| A |
15 |
| Function/Message
Description |
Function/Message Name |
Mandatory/
Optional |
Can provide these web
service functions |
Can initiate these messages |
| Lookup Matching Guest Profiles |
ProfileLookup |
Mandatory |
YES/NO |
YES/NO |
| Fetch detailed information for
a specific guest profile |
FetchProfile |
Mandatory |
YES/NO |
YES/NO |
| Create new profile |
NewProfile |
Optional |
YES/NO |
YES/NO |
| Modify existing profile |
UpdateProfile |
Mandatory |
YES/NO |
YES/NO |
| Link new profile ID to another
system |
Subscription |
Mandatory |
YES/NO |
YES/NO |
|
| Q |
16 |
Itinerary
Consolidation System |
| |
|
If
the product performs the role of an
Itinerary Consolidation System please indicate which functions and
messages are supported. Shaded cells indicate mandatory
functionality. Black cells are not applicable. |
| A |
16 |
| Function/Message Description |
Function/Message Name |
Mandatory/
Optional |
Can provide these web
service functions |
Can initiate these
messages |
| Lookup Activities for matching guests |
ActivityLookup |
Mandatory |
YES/NO |
YES/NO |
| Create Activity |
CreateActivity |
Mandatory |
YES/NO |
|
| Update Activity |
UpdateActivity |
Mandatory |
YES/NO |
|
| Cancel Activity |
CancelActivity |
Mandatory |
YES/NO |
|
| List Activities for a specific guest |
FetchActivities |
Mandatory |
YES/NO |
YES/NO |
|
| Q |
17 |
Itinerary Display System |
| |
|
If
the product performs the role of an
Itinerary Display System please indicate which functions and messages
are supported. Shaded cells indicate mandatory functionality.
Black cells are not applicable. |
| A |
17 |
| Function/Message
Description |
Function/Message Name |
Mandatory/
Optional |
Can provide these web
service functions |
Can initiate these messages |
| List Activities for a specific
guest |
FetchActivities |
Mandatory |
|
YES/NO |
| Lookup matching reservations |
ReservationLookup |
Mandatory |
|
YES/NO |
|
| Certification
Summary |
| |
|
The
Trademark License Agreement allows for a
Certification Summary to be required to be displayed along with the
Trademark. For this Product Specification, the form of the
summary is a table as follows: |
| |
|
| Date of
joining HTNG |
<insert
date> |
| Date of
achieving Property Web Services certification |
<insert
date> |
| HTNG
Framework 2.0 supported? |
YES/NO |
| |
HTNG Property/Distribution
Usage Profile - Reservations supported? |
YES/NO |
| |
HTNG Property/Distribution
Usage Profile - Availability supported? |
YES/NO |
| |
HTNG Property/Distribution
Usage Profile - Rates supported? |
YES/NO |
| HTNG Single
Guest Itinerary (SGI) supported? |
YES/NO |
| The following entries are only required if HTNG
Single Guest Itinerary is
supported. |
| |
HTNG SGI Activity Reservation
System role supported? |
YES/NO |
| |
HTNG SGI Accommodation
Reservation System role supported? |
YES/NO |
| |
HTNG SGI Posting System role
supported? |
YES/NO |
| |
HTNG SGI Folio System role
supported? |
YES/NO |
| |
HTNG SGI Customer Profile
System role supported? |
YES/NO |
| |
HTNG SGI Itinerary
Consolidation System role supported? |
YES/NO |
| |
HTNG SGI Itinerary Display
System role supported? |
YES/NO |
|
| Supporting Document Table |
| |
|
The following table is provided for supporting
documents identified in Q6 and Q8. If
the document cannot be referenced as a URL, please insert the contents
of the document into a row of the table below, adding an
appropriate title and referencing it in A6 or A8 above. Insert
additional table entries as required.
|
| |
|
| |
Document
Title |
| 1 |
For
Q6 <insert web service name> - Interoperability
Test Report
or
for Q8 <insert web service name> -
<insert document title> |
| <insert document text> |
|