at&t u-verse ® enabled developer guidelines...pecuniary loss, arising out of or in any way...

© 2013 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.

AT&T U-verse® Enabled Developer Guidelines

Publication Date: November 1st, 2013

Legal Disclaimer


i

This document and the information contained herein (collectively, the "Information") is provided to you (both the individual receiving

this document and any legal entity on behalf of which such individual is acting) ("You" and "Your") by AT&T, on behalf of itself and

its affiliates ("AT&T") for informational purposes only. AT&T is providing the Information to You because AT&T believes the

Information may be useful to You. The Information is provided to You solely on the basis that You will be responsible for making

Your own assessments of the Information and are advised to verify all representations, statements and information before using or

relying upon any of the Information. Although AT&T has exercised reasonable care in providing the Information to You, AT&T does

not warrant the accuracy of the Information and is not responsible for any damages arising from Your use of or reliance upon the

Information. You further understand and agree that AT&T in no way represents, and You in no way rely on a belief, that AT&T is

providing the Information in accordance with any standard or service (routine, customary or otherwise) related to the consulting,

services, hardware or software industries.

AT&T DOES NOT WARRANT THAT THE INFORMATION IS ERROR-FREE. AT&T IS PROVIDING THE INFORMATION TO YOU

"AS IS" AND "WITH ALL FAULTS." AT&T DOES NOT WARRANT, BY VIRTUE OF THIS DOCUMENT, OR BY ANY COURSE OF

PERFORMANCE, COURSE OF DEALING, USAGE OF TRADE OR ANY COLLATERAL DOCUMENT HEREUNDER OR

OTHERWISE, AND HEREBY EXPRESSLY DISCLAIMS, ANY REPRESENTATION OR WARRANTY OF ANY KIND WITH

RESPECT TO THE INFORMATION, INCLUDING, WITHOUT LIMITATION, ANY REPRESENTATION OR WARRANTY OF

DESIGN, PERFORMANCE, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, OR

ANY REPRESENTATION OR WARRANTY THAT THE INFORMATION IS APPLICABLE TO OR INTEROPERABLE WITH ANY

SYSTEM, DATA, HARDWARE OR SOFTWARE OF ANY KIND. AT&T DISCLAIMS AND IN NO EVENT SHALL BE LIABLE FOR

ANY LOSSES OR DAMAGES OF ANY KIND, WHETHER DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, PUNITIVE,

SPECIAL OR EXEMPLARY, INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS

INTERRUPTION, LOSS OF BUSINESS INFORMATION, LOSS OF GOODWILL, COVER, TORTIOUS CONDUCT OR OTHER

PECUNIARY LOSS, ARISING OUT OF OR IN ANY WAY RELATED TO THE PROVISION, NON-PROVISION, USE OR NON-USE

OF THE INFORMATION, EVEN IF AT&T HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSSES OR DAMAGES.

Table of Contents


ii

Contents

1 Introduction .......................................................................................................................................... 1

1.1 Terminology .................................................................................................................................. 1

1.2 AT&T U-verse Enabled Master License Agreement ...................................................................... 1

2 Application Acceptance Guidelines....................................................................................................... 2

2.1 Branding Guidelines ...................................................................................................................... 2

2.2 User Interface Guidelines.............................................................................................................. 3

2.3 Goodwill / Community Guidelines ................................................................................................ 3

2.4 Advertising and Marketing ............................................................................................................ 4

2.5 Privacy and Legal Requirements ................................................................................................... 4

2.6 Application FAQs ........................................................................................................................... 5

2.7 Prohibitions ................................................................................................................................... 5

2.7.1 Data Collection and Usage .................................................................................................... 5

2.7.2 Objectionable Content .......................................................................................................... 6

2.7.3 Content Restrictions.............................................................................................................. 6

2.8 Testing Criteria .............................................................................................................................. 7

2.9 Acceptance Testing Failure Procedure ....................................................................................... 10

2.10 Application Revocation ............................................................................................................... 10

3 Best Practices ...................................................................................................................................... 11

3.1 Handle SetTopBox powerModeOff Correctly ............................................................................. 11

3.2 Tune to URL Media Guidelines.................................................................................................... 11

3.2.1 Audio ................................................................................................................................... 11

3.2.2 Video/Audio ........................................................................................................................ 12

3.3 U-verse Enabled Function Progress ............................................................................................ 12

3.4 Help and About ........................................................................................................................... 13

Table of Contents


iii

3.5 Application Hidden Features ....................................................................................................... 13

4 Other Useful Information .................................................................................................................... 14

4.1 FAQs ............................................................................................................................................ 14

4.2 Contact AT&T Developer Support ............................................................................................... 14

4.3 Control Panel ............................................................................................................................... 14

4.4 Developer Guidelines Update Process ........................................................................................ 14


Page 1 of 14

1 Introduction

This document’s main purpose is to detail AT&T’s developer guidelines for the U-verse Enabled platform and associated SDK. For the developer, the purpose of this document is to inform you of what is possible with the U-verse Enabled platform and the types of criteria against which AT&T will perform acceptance testing on your application.

1.1 Terminology

Application - A software program that provides a useful function. The type of application may be specified by the device it is intended for. Receiver applications run on the U-verse receiver. Device or U-verse Enabled applications run on a LAN-connected device, such as a smartphone or personal computer.

Associate, Association - A durable relationship between a U-verse Enabled capable device and a U-verse receiver that allows an application on the device to engage the receiver; association options are managed by the U-verse "My Enabled Devices" receiver application on channel 9301.

AT&T U-verse Enabled Developer Ecosystem – The overall process for a developer to work with AT&T to develop U-verse Enabled applications.

Discovery - A device application function which identifies UvE-capable receivers that are visible on the Local Area Network.

Engage, Engagement - A short-term relationship between an application and a U-verse receiver, during which the application may use the UvE application programming interface (API) to send commands to the receiver, and retrieve information from the receiver.

Receiver (Set Top Box) – The residential device that enables the user to watch and record AT&T U-verse programming. The receiver may or may not support DVR functions.

1.2 AT&T U-verse Enabled Master License Agreement

You are responsible for adhering to all the legal terms and conditions outlined in the AT&T U-verse Enabled Master License Agreement. You can find the Master License Agreement on the AT&T Developer Program web site.


Page 2 of 14

2 Application Acceptance Guidelines

2.1 Branding Guidelines

These guidelines ensure that AT&T, its products and brand are accurately and fairly reflected in the application, any marketing and PR.

References within the application to the “available receivers” need to include either:

o AT&T U-verse, text or logo

o U-verse TV, text or logo

References to AT&T brand will need to include AT&T U-verse Enabled in the following scenarios:

o Application Name – U-verse when developed by/for U-verse specifically

o Application Store Description – U-verse Enabled required in all

application descriptions

o Key Word Search Terms – AT&T U-verse Enabled required for all

applications

o Any use of AT&T, U-verse Enabled or any combination in any PR,

branding or marketing

All uses of the AT&T name and brand will require AT&T review and approval before public use

o Can be delivered via screen shots or content submissions

Our aim is to clearly present the AT&T signature as secondary, without overwhelming your logo. Although there is no set formula for size relationship between your logo and the AT&T signature, consider the sizes and shapes of both logos, as well as the application itself, to properly design your layout.

The AT&T signature may range in size from one-fourth to one-half the size of your logo depending on the graphic impact of that logo.

Your logo should be the more visually dominant or prominent logo, with the AT&T logo being secondary, but clearly visible.

Always allow adequate clear space to ensure separation from copy. In addition, maintain a space between your logo and the AT&T signature. This space should be at least 4x the width of the AT&T signature globe.

When the AT&T logo is one of multiple secondary logos displayed, all secondary logos should be of equal visual prominence. Avoid crowding of secondary logos by maintaining a minimum of 2x between logos.


Page 3 of 14

In addition, to accurately display the applicable logos, always use descriptive copy to explain the relationship between the companies.

Approved Logos (Register on the brand site and download approved “AT&T U-verse” logos from the Brand page):

2.2 User Interface Guidelines

The guidelines are meant to ensure our customers see the same language consistently, particularly when pairing. Developers have almost complete control over the user-interface, but AT&T has a few requirements:

The set top box is always referred to as an AT&T U-verse Receiver.

Applications should not alter the functions of standard remote control commands.

All U-verse Enabled apps should provide a consistent method for customers to manage devices and receivers. Developers must comply with all requirements and steps as demonstrated in the AT&T U-verse ® Enabled User Device Interface Design Guidelines. Developers may skin the interface to match the overall application design, but should not change any of the user flows or interactions. Minor content changes are allowed as long as they do not violate any branding guidelines or change the user interactions.

2.3 Goodwill / Community Guidelines

The following general guidelines advise how to interact with other developers, content providers, and U-verse customers. In general, the guidelines are common sense. Treat people well and build apps meant to provide value, and do not cause harm. General guidelines:

https://brand.att.com/att/scripts/asset/result.aspx?nodeid=-6&libid=5

https://brand.att.com/att/scripts/asset/result.aspx?nodeid=-6&libid=5


Page 4 of 14

1. We will not accept applications that are derogatory, defamatory, or otherwise provide inappropriate, objectionable (see below), or abusive content that insults or otherwise injures content providers, other developers or AT&T U-verse customers.

2. Developers are expected to act professionally and treat each other with respect while interacting online, or otherwise.

3. We expect applications to be accurately represented. We will not accept applications that appear to be created to deceive or have malicious intent.

4. Applications must respect the privacy of end users and other developers.

5. AT&T cares about children. Applications should adequately protect children from mature content.

2.4 Advertising and Marketing

AT&T U-verse Enabled marketing strategy is intended to present a unified and cohesive awareness of all the supported and specialized applications delivered by this cutting edge platform. The approach will allow our members to easily find, download, use applications, and share awareness with their U-verse family.

Applications will be marketed under the AT&T U-verse Enabled umbrella

Best effort will be made but not guaranteed to message individual applications in acquisition and member tactics when possible

Efforts will be made in the following standard tactics:

o On-Air Member tactics

o Print Member and Acquisition tactics

o Online Member and Acquisition tactics

o Social Media

AT&T will provide a PR kit to guide unacceptable press representation

AT&T will review and approve any joint press

No press or announcement of the alliance/development/product launch will be released without AT&T approval

2.5 Privacy and Legal Requirements

As the provider of the Application, You are responsible for protecting the privacy and legal rights of Your users. At a minimum, AT&T requires the following:


Page 5 of 14

Your Application must include and You must give Your users access to a Privacy Policy which outlines Your use of customer information, including but not limited to personally identifiable information (collectively, “Personal Information”).

If your Application accesses or uses Personal Information, you must make the user aware that the Personal Information will be available to you or anyone else that may receive the Personal Information.

If your application stores Personal Information or causes Personal Information to be stored by you in any way, you must do so securely utilizing current, commercially reasonable security measures.

Any form of data collection for Personal Information or other data must comply with all applicable privacy laws and regulations.

Your application must include a commercially reasonable end user license agreement (“EULA”) or terms of service (“TOS”) which is solely between you and the Customer and that complies with all applicable laws. AT&T will have no responsibility or liability whatsoever to the end user customer under your EULA or TOS.

You must inform users that Your application will continue to run and collect information until the user closes Your application.

2.6 Application FAQs

To ensure a seamless experience for our consumers, we suggest each application include a set of FAQs on U-verse pairing and other topics.

2.7 Prohibitions

2.7.1 Data Collection and Usage

Data collected through the use of the U-verse Enabled platform is subject to limitations. As a general requirement, data may only be collected and used to support the primary functions of Your Application which should directly benefit Your users, for example, customizing or personalizing Your Application. Applications should not be designed explicitly for the purposes of gathering data to support advertising or other commerce activity outside your application. Other requirements include:

Any data collection must be done in a manner consistent with Your Privacy Policy.


Page 6 of 14

You may not provide data which is collected through the U-verse Enabled platform to third-parties for the purposes of marketing or advertising without explicit approval by AT&T and the customer.

Without limiting any other restrictions in these U-verse Enabled Developer Guidelines or the related Master License Agreement, any information collected by You or Your Application may be shared outside the Application only when the sharing is initiated by the user.

2.7.2 Objectionable Content

The following types of content have been deemed objectionable and will not be accepted:

Pornographic content

Excessively violent content

Content which defames religion, culture, race, and/or ethnicity

2.7.3 Content Restrictions

Due to AT&T’s contractual relationships with content providers, Your Application must comply with a number of restrictions related to (1) how video is displayed on the TV and (2) other events within U-verse that your application may initiate. Those restrictions include the following:

Your Application shall not tune a customer away from U-verse TV content, invoke a U-verse menu or application (e.g., U-bar, Multiview, etc.), or do any other action which impacts the customers’ viewing of U-verse TV content (collectively, “tune events”) unless the customer explicitly initiates such tune events using Your Application (for example, the customer clicks on a button to tune to a specific channel, etc.). There shall be no tune events within Your Application:

o That are automatically synced to particular programming or content

displayed in Your Application or to content or programming (including

commercials) being displayed on a customer’s TV screen (for example,

automatically tuning away from a TV program when a specific event

within the Application or on the TV occurs); or

o That automatically, without explicit action on the part of the customer,

take the customer away from the U-verse TV content currently displayed

on the customer’s TV screen.

Your Application shall not display any content, information, or other images (whether or not initiated or created by the customer) on a customer’s TV


Page 7 of 14

screen at the same time U-verse TV content appears on the same screen. This includes, but is not limited to, content appearing beside, over, under, or around, a reduced version of the U-verse TV content ("Squeezeback" – defined further below) ,or the Overlay of any content on top of U-verse TV content.

AT&T is not providing you with a license or rights for any content contained within your application (e.g., images, logos, videos, etc.). You are solely responsible for obtaining all licenses and consents required for any and all content appearing within Your Application.

As used in this section, the following terms shall have the following meaning:

“Squeezeback” means shrinking or minimizing the television screen viewing area in which the U-verse TV content appears and then displaying content, information, or images in the television screen border areas surrounding the U-verse TV content.

“Overlay” means any content, information or other image that partially or fully covers any onscreen U-verse TV content.

“U-verse TV content” means any and all content that is provided to a customer by AT&T U-verse as part of their U-verse TV service, including, but not limited to, live, recorded (i.e., DVR), pay-per-view or on-demand content.

2.8 Testing Criteria

Your applications will be acceptance tested against the following requirements when you submit to AT&T:

6. The specified application must be able to associate with the U-verse receiver on the network and engage with the receiver.

7. If the application has a remote control function, the application must execute appropriately when the function is used. (i.e. If the application has a remote functionality, then each remote control key used must function appropriately.)

8. If the application has a search function, the application must execute appropriately when the function is used.

9. AT&T U-verse branding must exist within any application store description. The application must be categorized or labeled as U-verse Enabled in the application storefront. If the application does contain AT&T U-verse branding, then it must follow the branding guidelines in Section Branding Guidelines2.1 Branding Guidelines.

10. Text for AT&T must always be in lowercase when found next to the AT&T logo (e.g. at&t).


Page 8 of 14

11. All AT&T guidelines following secondary logos and signatures are applied to the application. The AT&T logo/signature should be considered/represented secondary (smaller) when compared to the associate's logo/signature.

12. References will need to include AT&T U-verse Enabled in the following scenarios: Any use of AT&T, U-verse Enabled or any combination in any PR, branding or marketing.

13. All uses of the AT&T name and brand within the application must have been previously approved.

14. If no U-verse receivers are displayed to user, the application must not connect to any U-verse receivers.

15. If there are two receivers on the same U-verse account and one is set to custom mode and the other is not set up for U-verse Enabled, the application must connect to the receiver in custom mode.

In order to engage a receiver in custom mode, the application must prompt user for a PIN. User must not be able to engage a receiver in custom mode without entering a correct PIN.

For a receiver in custom mode, user must not be able to use the same PIN on multiple devices.

16. If there are multiple receivers on the same U-verse account that are set up for U-verse Enabled, the application must be able to connect to any receiver that has been set up for U-verse Enabled.

17. When receiver is in custom mode, if user cancels PIN entry, the application must not associate with receiver. The previous association status must be retained.

18. The application must display an appropriate error message if the wrong numbers are entered during association with a receiver in custom mode.

Note: For the appropriate error messages, see AT&T U-verse ® Enabled User Device Interface Design Guidelines.

19. If the receiver mode is set to disabled during association, the application must display an appropriate error message. The disabled receiver should not appear in the list of U-verse receivers.


20. The application must display an appropriate error message if the user attempts to connect to a U-verse receiver, but is not connected to Wifi.



Page 9 of 14

21. The application must display an appropriate error message if the user attempts to connect to a U-verse receiver, but is not connected to a U-verse wireless network.


22. The application must display an appropriate error message if the user attempts to connect to a U-verse receiver, but is not connected to the internet.


23. The user must be able to switch device association from receiver A to receiver B, and vice versa. These receivers must be on the same U-verse account.

24. Applications must include an end user license agreement or terms of service as well as a privacy policy. It is preferred that users accept the policies during setup, but not a requirement.

25. The application must not tune away from the television content unless the user initiates the process through the application.

26. The application must not modify U-verse channel content in any way prohibited by the guidelines, including the use of audio or video overlays, or improper re-sizing (“squeezeback”). The audio and video on channel should never be separated.

27. While an application is being executed, a received phone call should be handled gracefully, and in such a way that the user’s U-verse experience is not impaired.

28. While an application is being executed, a received message should be handled gracefully, and in such a way that the user’s U-verse experience is not impaired.

29. The application must not alter the functions of standard remote control commands.

30. The application must not crash.

31. The application must not have any objectionable content. The following types of content have been deemed objectionable and will not be accepted:

o Pornographic content

o Excessively violent content

o Content which defames religion, culture, race, and/or ethnicity


Page 10 of 14

32. The application must not monitor the user’s television watching habits while in the background.

33. Application must not be profane, derogatory, aimed to defame or to otherwise provide inappropriate or abusive types of content that would insult or otherwise injure content providers, other developers or AT&T U-verse customers.

34. The application functionality must match the application description provided.

35. The application category listed must be appropriate based on application content and functionality.

36. If an application contains mature content, the application must prompt the user to certify that they are over the age of responsibility.

2.9 Acceptance Testing Failure Procedure

If your application doesn’t pass AT&T’s acceptance testing process, you’ll be notified through our U-verse Control Panel. You will have the opportunity to make any necessary changes to your application and resubmit when ready. The Control Panel is accessed from the Launch Center tab in the header when you are signed in to developer.att.com.

2.10 Application Revocation

If your application is in the market and violates AT&T’s testing criteria, AT&T reserves the right to disable the U-verse Enabled functionality in your application.


Page 11 of 14

3 Best Practices

This section provides some suggestions to help developers avoid potentially confusing situations.

3.1 Handle SetTopBox powerModeOff Correctly

If a SetTopBox is returned by the U-verse Enabled Server, but the U-verse Enabled library never received an SSDP response from it (it is powered off, or not even in the household anymore), then the powerMode property of that SetTopBox is powerModeOff.

It’s up to the developer to determine how this information might be used. For example, the application could list the powered-off receiver, but display a warning message if the user tries to select it, advising the user to turn the receiver on. Alternatively, the application could filter that receiver from the list.

3.2 Tune to URL Media Guidelines

To achieve a successful user experience, it is important to use properly-encoded media. Because of the great variability in media successful playback cannot be guaranteed. Start by consulting the guidelines in AT&T U-verse ® Enabled Audio-Visual Formats Supported. In addition, AT&T recommends testing video media whenever possible for successful playback before making it available to consumers.

TuneToURL functionality requires a separately hosted web site that exposes the media file to direct url access. TuneToURL functionality will only support direct media access. It does not provide web browser support. A direct URL to the media is required when using the TuneToURL functionality.

3.2.1 Audio

For encoding audio, AT&T recommends using Windows Media Audio encoded content, commonly referred to as .WMA. The WMA-9/9.2 or WMA professional codec at 48 Khz has tested successfully. Better quality is available by using the WMA Professional codec option. A suggested audio rate of 96 kbps for WMA Professional is recommended.

As noted above, let AT&T U-verse ® Enabled Audio-Visual Formats Supported guide your design decisions. In addition, AT&T recommends testing audio media whenever possible for successful playback before making it available to consumers.

Currently, there is a limitation that prevents play back of stand-alone, AAC-encoded .MP4 audio files. However, they can be used as part of an MP4 video


Page 12 of 14

stream. (See below). MP3 files are supported by U-verse receivers. Please note that MP3 encoding files will be incompatible with the U-verse Client on the Microsoft XBOX 360.

3.2.2 Video/Audio

For encoding video, AT&T recommends H.264 MP4 encoding. For H.264 encoded video, AT&T recommends using HE-AACv1 audio. AAC-LC is also supported An audio rate of 96 kbps for stereo audio is desirable for music fidelity. The H.264 Main Profile codec option is recommended for video. Only single bit rate encoding is permitted. Adaptive or multi-bit rate encoding is not currently supported. Only non-fragmented MP4 encoding is supported. The fragmented MP4 container, used in the Microsoft Smooth Streaming specification, is not currently supported.

Media assets may include CEA-608 and/or CEA-608 plus CEA-708 closed captions.

Note that files must be encoded as “streaming-ready” which will put the in-stream metadata (the MOOV section) near the start of the file, before the media data payload (the MDAT section). Failure to do this will result in a failure to initiate playback.

Video resolutions of 640 x 480 p 24/30 (SD), 720 x 480 p 24/30 (Enhanced SD), and 1280 x 720 p 24/30 (720p) are supported. AT&T recommends testing media whenever possible for successful playback before making it available to consumers, and ensuring that there is enough bandwidth to support the resolution of the media for smooth playback.

For further details about the media formats supported please refer to the AT&T U-verse ® Enabled Audio-Visual Formats Supported guide.

3.3 U-verse Enabled Function Progress

Any U-verse Enabled function selected in the application should display evidence of activity within five seconds. There should be some visual indication that the function is being performed. The visual indication can be anything that the user would understand as a response, such as:

prompting for user input;

displaying splash screens or progress bars;

displaying text such as “Please wait...”, etc.


Page 13 of 14

3.4 Help and About

An application with user interface capable of displaying information to the user should contain standard Menu items Help & About (or equivalent information in a format easily found and understood by the user) to explain to the user how the Application works.

The user should also be able to easily identify the exact version of the application installed, the developer of the application, and the developer contact details.

If it is clear that the application’s purpose requires network coverage to operate, then it would be sufficient for the Help to be provided through a browser connection rather than being contained in the application. In the case where most functions of the application can be used while the device is offline, then the application should have Help that can be accessed without needing a data connection.

Menu items like Help and About should be presented on the main menu or other easily-found screen of the application.

About functions should contain the application name, application version number and author information.

Help should include the aim of the application, usage of the keys (e.g. for games) and other instructions. If the text of the help is too long, it should be divided into smaller sections and/or organized differently.

Help must be accurate and consistent with the application functionality and the handset specifics.

3.5 Application Hidden Features

The application should not introduce any hidden features: its functionality set should be consistent with the help and it should not harm the data on the device. However, the following hidden functions are OK:

Cheat codes and the unlocking of an application to upgrade from a demo version to a full version.


Page 14 of 14

4 Other Useful Information

4.1 FAQs

You can find answers to commonly asked questions in the FAQ listings.

4.2 Contact AT&T Developer Support

If you are experiencing problems in the development or management of your U-verse Enabled application, we recommend you look in our Developer Forum or in the FAQs.

Search for your issue in the Developer Forum and post to get help from the community. These forums are also monitored by AT&T Developer Support personnel.

If you need further assistance, and you have access to our help ticket system, please log a ticket by going to the Support tab in the header and selecting Log A Ticket. You must be signed in to developer.att.com to be able to log a ticket.

4.3 Control Panel

You can check on the status of your submitted U-verse Enabled application in the U-verse Control Panel which is accessed from the Launch Center tab in the header. You must be signed in to developer.att.com in order to access the Launch Center.

4.4 Developer Guidelines Update Process

Updates to this document will be communicated through posts in the Developer Forum.

https://developer.att.com/developer/forward.jsp?passedItemId=10100313

http://developerboards.att.lithium.com/t5/U-verse-Enabled/bd-p/UVerseEnabled

https://developer.att.com/developer/forward.jsp?passedItemId=10100313

http://infosphere.labs.att.com/sites/3/DES/PMO/Zeus/SDK%2025%20Content/post



at&t u-verse ® enabled developer guidelines...pecuniary loss, arising out of or in any way...

Documents