├── LICENSE ├── CDLA-Permissive-2.0.md ├── SECURITY.md └── README.md /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) Microsoft Corporation. 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE 22 | -------------------------------------------------------------------------------- /CDLA-Permissive-2.0.md: -------------------------------------------------------------------------------- 1 | # Community Data License Agreement - Permissive - Version 2.0 2 | 3 | This is the Community Data License Agreement - Permissive, Version 2.0 (the "agreement"). Data Provider(s) and Data Recipient(s) agree as follows: 4 | 5 | ## 1. Provision of the Data 6 | 7 | 1.1. A Data Recipient may use, modify, and share the Data made available by Data Provider(s) under this agreement if that Data Recipient follows the terms of this agreement. 8 | 9 | 1.2. This agreement does not impose any restriction on a Data Recipient's use, modification, or sharing of any portions of the Data that are in the public domain or that may be used, modified, or shared under any other legal exception or limitation. 10 | 11 | ## 2. Conditions for Sharing Data 12 | 13 | 2.1. A Data Recipient may share Data, with or without modifications, so long as the Data Recipient makes available the text of this agreement with the shared Data. 14 | 15 | ## 3. No Restrictions on Results 16 | 17 | 3.1. This agreement does not impose any restriction or obligations with respect to the use, modification, or sharing of Results. 18 | 19 | ## 4. No Warranty; Limitation of Liability 20 | 21 | 4.1. All Data Recipients receive the Data subject to the following terms: 22 | 23 | THE DATA IS PROVIDED ON AN "AS IS" BASIS, WITHOUT REPRESENTATIONS, WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 24 | 25 | NO DATA PROVIDER SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE DATA OR RESULTS, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 26 | 27 | ## 5. Definitions 28 | 29 | 5.1. "Data" means the material received by a Data Recipient under this agreement. 30 | 31 | 5.2. "Data Provider" means any person who is the source of Data provided under this agreement and in reliance on a Data Recipient's agreement to its terms. 32 | 33 | 5.3. "Data Recipient" means any person who receives Data directly or indirectly from a Data Provider and agrees to the terms of this agreement. 34 | 35 | 5.4. "Results" means any outcome obtained by computational analysis of Data, including for example machine learning models and models' insights. 36 | -------------------------------------------------------------------------------- /SECURITY.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | ## Security 4 | 5 | Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/Microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/). 6 | 7 | If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://aka.ms/opensource/security/definition), please report it to us as described below. 8 | 9 | ## Reporting Security Issues 10 | 11 | **Please do not report security vulnerabilities through public GitHub issues.** 12 | 13 | Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://aka.ms/opensource/security/create-report). 14 | 15 | If you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com). If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://aka.ms/opensource/security/pgpkey). 16 | 17 | You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://aka.ms/opensource/security/msrc). 18 | 19 | Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue: 20 | 21 | * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.) 22 | * Full paths of source file(s) related to the manifestation of the issue 23 | * The location of the affected source code (tag/branch/commit or direct URL) 24 | * Any special configuration required to reproduce the issue 25 | * Step-by-step instructions to reproduce the issue 26 | * Proof-of-concept or exploit code (if possible) 27 | * Impact of the issue, including how an attacker might exploit the issue 28 | 29 | This information will help us triage your report more quickly. 30 | 31 | If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our [Microsoft Bug Bounty Program](https://aka.ms/opensource/security/bounty) page for more details about our active programs. 32 | 33 | ## Preferred Languages 34 | 35 | We prefer all communications to be in English. 36 | 37 | ## Policy 38 | 39 | Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://aka.ms/opensource/security/cvd). 40 | 41 | 42 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # MS-LaTTE Dataset 2 | 3 | The Microsoft Locations and Times of Task Execution (**MS-LaTTE**) dataset is a collection of 10,101 to-do tasks, each of which is annotated for the likely locations and times of day at which it is completed. It is stored in the file **`MS-LaTTE.json`**. 4 | 5 | Each to-do task has been annotated by 3 annotators for location and 5 annotators for time to represent the propensities of different people, and resulting diversity, in when and where tasks are most often completed. 6 | 7 | In the dataset, each entry is a json dictionary with the following keys: 8 | 9 | 1. **ID**: an identifier for instances in the data. 10 | 11 | 2. **TaskTitle**: the name of the to-do task. 12 | 13 | 3. **ListTitle**: the name of the list in which the to-do task often appears. 14 | 15 | 4. **LocJudgements**: a list of 3 or 4 judgements for the likely locations at which this to-do task is completed. 4 judgements are supplied in cases when there is a 3-way disagreement between the first 3 judgements. Further, each judgement contains the following properties: 16 | 17 | - **Known**: a boolean value, indicating whether this to-do task is known to the annotator. The location labels specified below are given if and only if the value is Yes. 18 | - **Locations (optional)**: one or more broad location categories. They can be Home, Work or Public. 19 | - **PublicLocations (optional)**: one or more fine-grained public location categories, specified when Public is noted as one of the broad **Locations** categories. This list is populated from amongst 69 public location labels. 20 | 21 | 5. **TimeJudgements**: a list of 5 judgements for the likely times of day at which this to-do task is completed. Each judgement contains the following properties: 22 | 23 | - **Known**: a boolean value, indicating whether this to-do task is known to the annotator. The time labels are given if and only if this value is Yes. 24 | - **Times (optional)**: one or more times of day. These time labels are combinations of weekday (WD) or weekend (WE), and morning, afternoon, evening, night and anytime, yielding a total of 10 possible time labels. 25 | 26 | ### Note 27 | 28 | As described in our [paper](https://arxiv.org/abs/2111.06902), a pipeline to preserve user privacy was run on the source data to anonymize it. This included a replacement of names and numbers with random alternatives. As a result, there are some task descriptions in the data that may appear strange, such as "0 cucumbers" or "0 nails". 29 | 30 | ## Citation 31 | 32 | If you use the MS-LaTTE dataset in your work, please cite the following: 33 | 34 | ``` 35 | @article{jauhar2021mslatte, 36 | title={MS-LaTTE: A Dataset of Where and When To-do Tasks are Completed}, 37 | author={Jauhar, Sujay Kumar and Chandrasekaran, Nirupama and Gamon, Michael and White, Ryen W.}, 38 | journal={arXiv preprint 2111.06902}, 39 | year={2021} 40 | } 41 | ``` 42 | 43 | ## Contributing 44 | 45 | This project welcomes contributions and suggestions. Most contributions require you to agree to a 46 | Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us 47 | the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com. 48 | 49 | When you submit a pull request, a CLA bot will automatically determine whether you need to provide 50 | a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions 51 | provided by the bot. You will only need to do this once across all repos using our CLA. 52 | 53 | This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). 54 | For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or 55 | contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments. 56 | 57 | ## Trademarks 58 | 59 | This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft 60 | trademarks or logos is subject to and must follow 61 | [Microsoft's Trademark & Brand Guidelines](https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks/usage/general). 62 | Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. 63 | Any use of third-party trademarks or logos are subject to those third-party's policies. 64 | --------------------------------------------------------------------------------