Draft for Public Comment

Principles and Design Assumptions



2 Distribution of control: Distribution of the control of scholarly resources (pre-prints, post-prints, research data, supporting software, etc.) and scholarly infrastructures is an important principle which underpins this work. Without this, a small number of actors can gain too much control and can establish a quasi-monopolistic position – as has happened in the scholarly publishing industry. Note that this does not require the distribution of systems, although whatever solution we develop must certainly be able to thrive in and support such an architecture. Leave a comment on line 2 1

3 Inclusiveness: It is acknowledged that different institutions and regions have unique and particular needs (e.g diverse language, policies and priorities) and this will be reflected in the network. Leave a comment on line 3 0

4 Public good: The technologies, architectures and protocols adopted in the context of the global network for repositories will be available to everyone, wherever possible using global standards. Leave a comment on line 4 0

5 Intelligent openness: Scholarly resources, wherever possible, will be made openly available in order increase their value and maximize their benefit for scholarship and society. Leave a comment on line 5 0

6   Leave a comment on line 6 0

Design Assumptions

7 Focus on the resources themselves, not just associated metadata: For historical reasons, technical solutions have focused on metadata that describes scholarly resources instead of on the resources themselves. By considering both the scholarly resource and its metadata as web resources identified by distinct URIs, they can be treated on equal footing and can be appropriately interlinked. Leave a comment on line 7 0

8 Pragmatism: Given the choice, we tend to favour the simpler approach. Where possible, we choose technologies, solutions and paradigms which are already widely deployed. In practical terms, this means that we favour using standard Web technologies wherever possible. Leave a comment on line 8 0

9 Evolution, not revolution: We prefer to evolve solutions, adjusting existing software and systems where possible, to better exploit the ubiquitous Web environment within which they are situated. Leave a comment on line 9 0

10 Convention over configuration: Our preference is to adopt widely recognised conventions and encouraging everyone to use these where possible, rather than accommodating richer, more complex and varied approaches. As a corollary to this, we favour standardising only that which needs standardising and keeping constraints to a minimum, so that those implementing our systems can readily understand the constraints under which they must operate. Leave a comment on line 10 1

11 Engage with users where they are: Instead of always asking users to leave their environment and engage with one of our systems, integrate tools into the environments and systems where they are already engaged. Leave a comment on line 11 0

Page 5

Source: http://comment.coar-repositories.org/5-principles/