├── test ├── fixtures │ ├── rick.tile │ ├── tmp │ │ └── rick.tile │ └── rick │ │ ├── img │ │ └── rick.jpg │ │ ├── manifest.json │ │ └── index.html ├── data.js ├── writing.js └── reading.js ├── lib └── rel.js ├── todo.md ├── loader-experiment ├── index.html ├── mothership.js └── tile-loader.js ├── loader ├── public │ ├── index.html │ ├── shuttle.js │ └── worker.js ├── server.js └── loader.js ├── package.json ├── README.md ├── PROBLEMS.md ├── car-reader.js ├── .gitignore ├── writer.js ├── tile-loader.js └── LICENSE /test/fixtures/rick.tile: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/darobin/dasl-tiles/main/test/fixtures/rick.tile -------------------------------------------------------------------------------- /test/fixtures/tmp/rick.tile: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/darobin/dasl-tiles/main/test/fixtures/tmp/rick.tile -------------------------------------------------------------------------------- /test/fixtures/rick/img/rick.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/darobin/dasl-tiles/main/test/fixtures/rick/img/rick.jpg -------------------------------------------------------------------------------- /test/fixtures/rick/manifest.json: -------------------------------------------------------------------------------- 1 | { 2 | "sizing": { 3 | "width": 600, 4 | "height": 450 5 | } 6 | } 7 | -------------------------------------------------------------------------------- /lib/rel.js: -------------------------------------------------------------------------------- 1 | 2 | // call with makeRel(import.meta.url), returns a function that resolves relative paths 3 | export default function makeRel (importURL) { 4 | return (pth) => new URL(pth, importURL).toString().replace(/^file:\/\//, ''); 5 | } 6 | -------------------------------------------------------------------------------- /todo.md: -------------------------------------------------------------------------------- 1 | 2 | # Plan 3 | 4 | ## Loading 5 | - Finish the server, make this safely loadable 6 | - Deploy to webtil.es 7 | - Make loaders for: 8 | - CAR 9 | - WebXDC 10 | - AT 11 | 12 | ## Execution Contexts 13 | - Wishes 14 | - Indexing them 15 | - Calling one another 16 | - WebXDC 17 | - Telepath/AI 18 | - Web3/Dapp/Radicle Launcher 19 | -------------------------------------------------------------------------------- /loader-experiment/index.html: -------------------------------------------------------------------------------- 1 | 2 | 3 |
4 | 5 | 6 |
29 | hi!
`; 84 | } 85 | else if (path === '/style.css') { 86 | headers['content-type'] = 'text/css'; 87 | body = `body { background: ${id}; }\n`; 88 | } 89 | else { 90 | status = 404; 91 | headers['content-type'] = 'text/plain'; 92 | body = `BOOM — not found…\n`; 93 | } 94 | sendToShuttle(id, SND_WORKER_RESPONSE, { requestId, response: { status, headers, body: (new TextEncoder()).encode(body) } }); 95 | } 96 | } 97 | }); 98 | 99 | [ 100 | 'oklch(69.3% 0.151 180)', 101 | 'oklch(79.3% 0.136 270)', 102 | 'oklch(54.3% 0.091 270)', 103 | 'oklch(74.3% 0.143 0.31)', 104 | 'oklch(89.3% 0.121 90.3)', 105 | ].forEach(c => { 106 | const ifr = document.createElement('iframe'); 107 | ifr.setAttribute('width', '300'); 108 | ifr.setAttribute('height', '300'); 109 | ifr.setAttribute('data-colour', c); 110 | // ifr.setAttribute('sandbox', 'allow-scripts'); 111 | document.body.appendChild(ifr); 112 | id2shuttle.set(c, ifr); 113 | ifr.onload = () => sendToShuttle(c, SND_SHUTTLE_LOAD, { id: c }); 114 | ifr.setAttribute('src', 'https://load.webtiles.bast/.well-known/web-tiles/'); 115 | // ifr.setAttribute('src', 'loader.html'); 116 | } 117 | ); 118 | -------------------------------------------------------------------------------- /loader/public/worker.js: -------------------------------------------------------------------------------- 1 | 2 | /* 3 | ████████╗██╗██╗ ███████╗███████╗ 4 | ╚══██╔══╝██║██║ ██╔════╝██╔════╝ 5 | ██║ ██║██║ █████╗ ███████╗ 6 | ██║ ██║██║ ██╔══╝ ╚════██║ 7 | ██║ ██║███████╗███████╗███████║ 8 | ╚═╝ ╚═╝╚══════╝╚══════╝╚══════╝ 9 | •--~~~## SERVICE WORKER ##~~~--• 10 | 11 | This is a very simple Service Worker, almost all complexity that it might have 12 | had has been removed because life is too short to debug badly designed APIs. 13 | 14 | After being instantiated in the context that will load tile content (either the 15 | full tile or its card rendering), the following steps are expected: 16 | 17 | - It waits for a `action: tiles-worker-load` event with an associated unique `id` 18 | that we'll use to communicate up in case we need to be disambiguated. 19 | - It responds with `action: tiles-worker-ready`. 20 | - It can then communicate to the shuttle by messaging it with 21 | `action: tiles-worker-request`, with associated `type` for the request type and 22 | `payload` with whatever needed payload. 23 | - The shuttle responds with `action: tiles-worker-response` that also contains 24 | `payload` (if successful) or `error` (a string, if not). 25 | - Occasionally, an `action: tiles-worker-warn` message is sent, with an attached `msg` array 26 | of strings and worker `id`. This is so the container can warn, for debugging 27 | purposes. 28 | 29 | There is only one request type at this point, the type of which is `resolve-path` 30 | and data for which is the `path` being resolved (which may include a query string). 31 | 32 | It's worth noting that anything starting with `/.well-known/web-tiles/` the SW 33 | will treat as passthrough. This is the path that we load all support content from 34 | (including the index.html that loads us). 35 | */ 36 | 37 | 38 | let id; // keep track of our id so the shuttle knows who we are when we talk 39 | let shuttle; // hold on to the source so we can initiate sending up 40 | const { promise: readyToLoad, resolve: resolveReadyToLoad } = Promise.withResolvers(); 41 | 42 | // All of the below are described as communicating with the mothership, but it's 43 | // mediated by the shuttle. 44 | const PFX = 'tiles-worker-'; 45 | const RCV_LOAD = `${PFX}load`; // mothership tells us to start loading 46 | const SND_READY = `${PFX}ready`; // tell mothership we're loaded and ready 47 | const SND_REQUEST = `${PFX}request`; // request something from mothership 48 | const RCV_RESPONSE = `${PFX}response`; // mothership responds to a request 49 | const SND_WARNING = `${PFX}warn`; // warn mothership 50 | 51 | self.skipWaiting(); 52 | 53 | // --- Communicating with the shuttle 54 | const requestMap = new Map(); 55 | let currentRequest = 0; 56 | async function request (type, payload) { 57 | currentRequest++; 58 | warn(`[SW] current request ${currentRequest}`); 59 | const p = new Promise((resolve, reject) => { 60 | requestMap.set(currentRequest, { resolve, reject }); 61 | }); 62 | warn(`[SW] promise ready`, p); 63 | shuttle.postMessage({ action: SND_REQUEST, id, type, payload: { requestId: currentRequest, ...payload } }); 64 | warn(`[SW] posted to source…`); 65 | return p; 66 | } 67 | self.addEventListener('message', async (ev) => { 68 | warn(`[SW] MESSAGE`, ev.data); 69 | const { action } = ev.data || {}; 70 | if (!action) return; 71 | if (action === RCV_LOAD) { 72 | id = ev.data.id; 73 | resolveReadyToLoad(); 74 | shuttle = ev.source; 75 | ev.source.postMessage({ action: SND_READY, id }); 76 | } 77 | else if (action === RCV_RESPONSE) { 78 | const { payload, error } = ev.data; 79 | const { requestId } = payload; 80 | warn(`[SW] WORKER GOT RESPONSE ${requestId}`); 81 | if (!requestMap.has(requestId)) return console.error(`No response ID for "${requestId}".`); 82 | warn(`[SW] - had response ID`, requestMap.get(requestId)?.resolve?.toString()); 83 | const { resolve, reject } = requestMap.get(requestId); 84 | warn(`[SW] - have functions, will delete`) 85 | requestMap.delete(requestId); 86 | warn(`[SW] - error? ${error}`); 87 | if (error) return reject(error); 88 | warn(`[SW] - resolving`, payload); // XXX I think this nests response 89 | resolve(payload.response); 90 | } 91 | }); 92 | 93 | self.addEventListener('fetch', async (ev) => { 94 | warn('~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~'); 95 | warn(`FETCH of "${ev.request.url}"`); 96 | const url = new URL(ev.request.url); 97 | // IMPORTANT 98 | // We have to let this through since we do need to load the loader. But it means that tiles 99 | // can themselves load anything in loader space. 100 | if (/^\/\.well-known\/web-tiles\//.test(url.pathname)) return; 101 | warn('waiting to be ready to load…'); 102 | await readyToLoad; 103 | warn(`ready — has id? ${id}`); 104 | if (!id) return ev.respondWith(new Response('Not in a loaded state.', response())); 105 | // IMPORTANT: Here we have to be careful not to have a nested await (of a fetch at least). 106 | warn(`respondWith`); 107 | const { promise, resolve, reject } = Promise.withResolvers(); 108 | ev.respondWith(promise); 109 | warn(`making request`); 110 | try { 111 | const r = await request('resolve-path', { path: url.pathname }); // XXX this may be a nested await, delete this comment if it works 112 | warn(`got r `, r); 113 | warn(`res`, response(r.status, r.headers)); 114 | warn(`bod`, bodify(r.body)); 115 | // warn(`• fetch ${res.src.$link} got ${r.status}`) 116 | resolve(new Response(bodify(r.body), response(r.status, r.headers))); 117 | } 118 | catch (err) { 119 | reject(err); // XXX should get the error message out of this 120 | } 121 | }); 122 | 123 | function response (status = 200, headers = { 'content-type': 'text/plain' }) { 124 | return { 125 | status, 126 | headers, 127 | }; 128 | } 129 | 130 | // Tauri seems to turn Uint8Array into an Array, which isn't good. 131 | function bodify (body) { 132 | return Array.isArray(body) ? new Uint8Array(body) : body; 133 | } 134 | 135 | async function warn (...msg) { 136 | console.warn(...msg); 137 | if (!shuttle) return; 138 | shuttle.postMessage({ action: SND_WARNING, msg, id }); 139 | } 140 | -------------------------------------------------------------------------------- /tile-loader.js: -------------------------------------------------------------------------------- 1 | 2 | /* 3 | ████████╗██╗██╗ ███████╗███████╗ 4 | ╚══██╔══╝██║██║ ██╔════╝██╔════╝ 5 | ██║ ██║██║ █████╗ ███████╗ 6 | ██║ ██║██║ ██╔══╝ ╚════██║ 7 | ██║ ██║███████╗███████╗███████║ 8 | ╚═╝ ╚═╝╚══════╝╚══════╝╚══════╝ 9 | •--~~~## MOTHERSHIP ##~~~--• 10 | 11 | The tile-loading architecture has three levels that all communicate together: 12 | 13 | - At the top, the MOTHERSHIP. This has access to things in the real world like 14 | fetching from the internet or reading from the file system. It's the interface 15 | to tile loading, it gets configured in ways that are appropriate for its 16 | context. This is the entry point: you give it a URL and it'll instantiate that 17 | tile. To the extent possible, this should contain all the intelligence and all 18 | the configurability so that the other components can be deployed in entirely 19 | generic ways. 20 | - The mothership instantiates tiles by creating insulated contexts (a sandboxed 21 | iframe, an incognito window…) and loading a SHUTTLE in it. The role of the 22 | shuttle is to set up a service worker and an iframe to load the root of the 23 | tile into. It only exists because you need something to carry a service worker 24 | in. The only other thing that it does is (*drumroll*) shuttle messages back 25 | and forth between the worker and the mothership. 26 | - The WORKER is dispatched on a shuttle to handle resource loading for a tile. 27 | Apart from allow-listing some paths for itself and the shuttle, it passes all 28 | requests up, which the shuttle then hands over to the mothership. 29 | */ 30 | 31 | export class TileLoader { 32 | #loaders = []; 33 | // Adds a loader that will handle matching requests to load a tile. 34 | // - `loader` is an object that knows how to load a tile for a specific scheme 35 | // (and types) 36 | addLoader (loader) { 37 | this.#loaders.push(loader); 38 | } 39 | // Remove using same reference. 40 | removeLoader (loader) { 41 | this.#loaders = this.#loaders.filter(ldr => ldr !== loader); 42 | } 43 | // Load a tile. 44 | async loadTile (url) { 45 | let tile = false; 46 | for (const ldr of this.#loaders) { 47 | tile = await ldr.load(url); 48 | if (tile) break; 49 | } 50 | return tile; 51 | } 52 | } 53 | 54 | export class Tile { 55 | #url; 56 | #manifest; 57 | #pathLoader; 58 | constructor (url, manifest, pathLoader) { 59 | this.#url = url; 60 | this.#manifest = manifest; 61 | this.#pathLoader = pathLoader; 62 | } 63 | get url () { 64 | return this.#url; 65 | } 66 | get manifest () { 67 | return this.#manifest; 68 | } 69 | async resolvePath (path) { 70 | return this.#pathLoader.resolvePath(path); 71 | } 72 | } 73 | 74 | // ############################################ 75 | // ########################################## 76 | // #### NEXT STEPS ######################## 77 | // ########################################## 78 | // ############################################ 79 | // 80 | // - have the mothership change to being an experiment loading actual tiles 81 | // - support renderCard (pluggable too) 82 | // - implement the loaders one by one 83 | // - try each, stick to browser environments for now (we can add e.g. Tauri later) 84 | // - when it works, refactor 85 | // - publish to npm with the right metadata 86 | // - make a website with demo 87 | // - DASL spec 88 | // - WAG meeting 89 | 90 | 91 | 92 | // ----- specific loaders (refactor later) 93 | export class ATTileLoader { 94 | async load (url) { 95 | const u = new URL(url); 96 | if (u.protocol !== 'at:') return false; 97 | // XXX 98 | // - also check that the collection is correct 99 | // - load the record 100 | // - fail if it's not a valid tile record 101 | // - create a Tile with the right manifest, the url, and a way to load a path 102 | } 103 | } 104 | 105 | export class ATPathLoader { 106 | #did; 107 | #manifest; 108 | constructor (did, manifest) { 109 | this.#did = did; 110 | this.#manifest = manifest; 111 | } 112 | async resolvePath (path) { 113 | // XXX 114 | // - use the manifest to find the CID (make sure to ignore search & hash) 115 | // - use the DID to know where to load it from 116 | // - call for the blob 117 | // - make the right response with the media type and all 118 | } 119 | } 120 | 121 | // Here the idea is that you can load from multiple schemes, but you might not 122 | // want to. 123 | export class ContentSchemeTileLoader { 124 | #schemes; 125 | constructor (schemes = ['http', 'file']) { 126 | this.#schemes = new Set(schemes); 127 | } 128 | async load (url) { 129 | const u = new URL(url); 130 | if (u.protocol === 'https:' || u.protocol === 'http:') { 131 | if (!this.#schemes.has('http')) return false; 132 | // XXX 133 | // - get the data 134 | // - if it's not a zip file, return false 135 | // - give it to processContent 136 | } 137 | if (u.protocol === 'file:') { 138 | if (!this.#schemes.has('file')) return false; 139 | // XXX 140 | // - get the data 141 | // - if it's not a zip file, return false 142 | // - give it to processContent 143 | } 144 | } 145 | // async processZip (zipData) { 146 | // // XXX 147 | // // - generate a synthetic manifest 148 | // // - make a path loader that will point to the right part 149 | // } 150 | } 151 | 152 | export class WebXDCTileLoader extends ContentSchemeTileLoader { 153 | constructor (schemes) { 154 | super(schemes); 155 | } 156 | async processContent (zipData, scheme) { 157 | // XXX 158 | // - generate a synthetic manifest 159 | // - make a path loader that will point to the right part 160 | // - scheme doesn't matter because we always do this in memory 161 | } 162 | } 163 | 164 | export class CARTileLoader extends ContentSchemeTileLoader { 165 | constructor (schemes) { 166 | super(schemes); 167 | } 168 | async processContent (car, scheme) { 169 | // XXX 170 | // - for http we assume that we have the file in memory (we could do range 171 | // requests but let's not right now) 172 | // - for file, we scan and save offsets 173 | // - extract the manifest 174 | // - make a path loader that will point to the right part depending on scheme 175 | } 176 | } 177 | -------------------------------------------------------------------------------- /loader-experiment/tile-loader.js: -------------------------------------------------------------------------------- 1 | 2 | /* 3 | ████████╗██╗██╗ ███████╗███████╗ 4 | ╚══██╔══╝██║██║ ██╔════╝██╔════╝ 5 | ██║ ██║██║ █████╗ ███████╗ 6 | ██║ ██║██║ ██╔══╝ ╚════██║ 7 | ██║ ██║███████╗███████╗███████║ 8 | ╚═╝ ╚═╝╚══════╝╚══════╝╚══════╝ 9 | •--~~~## MOTHERSHIP ##~~~--• 10 | 11 | The tile-loading architecture has three levels that all communicate together: 12 | 13 | - At the top, the MOTHERSHIP. This has access to things in the real world like 14 | fetching from the internet or reading from the file system. It's the interface 15 | to tile loading, it gets configured in ways that are appropriate for its 16 | context. This is the entry point: you give it a URL and it'll instantiate that 17 | tile. To the extent possible, this should contain all the intelligence and all 18 | the configurability so that the other components can be deployed in entirely 19 | generic ways. 20 | - The mothership instantiates tiles by creating insulated contexts (a sandboxed 21 | iframe, an incognito window…) and loading a SHUTTLE in it. The role of the 22 | shuttle is to set up a service worker and an iframe to load the root of the 23 | tile into. It only exists because you need something to carry a service worker 24 | in. The only other thing that it does is (*drumroll*) shuttle messages back 25 | and forth between the worker and the mothership. 26 | - The WORKER is dispatched on a shuttle to handle resource loading for a tile. 27 | Apart from allow-listing some paths for itself and the shuttle, it passes all 28 | requests up, which the shuttle then hands over to the mothership. 29 | */ 30 | 31 | export class TileLoader { 32 | #loaders = []; 33 | // Adds a loader that will handle matching requests to load a tile. 34 | // - `loader` is an object that knows how to load a tile for a specific scheme 35 | // (and types) 36 | addLoader (loader) { 37 | this.#loaders.push(loader); 38 | } 39 | // Remove using same reference. 40 | removeLoader (loader) { 41 | this.#loaders = this.#loaders.filter(ldr => ldr !== loader); 42 | } 43 | // Load a tile. 44 | async loadTile (url) { 45 | let tile = false; 46 | for (const ldr of this.#loaders) { 47 | tile = await ldr.load(url); 48 | if (tile) break; 49 | } 50 | return tile; 51 | } 52 | } 53 | 54 | export class Tile { 55 | #url; 56 | #manifest; 57 | #pathLoader; 58 | constructor (url, manifest, pathLoader) { 59 | this.#url = url; 60 | this.#manifest = manifest; 61 | this.#pathLoader = pathLoader; 62 | } 63 | get url () { 64 | return this.#url; 65 | } 66 | get manifest () { 67 | return this.#manifest; 68 | } 69 | async resolvePath (path) { 70 | return this.#pathLoader.resolvePath(path); 71 | } 72 | } 73 | 74 | // ############################################ 75 | // ########################################## 76 | // #### NEXT STEPS ######################## 77 | // ########################################## 78 | // ############################################ 79 | // 80 | // - have the mothership change to being an experiment loading actual tiles 81 | // - support renderCard (pluggable too) 82 | // - implement the loaders one by one 83 | // - try each, stick to browser environments for now (we can add e.g. Tauri later) 84 | // - when it works, refactor 85 | // - publish to npm with the right metadata 86 | // - make a website with demo 87 | // - DASL spec 88 | // - WAG meeting 89 | 90 | 91 | 92 | // ----- specific loaders (refactor later) 93 | export class ATTileLoader { 94 | async load (url) { 95 | const u = new URL(url); 96 | if (u.protocol !== 'at:') return false; 97 | // XXX 98 | // - also check that the collection is correct 99 | // - load the record 100 | // - fail if it's not a valid tile record 101 | // - create a Tile with the right manifest, the url, and a way to load a path 102 | } 103 | } 104 | 105 | export class ATPathLoader { 106 | #did; 107 | #manifest; 108 | constructor (did, manifest) { 109 | this.#did = did; 110 | this.#manifest = manifest; 111 | } 112 | async resolvePath (path) { 113 | // XXX 114 | // - use the manifest to find the CID (make sure to ignore search & hash) 115 | // - use the DID to know where to load it from 116 | // - call for the blob 117 | // - make the right response with the media type and all 118 | } 119 | } 120 | 121 | // Here the idea is that you can load from multiple schemes, but you might not 122 | // want to. 123 | export class ContentSchemeTileLoader { 124 | #schemes; 125 | constructor (schemes = ['http', 'file']) { 126 | this.#schemes = new Set(schemes); 127 | } 128 | async load (url) { 129 | const u = new URL(url); 130 | if (u.protocol === 'https:' || u.protocol === 'http:') { 131 | if (!this.#schemes.has('http')) return false; 132 | // XXX 133 | // - get the data 134 | // - if it's not a zip file, return false 135 | // - give it to processContent 136 | } 137 | if (u.protocol === 'file:') { 138 | if (!this.#schemes.has('file')) return false; 139 | // XXX 140 | // - get the data 141 | // - if it's not a zip file, return false 142 | // - give it to processContent 143 | } 144 | } 145 | // async processZip (zipData) { 146 | // // XXX 147 | // // - generate a synthetic manifest 148 | // // - make a path loader that will point to the right part 149 | // } 150 | } 151 | 152 | export class WebXDCTileLoader extends ContentSchemeTileLoader { 153 | constructor (schemes) { 154 | super(schemes); 155 | } 156 | async processContent (zipData, scheme) { 157 | // XXX 158 | // - generate a synthetic manifest 159 | // - make a path loader that will point to the right part 160 | // - scheme doesn't matter because we always do this in memory 161 | } 162 | } 163 | 164 | export class CARTileLoader extends ContentSchemeTileLoader { 165 | constructor (schemes) { 166 | super(schemes); 167 | } 168 | async processContent (car, scheme) { 169 | // XXX 170 | // - for http we assume that we have the file in memory (we could do range 171 | // requests but let's not right now) 172 | // - for file, we scan and save offsets 173 | // - extract the manifest 174 | // - make a path loader that will point to the right part depending on scheme 175 | } 176 | } 177 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "[]" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright [yyyy] [name of copyright owner] 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | --------------------------------------------------------------------------------