com/us/developer/documentation/api/content/v2.0/csv_file_name_extension_full_specification.html 16 No: # See details at # https://www.example.com/us/developer/documentation/api/content/\ # v2.0/csv_file_name_extension_full_specification strings below. Modules Every file should contain license boilerplate. Choose the appropriate boilerplate for the license used by the project (for example, Apache 2.0, BSD, LGPL, GPL) Functions and Methods

Reusable  Metadata and data described with plurality of accurate and relevant attributes  Clear license, associated with provenance, meets community standards Reproducibility and RDM [https://www.go-fair University of Technology, WS 2021/22 RDM in Practice @DAMSLab  Code and Artifacts  Apache SystemDS: https://github.com/apache/systemds (OSS)  Complete code history, src/bin releases (SystemDS 2.2.0 in Oct

reluctant to use clever or unusual constructs: the absence of a prohibition is not the same as a license to proceed. Use your judgment, and if you are unsure, please don’t hesitate to ask your project leads consistent with how you comment and what style you use where. File Comments Start each file with license boilerplate. File comments describe the contents of a file. If a file declares, implements, or tests Notice and Author Line Every file should contain license boilerplate. Choose the appropriate boilerplate for the license used by the project (for example, Apache 2.0, BSD, LGPL, GPL). If you make significant

IBM Research – Almaden, USA  Declarative large-scale machine learning  Optimizer and runtime of Apache SystemML  2011 PhD TU Dresden, Germany  Cost-based optimization of integration flows  Systems  In-memory indexing and query processing Data Management Group DB group https://github.com/ apache/systemds 6 706.015 Introduction to Scientific Writing – 01 Introduction and Overview Matthias Boehm system internals DB system internals + prog. project Prog. projects in SystemDS [github.com/apache/systemds] Data Management Group Intro to Scientific Writing (WS) 7 706.015 Introduction to

1. License or copyright information, if present 2. Package statement 3. Import statements 4. Exactly one top-level class Exactly one blank line separates each section that is present. 3.1 License or or copyright information, if present If license or copyright information belongs in a file, it belongs here. 3.2 Package statement The package statement is not line-wrapped. The column limit (Section