{"component": "clause", "props": {"groups": [{"samples": [{"hash": "7vuG9scZzDA", "uri": "/contracts/7vuG9scZzDA#usability", "label": "Saas Master Software Subscription and Services Agreement", "score": 29.3836956024, "published": true}, {"hash": "iptiJSyKGem", "uri": "/contracts/iptiJSyKGem#usability", "label": "Saas Master Software Subscription and Services Agreement", "score": 24.2902126312, "published": true}], "size": 2, "snippet": "7.1 You are using the SERVICES at your own risk and you are responsible for verifying its suitability for your needs. Use of the SERVICES does not guarantee a particular result or compliance with applicable law.", "snippet_links": [{"key": "using-the-services", "type": "clause", "offset": [12, 30]}, {"key": "at-your-own-risk", "type": "clause", "offset": [31, 47]}, {"key": "responsible-for", "type": "clause", "offset": [60, 75]}, {"key": "use-of-the-services", "type": "clause", "offset": [118, 137]}, {"key": "guarantee-a", "type": "definition", "offset": [147, 158]}, {"key": "compliance-with-applicable-law", "type": "definition", "offset": [180, 210]}], "hash": "947946f83ef1a7afc448ed7d44ed221a", "id": 5}, {"samples": [{"hash": "liXlEc3Qhed", "uri": "/contracts/liXlEc3Qhed#usability", "label": "Standard Contribution Agreement", "score": 26.4880218506, "published": true}, {"hash": "gwVzdvBUPRk", "uri": "/contracts/gwVzdvBUPRk#usability", "label": "Standard Contribution Agreement", "score": 26.4880218506, "published": true}, {"hash": "g1NNowwkfKI", "uri": "/contracts/g1NNowwkfKI#usability", "label": "Standard Contribution Agreement", "score": 26.4880218506, "published": true}], "size": 5, "snippet": "Software applications must be modern, intuitive, and easy to use. It should be built with accessibility (Web Content Accessibility Guidelines / Section 508) in mind. Layouts and features should remain simple, consistent throughout, and to the point.", "snippet_links": [{"key": "software-applications", "type": "definition", "offset": [0, 21]}, {"key": "web-content-accessibility-guidelines", "type": "clause", "offset": [105, 141]}, {"key": "section-508", "type": "clause", "offset": [144, 155]}], "hash": "4ac064f331727c7b447e9f44791a9b6d", "id": 1}, {"samples": [{"hash": "hkQDXA6rjgU", "uri": "/contracts/hkQDXA6rjgU#usability", "label": "Rental Agreement", "score": 23.3422317505, "published": true}, {"hash": "dMvuf9hcuQV", "uri": "/contracts/dMvuf9hcuQV#usability", "label": "Rental Agreement", "score": 23.3422317505, "published": true}], "size": 4, "snippet": "Tenant has inspected the Premises and fixtures (or has had the Premises inspected on behalf of Tenant), and acknowledges that the Premises are in a reasonable and acceptable condition of usability for their intended use, and the agreed rent payments are fair and reasonable. If the condition changes so that, in Tenant's opinion, the usability and rental value of the Premises are adversely affected, Tenant shall promptly provide reasonable notice to Landlord.", "snippet_links": [{"key": "the-premises", "type": "clause", "offset": [21, 33]}, {"key": "of-tenant", "type": "clause", "offset": [92, 101]}, {"key": "condition-of", "type": "clause", "offset": [174, 186]}, {"key": "intended-use", "type": "definition", "offset": [207, 219]}, {"key": "rent-payments", "type": "clause", "offset": [236, 249]}, {"key": "fair-and-reasonable", "type": "definition", "offset": [254, 273]}, {"key": "the-condition", "type": "clause", "offset": [278, 291]}, {"key": "rental-value", "type": "clause", "offset": [348, 360]}, {"key": "adversely-affected", "type": "definition", "offset": [381, 399]}, {"key": "tenant-shall", "type": "clause", "offset": [401, 413]}, {"key": "promptly-provide", "type": "clause", "offset": [414, 430]}, {"key": "notice-to-landlord", "type": "clause", "offset": [442, 460]}], "hash": "054b94fad113d0be71f4dc6ff6a6b5c3", "id": 2}, {"samples": [{"hash": "9uL1aIXpgsq", "uri": "/contracts/9uL1aIXpgsq#usability", "label": "Grant Agreement", "score": 24.3597660065, "published": true}, {"hash": "gSewGigkJyv", "uri": "/contracts/gSewGigkJyv#usability", "label": "Grant Agreement", "score": 24.1818370819, "published": true}], "size": 3, "snippet": "Installation Installation instructions are available and up-to-date in the wiki of the project documentation (\u2587\u2587\u2587\u2587\u2587://\u2587\u2587\u2587\u2587.\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587.\u2587\u2587\u2587). Moreover, an installation guide can be downloaded with the software (\u2587\u2587\u2587\u2587://\u2587\u2587\u2587.\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587.\u2587\u2587\u2587/software/downloads). Operative documentation A user guide can be downloaded along with the OpenDaylight release. Additionally, a starting guide is also available in the website (\u2587\u2587\u2587\u2587://\u2587\u2587\u2587.\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587.\u2587\u2587\u2587/resources/getting-started-guide). Development Development documentation A wiki is available for developers at (\u2587\u2587\u2587\u2587\u2587://\u2587\u2587\u2587\u2587.\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587.\u2587\u2587\u2587). It is a live document so it is updated periodically as long as the OpenDaylight project evolves. There is also a set of mailing lists and an IRC channel. Documentation for application development Refer to previous point. Development roadmap Refer to each project section in the OpenDaylight developers\u2019 wiki (\u2587\u2587\u2587\u2587\u2587://\u2587\u2587\u2587\u2587.\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587.\u2587\u2587\u2587/view/GettingStarted:Developer_Main). Also, several sample applications are developed. (\u2587\u2587\u2587\u2587\u2587://\u2587\u2587\u2587\u2587.\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587.\u2587\u2587\u2587/view/OpenDaylight_Controller:Sample_Applications) Toolchain Java 1.7 + Maven + OSGi IDE integration As reported in the wiki of the project (\u2587\u2587\u2587\u2587\u2587://\u2587\u2587\u2587\u2587.\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587.\u2587\u2587\u2587/view/GettingStarted:_Eclipse), at present only the Controller and the OpenFlow plugin projects have been validated to import into Eclipse without compile errors. Deployment System requirements OpenDaylight Controller runs in a JVM. Being a Java application, it can potentially run on any operating system that supports Java. However, for best results a recent Linux distribution and Java 1.7 are recommended. The only information about system requirements for running the controller has been found is more than 1G RAM. Nonetheless, OpenDaylight provides a set of preconfigured VMs with the Hydrogen release of the controller installed. Such VMs contain a GNU/Linux Ubuntu server 13.04 distribution and recommend to allocate 4GB of RAM memory to run the controller. Although the OpenDaylight controller is developed as a normal Java project, it makes heavy use of the Xtend language in some places. While development is possible with bare tools, it is recommend to use Eclipse with the Xtend plugin. Reference target OS Recent Linux distribution is recommended although any OS running a Java 1.7 virtual machine should work. Runtime dependencies Java 1.7 Key features to support COSIGN extensions Supported OpenFlow OpenFlow versions 1.0 and 1.3 are supported. Supported protocols at D- CPI Netconf, SNMP, OVSDB, PCMM/COPS, SNBI, Plugin2OC, LISP, PCEP, BGP Support for additional protocols at D- CPI It is possible to support multiple south-bound plugins in OpenDaylight. Furthermore, OpenDaylight has been designed to allow the extensibility of every part of the architecture including the southbound interface. Integration with Cloud Management Systems OpenDaylight has driver for Neutron ML2 (Modular Layer 2) plugin to enable communication between Neutron and OpenDaylight. On the SDN controller side, OpenDaylight has northbound APIs to interact with Neutron and use OVSDB for southbound configuration of vSwitches on compute nodes. A-CPI language For the A-CPI, OpenDaylight supports the OSGi framework where Java is the developing language, bidirectional REST employing JSON and DOM API employing XML. Available core functions or services The base network service functions available in the OpenDaylight controller are: \u2022 Topology Manager \u2022 Statistics Manager \u2022 Switch Manager \u2022 Forwarding Rules Manager \u2022 Host Tracker Available applications OpenDOVE and VTN projects extist within the OpenDaylight initiative to implement overlay network virtualization. Moreover, OpenStack integration is enabled through a Neutron API. Available A- CPI methods The associated module directory for the northbound (REST) API reference content is listed below: \u2022 Topology REST API \u2022 Host Tracker REST API \u2022 Flow Programmer REST API \u2022 Static Routing REST API \u2022 Statistics REST API \u2022 Subnets REST API \u2022 Switch Manager REST API \u2022 User Manager REST API \u2022 Container Manager REST API \u2022 Connection Manager REST API \u2022 Bridge Domain REST API \u2022 Neutron ML2 / Network Configuration API Support for ODL-SDNi App entered as an incubation project in May 2014. This project is aimed C2C communicatio n to provide establishment of East-West interface (SDNi communication) between multiple opendaylight controllers. The application will be responsible for sharing and collecting information to/from such federated controllers. Exploitability License Eclipse Public License (EPL-1.0) Membership Not required Potential impact Major industrial partners IBM, CISCO, BROCADE, MICROSOFT, JUNIPER, DELL, HP, ERICSSON, INFINERA, INTEL, ORACLE, \u2026 Expert partners from COSIGN consortium IBM, NEXTWORKS, UNIVBRIS, UPC Popularity High. OpenDaylight has a strong support from both the industry and the Open Source community. Usage in research projects LIGHTNESS, \u2587\u2587\u2587\u2587\u2587\u2587\u2587, CONTENT Usage in industrial products Brocade has developed a commercial controller built directly from OpenDaylight code: The Brocade Vyatta Controller.", "snippet_links": [{"key": "installation-instructions", "type": "clause", "offset": [13, 38]}, {"key": "project-documentation", "type": "definition", "offset": [87, 108]}, {"key": "installation-guide", "type": "clause", "offset": [155, 173]}, {"key": "the-software", "type": "definition", "offset": [197, 209]}, {"key": "user-guide", "type": "definition", "offset": [286, 296]}, {"key": "the-website", "type": "clause", "offset": [404, 415]}, {"key": "development-documentation", "type": "definition", "offset": [491, 516]}, {"key": "mailing-lists", "type": "clause", "offset": [708, 721]}, {"key": "application-development", "type": "clause", "offset": [760, 783]}, {"key": "refer-to", "type": "clause", "offset": [784, 792]}, {"key": "project-section", "type": "definition", "offset": [843, 858]}, {"key": "at-present", "type": "definition", "offset": [1245, 1255]}, {"key": "the-controller", "type": "clause", "offset": [1261, 1275]}, {"key": "system-requirements", "type": "definition", "offset": [1387, 1406]}, {"key": "operating-system", "type": "definition", "offset": [1502, 1518]}, {"key": "best-results", "type": "clause", "offset": [1552, 1564]}, {"key": "requirements-for", "type": "clause", "offset": [1657, 1673]}, {"key": "release-of", "type": "clause", "offset": [1813, 1823]}, {"key": "virtual-machine", "type": "clause", "offset": [2309, 2324]}, {"key": "key-features", "type": "clause", "offset": [2368, 2380]}, {"key": "additional-protocols", "type": "definition", "offset": [2582, 2602]}, {"key": "to-allow-the", "type": "clause", "offset": [2729, 2741]}, {"key": "management-systems", "type": "clause", "offset": [2849, 2867]}, {"key": "layer-2", "type": "definition", "offset": [2917, 2924]}, {"key": "core-functions", "type": "definition", "offset": [3332, 3346]}, {"key": "service-functions", "type": "clause", "offset": [3376, 3393]}, {"key": "overlay-network", "type": "definition", "offset": [3643, 3658]}, {"key": "listed-below", "type": "clause", "offset": [3849, 3861]}, {"key": "rest-api", "type": "definition", "offset": [3874, 3882]}, {"key": "network-configuration", "type": "clause", "offset": [4151, 4172]}, {"key": "api-support", "type": "clause", "offset": [4173, 4184]}, {"key": "incubation-project", "type": "definition", "offset": [4216, 4234]}, {"key": "to-provide", "type": "clause", "offset": [4289, 4299]}, {"key": "establishment-of", "type": "clause", "offset": [4300, 4316]}, {"key": "the-application", "type": "clause", "offset": [4401, 4416]}, {"key": "responsible-for", "type": "clause", "offset": [4425, 4440]}, {"key": "collecting-information", "type": "clause", "offset": [4453, 4475]}, {"key": "public-license", "type": "clause", "offset": [4543, 4557]}, {"key": "membership-not-required", "type": "clause", "offset": [4568, 4591]}, {"key": "potential-impact", "type": "clause", "offset": [4592, 4608]}, {"key": "open-source-community", "type": "clause", "offset": [4874, 4895]}, {"key": "research-projects", "type": "definition", "offset": [4906, 4923]}, {"key": "content-usage", "type": "clause", "offset": [4944, 4957]}, {"key": "industrial-products", "type": "clause", "offset": [4961, 4980]}, {"key": "brocade-has", "type": "definition", "offset": [4981, 4992]}], "hash": "c2f1817ff1f5b6c74e889655f59dbdfc", "id": 3}, {"samples": [{"hash": "oQtoEUzFuS", "uri": "/contracts/oQtoEUzFuS#usability", "label": "Key Agreement Protocol", "score": 28.33436203, "published": true}, {"hash": "32UKAKDHgsc", "uri": "/contracts/32UKAKDHgsc#usability", "label": "Publication Agreement", "score": 23.4291572571, "published": true}], "size": 2, "snippet": "The ALPKA 1 scheme cannot be made multiple use, as the proxy requires the knowledge of the combined secret information from solely the sender and the receiver for the re-encryption key. \u2013 Transitivity: As this feature involves a property on the proxy re-encryption key, it is only relevant for ALPKA 1. Transitivity is obtained as the re- encryption key combines the secret information of both sender and receiver", "snippet_links": [{"key": "multiple-use", "type": "clause", "offset": [34, 46]}, {"key": "the-proxy", "type": "clause", "offset": [51, 60]}, {"key": "knowledge-of", "type": "definition", "offset": [74, 86]}, {"key": "information-from", "type": "clause", "offset": [107, 123]}, {"key": "encryption-key", "type": "definition", "offset": [170, 184]}, {"key": "information-of", "type": "clause", "offset": [374, 388]}], "hash": "1221344f29b659e4065f426a819f30db", "id": 4}, {"samples": [{"hash": "aVXxi5LCcxX", "uri": "/contracts/aVXxi5LCcxX#usability", "label": "Settlement Agreement", "score": 23.0657081604, "published": true}, {"hash": "3aoRIAzxCEo", "uri": "/contracts/3aoRIAzxCEo#usability", "label": "Settlement Agreement", "score": 23.0657081604, "published": true}], "size": 2, "snippet": "\u200c Operator opens the Offload Application and adds a new task to the queue by selecting a bus and the time to be downloaded. Task is created with status \u201cwaiting for bus\u201d on the queue status pane. \u2022 The bus will be selected from a drop down list that is updated every time a new SVR is registered to the Video Offload Service. Upon bus arrival to garage, video offload request is sent to the bus and video is downloaded to the center. Status bar shows \u201cdownloading\u201d status with progress. If video is not available on the bus (elapsed retention time) or there is a problem writing to the garage server, an Error status will be shown in the status bar. When download is completed a new case is opened on Inform and status changes to \u201ccase ID is ready on Inform\u201d. Correlation between offload queue and inform case will be by the case name (with reference on the queue manager to the Inform case name).", "snippet_links": [{"key": "drop-down", "type": "definition", "offset": [230, 239]}, {"key": "the-center", "type": "definition", "offset": [422, 432]}, {"key": "status-bar", "type": "clause", "offset": [434, 444]}, {"key": "not-available", "type": "clause", "offset": [499, 512]}, {"key": "retention-time", "type": "definition", "offset": [533, 547]}, {"key": "changes-to", "type": "clause", "offset": [719, 729]}, {"key": "the-case", "type": "definition", "offset": [821, 829]}], "hash": "fbadb163b5520fe56a8ff6510df81c1f", "id": 6}, {"samples": [{"hash": "fLmKh5rhp9h", "uri": "/contracts/fLmKh5rhp9h#usability", "label": "Enterprise Care Management Solutions", "score": 22.8480491638, "published": true}, {"hash": "7XArScOQrgV", "uri": "/contracts/7XArScOQrgV#usability", "label": "Contract for Personal Services", "score": 18.7008895874, "published": true}], "size": 2, "snippet": "The Contractor\u2019s System must be designed to provide a browser based, or a Rich Internet Application, that will utilize feature rich applications that will be updated over the Wide Area Network (WAN) and the Internet, and will deliver a consistent User experience to Vermont Citizens, AHS employees, providers, contractors, and partners. The Contractor will send and retrieve data in the background without interfering with or delaying User interface behavior in the browser. As newer browsers are released and are more capable of supporting technologies such as HTML5, the Contractor will capitalize on those improvements and incorporate them in the application. The Contractor\u2019s System shall provide a dynamic Graphic User Interface (GUI) that allows access to information based on a User\u2019s role and associated permissions. Configurable functions as well as the current state of User interaction at any given point in time will be achieved via configurable business rules or branching logic that is associated with real-time responses within the application. The Contractor\u2019s System shall present only what is relevant to, or required of, the User to accomplish a specific data entry or review scenario while still ensuring all pertinent data is captured. All fields will include appropriate User entry validation such as data type, masking, and length. The Contractor will use zero footprint technology, architecture, and applications that can be \u201cstyled\u201d or \u201cskinned\u201d to the AHS color palette and logo. The Contractor will provide secure single sign-on options to integrate into an existing client portal. Single Sign-On Options will include:\n1. \u2587\u2587\u2587\u2587 2.0 Tokens and Protocol", "snippet_links": [{"key": "provide-a", "type": "definition", "offset": [44, 53]}, {"key": "internet-application", "type": "definition", "offset": [79, 99]}, {"key": "wide-area-network", "type": "definition", "offset": [175, 192]}, {"key": "the-internet", "type": "clause", "offset": [203, 215]}, {"key": "user-experience", "type": "clause", "offset": [247, 262]}, {"key": "the-contractor-will", "type": "clause", "offset": [337, 356]}, {"key": "the-background", "type": "clause", "offset": [383, 397]}, {"key": "user-interface", "type": "definition", "offset": [435, 449]}, {"key": "capable-of", "type": "definition", "offset": [519, 529]}, {"key": "the-application", "type": "clause", "offset": [646, 661]}, {"key": "access-to-information", "type": "clause", "offset": [752, 773]}, {"key": "based-on", "type": "definition", "offset": [774, 782]}, {"key": "state-of", "type": "clause", "offset": [871, 879]}, {"key": "in-time", "type": "clause", "offset": [916, 923]}, {"key": "business-rules", "type": "definition", "offset": [958, 972]}, {"key": "associated-with", "type": "definition", "offset": [1000, 1015]}, {"key": "the-user", "type": "clause", "offset": [1140, 1148]}, {"key": "data-entry", "type": "clause", "offset": [1174, 1184]}, {"key": "pertinent-data", "type": "clause", "offset": [1229, 1243]}, {"key": "data-type", "type": "definition", "offset": [1323, 1332]}, {"key": "will-provide", "type": "clause", "offset": [1521, 1533]}, {"key": "single-sign", "type": "clause", "offset": [1541, 1552]}, {"key": "client-portal", "type": "clause", "offset": [1594, 1607]}], "hash": "2d88e6e9b5dc836638488c20360adbf9", "id": 7}, {"samples": [{"hash": "abhsKrefyuB", "uri": "/contracts/abhsKrefyuB#usability", "label": "Cen Workshop Agreement", "score": 29.8947238922, "published": true}], "size": 2, "snippet": "working system is not enough when it comes to a CIS. A CIS shall always be under control: \u201cwhen running a CIS has to report on its state and to give evidence of its well being. It is mandatory to know how the CIS is working and what difficulties it encounters or has encountered\u201d. It is preferable to check the CIS continuously in order to help ensure that it is well under control. This reporting information is valuable both: \u25aa For building a real time dashboard in order to detect earlier any possible deviation, \u25aa And \u201coff-line\u201d for calculating key quality of service indicators. This allows for example to relate the CIS performance with its capacity, and to know how it reacts to overloading or any unforeseen event. It also covers requirements related to traceability (e.g. audit trails, etc.). In addition, \u201ca CIS can be easily managed without impacting the quality of service\u201d: \u25aa Manipulations shall be risk-free (stopping/restarting the entire system and various components, etc.). \u25aa On-site presence of highly skilled personnel shall be as reduced as possible. CEN/ISSS WORKSHOP", "snippet_links": [{"key": "under-control", "type": "definition", "offset": [75, 88]}, {"key": "evidence-of", "type": "definition", "offset": [149, 160]}, {"key": "in-order-to", "type": "clause", "offset": [328, 339]}, {"key": "reporting-information", "type": "clause", "offset": [388, 409]}, {"key": "building-a", "type": "definition", "offset": [434, 444]}, {"key": "quality-of-service", "type": "definition", "offset": [553, 571]}, {"key": "for-example", "type": "definition", "offset": [596, 607]}, {"key": "unforeseen-event", "type": "definition", "offset": [705, 721]}, {"key": "related-to", "type": "clause", "offset": [751, 761]}, {"key": "audit-trails", "type": "clause", "offset": [781, 793]}, {"key": "in-addition", "type": "clause", "offset": [802, 813]}, {"key": "skilled-personnel", "type": "clause", "offset": [1021, 1038]}], "hash": "ae4a5c6f0011dac6cf9f76657d623cc9", "id": 8}, {"samples": [{"hash": "lvod98Zs8Uh", "uri": "/contracts/lvod98Zs8Uh#usability", "label": "Service Level Agreement", "score": 21.9130725861, "published": true}], "size": 1, "snippet": "Infoworks works with disability charities and experts build accessibility and usability into our design process \u2013 we deliver browser-based applications which are accessible and easy to use and understand. But we are information systems experts; not accessibility experts (though we can recommend one if needed). Accessibility and usability are not always synonymous. The Client should also be aware that changes to software over time may help usability but impinge on strict accessibility compliance. Further, compliance is a moving target and what is viewed accessible now may not be accessible next year. We do not guarantee that our software will always comply with any single standard. We exist to realise your business requirements in software. If your requirement includes compliance with a standard you must not sign off the software as complete until compliance is achieved. Once you sign a requirement off as complete, we will view as complete. In the final analysis it is the Client\u2019s responsibility to test the software we provide before acceptance to ensure compliance.", "snippet_links": [{"key": "design-process", "type": "clause", "offset": [97, 111]}, {"key": "information-systems", "type": "definition", "offset": [216, 235]}, {"key": "the-client", "type": "definition", "offset": [367, 377]}, {"key": "changes-to-software", "type": "clause", "offset": [404, 423]}, {"key": "over-time", "type": "clause", "offset": [424, 433]}, {"key": "accessibility-compliance", "type": "clause", "offset": [475, 499]}, {"key": "moving-target", "type": "definition", "offset": [526, 539]}, {"key": "our-software", "type": "clause", "offset": [632, 644]}, {"key": "comply-with", "type": "definition", "offset": [657, 668]}, {"key": "business-requirements", "type": "definition", "offset": [715, 736]}, {"key": "compliance-with-a", "type": "clause", "offset": [779, 796]}, {"key": "sign-off", "type": "clause", "offset": [819, 827]}, {"key": "the-software", "type": "definition", "offset": [828, 840]}, {"key": "final-analysis", "type": "definition", "offset": [961, 975]}, {"key": "we-provide", "type": "clause", "offset": [1031, 1041]}, {"key": "ensure-compliance", "type": "clause", "offset": [1063, 1080]}], "hash": "3dddafb6957f05f6d2b0e0eed9159ba7", "id": 9}, {"samples": [{"hash": "3Wk8doPgDHf", "uri": "/contracts/3Wk8doPgDHf#usability", "label": "Booking Agreement", "score": 17.0, "published": true}], "size": 1, "snippet": "Hawaii Beach Homes acts only as a sales and marketing agent for the homeowners, suppliers and contractors providing accommodation and services. Under no circumstances shall Hawaii Beach Homes and/or the property owner be responsible for any personal or property damage or loss, expense, damages, claim or injury direct, indirect, personal, consequential or otherwise whatsoever howsoever caused or incurring to Clients(s) or their/his/her guests whether arising in contract or residency in the home or otherwise in law or equity as a result of rendering of the service or accommodations as described or substituted, the maintenance and construction of the rented premises, damages to the premises, and including, without restricting the generality of the foregoing as a result of any delay(s), substitution(s) or change(s) in the provision of services or housing accommodations. Hawaii Beach Homes may make recommendations or referrals to Client as part of a concierge service. Client(s) release, acquit and forever discharge Hawaii Beach Homes of and from any and all claims, actions, causes or action, demands, rights, damages, costs, expense and compensation whatsoever, including all claims for negligence, property damage, personal injury and/or wrongful death which may occur or which may hereafter accrue on account of and in any way growing out of actions upon such recommendations or referrals.", "snippet_links": [{"key": "marketing-agent", "type": "definition", "offset": [44, 59]}, {"key": "contractors-providing", "type": "clause", "offset": [94, 115]}, {"key": "accommodation-and-services", "type": "definition", "offset": [116, 142]}, {"key": "no-circumstances", "type": "clause", "offset": [150, 166]}, {"key": "property-owner", "type": "clause", "offset": [203, 217]}, {"key": "responsible-for", "type": "clause", "offset": [221, 236]}, {"key": "property-damage-or-loss", "type": "clause", "offset": [253, 276]}, {"key": "in-contract", "type": "clause", "offset": [462, 473]}, {"key": "in-the-home", "type": "definition", "offset": [487, 498]}, {"key": "the-service", "type": "clause", "offset": [557, 568]}, {"key": "construction-of-the", "type": "clause", "offset": [636, 655]}, {"key": "rented-premises", "type": "definition", "offset": [656, 671]}, {"key": "damages-to-the-premises", "type": "clause", "offset": [673, 696]}, {"key": "the-foregoing", "type": "clause", "offset": [751, 764]}, {"key": "the-provision-of-services", "type": "clause", "offset": [826, 851]}, {"key": "housing-accommodations", "type": "clause", "offset": [855, 877]}, {"key": "make-recommendations", "type": "clause", "offset": [902, 922]}, {"key": "to-client", "type": "definition", "offset": [936, 945]}, {"key": "concierge-service", "type": "clause", "offset": [959, 976]}, {"key": "all-claims", "type": "definition", "offset": [1065, 1075]}, {"key": "and-compensation", "type": "clause", "offset": [1145, 1161]}, {"key": "claims-for", "type": "clause", "offset": [1188, 1198]}, {"key": "personal-injury", "type": "clause", "offset": [1228, 1243]}, {"key": "wrongful-death", "type": "clause", "offset": [1251, 1265]}], "hash": "e3aef18007a5852c69d30cb674557c0f", "id": 10}], "next_curs": "ClISTGoVc35sYXdpbnNpZGVyY29udHJhY3Rzci4LEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2IhJ1c2FiaWxpdHkjMDAwMDAwMGEMogECZW4YACAA", "clause": {"title": "Usability", "size": 58, "children": [["", ""], ["user-authentication-and-authorization", "User Authentication and Authorization"], ["temporal-limit", "Temporal limit"], ["update-rights", "Update Rights"], ["activation-of-pvsyst", "Activation of PVsyst"]], "parents": [["severability", "Severability"], ["alternative-transportation", "Alternative Transportation"], ["solution-specification", "Solution Specification"], ["architecture-policy-requirement", "Architecture Policy Requirement"], ["intellectual-property", "INTELLECTUAL PROPERTY"]], "id": "usability", "related": [["dependability", "Dependability", "Dependability"], ["employability", "Employability", "Employability"], ["divisibility", "Divisibility", "Divisibility"], ["grievability", "Grievability", "Grievability"], ["interoperability", "Interoperability", "Interoperability"]], "related_snippets": [], "updated": "2025-07-10T05:58:13+00:00", "also_ask": ["What essential elements must a 'Usability' clause include to be enforceable?", "How can parties strategically define 'usability' to align with their business objectives?", "What are common pitfalls or ambiguities in 'Usability' clauses that lead to disputes?", "How do courts typically interpret and enforce 'Usability' provisions in contracts?", "How does a 'Usability' clause compare to similar provisions like 'fitness for purpose' or 'performance standards'?"], "drafting_tip": "Specify usability standards, define measurement criteria, and outline remedies for non-compliance to ensure clarity, facilitate assessment, and provide enforceable recourse.", "explanation": "The Usability clause defines the standards and requirements that a product, service, or system must meet to ensure it is user-friendly and accessible to its intended audience. This clause typically outlines criteria such as ease of navigation, clarity of instructions, and the ability for users to accomplish tasks efficiently, often referencing industry standards or specific user testing benchmarks. Its core practical function is to ensure that the end product is practical and effective for users, thereby reducing confusion, minimizing errors, and enhancing overall satisfaction."}, "json": true, "cursor": ""}}