Wikipedia is an online encyclopedia that can be edited by anyone. It uses the wiki software MediaWiki and is governed by policies of neutral point of view, verifiability, and not including original research. The Wikimedia Foundation oversees Wikipedia and other wiki projects to support sharing knowledge freely.
- The document discusses different data types in R including vectors, matrices, arrays, lists, and data frames.
- It provides examples of how to create, subset, and coerce between each data type.
- The document is a set of lecture slides that introduces basic R data structures and manipulation functions.
This document discusses data models and databases. It begins by explaining the components of a data model: structures, constraints, and operations. It then defines what a database is as a collection of organized information for efficient retrieval. The document goes on to discuss relational databases and their advantages like sharing data, enforcing data models, scaling to large datasets, and flexibility. It covers concepts like declarative query languages, views, indexes, and using databases for analytics like matrix operations and experiment design.
The document discusses functional programming concepts like recursion, higher-order functions, and combinators. It provides examples of using recursion to solve problems like calculating factorials and sorting arrays. It also discusses how concepts like tail-call elimination and garbage collection make recursion practical for modern languages. Resources for further studying functional programming patterns and concepts are provided.
This document discusses the evolution of the web from a network of documents to a network of linked data. It begins by describing the original web of documents, which organized information in silos and had implicit semantics. The document then introduces the concept of the semantic web and linked data, which structures information as interconnected data using explicit semantics. It provides examples of how linked data can be represented using RDF triples and describes the principles of linked data for publishing and connecting data on the web. Finally, it discusses characteristics and examples of linked data applications.
Sir Tim Berners-Lee, who invented the World Wide Web, gave a lecture examining its origins and future development. He discussed how the number of web pages now exceeds the world's population and continues growing exponentially each year. Web science is championed by Berners-Lee as a new field to better understand this growth and improve the user experience. He also emphasized that the web's success is largely due to collaboration and creativity between its users.
This document provides an overview of wiki technologies and their history. It discusses how wikis originated in the 1990s and were popularized by Wikipedia in the early 2000s. Key features of wikis are outlined, such as their open source nature, ease of editing, and support for collaboration. Wikipedia's enormous growth and collaborative model are also summarized. The document concludes with an introduction to using the MediaWiki software that powers Wikipedia.
2010 07 modeling web evolution amarantidis antoniou vafopoulos finalvafopoulos
油
This paper analyzes and simulates the KKPS model of web evolution to address open issues. Simulations show that as the number of endorsed documents (b) or topics (k) increases, the power law distribution of document in-degrees becomes less significant. They also found that increasing the number of endorsements (b) can decrease the efficiency of the search algorithm, contrary to expectations. The paper aims to clarify these issues and highlight future directions for more realistic web modeling.
This document discusses the evolution of the web from a web of documents to a web of linked data. It outlines the principles of linked data, which involve using URIs to identify things and linking those URIs to other URIs so that machines can discover more data. RDF is introduced as a standard data model for publishing linked data on the web using triples. Examples of linked data applications and datasets are provided to illustrate how linked data allows the web to function as a global database.
The document discusses the Publicspending.gr (PSGR) program in Greece, which aims to provide transparency in public expenditure through network analysis and visualization of spending data. The key points are:
1) PSGR manifests the value of open data and ex-ante reporting of government decisions, shifting the paradigm for 40,000 public servants.
2) Since launching in 2011, PSGR has progressed from believing open data is valuable to realizing it requires refining like chiseling jewelry from rocks in a goldmine.
3) Network analysis is a basic tool used by PSGR to analyze and visualize linked spending data, enabling the study of relationships between important payees and payers and economic impacts
2010 06-08 chania stochastic web modelling - copyvafopoulos
油
The document summarizes research on modeling the evolution of the World Wide Web as a complex system. It discusses the Web's structure as a directed graph and statistical properties like power law degree distributions and small world properties. It describes models of Web traffic and evolution that use concepts from statistical physics and complex networks. Game theoretic and query-based models are also summarized. The document focuses on a query-Web model that explains the Web's scale-free structure through the interaction of users, documents, and search engines.
This document discusses issues of trust as it relates to technology and society. It covers how trust underlies civilizations and how various technological developments from writing to the internet have both increased and challenged trust over time. It examines specific issues like network security threats, software safety, and privacy of personal data. The document argues that trustworthy systems and practices are important for democratic societies and that European policies need to nurture democratic values in the digital age. It outlines the EU's legal framework around data protection and privacy technology. Finally, it discusses the goals and activities of the RISEPTIS advisory board, which aims to provide guidance on security, privacy, and trustworthiness research and policy challenges.
This document discusses trustworthiness in the information society. It provides an overview of key concepts related to privacy, anonymity, accountability and the legal framework for data protection in Europe. It also discusses stakeholder perspectives from governments, business and citizens. Additionally, it considers research and technology development as well as infrastructure and governance issues. The document aims to start a discussion on how to develop an information society that respects democratic values and citizen privacy while still enabling innovation.
Dynamic languages, for software craftmanship groupReuven Lerner
油
Reuven Lerner's talk about dynamic programming languages in general, and about Ruby in particular. Why would you want to use a dynamic language? What can you do with one that isn't possible (or easy) with a static language?
Domain Driven Design with the F# type System -- F#unctional Londoners 2014Scott Wlaschin
油
(Video of these slides here http://fsharpforfunandprofit.com/ddd)
Statically typed functional programming languages like F# encourage a very different way of thinking about types. The type system is your friend, not an annoyance, and can be used in many ways that might not be familiar to OO programmers.
Types can be used to represent the domain in a fine-grained, self documenting way. And in many cases, types can even be used to encode business rules so that you literally cannot create incorrect code. You can then use the static type checking almost as an instant unit test making sure that your code is correct at compile time.
In this talk, we'll look at some of the ways you can use types as part of a domain driven design process, with some simple real world examples in F#. No jargon, no maths, and no prior F# experience necessary.
Code, links to video, etc., at http://fsharpforfunandprofit.com/ddd
NEW AND IMPROVED - added sections on:
* why OO, not FP is scary
* designing with states and transitions
This document provides examples comparing Java and Kotlin code for common programming tasks. It shows how Kotlin simplifies collections, extension functions, data classes, and defining steps in Allure reports compared to Java. For collections, Kotlin provides concise syntax like val classpath = listOf() instead of creating and adding to lists. Extension functions allow adding methods to existing classes like HtmlElement.waitForIt(). Data classes remove boilerplate from simple classes. And Kotlin step blocks cleanly define steps in Allure reports.
What/How to do with GraphQL? - Valentyn Ostakh (ENG) | Ruby Meditation 27Ruby Meditation
油
Speech of Valentyn Ostakh, Ruby Developer at Ruby Garage, at Ruby Meditation 27, Dnipro, 19.05.2019
際際滷share -
Next conference - http://www.rubymeditation.com/
This talk explores basic concepts of GraphQL.
The main goal is to show how GraphQL works and of what parts it consists of.
From the Ruby side we will look at how to create a GraphQL schema.
In addition, we will consider what pitfalls can be encountered at the start of work with GraphQL.
Announcements and conference materials https://www.fb.me/RubyMeditation
News https://twitter.com/RubyMeditation
Photos https://www.instagram.com/RubyMeditation
The stream of Ruby conferences (not just ours) https://t.me/RubyMeditation
Algorithm and Programming (Introduction of dev pascal, data type, value, and ...Adam Mukharil Bachtiar
油
This file contains explanation about introduction of dev pascal, data type, value, and identifier. This file was used in my Algorithm and Programming Class.
This document provides an overview of schema design and data modeling for both relational and non-relational databases. It discusses the history of data modeling including hierarchical and relational models. The goals of data modeling are to avoid anomalies, minimize redesign, and make the model informative for users. Common data modeling patterns like one-to-many, many-to-many, and tree structures are explained. Specific examples are given for modeling comments, products, and categories in a non-relational database.
Webinar: Strongly Typed Languages and Flexible SchemasMongoDB
油
This document discusses strategies for managing flexible schemas in strongly typed languages and databases, including decoupled architectures, object-document mappers (ODMs), versioning, and data migrations. It describes how decoupled architectures allow business logic and data storage to evolve independently. ODMs like Spring Data and Morphia reduce impedance mismatch and handle mapping between objects and database documents. Versioning strategies include incrementing fields, storing full documents, or maintaining separate collections for current and past versions. Migrations involve adding/removing fields, changing names/data types, or extracting embedded documents. The document outlines tradeoffs between these approaches.
ESWC SS 2012 - Tuesday Tutorial Dan Brickley and Denny Vrandecic: Linked Open...eswcsummerschool
油
The document outlines the agenda for a session on Linked Open Data including:
- Notation used in Linked Data diagrams
- Linked Open Data principles
- Applications of Linked Open Data principles including schema.org and Wikidata
- Open questions and topics for further research on the Semantic Web
- Hands-on demonstrations of Linked Data concepts and tools
This document provides an overview of wiki technologies and their history. It discusses how wikis originated in the 1990s and were popularized by Wikipedia in the early 2000s. Key features of wikis are outlined, such as their open source nature, ease of editing, and support for collaboration. Wikipedia's enormous growth and collaborative model are also summarized. The document concludes with an introduction to using the MediaWiki software that powers Wikipedia.
2010 07 modeling web evolution amarantidis antoniou vafopoulos finalvafopoulos
油
This paper analyzes and simulates the KKPS model of web evolution to address open issues. Simulations show that as the number of endorsed documents (b) or topics (k) increases, the power law distribution of document in-degrees becomes less significant. They also found that increasing the number of endorsements (b) can decrease the efficiency of the search algorithm, contrary to expectations. The paper aims to clarify these issues and highlight future directions for more realistic web modeling.
This document discusses the evolution of the web from a web of documents to a web of linked data. It outlines the principles of linked data, which involve using URIs to identify things and linking those URIs to other URIs so that machines can discover more data. RDF is introduced as a standard data model for publishing linked data on the web using triples. Examples of linked data applications and datasets are provided to illustrate how linked data allows the web to function as a global database.
The document discusses the Publicspending.gr (PSGR) program in Greece, which aims to provide transparency in public expenditure through network analysis and visualization of spending data. The key points are:
1) PSGR manifests the value of open data and ex-ante reporting of government decisions, shifting the paradigm for 40,000 public servants.
2) Since launching in 2011, PSGR has progressed from believing open data is valuable to realizing it requires refining like chiseling jewelry from rocks in a goldmine.
3) Network analysis is a basic tool used by PSGR to analyze and visualize linked spending data, enabling the study of relationships between important payees and payers and economic impacts
2010 06-08 chania stochastic web modelling - copyvafopoulos
油
The document summarizes research on modeling the evolution of the World Wide Web as a complex system. It discusses the Web's structure as a directed graph and statistical properties like power law degree distributions and small world properties. It describes models of Web traffic and evolution that use concepts from statistical physics and complex networks. Game theoretic and query-based models are also summarized. The document focuses on a query-Web model that explains the Web's scale-free structure through the interaction of users, documents, and search engines.
This document discusses issues of trust as it relates to technology and society. It covers how trust underlies civilizations and how various technological developments from writing to the internet have both increased and challenged trust over time. It examines specific issues like network security threats, software safety, and privacy of personal data. The document argues that trustworthy systems and practices are important for democratic societies and that European policies need to nurture democratic values in the digital age. It outlines the EU's legal framework around data protection and privacy technology. Finally, it discusses the goals and activities of the RISEPTIS advisory board, which aims to provide guidance on security, privacy, and trustworthiness research and policy challenges.
This document discusses trustworthiness in the information society. It provides an overview of key concepts related to privacy, anonymity, accountability and the legal framework for data protection in Europe. It also discusses stakeholder perspectives from governments, business and citizens. Additionally, it considers research and technology development as well as infrastructure and governance issues. The document aims to start a discussion on how to develop an information society that respects democratic values and citizen privacy while still enabling innovation.
Dynamic languages, for software craftmanship groupReuven Lerner
油
Reuven Lerner's talk about dynamic programming languages in general, and about Ruby in particular. Why would you want to use a dynamic language? What can you do with one that isn't possible (or easy) with a static language?
Domain Driven Design with the F# type System -- F#unctional Londoners 2014Scott Wlaschin
油
(Video of these slides here http://fsharpforfunandprofit.com/ddd)
Statically typed functional programming languages like F# encourage a very different way of thinking about types. The type system is your friend, not an annoyance, and can be used in many ways that might not be familiar to OO programmers.
Types can be used to represent the domain in a fine-grained, self documenting way. And in many cases, types can even be used to encode business rules so that you literally cannot create incorrect code. You can then use the static type checking almost as an instant unit test making sure that your code is correct at compile time.
In this talk, we'll look at some of the ways you can use types as part of a domain driven design process, with some simple real world examples in F#. No jargon, no maths, and no prior F# experience necessary.
Code, links to video, etc., at http://fsharpforfunandprofit.com/ddd
NEW AND IMPROVED - added sections on:
* why OO, not FP is scary
* designing with states and transitions
This document provides examples comparing Java and Kotlin code for common programming tasks. It shows how Kotlin simplifies collections, extension functions, data classes, and defining steps in Allure reports compared to Java. For collections, Kotlin provides concise syntax like val classpath = listOf() instead of creating and adding to lists. Extension functions allow adding methods to existing classes like HtmlElement.waitForIt(). Data classes remove boilerplate from simple classes. And Kotlin step blocks cleanly define steps in Allure reports.
What/How to do with GraphQL? - Valentyn Ostakh (ENG) | Ruby Meditation 27Ruby Meditation
油
Speech of Valentyn Ostakh, Ruby Developer at Ruby Garage, at Ruby Meditation 27, Dnipro, 19.05.2019
際際滷share -
Next conference - http://www.rubymeditation.com/
This talk explores basic concepts of GraphQL.
The main goal is to show how GraphQL works and of what parts it consists of.
From the Ruby side we will look at how to create a GraphQL schema.
In addition, we will consider what pitfalls can be encountered at the start of work with GraphQL.
Announcements and conference materials https://www.fb.me/RubyMeditation
News https://twitter.com/RubyMeditation
Photos https://www.instagram.com/RubyMeditation
The stream of Ruby conferences (not just ours) https://t.me/RubyMeditation
Algorithm and Programming (Introduction of dev pascal, data type, value, and ...Adam Mukharil Bachtiar
油
This file contains explanation about introduction of dev pascal, data type, value, and identifier. This file was used in my Algorithm and Programming Class.
This document provides an overview of schema design and data modeling for both relational and non-relational databases. It discusses the history of data modeling including hierarchical and relational models. The goals of data modeling are to avoid anomalies, minimize redesign, and make the model informative for users. Common data modeling patterns like one-to-many, many-to-many, and tree structures are explained. Specific examples are given for modeling comments, products, and categories in a non-relational database.
Webinar: Strongly Typed Languages and Flexible SchemasMongoDB
油
This document discusses strategies for managing flexible schemas in strongly typed languages and databases, including decoupled architectures, object-document mappers (ODMs), versioning, and data migrations. It describes how decoupled architectures allow business logic and data storage to evolve independently. ODMs like Spring Data and Morphia reduce impedance mismatch and handle mapping between objects and database documents. Versioning strategies include incrementing fields, storing full documents, or maintaining separate collections for current and past versions. Migrations involve adding/removing fields, changing names/data types, or extracting embedded documents. The document outlines tradeoffs between these approaches.
ESWC SS 2012 - Tuesday Tutorial Dan Brickley and Denny Vrandecic: Linked Open...eswcsummerschool
油
The document outlines the agenda for a session on Linked Open Data including:
- Notation used in Linked Data diagrams
- Linked Open Data principles
- Applications of Linked Open Data principles including schema.org and Wikidata
- Open questions and topics for further research on the Semantic Web
- Hands-on demonstrations of Linked Data concepts and tools
Daniel Greenfeld gave a presentation titled "Intro to Python". The presentation introduced Python and covered 21 cool things that can be done with Python, including running Python anywhere, learning Python quickly, introspecting Python objects, working with strings, lists, generators, sets and dictionaries. The presentation emphasized Python's simplicity, readability, extensibility and how it can be used for a wide variety of tasks.
With all of the focus on OOP and frameworks, sometimes the utilities get ignored. These modules provide us with lightweight, simple, effective solutions to everyday problems, saving us all from reinventing the wheel. This talk looks at a several of the utilities and shows some of the less common ways they can save a lot of time.
Daniel Greenfeld gave a presentation titled "Intro to Python" where he demonstrated 21 cool things that can be done with Python. These included running Python anywhere, learning it quickly, introspecting objects to see their attributes and methods, performing string operations, formatting strings, basic math operations, and working with lists. The presentation emphasized Python's simplicity, readability, and extensive standard library and ecosystem.
2017 02-07 - elastic & spark. building a search geo locatorAlberto Paro
油
Presentazione dell'evento EsInRome del 7 Febbraio 2017 - Integrazione Elasticsearch in architettura BigData e facilit di integrazione con Apache Spark.
2017 02-07 - elastic & spark. building a search geo locatorAlberto Paro
油
Using Elasticsearch in a BigData environment is very simple. In this talk, we analyse what's Big Data and we show how it is easy integrating ElasticSearch with Apache Spark
This document discusses the concept of the information society and its dual nature. It describes how information and communication technologies can enable knowledge-based development but also enable privacy violations. It outlines the positive potential of knowledge creation and sharing through semantic technologies and grid computing in a "g-work" model. However, it also discusses the negative risks of increased surveillance and data abuse compromising personal privacy. The document calls for a transdisciplinary approach balancing these opportunities and threats to achieve sustainable development.
This document summarizes key concepts in cryptography and number theory relevant to public key cryptography algorithms like RSA. It discusses number theoretic concepts like prime numbers, modular arithmetic, discrete logarithms, and one-way functions. It then provides an overview of the RSA algorithm, explaining how it uses the difficulty of factoring large numbers to enable secure public key encryption and digital signatures.
This document discusses information accountability and proposes augmenting information systems with mechanisms called Policy Awareness. Policy Awareness would provide transparency about how information is used according to associated policies. It aims to address issues around appropriate information use beyond just access restriction. The goal is to extend the web architecture to support accountability when information is intentionally or accidentally misused, by maintaining information about provenance and usage policies in a machine-readable way. This could help balance interests around copyright, privacy and information sharing in a world where information spread is difficult to control.
This document outlines a framework for the emerging field of Web Science. It discusses the need to understand how decentralized information systems like the World Wide Web have evolved and continue developing in response to scientific, commercial and social pressures. The document proposes that Web Science should take an interdisciplinary approach to both analyzing the Web and engineering its further development in a way that respects its architectural principles and social aspects. It surveys some of the key issues that Web Science may address, such as the development of the Semantic Web and ensuring important properties like privacy.
2. Five Pillars
油油油油油油油油油油油 Wikipedia is an online encyclopedia
油
油油油油油油油油油油油油Wikipedia has a neutral point of view
油
油 油 油 油 油 油 Wikipedia is free content that anyone can edit and distribute
油
油 油 油 油 油 油 Wikipedians should interact in a respectful and civil manner
油
油油 油油油 油油油 油Wikipedia does not have firm rules
油
3. Policy
Wikipedia is not a paper encyclopedia
Wikipedia is not a dictionary
Wikipedia is not a publisher of original thought
Wikipedia is not a soapbox or means of promotion
Wikipedia is not a mirror or a repository of links, images, or
media files
Wikipedia is not a blog, webspace provider, social networking,
or memorial site
Wikipedia is not a directory
Wikipedia is not a manual, guidebook, textbook, or scientific
journal
Wikipedia is not a crystal ball
Wikipedia is not an indiscriminate collection of information
Wikipedia is not censored
4. Policy
Wikipedia is not a democracy
Wikipedia is not a bureaucracy
Wikipedia is not a battleground
Wikipedia is not an anarchy
7. MediaWiki
MediaWiki is a popular free web-based wiki
software application.
It is developed by, and it runs, all the projects of the
Wikimedia Foundation, including Wikipedia,
Wiktionary, and Wikinews, as well as powering
many other wiki websites worldwide.
It is written in the PHP programming language and
uses a backend database.
10. MediaWiki
Page content is generated through the use of a
markup language and limited HTML.
Examples:
油
'''Bold'''油 :油 Bold
''Italics'' : Italics
[[Linux]] : link to article "Linux"
[http://www.gnu.org/ GNU Project] : External link
11. System architecture
Wikipedia currently runs on dedicated clusters of Linux
servers (mainly Ubuntu), with a few OpenSolaris
machines for ZFS. As of December 2009, there were
300 in Florida and 44 in Amsterdam
13. Wikimedia Foundation
油
油
油
油
Imagine a world in which every single human being
can freely share in the sum of all knowledge.
That's our commitment.
28. Template code:
You gave {{{par1|lion}}} and {{{par2|tiger}}}.
Article code:
{{mybox| par2 = mule }}
Article output:
You gave lion and mule.
29. Template code:
You gave {{{par1|{{{1}}} }}} and
{{{par1|{{{1|lion}}} }}}.
Article code:
{{mybox| tiger | par2 = mule }}
Article output:
You gave tiger and mule.
30. Template code:
{| class=infobox
| First name
| {{{par1|}}}
|-
| Last name
| {{{par2|}}}
|}
Article code:
{{mybox| par1 = King | par2 = Kong }}
Article output:
First name King
Last name Kong
31. Template code:
{| class=infobox
| First name
| {{{par1|}}}
|-
| Last name
| {{{par2|}}}
|}
Article code:
{{mybox| par1 = | par2 = Kong }}
Article output:
First name
Last name Kong
32. {{#if: test string | value if true | value if false }}
{{#if: {{{par1|}}} | value if true | value if false }}
Remember: When checking infobox parameters, default value
should always be empty (=false).
33. Template code:
{| class=infobox
{{#if: {{{par1|}}} |
{{!}} First name
{{!}} {{{par1}}}
}}
|-
{{#if: {{{par2|}}} |
{{!}} Last name
{{!}} {{{par2}}}
}}
|}
Article code:
{{infobox| par1 = | par2 = Kong }}
Article output:
Last name Kong
39. Template code:
{{Infobox
|label1 = Name
|data1 = {{{name}}}
|label2 = Birth date
|data2 = {{{birth_date|}}}
|label3 = Birth place
|data3 = {{{birth_place|}}}
|label4 = Death date
|data4 = {{{birth_date|}}}
|label5 = Death place
|data5 = {{{birth_place|}}}
|label6 = Nationality
|data6 = {{{nationality|}}}
|label7 = Other names
|data7 = {{{other_names|}}}
|label8 = Occupation
|data8 = {{{occupation|}}}
}}
40. Template code:
{{Infobox
|label1 = Name
|data1 = {{{name}}}
Obligatory parameter
|label2 = Birth date
|data2 = {{{birth_date|}}} Optional parameter
|label3 = Birth place
|data3 = {{{birth_place|}}}
|label4 = Death date
|data4 = {{{birth_date|}}}
|label5 = Death place
|data5 = {{{birth_place|}}}
|label6 = Nationality
|data6 = {{{nationality|}}}
|label7 = Other names
|data7 = {{{other_names|}}}
|label8 = Occupation
|data8 = {{{occupation|}}}
}}
41. Template code:
{| class=infobox
{{Infobox {{#if: {{{name|}}} |
|label1 = Name {{!}} Name
|data1 = {{{name}}}
{{!}} {{{name}}}
|label2 = Birth date
}}
|data2 = {{{birth_date|}}}
|label3 = Birth place |-
|data3 = {{{birth_place|}}} {{#if: {{{birth_date|}}} |
|label4 = Death date {{!}} Birth date
|data4 = {{{birth_date|}}} {{!}} {{{birth_date}}}
|label5 = Death place }}
|data5 = {{{birth_place|}}} |-
|label6 = Nationality {{#if: {{{birth_place|}}} |
|data6 = {{{nationality|}}} {{!}} Birth place
|label7 = Other names {{!}} {{{birth_place}}}
|data7 = {{{other_names|}}} }}
|label8 = Occupation ...
|data8 = {{{occupation|}}} |}
}}
42. Complex code can be used if needed:
| label6 = 略龍留
| data6 = {{#if:{{{mass|}}}|{{{mass}}} kg}}
43. Important parameters of meta-template Infobox:
name - the name of the infobox important for many features
title - title that appears at the top of our box
image image to show on the top of our box
headerD
labelD
dataD
Text to use in corresponding row.
Headers, labels and data items with the same D-value are
mutually exclusive; if all are defined, only header will be
displayed.
If data is not defined, label is not displayed.