{"component": "clause", "props": {"groups": [{"size": 2, "snippet": "Where we have connected new equipment to your existing system, we cannot accept responsibility for the cost of repairing or replacing parts of your existing system that later develop faults including any water or gas leaks.", "samples": [{"hash": "bFOb8wX1Dhj", "uri": "/contracts/bFOb8wX1Dhj#existing-system", "label": "Terms of Business", "score": 30.0534902886, "published": true}, {"hash": "MVXLXK2McO", "uri": "/contracts/MVXLXK2McO#existing-system", "label": "Terms of Business", "score": 29.9357834827, "published": true}], "snippet_links": [{"key": "new-equipment", "type": "clause", "offset": [24, 37]}, {"key": "responsibility-for", "type": "clause", "offset": [80, 98]}, {"key": "cost-of", "type": "definition", "offset": [103, 110]}], "hash": "adca784b05f1aad91a26fd1a7985e5f3", "id": 1}, {"size": 1, "snippet": "\u2587\u2587\u2587\u2587\u2587 and \u2587\u2587\u2587 [9] proposed a property-based proxy re-encryption scheme to enable users to achieve authorization in access control environments. However, \u2587\u2587\u2587\u2587\u2587 and Au [10] pointed out that this scheme does not have Adaptive security and CCA security features. Sun et al. [12] introduced a new proxy broadcast repeat encryption (PBRE) scheme and proved its security against selective cipher text attack (CCA) in a random oracle model under the decision n-BDHE hypothesis. \u2587\u2587 and \u2587\u2587\u2587 [13] proposed a broadcast agent encryption (RIBBPRE) security concept based on revocable identity to solve the key revocation problem. In this RIB-BPRE scheme, the agent can undo a set of delegates specified by the principal from the re-encryption key. They also pointed out that the identity-based broadcast agent re-encryption (RIB-BPRE) schemes do not take advantage of cloud computing, thus causes inconvenience to cloud users. \u2587\u2587\u2587 et al. [14] proposed a secure multi-owner data sharing scheme for dynamic groups in the cloud. Based on group signature and dynamic broadcast encryption technology, any cloud user can share their data anonymously with others. \u2587\u2587\u2587\u2587 et al. [15] proposed a cloud user data integrity check scheme based on polynomial authentication tag and agent tag update technology, which supports multi-user modification to resist collusive attack and other features. \u2587\u2587\u2587 et al. [16] proposed a secure data sharing cloud (SeDaSC) method using a single encryption key to encrypt files. This scheme provides data confidentiality and integrity, forward and backward access control, data sharing and other functions. \u2587\u2587 et al. [17] proposed a new attribute-based data sharing scheme to assist mobile users with limited resources based on cloud computing. Authentication and key agreement is a method that enables both parties to secretly calculate the session key on a public channel, which have been widely studies [18]\u2013[31]. As early as 1993, \u2587\u2587\u2587\u2587\u2587\u2587 [18] proposed that only a difference in the received signals helps achieving perfect cryptographic security, regardless of the enemy\u2019s computing power. But they have not considered the advantage of legitimate communicants. suffices for achieving perfect cryptographic security, regardless of the enemy\u2019s computing power. \u2587\u2587 and \u2587\u2587\u2587 [19] proposed a medical key negotiation scheme based on patient symptom matching. However, He et al. [32] pointed out that \u2587\u2587\u2019s scheme does not provide an identity tracking and resistance modification function and further proposed a cross-domain handshake scheme applicable to medical mobile social network and developed an android app for experimental analysis. Later, \u2587\u2587\u2587 and \u2587\u2587 [20] found that He et al.\u2019s scheme does not resist replay attack.", "samples": [{"hash": "6BcJEZziXsN", "uri": "/contracts/6BcJEZziXsN#existing-system", "label": "Authentication and Key Agreement Scheme", "score": 31.550830355, "published": true}], "snippet_links": [{"key": "enable-users", "type": "clause", "offset": [74, 86]}, {"key": "access-control", "type": "clause", "offset": [115, 129]}, {"key": "security-and", "type": "clause", "offset": [223, 235]}, {"key": "security-features", "type": "clause", "offset": [240, 257]}, {"key": "the-decision", "type": "clause", "offset": [438, 450]}, {"key": "security-concept", "type": "definition", "offset": [534, 550]}, {"key": "based-on", "type": "clause", "offset": [551, 559]}, {"key": "the-agent", "type": "clause", "offset": [641, 650]}, {"key": "by-the-principal", "type": "clause", "offset": [689, 705]}, {"key": "encryption-key", "type": "definition", "offset": [718, 732]}, {"key": "cloud-computing", "type": "definition", "offset": [854, 869]}, {"key": "data-sharing", "type": "clause", "offset": [959, 971]}, {"key": "encryption-technology", "type": "clause", "offset": [1059, 1080]}, {"key": "check-scheme", "type": "definition", "offset": [1197, 1209]}, {"key": "modification-to", "type": "clause", "offset": [1308, 1323]}, {"key": "other-features", "type": "clause", "offset": [1352, 1366]}, {"key": "secure-data", "type": "clause", "offset": [1395, 1406]}, {"key": "confidentiality-and-integrity", "type": "clause", "offset": [1511, 1540]}, {"key": "other-functions", "type": "clause", "offset": [1596, 1611]}, {"key": "to-assist", "type": "clause", "offset": [1679, 1688]}, {"key": "key-agreement", "type": "clause", "offset": [1770, 1783]}, {"key": "both-parties", "type": "clause", "offset": [1809, 1821]}, {"key": "calculate-the", "type": "clause", "offset": [1834, 1847]}, {"key": "session-key", "type": "definition", "offset": [1848, 1859]}, {"key": "public-channel", "type": "definition", "offset": [1865, 1879]}, {"key": "that-\u2587", "type": "clause", "offset": [2398, 2404]}, {"key": "applicable-to", "type": "clause", "offset": [2543, 2556]}, {"key": "social-network", "type": "definition", "offset": [2572, 2586]}, {"key": "replay-attack", "type": "clause", "offset": [2712, 2725]}], "hash": "e267b132d77c39ad4bad0ccaa92fa42c", "id": 4}, {"size": 2, "snippet": "Key pre-conveyance framework (KPS) (a.k.a. no interactive gathering appropriation framework) can be viewed as a non-intelligent gathering key exchange. For this situation, the mutual key of a given gathering is settled after the setup. In the event that a gathering is overhauled, then the mass key changes to the common key of the new amass. The disadvantage of KPS is that the client key size is combinatorial huge in the aggregate number of clients (if the framework is genuinely secure). Another downside is that the gathering key of guaranteed gather can't be changed regardless of the possibility that it is spilled surprisingly (e.g., cryptanalysis of figure writings bearing this key). The key size issue might be overcome if a calculationally secure framework is utilized, while the key spillage issue is difficult. Assist, calculationally secure KPS is just familiar for the two party case and the three-party case KPS with a gathering size more noteworthy than 3 is still open. The client key size is combinatorial substantial in the aggregate number of clients (if the framework is unequivocally secure).The assemble key of a given gathering can't be changed regardless of the possibility that it is spilled suddenly.", "samples": [{"hash": "c60M64sMuwV", "uri": "/contracts/c60M64sMuwV#existing-system", "label": "Group Key Agreement", "score": 24.6536797541, "published": true}, {"hash": "1FGeMKsegy1", "uri": "/contracts/1FGeMKsegy1#existing-system", "label": "Group Key Agreement", "score": 24.2430746171, "published": true}], "snippet_links": [{"key": "a-non", "type": "clause", "offset": [110, 115]}, {"key": "the-mutual", "type": "definition", "offset": [172, 182]}, {"key": "in-the-event", "type": "clause", "offset": [236, 248]}, {"key": "changes-to-the", "type": "definition", "offset": [299, 313]}, {"key": "the-client", "type": "definition", "offset": [375, 385]}, {"key": "number-of-clients", "type": "clause", "offset": [434, 451]}, {"key": "the-framework", "type": "clause", "offset": [456, 469]}], "hash": "ac447ae003002fa2ea153367941b8f79", "id": 2}, {"size": 2, "snippet": "Electrical service for the Building is supplied by National Grid. The existing generator at the Bulding supports life-safety systems within the Building, and may also be used by other tenants of the Project. Subject to system capacity, Tenant shall have the right to install two 60-AMP circuits on the UPS system and back-up generator currently existing at the Building at Tenant\u2019s sole cost and expense. Landlord makes no representation or warranty concerning the said UPS system and/or back-up generator and SPECIFICALLY DISCLAIMS ANY AND ALL REPRESENTATIONS AND WARRANTIES, INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTIBILITY OR FITNESS FOR A PARTICULAR PURPOSE. TENANT\u2019S USE OF, INTENDED USE OF, AND/OR RELIANCE ON SAID UPS SYSTEM AND/OR BACK-UP GENERATOR SHALL BE AT TENANT\u2019S SOLE RISK. The UPS system and back-up generator shall be separately metered and Tenant shall be responsible for a pro-rata share of electrical and maintenance costs and expenses. Landlord shall have no obligation to maintain, repair, service or replace said UPS System and/or back-up generator.", "samples": [{"hash": "9dcErbTBbm1", "uri": "/contracts/9dcErbTBbm1#existing-system", "label": "Office Lease (Exact Sciences Corp)", "score": 21.0, "published": true}, {"hash": "8OLYYkzUhAN", "uri": "/contracts/8OLYYkzUhAN#existing-system", "label": "Sublease Agreement (Exact Sciences Corp)", "score": 21.0, "published": true}], "snippet_links": [{"key": "electrical-service", "type": "definition", "offset": [0, 18]}, {"key": "for-the-building", "type": "clause", "offset": [19, 35]}, {"key": "national-grid", "type": "definition", "offset": [51, 64]}, {"key": "existing-generator", "type": "clause", "offset": [70, 88]}, {"key": "safety-systems", "type": "clause", "offset": [118, 132]}, {"key": "other-tenants", "type": "definition", "offset": [178, 191]}, {"key": "the-project", "type": "clause", "offset": [195, 206]}, {"key": "subject-to", "type": "definition", "offset": [208, 218]}, {"key": "system-capacity", "type": "definition", "offset": [219, 234]}, {"key": "tenant-shall", "type": "clause", "offset": [236, 248]}, {"key": "right-to-install", "type": "clause", "offset": [258, 274]}, {"key": "ups-system", "type": "clause", "offset": [302, 312]}, {"key": "at-tenant", "type": "definition", "offset": [370, 379]}, {"key": "cost-and-expense", "type": "clause", "offset": [387, 403]}, {"key": "no-representation-or-warranty", "type": "clause", "offset": [420, 449]}, {"key": "concerning-the", "type": "clause", "offset": [450, 464]}, {"key": "all-representations-and-warranties", "type": "clause", "offset": [541, 575]}, {"key": "including-without-limitation", "type": "clause", "offset": [577, 605]}, {"key": "fitness-for-a-particular-purpose", "type": "definition", "offset": [642, 674]}, {"key": "intended-use", "type": "clause", "offset": [693, 705]}, {"key": "reliance-on", "type": "clause", "offset": [717, 728]}, {"key": "sole-risk", "type": "clause", "offset": [791, 800]}, {"key": "separately-metered", "type": "definition", "offset": [848, 866]}, {"key": "responsible-for", "type": "clause", "offset": [887, 902]}, {"key": "rata-share", "type": "definition", "offset": [909, 919]}, {"key": "costs-and-expenses", "type": "definition", "offset": [950, 968]}, {"key": "landlord-shall", "type": "clause", "offset": [970, 984]}, {"key": "no-obligation-to-maintain", "type": "clause", "offset": [990, 1015]}], "hash": "4e35d9a82fcf99cafd7ad8974a9338a7", "id": 3}, {"size": 1, "snippet": "The works applies to disinfection at the STP and WTP. Below is an overview of each plant and a description of the deficiencies:", "samples": [{"hash": "9ZqOHtibb64", "uri": "/contracts/9ZqOHtibb64#existing-system", "label": "Professional Services", "score": 27.2614647502, "published": true}], "snippet_links": [{"key": "the-works", "type": "clause", "offset": [0, 9]}, {"key": "applies-to", "type": "clause", "offset": [10, 20]}, {"key": "an-overview", "type": "clause", "offset": [63, 74]}, {"key": "description-of-the", "type": "definition", "offset": [95, 113]}], "hash": "d534e3e6f7aad52bc738dbe914f92b34", "id": 5}, {"size": 1, "snippet": "The wireless networking is the without wired connection of linking two or more computing devices or nodes together for the purpose of sharing data and communication to each other nodes. Networks are built with combination of computing hardware and computer software. The wireless network is establishing the connection for the end- to-end paths are available. The previous systems are using he symmetric key encryption and decryption for the communication. Thus the method has to be producing the security into the communication. The source and destination is using the secret key for encryption and decryption, the source node is encrypting the original message into the chipper text using secret key. Thus the chipper text is transfer to the destination node and that the chipper text can be decrypt in to the plain text. The key is generated in the KGC (Key Generation Center). The KGC is generating the key in the previous stage of the communication that can\u2019t to be modified of change on the communication time and thus the key is constant for the end of the communication. The key is share to the entire group member and the attacker has to be easily track the key and decrypt the message. The key has not to be secured. The KGC is generating the key in the starting stage of the communication and that can\u2019t to be modified at the communication time. The key has to be generated after then user can\u2019t to be entering into the network", "samples": [{"hash": "vb16ncmqOc", "uri": "/contracts/vb16ncmqOc#existing-system", "label": "Asymmetric Group Key Agreement", "score": 24.7850787132, "published": true}], "snippet_links": [{"key": "wireless-networking", "type": "clause", "offset": [4, 23]}, {"key": "wired-connection", "type": "definition", "offset": [39, 55]}, {"key": "computing-devices", "type": "definition", "offset": [79, 96]}, {"key": "sharing-data", "type": "clause", "offset": [134, 146]}, {"key": "communication-to", "type": "clause", "offset": [151, 167]}, {"key": "computer-software", "type": "definition", "offset": [248, 265]}, {"key": "the-connection", "type": "clause", "offset": [304, 318]}, {"key": "previous-systems", "type": "definition", "offset": [364, 380]}, {"key": "encryption-and-decryption", "type": "clause", "offset": [408, 433]}, {"key": "the-method", "type": "definition", "offset": [462, 472]}, {"key": "the-security", "type": "clause", "offset": [493, 505]}, {"key": "the-source", "type": "clause", "offset": [530, 540]}, {"key": "original-message", "type": "clause", "offset": [646, 662]}, {"key": "transfer-to", "type": "definition", "offset": [728, 739]}, {"key": "the-destination", "type": "clause", "offset": [740, 755]}, {"key": "key-generation", "type": "definition", "offset": [857, 871]}, {"key": "of-change", "type": "clause", "offset": [980, 989]}, {"key": "group-member", "type": "definition", "offset": [1110, 1122]}, {"key": "the-starting", "type": "clause", "offset": [1260, 1272]}, {"key": "entering-into", "type": "clause", "offset": [1413, 1426]}, {"key": "the-network", "type": "clause", "offset": [1427, 1438]}], "hash": "037802629acdbd1d092f1141d5848d2b", "id": 6}, {"size": 1, "snippet": "i) Conduct a review and prepare a summary of the existing Sanitary Sewer System. Review to focus on ensuring the existing sewer main system has the capacity needed to service the future/built-out condition. \u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587, SUITE 350 \u00a7 SAN RAMON, CALIFORNIA 94583 \u00a7 (\u2587\u2587\u2587) \u2587\u2587\u2587-\u2587\u2587\u2587\u2587 \u00a7 \u2587\u2587\u2587.\u2587\u2587\u2587\u2587\u2587\u2587.\u2587\u2587\u2587 SAN \u2587\u2587\u2587\u2587\u2587 \u00a7 ROSEVILLE", "samples": [{"hash": "7vHpYoZVWcF", "uri": "/contracts/7vHpYoZVWcF#existing-system", "label": "Consultant Agreement", "score": 22.8056125941, "published": true}], "snippet_links": [{"key": "summary-of-the", "type": "clause", "offset": [34, 48]}, {"key": "sanitary-sewer-system", "type": "definition", "offset": [58, 79]}, {"key": "review-to", "type": "clause", "offset": [81, 90]}, {"key": "main-system", "type": "definition", "offset": [128, 139]}, {"key": "the-future", "type": "clause", "offset": [175, 185]}, {"key": "out-condition", "type": "clause", "offset": [192, 205]}, {"key": "suite-350", "type": "clause", "offset": [226, 235]}], "hash": "b65c0bb545f166d5e756aa966a65847f", "id": 7}, {"size": 1, "snippet": "Group key agreement (GKA) is another well-understood cryptographic primitive to secure group-oriented communications. A conventional GKA allows a group of members to establish a common secret key via open networks. However, whenever a sender wants to send a message to a group, he must first join the group and run a GKA protocol to share a secret key with the intended members. More recently, and to overcome this limitation, \u2587\u2587 et al. introduced asymmetric GKA, in which only a common group public key is negotiated and each group member holds a different decryption key. However, neither conventional symmetric GKA nor the newly introduced asymmetric GKA allow the sender to unilaterally exclude any particular member from reading the plaintext. Hence, it is essential to find more flexible cryptographic primitives allowing dynamic broadcasts without a fully trusted dealer.", "samples": [{"hash": "hvTdQbhufd4", "uri": "/contracts/hvTdQbhufd4#existing-system", "label": "Group Key Agreement", "score": 23.5505206193, "published": true}], "snippet_links": [{"key": "group-key-agreement", "type": "clause", "offset": [0, 19]}, {"key": "to-secure", "type": "clause", "offset": [77, 86]}, {"key": "of-members", "type": "clause", "offset": [152, 162]}, {"key": "to-establish", "type": "clause", "offset": [163, 175]}, {"key": "the-group", "type": "clause", "offset": [297, 306]}, {"key": "public-key", "type": "definition", "offset": [493, 503]}, {"key": "group-member", "type": "definition", "offset": [527, 539]}, {"key": "decryption-key", "type": "definition", "offset": [558, 572]}], "hash": "44e89da31ffc070f4da7f6ae8a42e6b2", "id": 8}, {"size": 1, "snippet": "Analysis Summary \u2013 AECOM will compile the findings from the tasks outlined above into a draft Existing System Analysis Summary document, including:\n1) \uf0a7 Base Map (1.", "samples": [{"hash": "kQHJzKU4iGo", "uri": "/contracts/kQHJzKU4iGo#existing-system", "label": "Contract for Planning Services", "score": 22.4291581109, "published": true}], "snippet_links": [{"key": "system-analysis", "type": "clause", "offset": [103, 118]}, {"key": "summary-document", "type": "definition", "offset": [119, 135]}, {"key": "base-map", "type": "definition", "offset": [153, 161]}], "hash": "53c5b4462a4242f831e8470f9fb03d1a", "id": 9}, {"size": 1, "snippet": "In cloud computing, a resource provisioning mechanism is required to supply cloud consumers a set of computing resources for processing the jobs and storing the data. Cloud providers can offer cloud consumers two resource provisioning plans, namely short-term on-demand and long-term reservation plans. Cloud providers which offer IaaS services with both plans. In general, pricing in on-demand plan is charged by pay-per-use basis (e.g., 1 day). Therefore, purchasing this on-demand plan, the consumers can dynamically provision resources at the moment when the resources are needed to fit the fluctu- ated and unpredictable demands. For reservation plan, pricing is charged by a onetime fee (e.g., 1 year) typical- ly before the computing resource will be utilized by cloud consumer. With the reservation plan, the price to utilize resources is cheaper than that of the on-demand plan. In this way, the consumer can reduce the cost of computing resource provisioning by using the reserva- tion plan", "samples": [{"hash": "lIca0zOEfcR", "uri": "/contracts/lIca0zOEfcR#existing-system", "label": "Service Level Agreement", "score": 22.2766289934, "published": true}], "snippet_links": [{"key": "cloud-computing", "type": "definition", "offset": [3, 18]}, {"key": "resources-for", "type": "clause", "offset": [111, 124]}, {"key": "the-data", "type": "clause", "offset": [157, 165]}, {"key": "cloud-providers", "type": "clause", "offset": [167, 182]}, {"key": "in-general", "type": "clause", "offset": [362, 372]}, {"key": "demand-plan", "type": "definition", "offset": [388, 399]}, {"key": "by-pay", "type": "clause", "offset": [411, 417]}, {"key": "the-price", "type": "clause", "offset": [813, 822]}, {"key": "the-consumer", "type": "definition", "offset": [901, 913]}, {"key": "cost-of", "type": "definition", "offset": [929, 936]}], "hash": "feae225e05a9f066fc27e01701fff546", "id": 10}], "next_curs": "ClgSUmoVc35sYXdpbnNpZGVyY29udHJhY3RzcjQLEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2IhhleGlzdGluZy1zeXN0ZW0jMDAwMDAwMGEMogECZW4YACAA", "clause": {"size": 19, "title": "Existing System", "parents": [["miscellaneous", "Miscellaneous"], ["existing-and-proposed-systems", "Existing and Proposed Systems"], ["price-list", "Price List"], ["counterparts", "Counterparts"], ["sanitary-sewer-master-plan-update", "Sanitary Sewer Master Plan Update"]], "children": [["water-treatment-plant", "Water Treatment Plant"], ["sewage-treatment-plant", "Sewage Treatment Plant"], ["proposed-system", "PROPOSED SYSTEM"], ["", ""], ["capital-improvement-strategies-and-action-plan", "Capital Improvement Strategies and Action Plan"]], "id": "existing-system", "related": [["filing-systems-and-equipment", "Filing Systems and Equipment", "Filing Systems and Equipment"], ["building-systems", "Building Systems", "Building Systems"], ["developer-attachment-facilities", "Developer Attachment Facilities", "Developer Attachment Facilities"], ["customer-equipment", "Customer Equipment", "Customer Equipment"], ["changes-in-equipment-systems-etc", "Changes in Equipment, Systems, Etc", "Changes in Equipment, Systems, Etc"]], "related_snippets": [], "updated": "2025-07-07T16:38:45+00:00"}, "json": true, "cursor": ""}}