{"component": "clause", "props": {"groups": [{"samples": [{"hash": "9fA1xO7umFe", "uri": "/contracts/9fA1xO7umFe#problem-definition", "label": "General Terms and Conditions", "score": 24.5222450376, "published": true}, {"hash": "hTesLu25Z0G", "uri": "/contracts/hTesLu25Z0G#problem-definition", "label": "Services Agreement", "score": 24.4195756331, "published": true}], "snippet_links": [{"key": "to-assist", "type": "clause", "offset": [0, 9]}, {"key": "the-customer-should", "type": "clause", "offset": [57, 76]}, {"key": "for-reference", "type": "clause", "offset": [110, 123]}, {"key": "the-information", "type": "clause", "offset": [143, 158]}, {"key": "error-messages", "type": "clause", "offset": [175, 189]}, {"key": "the-user", "type": "clause", "offset": [269, 277]}, {"key": "customer-may", "type": "clause", "offset": [398, 410]}, {"key": "the-problem", "type": "clause", "offset": [439, 450]}, {"key": "product-version", "type": "clause", "offset": [459, 474]}], "size": 2, "snippet": "To assist in expeditiously resolving Customer\u2019s problem, the Customer should record the following information for reference and should provide the information to Alchemy: (a) error messages and indications that Customer received when the malfunction occurred,\n(b) what the user was doing when the malfunction occurred, (c) what steps Customer has taken to reproduce the malfunction, (d) what steps Customer may have already taken to solve the problem and (e) product version.", "hash": "112ea36d8effeb2e9a8305541a55b9c1", "id": 2}, {"samples": [{"hash": "2W3oVlHOMAQ", "uri": "/contracts/2W3oVlHOMAQ#problem-definition", "label": "Joint Reliability Coordination Agreement", "score": 34.1562804949, "published": true}, {"hash": "3nFBicOmlSg", "uri": "/contracts/3nFBicOmlSg#problem-definition", "label": "Joint Reliability Coordination Agreement", "score": 32.3303517046, "published": true}, {"hash": "cvRr6NrHu5O", "uri": "/contracts/cvRr6NrHu5O#problem-definition", "label": "Joint Reliability Coordination Agreement", "score": 32.1535977297, "published": true}], "snippet_links": [{"key": "nature-of", "type": "clause", "offset": [10, 19]}], "size": 8, "snippet": "1.1.1 The Nature of Energy Flows", "hash": "62089b6b37f08ae66b38f7d10cf3aab0", "id": 1}, {"samples": [{"hash": "lR1bVgVwjNE", "uri": "/contracts/lR1bVgVwjNE#problem-definition", "label": "Service Level Agreement", "score": 33.0295191148, "published": true}, {"hash": "4YnuV30eArn", "uri": "/contracts/4YnuV30eArn#problem-definition", "label": "Service Level Agreement", "score": 31.2743562294, "published": true}], "snippet_links": [{"key": "will-apply-to", "type": "clause", "offset": [43, 56]}, {"key": "the-performance", "type": "clause", "offset": [57, 72]}, {"key": "youth-services", "type": "definition", "offset": [83, 97]}, {"key": "service-level-agreement", "type": "clause", "offset": [109, 132]}, {"key": "priority-1", "type": "clause", "offset": [134, 144]}, {"key": "mission-critical", "type": "definition", "offset": [145, 161]}, {"key": "financial-impact", "type": "definition", "offset": [186, 202]}, {"key": "priority-2", "type": "definition", "offset": [203, 213]}, {"key": "significant-service", "type": "clause", "offset": [231, 250]}, {"key": "priority-3", "type": "definition", "offset": [275, 285]}, {"key": "priority-4", "type": "clause", "offset": [332, 342]}, {"key": "medium-priority", "type": "definition", "offset": [343, 358]}, {"key": "priority-5", "type": "definition", "offset": [399, 409]}, {"key": "low-priority", "type": "definition", "offset": [410, 422]}], "size": 2, "snippet": "The following standard problem definitions will apply to the performance of Member Youth Services under this Service Level Agreement. Priority 1 Mission critical Serious service, and/or financial impact Priority 2 Extremely urgent Significant service and/or financial impact Priority 3 Urgent Medium service and/or financial impact Priority 4 Medium priority Minimal service and/or financial impact Priority 5 Low Priority No service and/or financial impact", "hash": "1ae055c74efbe28fcbf61e2e565e1f65", "id": 3}, {"samples": [{"hash": "4Q67u9rBeHE", "uri": "/contracts/4Q67u9rBeHE#problem-definition", "label": "Master Relationship Agreement", "score": 35.929168379, "published": true}, {"hash": "gxzutv9pj4r", "uri": "/contracts/gxzutv9pj4r#problem-definition", "label": "Master Relationship Agreement", "score": 34.2689566329, "published": true}], "snippet_links": [{"key": "customer-shall", "type": "clause", "offset": [0, 14]}, {"key": "for-reference", "type": "clause", "offset": [48, 61]}, {"key": "the-user", "type": "clause", "offset": [188, 196]}, {"key": "customer-may", "type": "clause", "offset": [317, 329]}, {"key": "the-problem", "type": "clause", "offset": [358, 369]}, {"key": "system-logging", "type": "clause", "offset": [379, 393]}], "size": 2, "snippet": "Customer shall record the following information for reference and provide it to Iternal: (a) Defect messages and indications that Customer received when the malfunction occurred; (b) what the User was doing when the malfunction occurred; (c) what steps Customer has taken to reproduce the malfunction; (d) what steps Customer may have already taken to solve the problem; and (e) system logging.", "hash": "73663c3d9b9d58ac1095008067d6c4a9", "id": 4}, {"samples": [{"hash": "eqS0wp036ZA", "uri": "/contracts/eqS0wp036ZA#problem-definition", "label": "Master Services Agreement", "score": 26.9082819986, "published": true}, {"hash": "kXULVEJsxvt", "uri": "/contracts/kXULVEJsxvt#problem-definition", "label": "Master Services Agreement", "score": 26.2087611225, "published": true}], "snippet_links": [{"key": "customer-shall", "type": "clause", "offset": [0, 14]}, {"key": "for-reference", "type": "clause", "offset": [48, 61]}, {"key": "error-messages", "type": "clause", "offset": [92, 106]}, {"key": "the-user", "type": "clause", "offset": [186, 194]}, {"key": "customer-may", "type": "clause", "offset": [315, 327]}, {"key": "the-problem", "type": "clause", "offset": [356, 367]}, {"key": "system-logging", "type": "clause", "offset": [377, 391]}, {"key": "system-defect", "type": "definition", "offset": [421, 434]}, {"key": "business-critical", "type": "definition", "offset": [449, 466]}, {"key": "loss-of-customer-data", "type": "clause", "offset": [570, 591]}, {"key": "related-defect", "type": "definition", "offset": [626, 640]}, {"key": "material-specifications", "type": "definition", "offset": [770, 793]}], "size": 2, "snippet": "Customer shall record the following information for reference and provide it to Upland: (a) error messages and indications that Customer received when the malfunction occurred; (b) what the user was doing when the malfunction occurred; (c) what steps Customer has taken to reproduce the malfunction; (d) what steps Customer may have already taken to solve the problem; and (e) system logging Severity Impact 1 Production system Defect that prevents business critical work from being done, no Workaround exists, and Defect impacts most Users; or Defect causes a material loss of Customer Data in production system; or Security-related Defect. 2 Production system Defect that prevents business critical work from being done and a Workaround exists; or Defect violates the material specifications in the Documentation and impacts Customer\u2019s production system.", "hash": "1457be516e3babbb6d6ff6be0e37f58a", "id": 5}, {"samples": [{"hash": "5awThMpexaW", "uri": "/contracts/5awThMpexaW#problem-definition", "label": "Wireless Agreement", "score": 33.7933323718, "published": true}], "snippet_links": [{"key": "of-information", "type": "definition", "offset": [28, 42]}, {"key": "first-time", "type": "definition", "offset": [165, 175]}, {"key": "action-by", "type": "clause", "offset": [351, 360]}, {"key": "ready-to", "type": "clause", "offset": [472, 480]}, {"key": "the-final", "type": "clause", "offset": [488, 497]}, {"key": "in-order-to", "type": "clause", "offset": [617, 628]}, {"key": "time-of-the", "type": "clause", "offset": [697, 708]}, {"key": "figure-1", "type": "definition", "offset": [727, 735]}, {"key": "by-the-city", "type": "clause", "offset": [865, 876]}, {"key": "communication-channel", "type": "clause", "offset": [954, 975]}, {"key": "other-general", "type": "clause", "offset": [1033, 1046]}, {"key": "to-exchange", "type": "clause", "offset": [1103, 1114]}, {"key": "acknowledgement-of", "type": "clause", "offset": [1155, 1173]}, {"key": "original-message", "type": "clause", "offset": [1223, 1239]}, {"key": "an-agreement", "type": "clause", "offset": [1304, 1316]}, {"key": "of-the-sender", "type": "definition", "offset": [1411, 1424]}], "size": 2, "snippet": "\u200c To agree on a given piece of information is a classical co- ordination problem in distributed computing. The Two Gen- erals\u2019 Agreement Problem, formulated for the first time by \u2587\u2587\u2587 \u2587\u2587\u2587\u2587 [3] to illustrate the two-phase commit protocol in distributed database systems, is often used to explain the de- sign challenges when attempting to coordinate an action by communicating over a faulty channel, and can be described as follows. Two battalions are encamped near a city, ready to launch the final attack. Because of the redoubtable fortifications, the attack must be carried out by both battallions at the same time in order to succeed. \u2587\u2587\u2587\u2587\u2587, the generals of the two armies need to agree on the time of the attack, and their Figure 1: N-way handshake between nodes S and R. only way to communicate is to send messengers through the valley. The latter is occupied by the city\u2019s defenders, and a messenger can be captured and its message lost, i.e., the communication channel is unreliable. Since each general must be aware that the other general has agreed on the attack plan, messengers are used also to exchange acknowledg- ments. However, because the acknowledgement of a mes- sage receipt can be lost as easily as the original message, a potentially infinite series of messages is required to reach an agreement. A different problem that we are not addressing in this work is how to guarantee the identity of the sender of the message, as well as how to cope with misbehaving parties.", "hash": "a711cffeab14c592d92a6a065b05c294", "id": 6}, {"samples": [{"hash": "fuGMg0UzWsy", "uri": "/contracts/fuGMg0UzWsy#problem-definition", "label": "Quality Assurance Project Plan", "score": 33.4884009787, "published": true}], "snippet_links": [{"key": "are-properties", "type": "definition", "offset": [12, 26]}, {"key": "environmental-contamination", "type": "definition", "offset": [51, 78]}, {"key": "real-estate-transactions", "type": "clause", "offset": [96, 120]}, {"key": "prospective-purchasers", "type": "clause", "offset": [144, 166]}, {"key": "responsibility-for", "type": "clause", "offset": [285, 303]}, {"key": "costs-of", "type": "clause", "offset": [409, 417]}, {"key": "an-interest", "type": "clause", "offset": [446, 457]}, {"key": "environmental-issues", "type": "clause", "offset": [473, 493]}, {"key": "property-owners", "type": "definition", "offset": [582, 597]}, {"key": "ability-to-perform", "type": "clause", "offset": [632, 650]}, {"key": "environmental-assessments", "type": "clause", "offset": [651, 676]}, {"key": "property-transaction", "type": "definition", "offset": [701, 721]}, {"key": "a-site", "type": "definition", "offset": [747, 753]}, {"key": "to-provide", "type": "definition", "offset": [768, 778]}, {"key": "information-of", "type": "clause", "offset": [793, 807]}, {"key": "property-transfers", "type": "definition", "offset": [891, 909]}, {"key": "productive-use", "type": "clause", "offset": [970, 984]}], "size": 1, "snippet": "Brownfields are properties with known or potential environmental contamination that complicates real estate transactions or site redevelopment. Prospective purchasers of such properties need to protect their interests and limit potential losses by defining environmental liability and responsibility for cleanup before taking ownership. Those involved in site reuse planning must also consider the additional costs of cleanup, and therefore have an interest in identifying environmental issues before investing in site redevelopment. For varying reasons, prospective purchasers and property owners may not have the resources or the ability to perform environmental assessments necessary to complete a property transaction or to begin redeveloping a site. The ABP aims to provide environmental information of sufficient quality to allow prospective purchasers and property owners to complete property transfers, get sites cleaned up, and put \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 sites back into a productive use.", "hash": "2e31b0b53e5cdd05e30a46b80cef5247", "id": 7}, {"samples": [{"hash": "5Yrz11TEELH", "uri": "/contracts/5Yrz11TEELH#problem-definition", "label": "Service Level Agreement (Sla)", "score": 19.1314168378, "published": true}], "snippet_links": [{"key": "by-either-party", "type": "clause", "offset": [65, 80]}], "size": 1, "snippet": "A problem is defined as an unsatisfactory experience encountered by either Party which requires a resolution.", "hash": "24a12bd8fab8332a463409f35947e93a", "id": 8}, {"samples": [{"hash": "gHYebh5HgRQ", "uri": "/contracts/gHYebh5HgRQ#problem-definition", "label": "Group Key Agreement Protocol", "score": 19.0, "published": true}], "snippet_links": [{"key": "the-internet", "type": "clause", "offset": [95, 107]}, {"key": "the-members", "type": "clause", "offset": [124, 135]}, {"key": "group-key-agreement-protocols", "type": "clause", "offset": [214, 243]}, {"key": "all-members", "type": "definition", "offset": [252, 263]}, {"key": "a-member", "type": "clause", "offset": [329, 337]}, {"key": "network-latency", "type": "definition", "offset": [356, 371]}, {"key": "media-access-control", "type": "definition", "offset": [388, 408]}, {"key": "member-information", "type": "definition", "offset": [438, 456]}, {"key": "approving-members", "type": "definition", "offset": [467, 484]}, {"key": "to-generate", "type": "definition", "offset": [521, 532]}, {"key": "the-blind", "type": "definition", "offset": [629, 638]}, {"key": "order-of-arrival", "type": "clause", "offset": [659, 675]}, {"key": "the-group", "type": "clause", "offset": [743, 752]}, {"key": "key-generation", "type": "definition", "offset": [753, 767]}, {"key": "group-controller", "type": "definition", "offset": [771, 787]}, {"key": "similar-to", "type": "definition", "offset": [804, 814]}, {"key": "each-member", "type": "definition", "offset": [1049, 1060]}, {"key": "other-members", "type": "definition", "offset": [1070, 1083]}, {"key": "the-proposed-protocol", "type": "clause", "offset": [1449, 1470]}, {"key": "responsible-for", "type": "clause", "offset": [1479, 1494]}, {"key": "communication-protocols", "type": "clause", "offset": [1516, 1539]}, {"key": "figure-2", "type": "clause", "offset": [1552, 1560]}, {"key": "figure-3", "type": "definition", "offset": [1608, 1616]}, {"key": "public-key", "type": "definition", "offset": [1795, 1805]}, {"key": "directly-affect", "type": "definition", "offset": [1930, 1945]}, {"key": "the-performance", "type": "clause", "offset": [1946, 1961]}, {"key": "time-taken", "type": "clause", "offset": [2026, 2036]}, {"key": "the-network", "type": "clause", "offset": [2078, 2089]}, {"key": "number-of", "type": "clause", "offset": [2251, 2260]}, {"key": "group-size", "type": "definition", "offset": [2303, 2313]}, {"key": "first-level", "type": "clause", "offset": [2388, 2399]}, {"key": "for-example", "type": "definition", "offset": [3143, 3154]}, {"key": "all-levels", "type": "clause", "offset": [3412, 3422]}, {"key": "the-final", "type": "clause", "offset": [3424, 3433]}, {"key": "to-compensate", "type": "clause", "offset": [3487, 3500]}, {"key": "our-approach", "type": "clause", "offset": [3531, 3543]}], "size": 1, "snippet": "As mentioned earlier, members in a distributed comput- ing environment can be distributed over the Internet. Fur- thermore, the members can be at a workstation, a laptop, or even at a mobile computer. Conventional group key agreement protocols request all members to contribute to a GK. Consequently, a low performance member or a member located on a high network latency area could MAC (Media Access Control) address [9] by checking his member information DB. After approving members iden- tification, all members start to generate a group key by sending his blind key to the GCS who collects all blind keys and store them into the Blind Key Queues (BKQ) in order of arrival. Then the GCS informs participants who will join the next level of the group key generation. A group controller server (GCS) is similar to the Vir- tual Synchrony [16] that uses a client daemon program to manage membership. The Virtual Synchrony (VS) dae- mon runs on each members machine and synchronizes with other VSs to update membership whenever mem- bership changes. Each member can know other members status due to VS. TGDH uses a VS for maintaining mem- berships. However, Using VS involves complex processes to synchronize with all other VS daemons because mem- bers request a lot of message exchanges to update their status. In the mean time, the QGDH establishes a GCS server instead of running VS daemons on all members machines. Therefore, only one machine in the proposed protocol takes a responsible for a GCS. Current group communication protocols use a self- Figure 2: Queue-based group \u2587\u2587\u2587\u2587\u2587\u2587-\u2587\u2587\u2587\u2587\u2587\u2587\u2587 entity model Figure 3: The blind key queues in group controller server signed certificate for member authentication, which has a well-known weakness in that members cannot ensure that the name on the public key is really a true member\u2019s to measure members computing power and the other is to measure network latency. These two factors directly affect the performance of a GKGP. No matter how high perfor- \u2587\u2587\u2587\u2587\u2587 the machine, if the time taken for communicational messages to traverse the network is long, then the member must be regarded as low performance. Therefore, BKQ is a simplest way to measure for computing power and net- work latency at once. The number of levels in the GKGP can be determined by a group size. If the group size is n, then the number of levels is log2(n + 1). In the first level, all members are required to generate a blind key. In the next level, The GCS assigns two blind keys located on the opposite side of the BKQ in Figure 3, and then the GCS requests members who are in the shaded spots in the BKQ to compute \u2587\u2587\u2587\u2587\u2587\u2587-\u2587\u2587\u2587\u2587\u2587\u2587\u2587 key exchange with those blind keys and to store them into the BKQ in order of arrival. Following each level of group key computation, the GCS collects and stores all computed partial group keys into the BKQ in the order of their arrival at every level of the GKGP. As noticed in Figure 3, the fastest members key is always stored into the A1 spot in each level, the second fastest members key is stored into the A2 spot, and so on. The BKQ automatically assigns a pair of key computations. For example, if a member is in the A1 spot, then he is assigned to compute with a member in the last spot, An. Thus, A1 spots blind key (gK2 mod p) will be computed with An spots blind key (gKn\u22121 mod p), A2 spots blind key (gK3 mod p) and so on. After having completed all levels, the final group key can be computed as Equation (2): name [8]. To compensate for this well-known weakness, our approach uses a GCS as a complete trusted party. Our", "hash": "9f41c1e58d94d31c5329a7c445e12c94", "id": 9}, {"samples": [{"hash": "bu11hJ9nxlu", "uri": "/contracts/bu11hJ9nxlu#problem-definition", "label": "Usable Key Agreement in Home Networks", "score": 21.0, "published": true}], "snippet_links": [{"key": "key-agreement", "type": "clause", "offset": [29, 42]}, {"key": "the-network", "type": "clause", "offset": [112, 123]}, {"key": "backward-secrecy", "type": "clause", "offset": [144, 160]}, {"key": "forward-secrecy", "type": "clause", "offset": [231, 246]}, {"key": "the-fact", "type": "clause", "offset": [260, 268]}], "size": 1, "snippet": "In this section we propose a key agreement scheme for secure home networks that would:\n1) Allow devices to join the network while main- taining backward secrecy;\n2) Allow devices to seamlessly leave the net- work while maintaining forward secrecy;\n3) Leverage the fact that a returning device was previously part of the network to allow this device to seamlessly rejoin the network.", "hash": "2b852cc1b981769ab08e28a9709851b6", "id": 10}], "next_curs": "ClsSVWoVc35sYXdpbnNpZGVyY29udHJhY3RzcjcLEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2Ihtwcm9ibGVtLWRlZmluaXRpb24jMDAwMDAwMGEMogECZW4YACAA", "clause": {"parents": [["introduction", "Introduction"], ["amendment", "Amendment"], ["general", "General"], ["entire-agreement", "Entire Agreement"], ["abbreviations-acronyms-and-definitions", "ABBREVIATIONS, ACRONYMS AND DEFINITIONS"]], "title": "Problem Definition", "children": [["granularity-in-the-idc", "Granularity in the IDC"], ["reduced-data-and-granularity-coarseness", "Reduced Data and Granularity Coarseness"], ["accounting-for-loop-flows", "Accounting for Loop Flows"], ["conclusion", "Conclusion"], ["severity-1", "Severity 1"]], "size": 38, "id": "problem-definition", "related": [["term-definition", "Term Definition", "Term Definition"], ["000-definitions", "000 DEFINITIONS", "000 DEFINITIONS"], ["key-definitions", "Key Definitions", "Key Definitions"], ["dpa-definitions", "DPA Definitions", "DPA Definitions"], ["new-definition", "New Definition", "New Definition"]], "related_snippets": [], "updated": "2025-07-07T12:37:53+00:00"}, "json": true, "cursor": ""}}