├── README-CDO-QUESTIONS.md ├── README-DATA-ARCHITECTURE.md └── LICENSE /README-CDO-QUESTIONS.md: -------------------------------------------------------------------------------- 1 | This document is in the public domain under the license: 2 | 3 | [![License: CC BY-NC-ND 4.0](https://img.shields.io/badge/License-CC%20BY--NC--ND%204.0-lightgrey.svg)](https://creativecommons.org/licenses/by-nc-nd/4.0/) 4 | 5 | ----- 6 | 7 | # Introduction 8 | 9 | The purpose of this document is to understand: 10 | 11 | - where an organisation sits on the Data Maturity chart 12 | - the key components of the data strategy and how those elements relate to the business strategy 13 | - the importance/urgency of each component of the data stategy 14 | 15 | # Organisation Structure 16 | 17 | Try to keep the answers for this section on one page. 18 | 19 | - How is the organisation structured? This could be by business unit 20 | - How many resources do you have in the following categories: 21 | - Data Architects 22 | - Data scientists 23 | - Data Engineer 24 | - Data Analysts 25 | - Data steward 26 | - Where do the resources sit in the organisation structure? 27 | 28 | # Data Strategy 29 | 30 | - Has a Data Strategy been created? 31 | - Is there a lineage between the elements of the Data Strategy showing how it supports the Business Strategy? 32 | - Where is the Business Strategy defined? E.g. 33 | - public company; annual report, xxx, yyy 34 | - ... 35 | - Has a data maturity assessment been carried out? 36 | - When was this done? 37 | - What were the results? 38 | 39 | # General 40 | 41 | - Has an analysis or discovery of data related organisational pain points been performed? 42 | - Do you have examples of poor data management resulting in operational inefficiencies? 43 | 44 | # Governance 45 | 46 | # ... 47 | -------------------------------------------------------------------------------- /README-DATA-ARCHITECTURE.md: -------------------------------------------------------------------------------- 1 | This document is in the public domain under the license: 2 | 3 | [![License: CC BY-NC-ND 4.0](https://img.shields.io/badge/License-CC%20BY--NC--ND%204.0-lightgrey.svg)](https://creativecommons.org/licenses/by-nc-nd/4.0/) 4 | 5 | ----- 6 | 7 | # Introduction 8 | 9 | This is a living document of typical [non-functional requirement](https://en.m.wikipedia.org/wiki/Non-functional_requirement) (NFR) questions for data intensive analytic architectures. 10 | 11 | Data intensive analytic architectures are typically 'fed' with data from other systems such as OLTP systems. The main data flow patterns for these architectures are: 12 | 13 | TODO diagram 14 | 15 | Analytic solution architectures are typically not the masters of the data they hold. If data has incorrect values, it is usually updated in the upstream source system and these updates then trickle through to the analytics solution. 16 | 17 | # Project/commercial 18 | 19 | This section lists the questions relating to the project. 20 | 21 | ## Goals/objectives 22 | 23 | - What are the top level goals of the project? 24 | - How does the project support the organisation's strategic drivers? 25 | - Does the project provide a new source of competitive advantage and/or allow you to differentiate in some way? 26 | - What are the business drivers? e.g. 27 | - increased revenue? 28 | - reduced costs? 29 | - confirm to regulation or compliance mandates? 30 | - How do the business drivers translate into project goals that can be measured? 31 | - goal 1 ... measured by ... 32 | - goal 2 ... measured by ... 33 | - goal n ... measured by ... 34 | - What is the type of project: 35 | - Development of a new set of capabilities? 36 | - Replace existing system? 37 | - Examples 38 | - automate a manual process 39 | - replace a legacy system 40 | - reduce costs 41 | - other (please describe) 42 | - What is the current architecture of the existing solution? 43 | - Who are the stakeholders? 44 | - What are their roles? 45 | - What are their responsibilities? 46 | - What are the strengths of the existing solution? 47 | - What are the weaknesses of the existing solution? 48 | - Can you provide a [System Context Diagram](https://en.wikipedia.org/wiki/System_context_diagram) for the existing solution? 49 | - What are the solution goals for the project? 50 | - Evaluating a potential solution? e.g. proof-of-concept 51 | - Verifing a potential solution, e.g. pilot 52 | - Implementing a solution? e.g. production solution 53 | - Who will maintain the solution in production? 54 | - Are there any secondary goals for the project? e.g. 55 | - Upskilling employees? 56 | - One option is to do nothing and carry on as normal - what would be the implications of doing nothing? 57 | 58 | ## Timelines/Budget 59 | 60 | - Is the project a single phase or multiple phases? 61 | - single phase: 62 | - What are the key milestones and their dates? 63 | - multiple phases: 64 | - What are the phases? 65 | - What are the key milestones and dates of each phase? 66 | - What is the overall budget and breakdown by phase? 67 | - What are the post-project budgets? e.g. 68 | - production running costs? 69 | - maintenance costs? e.g. bug fix 70 | - Is the budget approved, or does it need to go through an approval process? 71 | - What is the approval process? 72 | 73 | ## Stakeholders 74 | 75 | - Who are the key [stakeholders/team members](https://www.viewpoints-and-perspectives.info/home/stakeholders/) and what are their responsibilities ... 76 | - for the project: 77 | - Who will pay for the project? 78 | - Who will architect, develop, test the solution? 79 | - Who will manage the project? 80 | - Who is accountable for the project delivery? 81 | - for the production solution: 82 | - Who will use the system? 83 | - Who will maintain the solution in production? 84 | - Who pays for the solution maintenance/running costs? 85 | 86 | ## Constraints 87 | 88 | - Does the project have any constraints/preferences that it needs to adhere to? e.g. 89 | - enterprise architecture standards? 90 | - Do you have technology preferences/requirements? e.g. 91 | - hadoop vs rdbms 92 | - open source vs proprietary 93 | - specific software packages, e.g. presto 94 | - programming/data science tools (e.g. R, or Python) 95 | - If the solution is to replace an existing solution ... 96 | - do you have requirements for reuse code/assets, or is a ground up rewrite possible/desired (if that makes sense)? 97 | - Is the project going to be developed in-house or outsourced? 98 | - If outsourcing and the project is a differentiator: 99 | - how are you going to bring the skills/knowledge back inside? 100 | - How are you going to grow these differentiating skills/knowledge? 101 | 102 | ## Risks/Issues 103 | 104 | - What are the core project risks and issues? 105 | 106 | # Functional Requirements 107 | 108 | More questions coming soon... 109 | 110 | - Do you have hills, epics, user stories, or other functional requirements (use-cases, behavoir driven development specs)? 111 | - Do you have user interface visualisations/mock-ups? 112 | 113 | # System Requirements 114 | 115 | This section lists the questions relating to the solution. 116 | 117 | ## Type of System 118 | 119 | - What is the main purpose of the system? 120 | - Data Lake 121 | - IoT Persistence 122 | - A.I. Model build and deploy 123 | - Data Warehouse off-load 124 | - ... 125 | 126 | ## Ingest 127 | 128 | **Introduction** 129 | 130 | This section is to provide insight into the data ingest patterns to design the data ingest process. 131 | 132 | **Questions** 133 | 134 | - How will the data arrive? 135 | - As a continuous *stream* of data? 136 | - What is the peak rate of ingest in Gb/s? Now, 1YR, 3YRs, 5YRs? 137 | - What is the peak rate of ingest in records/second? Now, 1YR, 3YRs, 5YRs? 138 | - What does the load curve look like? E.g. is it fairly flat and consistent, or does it vary a lot? 139 | - What are the required delivery guarantees (exactly once, at most once, at least once)? Hint: do downstream queries on landed data need to be 100% accurate? 140 | - As periodic *batches* of data? 141 | - What frequency? 142 | - What is specification for the batch data? 143 | - What are the file sizes? 144 | - Row count? 145 | - Size on disk? 146 | - How are the sizes expected to grow/shrink over time? 147 | - Will the ingest grow or decrease in volumes over time? 148 | - How are records identified? 149 | - How are the records distributed around the identifier? Is there any skew? 150 | - What is considered late data? E.g. a shop loses network connectivity for a day due to a fault - how do we handle the late point-of-sales transactions? 151 | - When does the data load start arriving? 152 | - Do we need to back-load data prior to this (e.g. by batch load)? 153 | - How much data needs to be back-loaded in Gb? 154 | - How much data needs to be back-loaded in record counts? 155 | - After receiving the data how quickly should clients be able to see the data in queries (latency)? 156 | - Is the data structured or unstructued? 157 | - What is the data format/encoding? E.g. avro, json, csv, parquet, xls 158 | - If structured, can you share a sample of data? 159 | - If structured, can you share a schema for the data? 160 | - If file based, can you share a specification and files? 161 | - Can you provide some context for this source of data? E.g. 162 | - Where is the data coming from? 163 | - How is it generated? 164 | - Who is/will be the master of the data? E.g. 165 | - Is it a source relational database that we are performing change data capture from? 166 | - Is *this* system that we are building going to be the master? 167 | - How can we detect incremental changes in the source system? E.g. 168 | - Specialised off the shelf change data capture tools such as [InfoSphere CDC](https://www.ibm.com/support/knowledgecenter/en/SSX3HK_6.5.2/com.ibm.cdcdoc.mcadminguide.doc/concepts/overview_of_cdc.html) 169 | - Manually select changes based on timestamp or row versioning in RDBMS? [Wikipedia](https://en.m.wikipedia.org/wiki/Change_data_capture) 170 | - Monitor filesystem folder for new files 171 | - How is the data model expected to change over time? I.e. do we need to use a format that is resistent to schema changes (such as avro)? 172 | - How can you verify that you have not ingested dirty (incorrect) data? 173 | - How can you verify that you have ingested all the required data? E.g. 174 | - Weekly row counts of records ingested cross-related to number of inserts/updates in source system 175 | - Who will build and maintain the data ingest process? 176 | - What are their core skills? 177 | - Will they be trained to provide necessary skills? 178 | - What is your development lifecycle, or are you flexible? e.g. [pause and resume with savepoints](https://ci.apache.org/projects/flink/flink-docs-release-1.4/setup/savepoints.html#overview) 179 | - Who will monitor the streams? 180 | - What do they want to monitor? [Flink example](https://ci.apache.org/projects/flink/flink-docs-release-1.4/monitoring/checkpoint_monitoring.html), [IBM Streaming Analytics](https://www.ibm.com/blogs/bluemix/2016/07/streaming-analytics-metrics-using-rest-api/) 181 | 182 | ## Predict 183 | 184 | - Do you have an existing machine learning model, or will a new one be created? 185 | - Existing model? 186 | - How was the model created? 187 | - Libraries/frameworks? 188 | - Versions? 189 | - How big is the model, how much memory space does it take? 190 | - Create a new one? 191 | - Do you have a preferences on libraries/frameworks to use? 192 | - How frequently will the model be refreshed? 193 | - How will it be refreshed? manually? automatically? 194 | - What is the business purpose of the model? 195 | - How is the business success of the model measured? E.g. profit generated 196 | - Is the problem domain perceptual and requiring deep learning? E.g. working with audio, image, video 197 | - What is the type of problem? E.g. regression, classification, collaborative filtering, ... 198 | - Is the prediction task batch or near real-time? 199 | - Now ask the ingest questions for each batch/stream of data for prediction. 200 | 201 | ## Analyse (realtime) 202 | 203 | - Completeness: How important is it to have all of your data before you compute your result? 204 | - Latency: How long do you want to wait for data? For example, do you wait until you think you have all data? Do you process data as it arrives? 205 | - Cost: How much compute power/money are you willing to spend to lower the latency? 206 | 207 | ## Retrieval (query) 208 | 209 | **Introduction** 210 | 211 | This section is to provide insight into the data access patterns to help decide what persistence technologies are appropriate along with data models and data formats. 212 | 213 | **Questions** 214 | 215 | - How will client systems access the data? JDBC? ODBC? API? 216 | - Who are the clients that execute the queries? Systems (code) or humans? 217 | - What is the business purpose for the queries and what are the key requirements? E.g. 218 | - Financial reconcilliation report requiring high accuracy 219 | - A page hit counter that only needs to be approximate 220 | - Build/update machine learning model 221 | - What types of queries will be run on the data? 222 | - Preknown (canned) queries? 223 | - Exploratory (ahdoc) queries? 224 | - Slice and dice (data warehouse/mart style queries)? 225 | - Free text search? 226 | - When will the queries be run? E.g. 227 | - query 'abc' Monday to Friday between 9am and 5pm GMT 228 | - query 'def' once a day between 02:00 to 04:00 BST 229 | - Are the queries OLAP or OLTP? 230 | - What frequency will the queries be run? 231 | - What are the expectations around retrieval rate? 232 | - Number of records/second? 233 | - Mb/s? 234 | - What are the latency requirements? I.e. how quickly do you expect to see your query data returned? 235 | - What windows are available for maintenance at which time queries cannot be run? (if any) 236 | - Can data be separated into hot data (newer) and cold data (older)? 237 | - Do the retrieval requirements change depending on the hotness? Can we take longer to query cold data? 238 | - What are the consistency requirements? [research paper](https://www.microsoft.com/en-us/research/publication/replicated-data-consistency-explained-through-baseball/) 239 | - What are the transaction isolation requirements? [Wikipedia](https://en.wikipedia.org/wiki/Isolation_(database_systems)) 240 | - Do you have a specific data model that you require or is this flexible? 241 | - Can we denormalise data at write time to reduce reads at query time? 242 | 243 | ## Resilience 244 | 245 | - What are the availability requirements? E.g. HA with DC, HA across DC 246 | - for the solution? 247 | - for individual parts of the solution? 248 | 249 | ## Locality 250 | 251 | - Must the data remain inside a country's boundary? 252 | - Are there requiremebts for internationalisation of user interface labels? 253 | 254 | ## Security 255 | 256 | - What are your backup requirements? 257 | - Recovery point objective (RPO)? [wikipedia](https://en.wikipedia.org/wiki/Recovery_point_objective) 258 | - Recovery time objective (RTO)? [wikipedia](https://en.wikipedia.org/wiki/Recovery_time_objective) 259 | - What are the confidentiality requirements (e.g. encryption)? 260 | - What are the network security requirments (e.g. VPC/VPN)? 261 | - What are the requirements for physical isolation of data at rest? e.g. multi-tenant solutions ok? 262 | - What are the requirements for key management? e.g. shared vendor keys/dedicated vendor keys/customer provides own key 263 | - What are the requirements for authentication? e.g. enterprise ldap/sso integration 264 | - Are there any access log/auditing requirements? 265 | - How do you want to control access to the data? E.g. 266 | - Role-based access control (RBAC) [wikipedia](https://en.m.wikipedia.org/wiki/Role-based_access_control) 267 | - What is the granularity of access permissions? E.g. Table, row, cell? 268 | 269 | ## Compliance 270 | 271 | - Will the system hold data that has compliance requirements, such as GDPR? 272 | - What are the requirements and how do you want to comply? E.g. 273 | - Requirement: Right to be forgotten 274 | - Approach: Anonymise individual's PI data records 275 | 276 | ## Archival 277 | 278 | - When is data considered hot/cold? 279 | - Are the non-functional requirements different for hot/cold data? 280 | - Can hot/cold data be accessed differently? E.g. 281 | - hot in rdbms for lower latency retrieval 282 | - cold in object storage 283 | 284 | ## Maintainability 285 | 286 | - What environments do you need? E.g. dev, test, stage, prod 287 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Attribution-NonCommercial-NoDerivatives 4.0 International 2 | 3 | ======================================================================= 4 | 5 | Creative Commons Corporation ("Creative Commons") is not a law firm and 6 | does not provide legal services or legal advice. Distribution of 7 | Creative Commons public licenses does not create a lawyer-client or 8 | other relationship. Creative Commons makes its licenses and related 9 | information available on an "as-is" basis. Creative Commons gives no 10 | warranties regarding its licenses, any material licensed under their 11 | terms and conditions, or any related information. Creative Commons 12 | disclaims all liability for damages resulting from their use to the 13 | fullest extent possible. 14 | 15 | Using Creative Commons Public Licenses 16 | 17 | Creative Commons public licenses provide a standard set of terms and 18 | conditions that creators and other rights holders may use to share 19 | original works of authorship and other material subject to copyright 20 | and certain other rights specified in the public license below. The 21 | following considerations are for informational purposes only, are not 22 | exhaustive, and do not form part of our licenses. 23 | 24 | Considerations for licensors: Our public licenses are 25 | intended for use by those authorized to give the public 26 | permission to use material in ways otherwise restricted by 27 | copyright and certain other rights. Our licenses are 28 | irrevocable. Licensors should read and understand the terms 29 | and conditions of the license they choose before applying it. 30 | Licensors should also secure all rights necessary before 31 | applying our licenses so that the public can reuse the 32 | material as expected. Licensors should clearly mark any 33 | material not subject to the license. This includes other CC- 34 | licensed material, or material used under an exception or 35 | limitation to copyright. More considerations for licensors: 36 | wiki.creativecommons.org/Considerations_for_licensors 37 | 38 | Considerations for the public: By using one of our public 39 | licenses, a licensor grants the public permission to use the 40 | licensed material under specified terms and conditions. If 41 | the licensor's permission is not necessary for any reason--for 42 | example, because of any applicable exception or limitation to 43 | copyright--then that use is not regulated by the license. Our 44 | licenses grant only permissions under copyright and certain 45 | other rights that a licensor has authority to grant. Use of 46 | the licensed material may still be restricted for other 47 | reasons, including because others have copyright or other 48 | rights in the material. A licensor may make special requests, 49 | such as asking that all changes be marked or described. 50 | Although not required by our licenses, you are encouraged to 51 | respect those requests where reasonable. More_considerations 52 | for the public: 53 | wiki.creativecommons.org/Considerations_for_licensees 54 | 55 | ======================================================================= 56 | 57 | Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 58 | International Public License 59 | 60 | By exercising the Licensed Rights (defined below), You accept and agree 61 | to be bound by the terms and conditions of this Creative Commons 62 | Attribution-NonCommercial-NoDerivatives 4.0 International Public 63 | License ("Public License"). To the extent this Public License may be 64 | interpreted as a contract, You are granted the Licensed Rights in 65 | consideration of Your acceptance of these terms and conditions, and the 66 | Licensor grants You such rights in consideration of benefits the 67 | Licensor receives from making the Licensed Material available under 68 | these terms and conditions. 69 | 70 | 71 | Section 1 -- Definitions. 72 | 73 | a. Adapted Material means material subject to Copyright and Similar 74 | Rights that is derived from or based upon the Licensed Material 75 | and in which the Licensed Material is translated, altered, 76 | arranged, transformed, or otherwise modified in a manner requiring 77 | permission under the Copyright and Similar Rights held by the 78 | Licensor. For purposes of this Public License, where the Licensed 79 | Material is a musical work, performance, or sound recording, 80 | Adapted Material is always produced where the Licensed Material is 81 | synched in timed relation with a moving image. 82 | 83 | b. Copyright and Similar Rights means copyright and/or similar rights 84 | closely related to copyright including, without limitation, 85 | performance, broadcast, sound recording, and Sui Generis Database 86 | Rights, without regard to how the rights are labeled or 87 | categorized. For purposes of this Public License, the rights 88 | specified in Section 2(b)(1)-(2) are not Copyright and Similar 89 | Rights. 90 | 91 | c. Effective Technological Measures means those measures that, in the 92 | absence of proper authority, may not be circumvented under laws 93 | fulfilling obligations under Article 11 of the WIPO Copyright 94 | Treaty adopted on December 20, 1996, and/or similar international 95 | agreements. 96 | 97 | d. Exceptions and Limitations means fair use, fair dealing, and/or 98 | any other exception or limitation to Copyright and Similar Rights 99 | that applies to Your use of the Licensed Material. 100 | 101 | e. Licensed Material means the artistic or literary work, database, 102 | or other material to which the Licensor applied this Public 103 | License. 104 | 105 | f. Licensed Rights means the rights granted to You subject to the 106 | terms and conditions of this Public License, which are limited to 107 | all Copyright and Similar Rights that apply to Your use of the 108 | Licensed Material and that the Licensor has authority to license. 109 | 110 | g. Licensor means the individual(s) or entity(ies) granting rights 111 | under this Public License. 112 | 113 | h. NonCommercial means not primarily intended for or directed towards 114 | commercial advantage or monetary compensation. For purposes of 115 | this Public License, the exchange of the Licensed Material for 116 | other material subject to Copyright and Similar Rights by digital 117 | file-sharing or similar means is NonCommercial provided there is 118 | no payment of monetary compensation in connection with the 119 | exchange. 120 | 121 | i. Share means to provide material to the public by any means or 122 | process that requires permission under the Licensed Rights, such 123 | as reproduction, public display, public performance, distribution, 124 | dissemination, communication, or importation, and to make material 125 | available to the public including in ways that members of the 126 | public may access the material from a place and at a time 127 | individually chosen by them. 128 | 129 | j. Sui Generis Database Rights means rights other than copyright 130 | resulting from Directive 96/9/EC of the European Parliament and of 131 | the Council of 11 March 1996 on the legal protection of databases, 132 | as amended and/or succeeded, as well as other essentially 133 | equivalent rights anywhere in the world. 134 | 135 | k. You means the individual or entity exercising the Licensed Rights 136 | under this Public License. Your has a corresponding meaning. 137 | 138 | 139 | Section 2 -- Scope. 140 | 141 | a. License grant. 142 | 143 | 1. Subject to the terms and conditions of this Public License, 144 | the Licensor hereby grants You a worldwide, royalty-free, 145 | non-sublicensable, non-exclusive, irrevocable license to 146 | exercise the Licensed Rights in the Licensed Material to: 147 | 148 | a. reproduce and Share the Licensed Material, in whole or 149 | in part, for NonCommercial purposes only; and 150 | 151 | b. produce and reproduce, but not Share, Adapted Material 152 | for NonCommercial purposes only. 153 | 154 | 2. Exceptions and Limitations. For the avoidance of doubt, where 155 | Exceptions and Limitations apply to Your use, this Public 156 | License does not apply, and You do not need to comply with 157 | its terms and conditions. 158 | 159 | 3. Term. The term of this Public License is specified in Section 160 | 6(a). 161 | 162 | 4. Media and formats; technical modifications allowed. The 163 | Licensor authorizes You to exercise the Licensed Rights in 164 | all media and formats whether now known or hereafter created, 165 | and to make technical modifications necessary to do so. The 166 | Licensor waives and/or agrees not to assert any right or 167 | authority to forbid You from making technical modifications 168 | necessary to exercise the Licensed Rights, including 169 | technical modifications necessary to circumvent Effective 170 | Technological Measures. For purposes of this Public License, 171 | simply making modifications authorized by this Section 2(a) 172 | (4) never produces Adapted Material. 173 | 174 | 5. Downstream recipients. 175 | 176 | a. Offer from the Licensor -- Licensed Material. Every 177 | recipient of the Licensed Material automatically 178 | receives an offer from the Licensor to exercise the 179 | Licensed Rights under the terms and conditions of this 180 | Public License. 181 | 182 | b. No downstream restrictions. You may not offer or impose 183 | any additional or different terms or conditions on, or 184 | apply any Effective Technological Measures to, the 185 | Licensed Material if doing so restricts exercise of the 186 | Licensed Rights by any recipient of the Licensed 187 | Material. 188 | 189 | 6. No endorsement. Nothing in this Public License constitutes or 190 | may be construed as permission to assert or imply that You 191 | are, or that Your use of the Licensed Material is, connected 192 | with, or sponsored, endorsed, or granted official status by, 193 | the Licensor or others designated to receive attribution as 194 | provided in Section 3(a)(1)(A)(i). 195 | 196 | b. Other rights. 197 | 198 | 1. Moral rights, such as the right of integrity, are not 199 | licensed under this Public License, nor are publicity, 200 | privacy, and/or other similar personality rights; however, to 201 | the extent possible, the Licensor waives and/or agrees not to 202 | assert any such rights held by the Licensor to the limited 203 | extent necessary to allow You to exercise the Licensed 204 | Rights, but not otherwise. 205 | 206 | 2. Patent and trademark rights are not licensed under this 207 | Public License. 208 | 209 | 3. To the extent possible, the Licensor waives any right to 210 | collect royalties from You for the exercise of the Licensed 211 | Rights, whether directly or through a collecting society 212 | under any voluntary or waivable statutory or compulsory 213 | licensing scheme. In all other cases the Licensor expressly 214 | reserves any right to collect such royalties, including when 215 | the Licensed Material is used other than for NonCommercial 216 | purposes. 217 | 218 | 219 | Section 3 -- License Conditions. 220 | 221 | Your exercise of the Licensed Rights is expressly made subject to the 222 | following conditions. 223 | 224 | a. Attribution. 225 | 226 | 1. If You Share the Licensed Material, You must: 227 | 228 | a. retain the following if it is supplied by the Licensor 229 | with the Licensed Material: 230 | 231 | i. identification of the creator(s) of the Licensed 232 | Material and any others designated to receive 233 | attribution, in any reasonable manner requested by 234 | the Licensor (including by pseudonym if 235 | designated); 236 | 237 | ii. a copyright notice; 238 | 239 | iii. a notice that refers to this Public License; 240 | 241 | iv. a notice that refers to the disclaimer of 242 | warranties; 243 | 244 | v. a URI or hyperlink to the Licensed Material to the 245 | extent reasonably practicable; 246 | 247 | b. indicate if You modified the Licensed Material and 248 | retain an indication of any previous modifications; and 249 | 250 | c. indicate the Licensed Material is licensed under this 251 | Public License, and include the text of, or the URI or 252 | hyperlink to, this Public License. 253 | 254 | For the avoidance of doubt, You do not have permission under 255 | this Public License to Share Adapted Material. 256 | 257 | 2. You may satisfy the conditions in Section 3(a)(1) in any 258 | reasonable manner based on the medium, means, and context in 259 | which You Share the Licensed Material. For example, it may be 260 | reasonable to satisfy the conditions by providing a URI or 261 | hyperlink to a resource that includes the required 262 | information. 263 | 264 | 3. If requested by the Licensor, You must remove any of the 265 | information required by Section 3(a)(1)(A) to the extent 266 | reasonably practicable. 267 | 268 | 269 | Section 4 -- Sui Generis Database Rights. 270 | 271 | Where the Licensed Rights include Sui Generis Database Rights that 272 | apply to Your use of the Licensed Material: 273 | 274 | a. for the avoidance of doubt, Section 2(a)(1) grants You the right 275 | to extract, reuse, reproduce, and Share all or a substantial 276 | portion of the contents of the database for NonCommercial purposes 277 | only and provided You do not Share Adapted Material; 278 | 279 | b. if You include all or a substantial portion of the database 280 | contents in a database in which You have Sui Generis Database 281 | Rights, then the database in which You have Sui Generis Database 282 | Rights (but not its individual contents) is Adapted Material; and 283 | 284 | c. You must comply with the conditions in Section 3(a) if You Share 285 | all or a substantial portion of the contents of the database. 286 | 287 | For the avoidance of doubt, this Section 4 supplements and does not 288 | replace Your obligations under this Public License where the Licensed 289 | Rights include other Copyright and Similar Rights. 290 | 291 | 292 | Section 5 -- Disclaimer of Warranties and Limitation of Liability. 293 | 294 | a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE 295 | EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS 296 | AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF 297 | ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, 298 | IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, 299 | WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR 300 | PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, 301 | ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT 302 | KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT 303 | ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. 304 | 305 | b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE 306 | TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, 307 | NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, 308 | INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, 309 | COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR 310 | USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN 311 | ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR 312 | DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR 313 | IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. 314 | 315 | c. The disclaimer of warranties and limitation of liability provided 316 | above shall be interpreted in a manner that, to the extent 317 | possible, most closely approximates an absolute disclaimer and 318 | waiver of all liability. 319 | 320 | 321 | Section 6 -- Term and Termination. 322 | 323 | a. This Public License applies for the term of the Copyright and 324 | Similar Rights licensed here. However, if You fail to comply with 325 | this Public License, then Your rights under this Public License 326 | terminate automatically. 327 | 328 | b. Where Your right to use the Licensed Material has terminated under 329 | Section 6(a), it reinstates: 330 | 331 | 1. automatically as of the date the violation is cured, provided 332 | it is cured within 30 days of Your discovery of the 333 | violation; or 334 | 335 | 2. upon express reinstatement by the Licensor. 336 | 337 | For the avoidance of doubt, this Section 6(b) does not affect any 338 | right the Licensor may have to seek remedies for Your violations 339 | of this Public License. 340 | 341 | c. For the avoidance of doubt, the Licensor may also offer the 342 | Licensed Material under separate terms or conditions or stop 343 | distributing the Licensed Material at any time; however, doing so 344 | will not terminate this Public License. 345 | 346 | d. Sections 1, 5, 6, 7, and 8 survive termination of this Public 347 | License. 348 | 349 | 350 | Section 7 -- Other Terms and Conditions. 351 | 352 | a. The Licensor shall not be bound by any additional or different 353 | terms or conditions communicated by You unless expressly agreed. 354 | 355 | b. Any arrangements, understandings, or agreements regarding the 356 | Licensed Material not stated herein are separate from and 357 | independent of the terms and conditions of this Public License. 358 | 359 | 360 | Section 8 -- Interpretation. 361 | 362 | a. For the avoidance of doubt, this Public License does not, and 363 | shall not be interpreted to, reduce, limit, restrict, or impose 364 | conditions on any use of the Licensed Material that could lawfully 365 | be made without permission under this Public License. 366 | 367 | b. To the extent possible, if any provision of this Public License is 368 | deemed unenforceable, it shall be automatically reformed to the 369 | minimum extent necessary to make it enforceable. If the provision 370 | cannot be reformed, it shall be severed from this Public License 371 | without affecting the enforceability of the remaining terms and 372 | conditions. 373 | 374 | c. No term or condition of this Public License will be waived and no 375 | failure to comply consented to unless expressly agreed to by the 376 | Licensor. 377 | 378 | d. Nothing in this Public License constitutes or may be interpreted 379 | as a limitation upon, or waiver of, any privileges and immunities 380 | that apply to the Licensor or You, including from the legal 381 | processes of any jurisdiction or authority. 382 | 383 | ======================================================================= 384 | 385 | Creative Commons is not a party to its public 386 | licenses. Notwithstanding, Creative Commons may elect to apply one of 387 | its public licenses to material it publishes and in those instances 388 | will be considered the “Licensor.” The text of the Creative Commons 389 | public licenses is dedicated to the public domain under the CC0 Public 390 | Domain Dedication. Except for the limited purpose of indicating that 391 | material is shared under a Creative Commons public license or as 392 | otherwise permitted by the Creative Commons policies published at 393 | creativecommons.org/policies, Creative Commons does not authorize the 394 | use of the trademark "Creative Commons" or any other trademark or logo 395 | of Creative Commons without its prior written consent including, 396 | without limitation, in connection with any unauthorized modifications 397 | to any of its public licenses or any other arrangements, 398 | understandings, or agreements concerning use of licensed material. For 399 | the avoidance of doubt, this paragraph does not form part of the 400 | public licenses. 401 | 402 | Creative Commons may be contacted at creativecommons.org. 403 | --------------------------------------------------------------------------------