PageSourceSearch

https://opensciencesociety.github.io/

html opensciencesociety.github.io collected 2026-10-03 09:43:13 UTC 1,766 bytes, 47 lines download raw bytes

1<!DOCTYPE html>
2<html>
3
4<head>
5
6<meta charset='utf-8' />
7
8<link rel="stylesheet" type="text/css" media="screen" href="style.css" />
9
10<title>Open Science for an Open Society</title>
11
12</head>
13
14<body>
15
16<div id="header_wrap" class="outer">
17<header class="inner">
18<h1 id="title" class="header_text">Open Science for an Open Society</h1>
19</header>
20</div>
21
22<div id="main_content_wrap" class="outer">
23<section id="main_content" class="inner">
24
25<p>The recent years have witnessed an increasing interest by researchers to explain and build models of bottom-up open collaboration (e.g., open source software development, Wikipedia), using theories and tools borrowed from complex systems science, such as self-organization, critical cascades, and complex networks. As research in nature and society gets increasingly driven by data and computation, the “data science way” has emerged as a powerful leverage to, on the one hand, help researchers keep better account of their collaborative work in a transparent way and, on the other hand, to reach out and engage with a larger community of researchers and science enthusiasts, ready to help, driven by intrinsic motivation and fun. Furthermore, the “data science way”, is also deeply associated with the emergence of collective intelligence through social interactions and physical meetings where people do stuff together (e.g., hackathons). Unfortunately, the structure and the dynamics of these punctual meetings have not yet been completely understood.</p>
26
27<h3 id="workshop">Workshop</h3>
28
29<ul>
30  <li><a href="ccs16/">Workshop at the 2016 Conference on Complex Systems (CCS)</a></li>
31</ul>
32
33
34
35</section>
36</div>
37
38
39<div id="footer_wrap" class="outer">
40<footer class="inner">
41<p></p>
42</footer>
43</div>
44
45</body>
46
47</html>

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.