Publications¶
This chapter is based on the notes 2022-05-10_SPSE_Publication.pdf
Open Access and Open Science¶
People always have been asking for access to knowledge
But access is limited through society and technology.
Examples for knowledge transfer:
450 BCE: Laws of the Twelve Tables. Written and publicly accessible law
Science: Lectures
Bible: Translation 1522 (to understand), Printing 1452 (to spread)
Technology: Patents and Documentation
Aspects that regulate access:
Availability (libraries, internet)
Authorship (“Urheberrecht”)
Copyright (“Verwertungsrecht”)
Personality rights
Patents
Licenses determine the given rights for published works.
Software:¶
Closed Source
secret
proprietary
freeware/shareware
Restricted Open Source
Open Source
BSD, MIT, Apache 2.0
GPL
Careful: open != free
Papers:¶
Access Restricted (“pay wall”): subscription or payment necessary
Green Open Access: Authors are allowed to publish their work on their own homepage (non-commercial)
Gold Open Access:
Everybody can access the work
Different copyright and licensing models:
Copyright with author or publisher
Publisher may hold exclusive rights/license
Publisher may hold non-exclusive license; author can share other licenses on their own
Examples for non-exclusive licenses:
Why should you want to transfer copyright to a publisher?
Publisher demands it; no other option or expensive.
Publishers protect the rights of the paper.
Publishing Fees¶
Publishing is expensive. So why publish with a publisher, and not yourself?
Peer-reviewing often organized by publisher or conference
Reputation
Copy-Editing, rights management, hosting, metadata management, indexing
Accessibility is guaranteed, easy to find, long-term available
Added to libraries
Print versions
Influence on academic ranking/impact factors
May be required by funding agency
And who pays publishing fees?
Depends on license (publisher, author, or community)
Community: Conference participants, tax payers (in Germany: “Project DEAL”)
Attention: There are predatory publishers!
Paper Repositories¶
Non-authorative versions:
Authorative-versions (also called ‘version of record’):
at publisher repositories: Springer Publishing, ACM, IEEE, Elsevier, Wiley, etc.
(These organize conference proceedings and journals)Popularity and use of individual repositories depends on concrete science.
Bibliographic Data¶
Homepage: Low confidence. May be incomplete or inconsistent
-> Not suited for citationDBLP: Highest confidence. Human-maintained and reliable.
Google Scholar: Complete, but automatically generated and may be inaccurate (e.g., uses ‘et al.’).
But: Nice notifications about new papers that cite own workORCID: Automatically generated, grows in use. Nice notifications about new own papers, connected via digital object identifiers (DOIs).
CrossRef (papers) and DataCite (data): DOI agencies, manage metadata
Ideal Requirements for Publishing¶
Hard requirements:
long-term available (archived)
immutable (is always the same version referenced?)
identifiable (is the correct version referenced?)
DOI is industry standard for this.
Weak requirement: Open Access
Unique Identification¶
DOI: Digital Object Identifier, mostly for papers
Resolver: DOI -> URL (e.g., doi.org)
points to landing page of publication
linked to metadata
DOI pointers to landing-page URLs are maintained
ORCID for scientists
Archival Resource Keys (ARK) for all kinds of objects
Publications: Details¶
This chapter is based on the notes 2022-05-17_SPSE_Publication-Part2.pdf
Open Access and Open Science¶
People always have been asking for access to knowledge
But access is limited through society and technology.
Examples for knowledge transfer:
Paper Preprint¶
paper version accepted at conference
not the officially published version
part of green open access
Contributing to Software:¶
Contributor-License-Agreement (CLA)
maintainers free to use, share and modify
legally sound
no CLA
simple process, no entry barrier
no confirmation by contributor’s employer necessary
Developer Certificate of Origin (DCO)
contributor asserts that she is allowed to commit the code
clarifies license of the committed code patch
Making copyright and licenses explicit¶
Very important!
SPDX is common format to share important data
clarifies how software (patches) are licensed
easy to maintain
automated checks with REUSE
Example for Java: CPAchecker Source Code
Artifacts¶
Reproduction packages.
Examples:
Data sets, statistics
software
machine-readable proofs
appendices
(Don’t forget to license!)
Three dimensions:
Repeat
Reproduce
Replicate
ACM badges qualify papers with regards to their reproduction packages:
Artifact available
Artifact evaluated (a) functional and/or (b) reusable
Results reproduced
Results replicated
Repositories:
Discussions¶
Is replication always good? Example: Google
Negative reproduction study example: https://dl.acm.org/doi/pdf/10.1145/3340571
Publication Process¶
This chapter is based on the notes 2022-05-24_SPSE_Rankings.pdf