{"component": "clause", "props": {"groups": [{"size": 7, "snippet_links": [{"key": "text-message", "type": "definition", "offset": [44, 56]}, {"key": "your-physician", "type": "clause", "offset": [60, 74]}, {"key": "administrative-team", "type": "definition", "offset": [82, 101]}, {"key": "for-non", "type": "clause", "offset": [124, 131]}, {"key": "urgent-matters", "type": "clause", "offset": [132, 146]}, {"key": "appointment-reminders", "type": "clause", "offset": [155, 176]}, {"key": "side-effect", "type": "definition", "offset": [328, 339]}, {"key": "immediate-response", "type": "clause", "offset": [410, 428]}, {"key": "refer-to-the", "type": "definition", "offset": [437, 449]}, {"key": "management-of", "type": "clause", "offset": [478, 491]}, {"key": "urgent-issues", "type": "clause", "offset": [492, 505]}, {"key": "business-days", "type": "clause", "offset": [546, 559]}, {"key": "monday-morning", "type": "clause", "offset": [723, 737]}], "samples": [{"hash": "3uQak2uKI9V", "uri": "/contracts/3uQak2uKI9V#messaging", "label": "Practice Policies and Agreement", "score": 31.1812858582, "published": true}, {"hash": "5CP7EjdjY23", "uri": "/contracts/5CP7EjdjY23#messaging", "label": "Practice Policies and Agreement", "score": 31.1046390533, "published": true}, {"hash": "806qSDlitjL", "uri": "/contracts/806qSDlitjL#messaging", "label": "Practice Policies and Agreement", "score": 30.9951438904, "published": true}], "snippet": "You can send messages through luminello, or text message to your physician or the administrative team. Messages can be used for non urgent matters such as appointment reminders, medication refill, insurance questions. You should NOT use the Luminello messaging software for any urgent questions including symptoms of medication side effect, experiencing desire to harm yourself or others, or are in need of an Immediate response. Please refer to the Emergency section above for management of urgent issues. Messages will not be read after 5pm on business days, nor will they be read on weekends. We will try our best to response to messages within 48 ours. Any messages left late on Friday will most likely be processed on Monday morning.", "hash": "ffa14ce692d83423b8df9a0561d8d024", "id": 4}, {"size": 21, "snippet_links": [{"key": "submission-of", "type": "clause", "offset": [46, 59]}, {"key": "liability-for", "type": "clause", "offset": [117, 130]}, {"key": "distribution-of", "type": "clause", "offset": [135, 150]}, {"key": "not-limited", "type": "clause", "offset": [226, 237]}, {"key": "emergency-alert-system", "type": "definition", "offset": [263, 285]}, {"key": "commercial-mobile", "type": "clause", "offset": [293, 310]}, {"key": "by-everbridge", "type": "clause", "offset": [363, 376]}, {"key": "failure-to-receive", "type": "clause", "offset": [433, 451]}, {"key": "additional-features", "type": "definition", "offset": [517, 536]}, {"key": "not-supported", "type": "clause", "offset": [537, 550]}, {"key": "to-provide", "type": "definition", "offset": [619, 629]}, {"key": "to-client", "type": "definition", "offset": [655, 664]}, {"key": "client-shall", "type": "clause", "offset": [675, 687]}, {"key": "the-content", "type": "clause", "offset": [725, 736]}, {"key": "access-codes", "type": "clause", "offset": [799, 811]}], "samples": [{"hash": "femjBziwIe", "uri": "/contracts/femjBziwIe#messaging", "label": "End User License Agreement", "score": 35.5326042175, "published": true}, {"hash": "kmxjUxaROH6", "uri": "/contracts/kmxjUxaROH6#messaging", "label": "Master Services Agreement", "score": 33.2360343933, "published": true}, {"hash": "ahLXbwtgoKO", "uri": "/contracts/ahLXbwtgoKO#messaging", "label": "End User License Agreement", "score": 32.3748130798, "published": true}], "snippet": "Client acknowledges and agrees that: (i) upon submission of messages to IPAWS-OPEN, Everbridge shall have no further liability for the distribution of such message, and that the distribution through IPAWS-OPEN, including, but not limited to, delivery through the Emergency Alert System or the Commercial Mobile Alert System, is in no way guaranteed or controlled by Everbridge; (ii) Everbridge shall not be liable as a result of any failure to receive messages distributed through IPAWS-OPEN; (iii) IPAWS may include additional features not supported through the Everbridge system, and Everbridge shall not be required to provide such additional features to Client; and (iv) Client shall be solely responsible and liable for the content of any and all messages sent through IPAWS-OPEN utilizing its access codes.", "hash": "bfc28fbba509a53b13dae5951a3e864b", "id": 1}, {"size": 5, "snippet_links": [{"key": "exchanging-information", "type": "clause", "offset": [69, 91]}, {"key": "services-and", "type": "clause", "offset": [98, 110]}, {"key": "higher-level", "type": "definition", "offset": [138, 150]}, {"key": "monitoring-tools", "type": "clause", "offset": [181, 197]}, {"key": "access-control", "type": "clause", "offset": [278, 292]}, {"key": "the-information", "type": "clause", "offset": [421, 436]}, {"key": "transport-service", "type": "clause", "offset": [473, 490]}, {"key": "access-to-information", "type": "clause", "offset": [583, 604]}, {"key": "development-of", "type": "clause", "offset": [613, 627]}, {"key": "service-requests", "type": "definition", "offset": [681, 697]}, {"key": "messaging-service", "type": "clause", "offset": [827, 844]}, {"key": "red-hat", "type": "definition", "offset": [850, 857]}, {"key": "comply-with-the", "type": "clause", "offset": [877, 892]}, {"key": "security-mechanisms", "type": "clause", "offset": [902, 921]}, {"key": "grid-services", "type": "clause", "offset": [934, 947]}, {"key": "usage-of-the", "type": "clause", "offset": [1027, 1039]}, {"key": "to-provide", "type": "definition", "offset": [1066, 1076]}, {"key": "access-to-the", "type": "clause", "offset": [1082, 1095]}, {"key": "business-models", "type": "clause", "offset": [1135, 1150]}, {"key": "most-important", "type": "clause", "offset": [1296, 1310]}, {"key": "data-format", "type": "clause", "offset": [1403, 1414]}, {"key": "based-on", "type": "clause", "offset": [1415, 1423]}, {"key": "accounting-for", "type": "clause", "offset": [1470, 1484]}, {"key": "of-operations", "type": "clause", "offset": [1496, 1509]}, {"key": "data-management", "type": "clause", "offset": [1515, 1530]}, {"key": "the-accounting", "type": "clause", "offset": [1570, 1584]}, {"key": "the-infrastructure", "type": "clause", "offset": [1599, 1617]}, {"key": "standard-service", "type": "clause", "offset": [1665, 1681]}, {"key": "the-context", "type": "clause", "offset": [1813, 1824]}, {"key": "large-scale-production", "type": "definition", "offset": [1836, 1858]}, {"key": "service-management", "type": "clause", "offset": [1905, 1923]}, {"key": "commercial-applications", "type": "clause", "offset": [2075, 2098]}, {"key": "standard-definitions", "type": "definition", "offset": [2108, 2128]}, {"key": "information-model", "type": "clause", "offset": [2145, 2162]}, {"key": "by-ibm", "type": "clause", "offset": [2180, 2186]}, {"key": "standard-monitoring", "type": "definition", "offset": [2419, 2438]}, {"key": "programming-environment", "type": "clause", "offset": [2617, 2640]}, {"key": "low-level", "type": "definition", "offset": [2656, 2665]}, {"key": "will-provide", "type": "clause", "offset": [2743, 2755]}, {"key": "user-interfaces", "type": "clause", "offset": [2861, 2876]}, {"key": "cloud-technology", "type": "clause", "offset": [3063, 3079]}, {"key": "new-business", "type": "definition", "offset": [3093, 3105]}, {"key": "for-managing", "type": "clause", "offset": [3112, 3124]}, {"key": "storage-resources", "type": "clause", "offset": [3151, 3168]}, {"key": "service-levels", "type": "definition", "offset": [3345, 3359]}, {"key": "and-information", "type": "clause", "offset": [3596, 3611]}, {"key": "carry-on", "type": "definition", "offset": [3770, 3778]}, {"key": "ease-of-use", "type": "clause", "offset": [3873, 3884]}, {"key": "resource-management", "type": "definition", "offset": [3905, 3924]}, {"key": "number-of", "type": "clause", "offset": [3999, 4008]}, {"key": "to-strengthen", "type": "clause", "offset": [4066, 4079]}, {"key": "for-research", "type": "clause", "offset": [4098, 4110]}, {"key": "end-users", "type": "clause", "offset": [4254, 4263]}, {"key": "will-work", "type": "clause", "offset": [4286, 4295]}, {"key": "with-providers", "type": "clause", "offset": [4305, 4319]}, {"key": "cloud-solutions", "type": "clause", "offset": [4338, 4353]}, {"key": "in-particular", "type": "clause", "offset": [4494, 4507]}, {"key": "job-definition", "type": "clause", "offset": [4535, 4549]}, {"key": "the-resource", "type": "definition", "offset": [4570, 4582]}, {"key": "to-request", "type": "clause", "offset": [4618, 4628]}, {"key": "virtualized-environments", "type": "clause", "offset": [4638, 4662]}, {"key": "resource-allocations", "type": "clause", "offset": [5293, 5313]}, {"key": "in-detail", "type": "clause", "offset": [5340, 5349]}, {"key": "specific-capabilities", "type": "clause", "offset": [5414, 5435]}, {"key": "the-content", "type": "clause", "offset": [5612, 5623]}, {"key": "other-non", "type": "clause", "offset": [5704, 5713]}, {"key": "creation-of-the-portal", "type": "clause", "offset": [5762, 5784]}, {"key": "availability-of", "type": "clause", "offset": [5795, 5810]}, {"key": "the-design", "type": "clause", "offset": [5874, 5884]}, {"key": "web-portal", "type": "definition", "offset": [6079, 6089]}, {"key": "collaborate-with", "type": "clause", "offset": [6441, 6457]}, {"key": "primary-commitment", "type": "definition", "offset": [6564, 6582]}, {"key": "scientific-research", "type": "clause", "offset": [6691, 6710]}, {"key": "collaborative-efforts", "type": "clause", "offset": [6736, 6757]}, {"key": "commitment-to", "type": "clause", "offset": [6818, 6831]}, {"key": "standards-development", "type": "clause", "offset": [6985, 7006]}, {"key": "the-open", "type": "clause", "offset": [7026, 7034]}, {"key": "existing-standards", "type": "clause", "offset": [7097, 7115]}, {"key": "working-group", "type": "clause", "offset": [7190, 7203]}, {"key": "attention-to", "type": "definition", "offset": [7327, 7339]}, {"key": "in-the-united-states", "type": "clause", "offset": [7365, 7385]}, {"key": "context-of-the", "type": "clause", "offset": [7393, 7407]}, {"key": "open-science", "type": "clause", "offset": [7408, 7420]}, {"key": "the-standards", "type": "definition", "offset": [7565, 7578]}, {"key": "supported-services", "type": "clause", "offset": [7586, 7604]}, {"key": "other-providers", "type": "clause", "offset": [7693, 7708]}], "samples": [{"hash": "ezc5dr5bf7n", "uri": "/contracts/ezc5dr5bf7n#messaging", "label": "Grant Agreement", "score": 17.2272415161, "published": true}, {"hash": "5KyQn5FNlyL", "uri": "/contracts/5KyQn5FNlyL#messaging", "label": "Grant Agreement", "score": 17.2258720398, "published": true}, {"hash": "7NBT9WnoMTo", "uri": "/contracts/7NBT9WnoMTo#messaging", "label": "Grant Agreement", "score": 17.2190284729, "published": true}], "snippet": "All current middleware implementations lack a standard mechanism for exchanging information among services and between the middleware and higher level consumers like accounting and monitoring tools. Although effort has been put in the past to define how 15 \u2587. \u2587\u2587\u2587\u2587\u2587, extensible Access Control Markup Language (XACML) Version 2.0, February, 2005, \u2587\u2587\u2587\u2587://\u2587\u2587\u2587.\u2587\u2587\u2587\u2587\u2587-\u2587\u2587\u2587\u2587.\u2587\u2587\u2587/committees/tc_home.php?wg_abbrev=xacml - XACML20 the information must be encoded, there is no common transport service independent of the information content. Such a transport service would provide standardized access to information and the development of common ways of managing policies, configurations and service requests. EMI will add such service to its middleware starting from existing off-the-shelf components like the Apache ActiveMQ or the MRG messaging service from Red Hat, extending them to comply with the standard security mechanisms used by the grid services. \u2022 Accounting An efficient accounting mechanism compliant with the distributed usage of the grid service is necessary to provide fair access to the resources and in future establish real business models. Various accounting solutions are presently available, but they all make use of proprietary formats and transport mechanisms. EMI will adapt the most important accounting sensors and collectors to use the common messaging infrastructure and a standard data format based on the UR specification, extending it to provide accounting for more types of operations like data management and providing a uniform foundation for the accounting tools used by the infrastructure providers. \u2022 Service monitoring and management Standard service monitoring and management interfaces are currently largely absent from grid middleware, but their necessity is becoming obvious in the context of running large scale production infrastructures. The correct approach to grid service management is still discussed in relevant standardisation forums and no clear recipe exists yet. However, established technologies are available and used in many commercial applications based on standard definitions like the Common Information Model (CIM), developed by IBM, Microsoft and Intel among others, and the QPID Modeling Framework (QMF) recently adopted by the leading Linux provider, Red Hat. EMI will investigate and adapt off-the- shelf solutions and develop sensors to be plugged in industry standard monitoring tools, such as Nagios and standard CIM-based tools. \u2022 MPI The Message Passing Interface (MPI) programming paradigm is poorly supported in grid environments. Users face a complex programming environment where too many low level details have to be specified to execute even the simplest parallel jobs. EMI will provide an interoperable MPI execution framework across the different middleware implementations to abstract the user interfaces from the underlying middleware and allow users to execute parallel applications in a uniform way, thus bridging the gap between HPC and HTC. \u2022 Virtualization and clouds access Recently, cloud technology emerged as a new business model for managing distributed computing and storage resources. Clouds focus on creating well-controlled uniform environments, predominantly through virtualization techniques, and usually in one administrative domain. This guarantees high service levels and transparent accountability, both of which have proved to be a challenge for Grids. However, in the context of international research communities, the top priority is the sharing of existing heterogeneous resources (computing, data, and information) and the creation of a single administrative domain is often unfeasible. This makes Grid an essential technology for distributed computing infrastructures to carry on research today, but interoperability with cloud-based solutions for increased flexibility and ease of use and the adoption of resource management solutions based on virtualization are becoming strong user requirement. A number of important initiatives have started or are being proposed to strengthen the use of Clouds for research (RESERVOIR, OpenNebula, Platform ISF, INFN WNoDeS16, etc), but a clear path towards bridging the different models in a transparent way for the end users is still missing. EMI will work together with providers and developers of cloud solutions, identifying and implementing missing functionality in the grid services to make them use efficiently such solutions as they become mature. In particular, extensions to the current job definition language (JSDL) and the resource modelling schema (GLUE) to be able to request specific virtualized environments to be instantiated by the underlying resource managers are currently needed. \u2022 Interoperability between HTC and HPC Interoperability between high-performance and high-throughput computing is receiving increasing attention as user communities like Fusion, Computational Chemistry or Astronomy need to access both supercomputers and shared grid nodes in their computational and data management workflows. Convergence to common standards across the UNICORE and traditional grid services will help bridge this gap. However, standards conformance alone may not be sufficient, as large differences still exist on the level of policies, resource allocations etc. EMI will investigate in detail the differences and provide documented solutions to exploit the specific capabilities of the two systems in different stages of complex computational tasks. \u2022 Portlets Portlets are pluggable components that generate dynamic contents in response to web requests. The content that a portlet produces is a fragment of mark-up code that, in aggregation with other non-overlapping portlet results, contributes to the creation of the portal page. The availability of standard portlet interfaces for the middleware services allows the design and creation of user-level portals and gateways that isolate the users from the underlying complexities of the middleware providing direct, customizable functionality. EMI will provide standard web portal interfaces for its services compliant with specifications like the Java Portlet Specifications (v1.0 JSR 168, v2.0 JSR 286), WSRP (WS for Remote Portlets) or the very recent Enterprise Mashups technologies17 16 INFN OCCI implementation on Grid Infrastructure (\u2587\u2587\u2587\u2587://\u2587\u2587\u2587.\u2587\u2587\u2587.\u2587\u2587\u2587/OGF27/materials/1742/03_INFN_OCCI_implementation.pptx) and will closely collaborate with user communities and projects to support their development of portals and gateways. \u2022 Standardization EMI primary commitment is the support and evolution of the grid middleware used by infrastructures and user communities to perform scientific research as part of international collaborative efforts. Such an engagement cannot be undertaken without a parallel commitment to define and adopt standards in collaboration with similar initiatives in Europe and worldwide. EMI will actively participate to the effort of established standards development organizations like the Open Grid Forum18 and OASIS19 helping to define and refine new and existing standards. In particular EMI commits to use the OGF Production Grid Infrastructures Working Group (PGI-WG) as a forum for ensuring that EMI is engaged with the rest of the world\u2018s production level middleware with special attention to initiatives taking place in the United States in the context of the Open Science Grid (OSG) infrastructure. In this context, the major innovative contribution that EMI will bring is the actual and validated implementation of the standards in its supported services and their transition to production infrastructures in collaboration with EGI, PRACE and other providers.", "hash": "cb492f910b3063f1910d68b8980102ea", "id": 6}, {"size": 17, "snippet_links": [{"key": "target2-system", "type": "definition", "offset": [29, 43]}, {"key": "to-parties", "type": "clause", "offset": [44, 54]}], "samples": [{"hash": "bfWbCgC3Ohh", "uri": "/contracts/bfWbCgC3Ohh#messaging", "label": "Annexes to the Instructions", "score": 26.4496917725, "published": true}, {"hash": "cMdj4t7wXG6", "uri": "/contracts/cMdj4t7wXG6#messaging", "label": "Annex to the Instructions", "score": 26.38945961, "published": true}, {"hash": "wIEJLsMr7p", "uri": "/contracts/wIEJLsMr7p#messaging", "label": "Cassa Di Compensazione E Garanzia Instructions", "score": 26.1252574921, "published": true}], "snippet": "The MT910 message, sent from Target2 System to parties who have requested it, shall, in the above cases, have the following layout: MT900 ASTransferInitiation S: TRGTXEP0ASI (for T&T Env) TRGTXEPMASI (for PROD Env)", "hash": "5531ff711e19ffd652791e3d3476dcb5", "id": 2}, {"size": 11, "snippet_links": [{"key": "ups-technology", "type": "definition", "offset": [8, 22]}, {"key": "ability-to", "type": "clause", "offset": [44, 54]}, {"key": "related-to", "type": "definition", "offset": [93, 103]}, {"key": "tendered-shipment", "type": "definition", "offset": [106, 123]}, {"key": "sms-text-messaging", "type": "clause", "offset": [138, 156]}, {"key": "you-agree-to", "type": "clause", "offset": [186, 198]}, {"key": "messaging-service", "type": "clause", "offset": [207, 224]}, {"key": "affiliated-with", "type": "definition", "offset": [313, 328]}, {"key": "responsible-for", "type": "clause", "offset": [369, 384]}, {"key": "the-content", "type": "clause", "offset": [385, 396]}, {"key": "message-content", "type": "definition", "offset": [482, 497]}, {"key": "in-no-event-shall", "type": "clause", "offset": [580, 597]}, {"key": "in-the-transmission", "type": "clause", "offset": [637, 656]}, {"key": "receipt-of", "type": "clause", "offset": [660, 670]}, {"key": "in-the-event", "type": "clause", "offset": [684, 696]}, {"key": "to-receive", "type": "definition", "offset": [758, 768]}, {"key": "relating-to", "type": "definition", "offset": [778, 789]}, {"key": "you-warrant", "type": "clause", "offset": [909, 920]}, {"key": "the-recipient", "type": "clause", "offset": [980, 993]}, {"key": "addresses-and-phone-numbers", "type": "clause", "offset": [1054, 1081]}, {"key": "intended-recipient", "type": "definition", "offset": [1136, 1154]}, {"key": "cost-and-expense", "type": "clause", "offset": [1195, 1211]}, {"key": "indemnify-and-hold-harmless", "type": "clause", "offset": [1213, 1240]}, {"key": "ups-indemnitees", "type": "definition", "offset": [1245, 1260]}, {"key": "arising-out-of", "type": "definition", "offset": [1342, 1356]}, {"key": "in-connection-with", "type": "clause", "offset": [1360, 1378]}, {"key": "the-warranties", "type": "clause", "offset": [1393, 1407]}], "samples": [{"hash": "aEMa9cjg1Tg", "uri": "/contracts/aEMa9cjg1Tg#messaging", "label": "Technology Agreement", "score": 33.851940155, "published": true}, {"hash": "7PKrjNbIWuu", "uri": "/contracts/7PKrjNbIWuu#messaging", "label": "Technology Agreement", "score": 27.1697463989, "published": true}, {"hash": "3VWp4vXXMY3", "uri": "/contracts/3VWp4vXXMY3#messaging", "label": "Technology Agreement", "score": 26.9383983612, "published": true}], "snippet": "Certain UPS Technology provide You with the ability to send a message comprising Information related to a Tendered Shipment via e-mail or SMS text messaging to a recipient You identify. You agree to use the messaging service solely to communicate information related to, and only to send a message to a recipient affiliated with, that Tendered Shipment. You are solely responsible for the content provided by You and transmitted as part of any message. You shall not include in any message content which is unlawful, lewd, offensive, harassing, defamatory, libelous or injurious. In no event shall UPS be liable for any failure or delay in the transmission or receipt of the message. In the event a recipient informs You that such recipient no longer wishes to receive messages relating to Tendered Shipments, You shall immediately cease using UPS Technology to direct UPS to send messages to such recipient. You warrant that You have secured the informed and specific consent of the recipient of each message to receive such message and that the e-mail addresses and phone numbers You provide to UPS are accurate and controlled by the intended recipient of the message. You shall, at Your sole cost and expense, indemnify and hold harmless the UPS Indemnitees from and against any and all Damages incurred or suffered by the UPS Indemnitees arising out of or in connection with any breach of the warranties in the previous sentence.", "hash": "61c81a35d7ab80dd6476120ff7a6f409", "id": 3}, {"size": 5, "snippet_links": [{"key": "school-hours", "type": "clause", "offset": [50, 62]}], "samples": [{"hash": "fVTrpUcWkF6", "uri": "/contracts/fVTrpUcWkF6#messaging", "label": "Technology Agreement", "score": 33.3121566772, "published": true}, {"hash": "1KlbQEKz27w", "uri": "/contracts/1KlbQEKz27w#messaging", "label": "Technology Agreement", "score": 25.2943191528, "published": true}, {"hash": "gZx1XT6jGlU", "uri": "/contracts/gZx1XT6jGlU#messaging", "label": "Technology Agreement", "score": 24.7645454407, "published": true}], "snippet": "Apple Messages will be allowed for use outside of school hours.", "hash": "9afe403882fb243dacd8eeede9a3836d", "id": 5}, {"size": 3, "snippet_links": [{"key": "voice-call", "type": "definition", "offset": [5, 15]}], "samples": [{"hash": "lT87eDwZSyx", "uri": "/contracts/lT87eDwZSyx#messaging", "label": "Service Agreement", "score": 28.699508667, "published": true}, {"hash": "acv7X9ZNH4J", "uri": "/contracts/acv7X9ZNH4J#messaging", "label": "Service Agreement", "score": 28.5212688446, "published": true}, {"hash": "bvV7kCAWpXc", "uri": "/contracts/bvV7kCAWpXc#messaging", "label": "Voice Call Back   Cloud Service Agreement", "score": 22.2785758972, "published": true}], "snippet": "This Voice Call Back - Cloud feature transitions voice calls to an SMS chat when Customer\u2019s End-user is presented with a callback option.", "hash": "3d0c5613c1e5b2502d5fa04fe6331858", "id": 7}, {"size": 3, "snippet_links": [{"key": "company-will", "type": "clause", "offset": [0, 12]}, {"key": "in-connection-with", "type": "clause", "offset": [60, 78]}, {"key": "prior-approval", "type": "definition", "offset": [114, 128]}], "samples": [{"hash": "jvnidmxmUbI", "uri": "/contracts/jvnidmxmUbI#messaging", "label": "Brand Ambassador Agreement", "score": 29.3408622742, "published": true}, {"hash": "keY2isgjUs4", "uri": "/contracts/keY2isgjUs4#messaging", "label": "Brand Ambassador Agreement (Giggles N' Hugs, Inc.)", "score": 27.0219020844, "published": true}], "snippet": "Company will not use Consultant\u2019s name or approved likeness in connection with any messaging without Consultant\u2019s prior approval.", "hash": "754d2ab123b10d0a848cf884904b7dfb", "id": 8}, {"size": 3, "snippet_links": [{"key": "except-for-emergencies", "type": "clause", "offset": [39, 61]}, {"key": "sensitive-matters", "type": "definition", "offset": [72, 89]}, {"key": "changes-and-delays", "type": "clause", "offset": [119, 137]}], "samples": [{"hash": "keK3NInW3pU", "uri": "/contracts/keK3NInW3pU#messaging", "label": "Parenting Coordinator Service Agreement", "score": 30.4723072052, "published": true}], "snippet": "There shall be no texting between CPPs except for emergencies and time- sensitive matters such as last-minute schedule changes and delays in a transition.", "hash": "686496eb8dfc4612701951a466e2f7b5", "id": 9}, {"size": 2, "snippet_links": [{"key": "contractor-shall-provide", "type": "clause", "offset": [0, 24]}, {"key": "upon-request", "type": "definition", "offset": [45, 57]}, {"key": "for-example", "type": "definition", "offset": [73, 84]}, {"key": "practice-changes", "type": "clause", "offset": [109, 125]}, {"key": "contractor-to", "type": "clause", "offset": [147, 160]}, {"key": "training-module", "type": "definition", "offset": [201, 216]}, {"key": "to-offer", "type": "definition", "offset": [217, 225]}, {"key": "new-areas", "type": "definition", "offset": [242, 251]}, {"key": "the-remainder-of-this-page-intentionally-left-blank", "type": "clause", "offset": [267, 318]}], "samples": [{"hash": "9bXQAyxKCQr", "uri": "/contracts/9bXQAyxKCQr#messaging", "label": "Professional Services", "score": 32.2287139893, "published": true}, {"hash": "9cmHwg1bRiO", "uri": "/contracts/9cmHwg1bRiO#messaging", "label": "Professional Services", "score": 24.8206710815, "published": true}], "snippet": "Contractor shall provide follow-up messaging upon request from the IURC; for example, if a particular law or practice changes, the IURC may direct Contractor to contact users who completed the related training module to offer training on the new areas of compliance. THE REMAINDER OF THIS PAGE INTENTIONALLY LEFT BLANK", "hash": "dc9fe95b07310fdc40d5e6758b1729ca", "id": 10}], "next_curs": "ClISTGoVc35sYXdpbnNpZGVyY29udHJhY3Rzci4LEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2IhJtZXNzYWdpbmcjMDAwMDAwMGEMogECZW4YACAA", "clause": {"size": 141, "parents": [["miscellaneous", "Miscellaneous"], ["general", "General"], ["general-usage-policies-and-requirements", "General Usage Policies and Requirements"], ["secure-messaging", "Secure Messaging"], ["country-specific-terms", "Country-Specific Terms"]], "children": [["messaging-indemnity", "Messaging Indemnity"], ["supplemental-messaging-terms", "Supplemental Messaging Terms"], ["compliance", "Compliance"], ["", ""], ["personnel-costs-name-position-title-hourly", "Personnel Costs Name Position Title Hourly"]], "title": "Messaging", "id": "messaging", "related": [["text-messaging-while-driving", "TEXT MESSAGING WHILE DRIVING", "TEXT <strong>MESSAGING</strong> WHILE DRIVING"], ["links", "Links", "Links"], ["alerts-via-text-message", "Alerts via Text Message", "Alerts via Text Message"], ["encryption", "Encryption", "Encryption"], ["reducing-text-messaging-while-driving", "Reducing Text Messaging While Driving", "Reducing Text <strong>Messaging</strong> While Driving"]], "related_snippets": [], "updated": "2025-11-12T05:19:44+00:00", "also_ask": ["What key terms must be included in a messaging clause to ensure clarity and enforceability?", "How can the messaging clause be strategically negotiated to protect client communications and data?", "What are the most common risks or pitfalls in messaging clauses that could undermine enforceability?", "How do messaging clauses in this agreement compare to industry standards or statutory requirements?", "What factors do courts consider when determining the validity and scope of a messaging clause?"], "drafting_tip": "Specify permitted messaging channels to prevent unauthorized communications, require encryption to protect confidentiality, and define response times to ensure timely interactions.", "explanation": "The Messaging clause defines the rules and procedures for how parties will communicate with each other under the agreement. Typically, it specifies acceptable methods of communication, such as email or written notice, and may outline requirements for confirming receipt or designating official contact persons. This clause ensures that important information is reliably transmitted and received, reducing the risk of misunderstandings or missed notifications between the parties."}, "json": true, "cursor": ""}}