OpenLLM-France/wikimedia huggingface dataset:
# Blended Learning in K-12/Pedagogical Models- blending constructivism, behaviorism and cognitivism

One of the harshest criticisms of Blended Learning is that the focus tends to be on the instructor, rather than on the learner. (Oliver and Trigwell, 2005).
Alonzo et al. point out that the concept of e-learning is new enough that practitioners have not yet begun to apply pedagogical principals to the process of e-learning. (2005)
Ideally, they continue, e-learning (and therefore Blended Learning) should be focused on the individual learner. The course designer should be able to utilize cognitive and constructionist theory to design an effective course. (Alonzo et al., 2005)
This course would be carefully organized so that students can easily insert new knowledge into their pre-existing schema. The organization should then reinforce the acquisition of new knowledge and activities should provide a scaffolded approach to help learners practice new skills by applying their knowledge. All of this is consistent with cognitive theories of learning, which tend to focus on the processes of information acquisition, organization, retrieval, and application.
Constructivist theories of learning describe learning as a process whereby the learner takes in new information, and inserts it into existing schema. Each learner constructs meaning differently based upon their own experiences. In other words, there is a disconnect between knowledge that is taught, and knowledge that is learned, because the learner will re-interpret what is being taught, and construct his or her own meaning from that knowledge.
To support the constructivist approach, a learning community should be created, and then guided through the process of collaboration so that learning is constructed by the group, rather than just the individual. (Alonzo et al., 2005)
In a traditional face-to-face learning environment, one of the more common methods of constructing group meaning is through discussion. The instructor typically begins the discussion by posing a question. The instructor then invites members of the class to make an impromptu response. Other class members then respond to the first student, and a discussion develops. In this way, students are exposed to several perspectives, and the answer to the original question is constructed for each learner based upon the individual's assessment of the group's responses.
In a blended environment, this discussion format can be easily adapted and enhanced. The discussion could be held synchronously, in group chat, or could be held asynchronously, in a forum to which learners post responses. In a blended environment, students have the capability of responding to several points at once. Since an asynchronous discussion can continue over a longer period of time, students can take time to formulate responses, and can respond to a particular part of a comment, even if the discussion has taken another route.
# Canadian Refugee Procedure/133-136 - Prosecution of Offences
## IRPA Sections 133-136

Sections 133-136 of the Immigration and Refugee Protection Act read:

### The deferral of prosecutions provided for in s. 133 of the IRPA tracks Canada's obligations pursuant to the Refugee Convention

Refugee Convention Article 31(1) states that "The Contracting States shall not impose penalties, on account of their illegal entry or presence, on refugees who, coming directly from a territory where their life or freedom was threatened in the sense of article 1, enter or are present in their territory without authorization, provided they present themselves without delay to the authorities and show good cause for their illegal entry or presence". While this provision of the Convention was not reflected in the 1976 Immigration Act, the Act was subsequently amended to include section 133 of the IRPA. This provision was inserted into the Act following the report to the Minister of Rabbi Plaut, who noted that "Until a claim is finally disposed of, it cannot be determined if the claimant is entitled to the protection of Article 31." He therefore recommended that "the Act be further amended to prohibit any prosecutions for illegal entry or presence in Canada during the determination process." While it is possible that, if a refugee claim is rejected, a claimant's irregular entry into Canada could be a legal offence, in practice this is pursued only in exceptional circumstances, as simply asking people to leave or having the authorities remove them for not having a visa is easier and more efficient.

## References

* ↑ W. Gunther Plaut, Refugee determination in Canada: A report to the Honourable Flora MacDonald, Minister of Employment and Immigration, April 1985, Government of Canada publication, page 161.
* ↑ Monica Boyd & Nathan T.B. Ly (2021) Unwanted and Uninvited: Canadian Exceptionalism in Migration and the 2017-2020 Irregular Border Crossings, American Review of Canadian Studies, 51:1, 95-121, DOI: 10.1080/02722011.2021.1899743 at page 97.
# Canadian Refugee Procedure/140 - Seizure
## IRPA Section 140

Section 140 of the Immigration and Refugee Protection Act reads:

### The Division and its Members are not designated to seize documents or other things pursuant to this provision

Section 140 of the Act provides that an officer may seize and hold the listed things if the listed conditions are met. Such officers who have this power are those designated by the Minister as per section 6 of the Act: Canadian Refugee Procedure/4-6 - Enabling Authority. This power must also be exercised in conformity with section 8 of the Charter of Rights and Freedoms which provides that everyone has the right to be secure against unreasonable search or seizure: Canadian Refugee Procedure/Charter of Rights and Freedoms#Section 8: Unreasonable search or seizure. The Division and its staff are not designated for the purposes of this section. That said, pursuant to their powers under the Inquiries Act, Members have the power of summoning before them any witnesses, and of requiring them to produce such documents and things as the commissioners deem requisite to the full investigation of the matters into which they are appointed to examine: Canadian Refugee Procedure/Powers of a Member#Part I of the Inquiries Act.

### An officer designated by the Minister may seize documents from the Division pursuant to this power

An officer designated by the Minister may seize and hold a document if the officer believes on reasonable grounds that it was fraudulently or improperly obtained or used or that the seizure is necessary to prevent its fraudulent or improper use or to carry out the purposes of IRPA pursuant to section 140(1) of that Act. The section does not contain any limitations as to from whom such a document can be seized. Therefore, the designated immigration officer may exercise this power to seize a claimant’s document that is in the possession of the Division.
# Canadian Refugee Procedure/154 - Disposition after member ceases to hold office
## IRPA Section 154

Section 154 of the Immigration and Refugee Protection Act reads:
# Canadian Refugee Procedure/15-17 - Immigration to Canada - Examination
## IRPA Sections 15-17

Sections 15-17 of the Immigration and Refugee Protection Act read:

### An officer has jurisdiction and authority to examine a refugee claimant pursuant to subsection 16(1.1) after the claim has been referred to the Refugee Protection Division for determination

A delegate of the Minister of Public Safety and Emergency Preparedness has jurisdiction and authority to examine a refugee claimant pursuant to subsection 16(1.1) of the Immigration and Refugee Protection Act about his or her refugee claim after the claim has been referred to the Refugee Protection Division for determination.

## References

* ↑ Canada (Citizenship and Immigration) v. Paramo de Gutierrez, 2016 FCA 211 (CanLII), [2017] 2 FCR 353, at para 56, <https://canlii.ca/t/gt6qj#par56>, retrieved on 2023-08-21.
# Canadian Refugee Procedure/153 - Chairperson and other members
## IRPA Section 153

Section 153 of the Immigration and Refugee Protection Act reads:

### One Deputy Chairperson for each Division is to be designated

The IRB states that each Division is headed by a Deputy Chair who manages the members of the Appeal Division and Refugee Division respectively. The Deputy Chairs set and oversee performance and productivity standards for members and provide leadership in the conduct of hearings and in ensuring philosophical and operational consistency.

## References

* ↑ Government of Canada, Refugee Determination: What It Is and How It Works, Pamphlet, 1989, Immigration and Refugee Board, page 11.
# Canadian Refugee Procedure/156 - Immunity and no summons
## IRPA Section 156

Section 156 of the Immigration and Refugee Protection Act reads:

### See commentary

See: Canadian Refugee Procedure/The right to an independent decision-maker#Board Members are neither competent nor compellable witnesses as a result of the principle of deliberative secrecy.
# Canadian Refugee Procedure/150.1 - Sharing of Information
## IRPA Section 150.1

Section 150.1 of the Immigration and Refugee Protection Act reads:

### Section 150.1(1)(c) provides that the regulations may provide for an matter relating to the disclosure of information relating to the professional or ethical conduct of certain representatives

See: Canadian Refugee Procedure/IRPR s. 13.1 - Authorized disclosure.
# Canadian Refugee Procedure/155 - Disposition if member unable to take part
## IRPA Section 155

Section 155 of the Immigration and Refugee Protection Act reads:
# Canadian Refugee Procedure/161 - Functioning of Board and Division Rules
## IRPA Section 161

Section 161 of the Immigration and Refugee Protection Act reads:

### 161(1)(b): The Chairperson may make rules respecting the conduct of persons in proceedings before the Board

Paragraph 161(1)(b) contemplates the issuance of rules relating to the conduct of persons appearing before the IRB. In its decision regarding Mumtaz Khan, the Board concluded that this provision codifies the Board's common law power to make rules regarding the conduct of persons in proceedings before the Board, but that this provision does not limit the Board's pre-existing powers to take action regarding misconduct.

## References

* ↑ re: Mumtaz Khan, December 18, 2020, <https://irb-cisr.gc.ca/en/decisions/Pages/mumtaz-khan.aspx> (Accessed February 1, 2021).
# Chemical Information Sources/Synthesis and Reaction Searches/Inorganic Reactions and Methods

| Volume | Year | Title |
| 1-2 | 1986-87 | The Formation of Bonds to Hydrogen, 1-2 |
| 3-4 | 1989-91 | The Formation of Bonds to Halogens, 1-2 |
| 5-6 | 1991-98 | The Formation of Bonds to O, S, Se, Te, Po, 1-2 |
| 7-8 | 1988-95 | The Formation of Bonds to N, P, As, Sb, Bi, 1-2 |
| 9-12 | 1988-91 | The Formation of Bonds to C, Si, Ge, Sn, Pb, 1-4 |
| 13 | 1991 | The Formation of Bonds to Group-I, -II, and -IIIB Elements |
| 14 | 1998 | The Formation of Bonds to Transition and Inner-Transition Metals; Oxidative-Addition and Reductive-Elimination Reactions; Insertion Reactions and Their Reverse |
| 15 | 1986 | Electron Transfer and Electrochemical Reactions; Photochemical and Other Energized Reactions |
| 16 | 1993 | Reactions Catalyzed by Inorganic Compounds |
| 17 | 1990 | Oligomerization and Polymerization; Formation of Intercalation Compounds |
| 18 | 1999 | Formation of Ceramics |
| Indexes | | Part 1. Author and Subject. Part 2. Compound. |
# Coding Cookbook/URL Encode

Encode special characters in a string, so that it can be used in an URL
# Coding Divert Sockets/Can I Use Them?

Though it might not be the question you really wanted to ask, it is definitely worthy of note before continuing.
Not all kernels are built with divert sockets and a compatible packet filter, and they are required to get divert sockets working. In case either or both of them are missing, you will need to recompile your kernel with IPDIVERT and IPFW enabled.
Note: If you have a preference for a different packet filter—other than the IPFW—it is possible as long as the filter supports divert/tee rules. Be sure to check out your packet filter's documentation on whatever rule you'd like to link to your divert socket(s) and how to do them. (If you would like to add to this book how to link a packet filter rule with a divert socket that isn't the IPFW, your contributions are greatly welcome.)
# Coding Divert Sockets/Introduction

Divert sockets are one of the many thinly documented APIs of Linux and BSD kernels. A simple wake up call is all you need to conquer the power of divert sockets and use it in your application.
In this wikibook, you will learn what are divert sockets, when you can use them, how, and why you should. Plus, you will learn how to set IPFW rules and gain a basic understanding of using raw IP sockets.
The more aware you are of networking, the easier it will be to understand the power of divert sockets.
# Coding Cookbook/Validate Email Address
## Regular Expressions?

There are many many proposed regular expression solutions to this problem, however the e-mail address format is so complicated that it is difficult to do with a regular expression alone. On the other hand, the vast majority of email addresses that people actually use fall into a small subset of the standard, and thus various usable regular expressions can be found of varying degrees accuracy scattered widely across the internet. If you want to look at a cool regular expression that performs a subset of the email validation process, stare at this for a while; there are also some quick not-quite-perfect solutions here.

## Practical solution

Because parsing an email address is so difficult, it makes little sense to even attempt it; particularly as it would be trivial for someone to give you a correctly formatted email address that still didn't work. This means that the best way to detect whether an email address is valid is to simply send it an email. If you can verify that the email was received, then you know for certain that the email address is valid (though it doesn't guarantee this for any length of time, as many services exist giving out temporary email addresses).
The most common way of doing this is to send someone an email containing a link to an http service with a long random string attached to it, only the email and your server contain the random key, so someone would have to read the email to find the correct link.
The purpose of the random string is to reduce the possibility that someone can make the server believe that the email address exists, while in fact it does not. For example, suppose that the link sent in the email is of the form http://myserver.com/validateemail?address=example@yourserver.com. Someone could use an existing, valid email address to see the pattern, and subsequently call the server with any random email address, even without receiving the actual mail containing the link.
Some servers require authentication when opening the link. For example, the user claiming the email address must supply his user id and password when validating it. While this is useful for confidentiality of the data shown on the validation page (including the statement that the address has been validated as an existing address), it does not prevent registering non-existent addresses. Only a long random string used as described above can do that.
Note also that the string must be random only from the client perspective, not necessarily from the server perspective. For example, the server can digitally sign the url, and validate the signature. In this case, the server does not need to store the random key to be able to validate it.

## For further reading

* JavaScript/Best Practices has some email validation tips.
# Coding Divert Sockets/How Do They Work?
## Divert Socket Anatomy

Divert sockets are quite similar to raw IP sockets. One major difference between them is instead of binding to an IP address, like raw IP sockets, divert sockets bind to a programmer-defined divert port. The IPFW program or other packet filter is used to match packets you want the socket to receive, and once a match is found, it can divert or tee the packet.

#### Is there a tee socket?

Nope. Teeing is a process in which a copy of the packet is sent to your divert socket, meanwhile diverting stops the packet completely from continuing up the network stack and requires the application reinject it into the network stack. Teeing is generally a good idea if you want to just capture packets.

### Receiving

Receiving incoming and outgoing packets happen through either one of the read, recv, and recvfrom calls. In the latter function, the address port returned is a tag set by the packet filter. IPFW, in this case, would set the port to the rule number of the matching rule that diverted the packet. As for the IP address field, incoming packets will trigger setting the IP address returned to the device that received the packet. The BSD name of the device is placed in the last 8 bytes of the address, assuming it fits. Otherwise, the IP address is simply set to INADDR_ANY when outgoing packets are received, and the last 8 bytes of the returned address are null.

### Sending

Sending packets works just as it does with raw IP sockets. You may send packets through the socket by using either of the write, send, or sendto calls. In the latter case, a destination address of INADDR_ANY will cause the packet to be treated as an outgoing packet. Any other address will cause the packet to be treated as an incoming packet.

#### Error checking on raw packets

When a raw packet enters IP processing, little error checking is done (just as in raw IP sockets.) If you send a packet with a bad IP checksum, it will be sent with a bad IP checksum and will report no error. If you send a packet with an incorrect datagram length, the packet will be dropped and errno will be set to EINVAL. It is your job to make sure there is no mistake when sending your packet, or it will forever be lost in the mighty depths of the Internet.

#### send or sendto to send packets?

Send is much easier to work with, but it does not allow you to explicitly choose which device will receive the packet you want to send. If you're clueless, you want send, save yourself a couple debug sessions.
# Coding Divert Sockets/What Are They?

A divert socket is a special socket that is bound to a divert port where the IPFW or other filter sends matching link level incoming/outgoing packets for processing in a user space process. Divert sockets allow you to send packets in a similar fashion raw IP sockets do, where they enter or re-enter IP packet processing.
Divert sockets are particularly useful when, for example, an application to act as a router with use of a divert rule linked to a divert socket to receive and re-inject re-routed packets into the network stack, or a packet capture application using a tee rule linked to a divert socket for capturing data at interrupt time resolution; with no concern for the link level (Ethernet, 802.11, etc.) headers.
Since divert sockets stop packets from continuing up the network stack, data can be modified before it reaches its destination without having the destination host know that the packet was modified.
Think of it as a libpcap that allows you to stop packets before they get to their destination and send raw packets, only without the bloat of libpcap.
# Coding Divert Sockets

This book serves as an introduction to coding divert sockets. Feel free to add.
* Introduction
** What Are They?
** Can I Use Them?
** How Do They Work?
* Your First Divert Socket
** Before You Begin
** Preparing the Divert Socket
** Using the Divert Socket
** Cleaning Up
# Coding Divert Sockets/Before You Begin

First, there are a couple (hopefully nothing new) include files you will need to know about.

## sys/types.h and sys/socket.h

This pair of header files is probably the most important one out of all the header files when coding any type socket. sys/socket.h contains several important constants (AF_INET? It's in here, as are all the other address families) and several less important constants, famous and infamous socket functions (socket anyone?). The main structure worthy of note here is sockaddr.

## netinet/in_systm.h and netinet/in.h

netinet/in_systm.h defines network times (which has nothing to do with divert sockets, but it is required by netinet/in.h to compile properly.) netinet/in.h is the more important header here. It defines all transport-level protocol numbers (as found in RFC 1700), sockaddr_in, fun IPFW defines, and more stuff you probably have dealt with in normal sockets.

## netinet/ip_fw.h

This header defines some structures we will send to instruct the IPFW program, later on in the book.

## netinet/ip.h, netinet/tcp.h, and netinet/udp.h

These files define protocol structures (as if you didn't know.)
# Chess Opening Theory/1. e3
## 1. e3 · Van't Kruijs Opening

An irregular opening, considered somewhat passive. Play may transpose to lines of the English Opening (c2–c4), Queen's Pawn Game (d2–d4), or reversed French Defence (delayed d2–d4), reversed Dutch Defence (f2–f4) positions or the modern variation of Larsen's Opening (b2–b3),or King's Isa Reverse Opening (e4–e5)

## Statistics

White Wins 47% Draw 5% Black Wins 49%

## Theory table

1. e3
| | 1 | 2 | 3 | 4 | 5 | 6 | 7 |
| 1 | ... d5 | = |
| 2 | ... e5 | = |
| 2 | ... e5 | Bc4 d5 | Bb3 Nf6 | d3 Nc6 | c4 dxc4 | Bxc4 Bb4+ | Bd2 Qe7 | Nf3 Na5 | b3 Nxc4 | =+ |
| 2 | ... f5 | = |
| 2 | ... Nf6 | = |

## All possible Black's moves

| Quick Navigation | Na6 a6 a5 | b6 b5 | Nc6 c6 c5 | d6 d5 | e6 e5 | Nf6 f6 f5 | g6 g5 | Nh6 h6 h5 |

## References

* Eric Schiller (2002). Unorthodox Chess Openings (Second ed.). Cardoza. ISBN 1-58042-072-9.
For explanation of theory tables, see theory table and for notation, see algebraic notation.
When contributing to this Wikibook, please follow the Conventions for organization.
# Nimzowitsch Defence: Pseudo-Spanish Variation
## 3. Bc4
## References

1. e4 Nc6 2. Bb5 Nd4 3. Bc4
# Lemming Defence/Mirrored Amar Opening
### 1...Na6

The Lemming Defense is a very rare and rather weak opening in response to 1. e4. The knight develops to a square that doesn't control the centre and as such, it's a wasted opportunity.
This opening is very rarely seen among serious chess players, and it's classified under the code B00 (Uncommon Opening).

## Theory table

For explanation of theory tables, see theory table and for notation, see algebraic notation.
1. e4 Na6?!
| 2 |
| d4 Nb8? | +/= |
When contributing to this Wikibook, please follow the Conventions for organization.

## References

* Eric Schiller (2002). Unorthodox Chess Openings (second edition ed.). Cardoza. ISBN 1-58042-072-9. {{cite book}}: |edition= has extra text (help)p. 302
# Nimzowitsch Defence: Pseudo-Spanish Variation
## 2...Nd4
## References

1. e4 Nc6 2. Bb5 Nd4
# Van 't Kruijs Opening
### 1. e3 d5

The response 1...d5 by black to the opening 1.e3 can be a choice to move the game closer to a variation of the Queen`s pawn opening, especially if white responds with 2. d4

### Statistics

Not enough data as opening is rarely played.

## Theory table

For explanation of theory tables, see theory table and for notation, see algebraic notation. .
* :1. e3 d5
When contributing to this Wikibook, please follow the Conventions for organization.

## References

* Eric Schiller (2002). Unorthodox Chess Openings (2nd ed.). Cardoza. ISBN 1-58042-072-9.