text:
Talk:Public International Law/Jurisdiction

Review: 14 June 2023
Dear Sué & Max,

This promises to become a great chapter and I only left some minor comments in the text.

Best, Raffaela

--Raffaela Kunz (discuss • contribs) 14:59, 14 June 2023 (UTC)

Review: 1 November 2021
-- In Part A's discussion of the definition of jurisdiction, my suggestion is to make sure to also engage with the question of what jurisdiction is on a practical level. For example, I believe that in the ILC's work on immunity of state officials from foreign criminal jurisdiction, the ILC was not able to arrive at a concrete definition of what counts as an exercise of jurisdiction, despite a fair amount of discussion. (i.e. Does surveillance count as an exercise of jurisdiction? Or investigating a person? Or taking a person in for questioning? etc. etc.). Other areas where it becomes confusing what jurisdiction is or isn't concern unilateral sanctions and taxation (and a host of other issues, as I'm sure you're aware), but perhaps these are too complicated to get into in a textbook.

-- I believe that it is important to clearly distinguish between criminal and civil jurisdiction, and their corresponding rules (or lack thereof) in international law. For example, in Part D, distinction along these lines would be helpful. Indeed, it seems to me that the question of where private international law "ends" and the public international law bases of jurisdiction "begins" remains very unclear, particularly in the civil context.

-- Forgive me because I am not nearly as well-versed in this area of the law, but I'm not sure I understand what the principle of distinction is in the context of Part A. In the context of this textbook, I wonder if some of the more nuanced points like this (which are currently mentioned as headline issues) should instead be subsumed into the discussion under the broader headings.

-- In the context of Part C, it may be worth considering whether a "nexus" is always required, as indeed there are debates (as I know you are aware). For example, governments often make agreements to transfer jurisdiction even absent such a nexus, or offer written or verbal consent allowing another State to exercise jurisdiction over their nationals. The controversial example of jurisdiction over vessels on the high seas comes to mind. Home States have on occasion consented to a foreign state's jurisdiction over nationals found either on vessels flying the home State's flag, or stateless vessels (see, e.g., enforcement of drug trafficking crimes).

-- Along similar lines, when discussing the concept of "nexus," it may be worth considering debates about whether notions of due process under human rights law require such a nexus, or whether such a nexus derives from another principle (or whether it remains unclear).

-- The list in Part D.II might need to include a section on treaties granting States additional jurisdictional bases, unless this will be covered elsewhere (see, e.g. hostages convention and other suppression conventions). Furthermore, you may wish to briefly mention issues where domestic jurisdiction is said to be "transferred" to international tribunals by virtue of treaties (see, e.g., Rome Statute and debates about head of state immunity in the Al Bashir case).

--Somewhere along the way it would of course be helpful to give an assessment of the relevance today of the Lotus case, and critiques of it. From what I understand, there may be some shift towards the requirement to affirmatively justify exercises of jurisdiction based on one of the principles you mention, not simply point to the lack of a principle prohibiting the exercise of jurisdiction. Accordingly, perhaps in your discussion of "sovereignty" in Part A you may wish to consider the extent to which that notion (or the principle of non-intervention) limits domestic exercises of jurisdiction (maybe this is what you are already planning).

--You may also wish to consider the extent to which the rules on jurisdiction are influenced by discretionary decisions on the part of judges / courts declining jurisdiction, for example, pursuant to doctrines like forum non conveniens.

These points are all just meant for the sake of brainstorming and discussion. I know that everything cannot possibly find its way into the chapter. In any event, the chapter sounds really fascinating and I'm very much looking forward to reading it! The outline shows a lot of great work and thinking.

Please don't hesitate to be in touch with any questions.

All best, Beatrice


text:
Talk:Public International Law/Sources of International Law

Review 17th May 2023
Dear Craig, Thanks for the chapter. Following up on my comment from more or less exactly one year ago, I wanted to stress gain that there is no need to discuss or even present the sources in detail, since this is being done in the subsequent sections. The aim here simply is to introduce to the concept of sources and to address the overarching questions that concern all sources, including the hierarchy question.

What role do sources play in the international legal order? Introduction to what we discuss when we teach sources/which questions fall under the sources umbrella - what is law in the international legal order? Who makes, interprets and changes the law in the international legal order? Particularities of law-making in the International order - decentralised character of the lawmaking; no centralised "world parliament"; importance of state consent etc. Please also consider to link to the "consent" chapter in the first part of the book.

--Raffaela Kunz (discuss • contribs) 07:42, 17 May 2023 (UTC)

27th of May 2022

Dear Craig, I wanted to mention again, agreeing with the comment below, that there is no need to discuss the subsidiary means at length here, since Lucas, Bernardo and diIscuss this in more detail in the "other sources" chapter. Will you include a reference to the formal/material distinction? Wondering because this came up on our chapter and we might want to add a link. Raffaela --Raffaela Kunz (discuss • contribs) 09:48, 27 May 2022 (UTC)

Review: May 12, 2023
The chapter provides an excellent introduction to sources of international law, laying out the key issues that underpin the field. The chapter is clearly written, and provides students with a solid foundation for understanding the following sub-chapters.

You will find some comments in your chapter in which I elaborate on something more specifically. To view these comments, just open you chapter page and click on "Edit" in the top-right toolbox.

Some parts are still missing in your contribution:

- It would be great if you could finish the chapter by the end of June at the latest. The sooner you finish, the better we can review your chapter and the more time you have to use our comments to improve the chapter.

- There are no footnotes in your chapter. Please add them using OSCOLA as the citation style.

- Note also that the following parts are still missing: required knowledge, learning objectives, conclusion, further readings

- You could add some links to other chapters of the textbook

Max Milas (discuss • contribs) 15:58, 12 May 2023 (UTC)

Review: 1 November 2021
In general I like the outline of the chapter on sources. I think it is particularily important to discuss sources beyond article 38 ICJ. There is a lot to be said there. I am therefore a bit uncertain whether the subchapters “soft law” and “unilateral declarations” will manage to capture all that should be included here. Or, put differently, I have some doubts whether “soft law” as a notion is really proper to capture the fact that we nowadays increasingly acknowledge a regulatory function e.g. of acts of international organizations. Also entire fields of law seem in essential ways to escape the article 38 construct (thinking about environmental law e.g.) as well as the “hard-soft” divide. I am also a bit uncertain about the “equity” chapter. As a general principle of (intenational) law it is certainly an important interpretative device. But perhaps it would better fit in the subchapter on general principles. Finally, “sources and subsidiary means”. I´m wondering whether subsidiary means need to be discussed here at any length? At any rate the phrasing should be consistent with the overall structure of the chapter at large (which it now isnt, as there is a chapter on “other sources” there). Would be good for authors to coordinate where to discuss the “other sources/sources beyond art 38” question, which is different from the “subsidiary means” question and its role in the ICJ charter.

Review / comments
In general I like the outline of the chapter on sources. I think it is particularly important to discuss sources beyond article 38 ICJ. There is a lot to be said there. I am therefore a bit uncertain whether the subchapters “soft law” and “unilateral declarations” will manage to capture all that should be included here. Also I have some doubts whether “soft law” as a notion is really proper to capture the fact that we nowadays increasingly acknowledge a regulatory function e.g. of acts of international organizations. Also entire fields of law seem in essential ways to escape the article 38 construct (thinking about environmental law e.g.) as well as the “hard-soft” divide.

I am also a bit uncertain about the “equity” chapter. As a general principle of (international) law it is certainly an important interpretative device. But perhaps it would better fit in the subchapter on general principles?

Finally, on “sources and subsidiary means”. I´m wondering whether subsidiary means need to be discussed here at any length? At any rate the phrasing should be consistent with the overall structure of the chapter at large (which it now isn´t, as there is a chapter on “other sources” there as well). Would be good for authors to coordinate where to discuss the “other sources/sources beyond art 38” question, which is different from the “subsidiary means” question and its role in the ICJ charter.

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/


text: Medical Machines/Printable version

title: Medical Machines/Printable version


text:
Wikijunior:Ancient Civilizations/Magyar

= The Magyars =

Who were they?
The Magyars were ancient ancestors of the people of modern-day Hungary. Over 1000 years ago, they lived in the far north. They were nomads, wandering from place to place in search of grazing land. They lived in cold northern regions then traveled southward. They were tent-dwellers. They hunted game in the forests and fished in rivers. They may have grown crops such as wheat for food. They moved southward settling in several areas before making a permanent home in the Great European Plain. The Great Plain was also called the Carpathian Basin. It is now the modern-day European nation of Hungary.

In their wandering, the Magyars learned from other peoples about agriculture and horse breeding. They became excellent horsemen. They used special Central Asian-style bows for fighting from horseback.

They were feared by other peoples of the time. They were such fierce warriors they were sometimes called Turks or Ongri. But they were not related to Turks as some believe. In modern times they are known as Hungarians, but they still refer to themselves Magyars (magyarok). They founded the present-day country of Hungary. Most people living in Hungary today are of ancient Magyar ancestry.

The Magyars were organized as family clans within tribes. The tribes were led south to the Great Plain of Europe by Grand Prince Arpad in the late 9th century. There were 10 tribes called the Ten Magyars or Ten Arrows. They crossed the Carpathian Mountains and settled in their permanent homeland. The people already living there were mostly Slavs. The Magyars drove out many, but some were allowed to stay and live under Magyar rule.

Arpad’s descendants ruled for over 400 years. When his great-grandson Vajk became king, he made many changes to Magyar life. He became a Christian and changed his name to Stephen. He established the Christian Kingdom of Hungary. The pagan practice of worshipping many gods was outlawed. Stephen built Hungary’s power and prestige in Europe. He made Hungary an important European country.

Where did they live?
Ancient Magyars lived far to the north in a region that is now part of modern-day Russia. They migrated southward to what is now central Russia. The early Magyars may have wandered into lands near the Volga River in present-day Kazan. During this time they possibly learned about agriculture from the Bulgar-Turks. Many Hungarian words about agriculture and raising livestock have Turkic roots.

In the 9th century, the Magyars were driven westward by Turkish tribes. They went to lands near the Danube, then over the Carpathian Mountains into the Great Plains (modern day Hungary).

The new Magyar homeland was surrounded by peoples of different origins and histories. They were unrelated to the Magyars. Their languages were strange and unfamiliar. They were Germanic, Slavic, Hunnic, Turkic, and Greek. The neighboring peoples disliked the Magyars. They blamed them for destroying churches and monasteries. Hostilities and conflicts were common, especially with the Turks.

The Great Plain was a great flat area surrounded by the Carpathian Mountains and the Alps. It was landlocked, meaning there was no access to the sea. The hills and mountains were forested. There were small low lying, marshy areas called fens. The soil was rich and good for agriculture.

Government
Magyars lived in tribes made up of family clans. There were 7 tribes of 108 clans. Before the migration, the 7 tribes were called the Seven Arrows (Hetumoge). They were led by a spiritual ruler (kende) and a chief military commander (gyula). The 7 were later joined by 3 Turkic tribes to form the Ten Arrows (On-ogur).

The chief military commander of the Ten Arrows was Arpad. In the late 9th century, it was Arpad who led his people into the Great Plains. The Magyars were feared by people of the surrounding kingdoms. There was strife and hostility, but eventually, treaties and alliances were made with neighboring kingdoms.

In the year 1000, Stephen was crowned king. He established the Christian Kingdom of Hungary. He changed his pagan name from Vajk to Stephen, a Christian name. King Stephen chose Western Christianity (Catholicism) as the religion of Hungary. His choice linked Hungary to the other Christian kingdoms of Europe.

King Stephen believed Christianity would play an important part in Hungary’s future. He had many churches and monasteries built. He brought priests from other countries to preach God’s word. King Stephen was named Saint Stephen by the Catholic Church. In Hungarian his name is Szent Istvan Kiraly.

King Stephen ruled Hungary from the year 1000 until his death in 1083. It was a time of peace and prosperity. The Magyars had left their nomadic past behind. They became settled Europeans. Hungary became more connected to its neighbors. It became less connected to Asian culture. After Stephen died, Hungary remained strong for another 1000 years. However, frequent fighting and skirmishes with enemies weakened the Kingdom. By the year 1300, Hungary had declined. But, fifty years later Hungary’s power was restored by King Louis the Great.

The next threat to Hungary came from the Ottoman Turks led by Suleiman the Magnificent. In 1526, the Turks defeated King Louis II. The Turks remained in Hungary until the 1600s. They destroyed towns and farmlands. Rich, fertile land that had once provided crops and grains became swamps where nothing could grow. People named it puszta meaning “wasteland” or “barren place”.

In modern times, the government has reclaimed and restored the land making it fertile again. Now wheat is grown and harvested. Hilly areas are planted with vineyards and orchards. Salty areas are pastures for sheep. Instead of wasteland, the word pusza now refers to farmland.

What did their buildings look like?
Hungary has many beautiful buildings. There are churches, abbeys, monasteries, basilicas, mosques, and castles. Some are recent. Others were built on centuries-old ruins.

Little remains of the plain stone structures of pagan times. Pagan temples and shrines were built into hills or set into the ground. Some were small, free-standing buildings. They were destroyed by early Christians who built churches on the ruins. Stone and other materials from the destroyed temples were used in building churches. Later, rather than destroying the temples, Christians made them into churches. They were converted and consecrated (declared sacred) as houses of worship.

Basilicas are special churches granted privileges by the leader, or Pope, of the Roman Catholic Church. The Basilica of Saint Stephen was the principal church of the rulers of Hungary. In the Middle Ages, the crown jewels and the holy crown of Hungary were kept there. Many Hungarian kings were buried there. Inside are beautiful marble sculptures. There are 2 large bell towers with 6 bells. One bell is Hungary’s largest, weighing 9 tons.

Esztergom Basilica is built on Castle Hill near the Danube River. Esztergom is said to be the birthplace of St. Stephen. He was crowned there. It is said to be the largest church in Hungary. It has tall columns in front with a large central dome. There are two smaller domes on the sides. Many religious art works, and holy relics are kept in its Christian Museum. It was originally built in the 12th century. Later, it was destroyed by the Turks and had to be rebuilt. There are 440 steps leading to the central dome.

Pannonhalma Abbey is an early Christian building founded in the 10th century. It is one of the oldest historical monuments in Hungary. It is still in use today.

A Muslim mosque is a place of worship for people who follow the Islamic religion. Mosques were built in Hungary by the Turks. Christians converted the Turkish mosques to churches after the Turks left. The Mosque of Pasha Qasim in Pécs was converted to a church in 1702. It has an octagonal shape (drum) with small windows on all 8 sides. It is covered by a dome. Inside, Ottoman decoration and inscriptions remain alongside Christian statues and artwork.

Budapest’s Cave Church is located at the foot of Gellért Hill. One part of the church is a natural cave (grotto) and the other part is man-made. It has a small chapel with warm water bubbling up at the entrance. A Magyar hermit called Iván once lived in the cave. He believed the waters could heal the sick. A group of Magyar pilgrims was inspired to build a shrine there. It was consecrated as a Christian church in 1926.

Egar Castle has stood since the mid-13th century. Egar was once a Magyar tribal town. The castle sits on a hill. It is famous because the larger Ottoman army was defeated there by the smaller Magyar army. Egar Castle Museum has an important exhibition of ancient weapons.

The Millennium Monument in Pest commemorates the 1000th anniversary of the settlement of the Magyars in Hungary. A tall pillar stands in the center. There is a winged statue on top. Around the plaza are statues of riders, horses, and chariots representing Hungarian history.

Some of the buildings in Hungary are Turkish bath houses. They were built near thermal (heated) springs. Inside a bath house is a pool of mineral-rich warm water. People go there for health reasons and to relax. Király Bath is said to be the oldest bath still in use today. It has an octagonal pool and a domed roof. There are small circular holes in the roof to let in light.

What did they wear?
Magyars used materials from plants and animals to make clothing. Women were skilled in spinning, weaving, and making cloth. Sheep wool and flax fiber was made into yarn and thread, then braided or woven into cloth. Animal hides could be made into leather for boots and belts. Some clothing was made of fur or leather. Peasant clothing was made mostly of sheepskin.

Flax was a plant used to make linen cloth. The stalks of flax plants were soaked in water, then spread out to dry. The stalks were beaten with a stick to soften them so the fibers could be pulled apart. The fine, soft fibers were brushed to prepare for thread-making and weaving. Shirts, trousers, and underwear were woven from linen. Often women dressed in white linen clothing. They carried tubs from camp to camp to keep their white clothes clean.

Wool from sheep was used to make thick, strong material called “felt”. Few tools were needed. Heat and moisture were applied to the raw wool. The wool was rubbed to bind the fibers and make the felt strong. Making felt was an important aspect of Magyar life. King Stephen wrote laws for people to follow when making felt. Felt was used to make a warm coat called a szűr.

Magyar clothing was designed for working, riding horses, movement, and protection. Some clothing was worn to show wealth or importance. Wealthy clan women decorated their clothing with objects made of precious metals like gold and silver. They used small decorative disks to hold their hair in braids. They wore high caps and headdresses.

Warriors wore loose clothing for ease of movement. Tunics opened down the front or fastened at the neck. Some warriors wore ear rings. A bow and other weapons needed to move freely, so no jewelry could be worn below the belt. Metal clasps were used to secure leather.

Magyar warriors had several articles made for protection. They wore pointed helmets and carried round shields. Boots were made of leather. A small flat bag called a tursoly was worn on the belt. It was meant to carry small items and often, protected the rider’s leg in battle. A slightly curved sword was carried in a sheath attached to the belt.

Women wore long, loose dresses or tunics called caftans. When putting up and taking down tents, women needed to move freely. Women’s skirts were made with openings on the sides for riding horses.

The szűr was a type of felt coat worn by Magyars. It was an important piece of clothing for shepherds, farmers, and peasants. It provided protection from sun, wind, and cold. At night it was used as a pillow and cover. The large collar covered the wearer when it rained. Magyar herdsmen had worn the szűr as far back as the Middle Ages.

A szűr was worn over the shoulders as a cape. It was often decorated with colorful, embroidered (sewn) leaves and flowers. Decorative felt cut-outs (appliqués) were sewn on. Older men wore a szűr decorated with black. A szűr for a young man was colorful. The szűr was worn when attending church and weddings.

One form of this coat had sleeves. It was a szűr-mantle. Sometimes the sleeves were sewn at the ends, so small utensils could be kept in them. Often, there were no sleeves.

A suba was protective outer-wear made of leather and wool. It was a round cloak made from 12 sheepskins. A suba was decorated and worn for festivals. Shepherds wore a suba and a cap called a süveg as protection from the weather. A suba could be used as a seat or bed. Sometimes a suba served as a surface for eating or drying meat.

Another important garment was a sleeved, sheepskin jacket called a ködmön. It either reached to above the waist or down to mid-thigh. A man’s ködmön often had a high neck. The neck of a woman’s ködmön was often cut out and worn over a shawl. Women’s were richly embroidered. The bottom and front of ködmön jackets were trimmed with fur. Some flared out from the waist, suitable for riding a horse.

Herdsmen made their own simple leather garments. The hátibőr (back hide) was made of a single sheepskin. The two hind legs tied at the waist. The two front legs tied at the neck. It covered only the back.

A chest warmer (mejjes) consisted of two parts—one worn on the back, the other on the chest. It was closed on both sides. Sometimes the skin was sewn up on one side and fastened with buttons on the other side. Some were embroidered on the front. Both men and women wore chest warmers.

As villages grew, clothing was made in homes. When many people make the same item at home, it is called a cottage industry. Specialized workers, such as tanners, furriers, and boot-makers also worked from home. Later in the Middle Ages, workers formed guilds. A guild is an association of people who do the same job. Guild members protect their special knowledge of how to make their product.

What did they eat?
Ancient Magyars ate meat from animals and food made from grains. They raised sheep, goats, pigs, and cattle. They were pastoral nomads, moving from place to place to feed their herds. They used horses in winter to break the snow on the steppes. The old vegetation underneath was collected as fodder (feed). This practice allowed them to use the steppes year-round to feed their animals. They hunted wild boar and other animals. Fishing and gathering wild plants did not provide as much food as animals and grains.

Ancient Magyars raided settlements to get food. When travelling for raids in enemy territory, they carried ingredients to make stew. They brought dried cubes of meat cooked with onions. It was fast and easy to add water for soup or stew at the campsite. Magyar stew was called gulyás (goulash). It was cooked in a large metal pot (cauldron) over the fire.

Today, goulash is the national dish of Hungary. It is seasoned with a bright red spice called paprika. Paprika was first used by poor people in the 16th century to keep food from spoiling. They could not afford expensive spices from Asia so they used paprika instead. It soon became popular with everyone.

Paprika became an essential ingredient in Hungarian cooking. It is made from dried red peppers. But it can be made from any color or shape of pepper. The peppers are harvested and hung up to dry. Then the dried peppers are ground up. One special pepper used for Hungarian paprika grows only in Hungary. A town called Szeged is the paprika capital of Hungary.

To soften the flavor of paprika and other spices, people use a thick, heavy sour cream (tejföl). It is a topping on goulash and other dishes. Langos a deep-fried potato dough is topped with sour cream and grated cheese.

Another popular, hearty stew, Lecso is made with chorizo sausage, stewed tomatoes, and onions. ''It is flavored with paprika. Fozelek is a snack of baked or fried vegetables. The vegetables are mixed into white sauce made of flour and fat.''

Fisherman's soup (halászlé) is a mixture of several kinds of poached fish, such as carp, catfish, perch, or pike. It is cooked in a cauldron over an open fire. It is seasoned with sweet and hot paprika.

What did their writing look like?
Ancient Magyars were pagans before becoming Christians. They believed in many gods and worshipped nature. They developed a unique kind of writing using rovás. Rovás were letters based on the sounds Magyars used when speaking.

Rovás letters are unlike any other known writing. The word refers to carving letters. Rovás were usually carved on wooden sticks or rocks. Ancient rovás writing has been found carved on stone objects and in old churches.

The letters and numbers had straight lines and were written right to left. The letter “M” looked like a backwards B except for having straight lines. “A” looked like a backwards P with straight lines. “V” looked like a capital M. “K” looked like a diamond. The first letter of a person’s name was drawn with thicker lines.

Magyars adopted Latin for writing when they became Christians. Even after abandoning paganism, Magyar shepherds used a rovás-stick to count their sheep.

What did they believe?
It is said Magyar pagans believed their gods lived in a Tree of Life. Leaves were the Upper World. The tree trunk was the Middle World. Humans and fantasy creatures lived in the tree trunk. Beneath the ground was the Underworld where bad spirits lived.

Parents of all the gods were Isten and Istenanya. The father god was Isten who watched humans in the Middle World of earth. Istenanya was the mother goddess who controlled the moon, fertility, and childbirth.

An important figure in Magyar religion was the shaman who was believed to have magical powers. People born with birth defects were chosen to be shamans. People believed shamans had special powers. They could climb the Tree of Life, talk to animals, and had super-human strength. The ancient Magyar religion has disappeared, but shamans still practice today in Hungary. They keep the old folktales and ancient customs alive.

Magyars believed in the Legend of the White Stag. It tells how the Magyar people began with twin brothers Hunnor and Magor. Their father was King Nimrod who ruled over a great ancient land. The sons, like their father, were skilled hunters. Once while hunting in the forest, they saw a beautiful white stag. They chased it through the forest and countryside. The stag led them into a beautiful land where it jumped into a river and disappeared.

Hunnor and Magor were heart-broken. When they returned, they told their father of the wondrous white stag. Their father built a temple to honor the stag. The brothers returned to their studies, so they could become great knights and rulers.

One day while wandering, they saw beautiful young women dancing and celebrating the White Stag. The two most beautiful young women were daughters of King Dula. The princes took them away and married them. They settled in a bountiful land. Their people prospered and their numbers grew. From these first people arose two great nations, the Huns and the Magyars. Both were bound together through this founding legend.

Are some of them famous today?
Many talented and creative Hungarian people are descendants of the Magyars. There are well-known entertainers, writers, actors, artists, and musicians.

William Fox was born in Hungary and moved to the United States. He was a Hollywood producer. He made his first film in 1914. He founded 20th Century Fox Studios in the 1920s. His work made many actors famous. His films influenced the lives of millions of people. Another movie producer was Adolph Zukor who founded Paramount Pictures. He was one of the fathers of the Hollywood film industry. Today Paramount is the fourth oldest surviving film studio in the world.

The actor Bela Lugosi was famous for playing Count Dracula in the movie Dracula. He became one of the most well known American stars.

The Great Houdini was a famous magician and escape artist. He was born in Budapest, Hungary. He performed all over the world.

Magda Szabó is the most translated Hungarian author. Her works have been translated into 30 different languages. Another Hungarian writer, Imre Kertész, was awarded the 2002 Nobel Prize for Literature.

Joseph Pulitzer was a world famous newspaper publisher. He crusaded against illegal practices in big business. He founded the Columbia School of Journalism. The Pulitzer Prizes for excellence are named in his honor.

The Hungarian Lipizzan horses are trained in Hungary. They were originally bred for battle. They could leap high into the air over attackers. They defended their rider and saddle from the enemy foot soldiers. Today the Lipizzans live on a farm in Szilvasvarad above the Great Hungarian Plain. They travel all over the world giving shows and demonstrations of their special abilities.

What is left of them today?
Evidence of the ancient Magyar people has been found by archeologists. Visitors to the Hungarian National Museum can view Magyar artifacts. Items on display include sabers, bows, arrow-heads, stirrups, and metal buttons. There is decorative jewelry made by Magyar gold-smiths and silver-smiths. There are weapons made by Magyar black-smiths.

The Crown of St. Stephen is displayed in Budapest’s Parliament building. St. Stephen’s crown is a famous symbol of Hungary’s nationhood. It was taken to America’s Fort Knox for safety during World War II. It was returned to the people of Hungary in 1978.

Esztergom Basilica has a museum that holds many ancient Magyar relics. The largest church in Hungary, it sits on the site of an earlier 12th century cathedral. Parts of the original church can be seen by visitors.

Evidence of the Magyar past can be seen in Hungarian clothing, music, dance, and even pets.

Some modern Hungarian clothing styles and decorations are similar to those of Magyar times. Suba and szur coats are still worn. Vests are often embroidered (adorned) with bright patterns, but modern embroidery patterns vary. Each region has its own unique pattern.

Hungarian folk music has roots in Magyar history. Sometimes called “peasant music,” folk songs were collected by composer Béla Bartók in the early 20th century. He was a musicologist, a person who studies music. He traveled to the Carpathian Basin to record songs on Thomas Edison’s recording machine.

Franz Liszt was a famous Hungarian composer. He wrote joyful rhapsodies based on popular gypsy and folk music. His piano compositions made Hungarian folk music known worldwide.

Kaláka is a folk music group from Budapest. They organize folk music festivals to entertain people. Muzsikás is another Hungarian folk music group. They travel to many countries to perform their music. This group also plays classical works by Béla Bartók

Many Hungarian dances come from Magyar times: dances for couples, dances for men alone (solo), jumping dances, and shepherd dances. They are accompanied by old style folk music. The Hungarian heyduck dance was a “weapons dance” performed by warriors. They danced while whirling weapons to practice their battle skills.

Historians believe Magyar tribes were expert dog breeders. The Hungarian Vizsla breed may have entered the Carpathian Basin with the Magyar tribes. The Vizsla (Hungarian Pointer) is one of the oldest breed of hunting dogs in the world. Vizsla means alert and responsive. Archeologists have found an ancient stone image showing a Magyar hunter with his Vizsla and his falcon. The Vizsla was highly valued by Hungarian nobility

Kuvasz dogs are snow white. They were bred by the Magyars to guard livestock. They were brought to Hungary in the Middle Ages. Patient and courageous, they were prized by Hungarian nobles. It is said that King Matthias I trusted his Kuvasz companions more than his palace guards.

The Hungarian Greyhound (Magyar Agár) was known as far back as the 8th century. It was used for hunting and coursing. Coursing is the sport of hunting game, such as rabbits, using sight rather than scent.

title: Wikijunior:Ancient Civilizations/Magyar


text:
Talk:Libreboot

BASLQC
Do we need a link to https://github.com/BASLQC/ in the header? --Alexey Vazhnov (discuss • contribs) 20:14, 1 November 2021 (UTC)

title: Talk:Libreboot


text:
Public-Private Partnership Policy Casebook/Maryland Purple Line

This case study reviews the Maryland Purple Line Project. The casebook is a product of the George Mason University graduate program, as an assignment for the Public-Private Partnership Policy course under Dr. Jonathan Gifford. It explores case elements such as key actors, event timeline, risks, financial and institutional structures, policy issues, and takeaways.

Summary
The Purple Line is a 16-mile light-rail line extending from New Carrollton in Prince George's County to Bethesda in Montgomery County and is currently under construction. It is a public-private partnership (P3), between the state of Maryland and concessionaire Purple Line Transit Partner, which is responsible for design, build, finance, operate, and maintain the project. The project is expected to cost over $2 billion, making it the largest transportation P3 in the U.S. according to Gov. Larry Hogan.

While the Purple Line was originally scheduled to open in 2022, a series of issues have pushed that back. The primary issue is that the main construction contractor terminated their contract, citing the cost overruns as the reason. Despite this major issue, the P3 agreement has been preserved with a new design-builder to be soon announced.

Public Actors

 * Maryland Department of Transportation (MDOT) and Maryland Transit Administration (MTA) are the public owners.

 * The National Capital Region Transportation Planning Board- The federal government's planning agency for the National Capital Region
 * Governor O’Malley- In 2008 his administration allocated $100 million to design the Purple Line within the six-year budget. In 2009 he endorsed a $1.52 billion version of the project.
 * Governor Hogan- Current governor of Maryland, succeeding Gov O’Malley.

Private Actors

 * Purple Line Transit Partners, LLC (PLTP)- Private partner, consisting of Meridiam and Star America.
 * Fluor- Texas based construction company. Originally the lead contractor to design and build the Purple Line, but left the project in September 2020 over delays which caused cost overruns. The company reached a $250 million settlement in 2021.
 * Maryland Transit Connectors, Maryland Purple Line Partners, and Purple Plus Alliance- The three other consortium that “short-listed” to bid on the project

Timeline of Events
2001 - 2005: Beginning of the endorsement for the 14-mile that the Purple Line Project would start construction on. A nonprofit named “Purple Line NOW” formed as a union to support the Purple Line plan.The National Environmental Policy Act was kicked off by the Federal and Maryland transit officials. This was for the Purple Line which would cause multiple alternatives and design options for the project.

2007: The Maryland Governor and Secretary of Transportation officially reverted the project’s name to be called “Purple Line”.

2008: Governor O'Malley put $100 million towards the design of the Purple Line. This amount was created for a six-year budget.

The Purple Line was endorsed by the Washington Post’s editorial board.

2009: Two major wins for the project: key backing by then Governor O’Malley and approval by the National Capital Region Transportation Planning Board.

2013: Reported by the Washington Post, there was $200 million that went to Maryland to buy private property in the Purple Line area.

O'Malley committed another $400 million toward construction. He stated the line needs to be built and operated from a public-private partnership.

There was a legal agreement signed between Maryland and Columbia Country Club. This was to ensure that the shift for the purple Line alignment would protect the golf course. Due to this, the club agreed to take legal action.

2014: Approval was earned for the purple line. This was granted by the Federal Transit Administration.

Capital Crescent Trail and a group of Chevy Chase residents filed a lawsuit against the Purple Line construction due to it hurting the environment during construction.

The Purple Line project is now costing $2.45 billion.

2015: Governor Hogan endorsed the Purple Line after meeting with county executives. However, Hogan decreased the cost of the project by cutting some provisions (environmentally friendly building materials, shortened platforms, and reduced the number of elevators).

2016: “Maryland’s Board of Public Works awards a 36-year, $5.6 billion contract to Purple Line Transit Partners — a partnership of Meridiam, Star America and Fluor Enterprises — to design, build, operate and maintain the new line.”.

2019: The completion date gets pushed to 2023 by the Purple Line Transit Partner. It increases the overall cost by $275 million.

The project gets hit with a second lawsuit.The first section of the Purple Line track is installed in Lanham.

The Maryland transportation officials said that the project will open in different sections, with some in operation by the end of 2022.

Early 2020: The purple line gets hit with a third lawsuit from Friends of the Capital Crescent. The Trail and Chevy Chase residents’ case is dismissed. While all this was happening, the Purple Line Transit Partners asked for an extended five months with $187.7 million. They needed this extra funding to build a crash wall where the Purple Line is supposed to run adjacent to CSX  trains. There was a post report estimate that the overall Purple Line cost overrun would end up at $526 million with a delay of about 17 months.

Late 2020: Fluor Enterprises, Lane Construction, and the Traylor brothers told MTA they would cease construction due to low funding costs. 60 days given or the partnership would be terminated. They were looking for a new state agreement, and in the agreement they laid off 700 workers. The state takes over due to PLT partners claiming $800 million in unpaid costs. $2 million sought from Montgomery County for businesses that were affected by construction. $250 million settlement for the continuation of the Purple line. Settlement approved with $100 million coming from the state's transportation fund, construction continues.

2023: Anticipation of when the Purple Line Project will be finished and complete.

Project Procurement
The Purple Line was procured as a public-private partnership. The concessionaire is responsible for design, build, finance, operate, and maintain the project. The Maryland state government hired a group of private sector firms that goes by the name Purple Line Transit Partners. The group of firms composes of Meridiam, Fluor Corporation, Star America, CAF and Alternate Concepts.

On March 2, 2016, Governor Hogan announced the chosen team for $3.3 billion over 30 years of operation and maintenance the a light-rail Purple Line in the Washington suburbs. On April 2016, Maryland’s Board of Public Works awards a 36-year, $5.6 billion contract to Purple Line Transit Partners.

Under the terms of this agreement, the private partners will accept risk from MDOT and MTA in exchange for availability payments, and they will complete five third-party projects that will complement the completed Purple Line.

Under the state’s plan, the Maryland Transit Administration would own the Purple Line and set fares. The private companies would design and build it over about five years, and then operate and maintain it over 30 years. The private team would finance some of the construction costs. The state would pay off the private sector’s debt service costs over time and pay the private team monthly for operating and maintenance costs.

On December 7, 2015, four teams composed of major American and international firms submitted their bids to realize the project. The four consortiums of private companies bidding on the project are: Maryland Purple Line Partners, Maryland Transit Connectors, Purple Line Transit Partners and Purple Plus Alliance :

 * "Maryland Purple Line Partners" composed of Vinci Concessions, Walsh Investors, InfraRed Capital, Alstom and Keolis,
 * "Maryland Transit Connectors" composed of John Laing Investments, Kiewit Development Company, Edgemoor Infrastructure & Real Estate and RATP Dev,
 * "Purple Line Transit Partners" composed of Meridiam, Fluor Corporation, Star America, CAF and Alternate Concepts,
 * "Purple Plus Alliance" compose of Macquarie Capital Group, Skanska, Kinki Sharyo and Transdev.

On April, 2016, Maryland’s Board of Public Works awards a 36-year, $5.6 billion contract to Purple Line Transit Partners (PLTP) to design, build, operate and maintain the new line.

Project Description
The Purple Line is a proposed 16-mile light-rail line extending from New Carrollton in Prince George's County to Bethesda in Montgomery County. The Purple Line project is designed to provide faster and more reliable east-west transit than buses, rejuvenate older inner-Beltway communities around its 21 stations, and connect Maryland's Metro lines with neighborhoods and Amtrak and MARC commuter rail stations.

The corridor is located along the Capital Beltway near Washington, D.C., in a densely populated area with continued commercial, institutional, mixed-use, and residential development. The Project will include five major activity center stations (Bethesda, Silver Spring, Takoma-Langley Park, College Park, and New Carrollton) and 16 smaller stations that serve residential communities, commercial districts, and institutional establishments. It will also provide direct connections to three branches of the existing Metrorail system, all three MARC commuter rail lines, and Amtrak’s Northeast Corridor line.

The Purple Line Project is primarily intended to address severe traffic congestion and improve mobility for transit-dependent neighborhoods, providing for an east-west transit option to complement the north-south option currently available through the existing Metrorail system and MARC lines. The Project is expected to reduce travel times by approximately 40% and eliminate approximately 17,000 auto trips per day.

Project Cost
The project cost is about $2 billion. It will be paid for out of several different sources, including federal grants, state transportation dollars and local contributions. The total cost to the state over the next 35 years will be $5.5 billion because of the payments Maryland must make to the private sector consortium hired to build, operate, finance and maintain the Purple Line. (Di Caro, 2017)

=== Financial Structure === The Purple Line Transit partners have secured their financing for this project. They were able to lock in $85 million towards the department of transportation. This happened through the Transportation Infrastructure finance innovation act loan.

Due to the FTAs Capital Investment Grant contribution, they were able to get 50% of the $162 million that was needed for the cost of the Purple Line Project.

The other half of this project costs are being funded by: Approved transit income tax, City of Indianapolis, Department of public works, and some other Federal Highway Administrations and FTA sources once this has all been set and confirmed, IndyGo would like to have some contractors bid on different construction packages they are offering on this project.

Funding Structure
The Purple Line budget for this project was projected at $2.6 billion. There were many funding sources that contributed to this overall project. Being that there were a number of funding sources, they are outlined below to show the amount disbursed among them all. This project received a direct loan from TIFIA credit assistance. They will need to repay this through September 2050. This agreement was signed on June 14, 2016. Currently the financial status is that of the repayment of the TIFIA loan. The payback of the loan will go through a 29-year maturity with a final maturity at about 2050.

Contract Type
The Purple Line project is a design, build, operate, maintain, and finance DBFOM public-private partnership between the public sector Maryland Department of Transportation (MDOT) and Maryland Transit Administration (MTA) and the private partner, Purple Line Transit Partners, LLC (PLTP). The contract for the operation and maintenance period is 30 years.

Risk Details

 * The financial risk for this project is shared by both the owner ( The Maryland Department of Transportation (MDOT) and the Maryland Transit Administration (MTA)) and the Concessionaire (Purple Line Transit Partners).
 * The risks in the design and build phase are assumed by differently by the key actors actors. The Owner is responsible for permits and permitting construction, while the Concessionaire is responsible for making sure the construction is done on time and at planned cost.
 * A force majeure is a risk for both parties. Events during the Design-Build Period both parties assume some risk. If an event occurs during the operations and maintenance period it could impact one or both parties. The Owner is at risk if it impacts ridership, while the Concessionaire is at risk if it impacts their operations and maintenance.
 * The Owner holds most of the risks for ridership. The Owner pays PLTP for the operation and maintenance, and sets the fare prices. This means that a decrease in ridership would impact the Owner’s costs.

Future Development
In November 2020, The Maryland Transit Administration (MTA) procured a second P3 to finish the work on its troubled Purple Line project, should the state not reach an agreement with the Meridiam-led Purple Line Transit Partners (PLTP) concessionaire. A second P3 contract would help the state with the remaining $1 billion in work that needs to be completed before the line reaches commercial operation. A second P3 would also see the company operate and maintain the 16-mile railway. (Zachary, 2020)

The Purple Line is currently under construction. Construction has been stalled since Fluor, the main construction company, withdrew from the project amidst contract dispute. The dispute has been settled and the partners are currently looking for a new construction company and plan to have one in place by early 2022.

Project Termination and Delays
On June 23 2020, PLTP formally notified the Maryland Transit Authority and Maryland Department of Transportation of its intent to terminate the partnership in 60 days, citing the cost overruns as the reason. (Zachary, 2020)

The joint venture has stopped construction, seemingly proceeding with plans to quit the light-rail project over $800 million in disputed cost overruns. The remaining 16 miles of unfinished construction includes tunnels and roadways through Prince George’s and Montgomery counties.

The Maryland Transit Administration (MTA), Meridiam-led Purple Line Transit Partners (PLTP) and the banks behind the debt package, have signed forbearance agreements to not withdraw from the deal until 30 October 2020. (Zachary, 2020)

The decision to retain the status quo creates a last-gasp opportunity for the Maryland Department of Transportation (MDOT) and Purple Line Transit Partners to reach agreement on the nearly $800 million in cost overruns. (DePuyt, 2020)

Montgomery County seeks $2 million from the state to aid businesses affected by Purple Line construction. Maryland and the Purple Line consortium reached a $250 million settlement to continue construction. Maryland's Board of Public Works approves the settlement, with a $100 million initial payment coming from the state's transportation fund. All litigation that could delay the project is settled. Maryland is overseeing day-to-day work but will solicit bids for new project managers.

Issue 1
In 2016 right after the Purple Line project was started, a lawsuit was brought by opponents of the project. In August 2016, US District Court judge Richard Leon ordered a new forecast on the light rail’s ridership to account for the decreasing ridership on Metro trains. After Leon's report of the new forecast, the Maryland Department of Transportation appealed the decision and halted all construction. After eleven months, a three-judge panel of the US Circuit Court of Appeals allowed for construction to continue, and the project broke ground in August 2017. (Wester, 2021)

 * Lessons Learned

 * The lawsuit was brought by opponents of the project. Communication and collaboration with the public or stakeholders are important to reduce the possibility of potential lawsuits.
 * It is important to have a solid ridership forecast with informative data at an early planning stage to sustain possible scrutiny and challenge the forecast.

Issue 2
Because of the delay, the projected operation date was pushed further and overrun fees started adding up. In June 2020, the partnership of construction firms wrote a letter saying they would stop work on the Purple Line because MTA would not pay added construction costs. After failed negotiations and lawsuits, the construction firms quit construction and walked off the job in September 2020. (Wester, 2021)

Lessons Learned

 * It is important the contract includes the responsibility of each part to handle the risk of delay. Development of scenarios of project delays with associated costs/resources to be allocated to which party would be helpful to mitigate the risk resulting from project being delayed.

Issue 3
PLTP is expected to finalize its decision for the new design-builder later in 2021.Some work has continued under the management oversight of MDOT MTA. The works mainly consist of underground and overhead utility relocation that is necessary for the new design-builder to resume full construction activities. (Wester, 2021)

Lessons Learned

 * It is good that the MDOT and MTA picked up the works and prepared for the project to get back on track. The underground and overhead utility relocation are preparation works for the project. The cost and ability for the relocation works can be reasonably handled by the state DOT.

Takeaways

 * The Purple Line is a 16-mile light-rail line extending from New Carrollton in Prince George's County to Bethesda in Montgomery County and is currently under construction (Donovan, 2019).
 * The Purple Line Project is primarily intended to address severe traffic congestion and improve mobility for transit-dependent neighborhoods. The Project is expected to reduce travel times by approximately 40% and eliminate approximately 17,000 auto trips per day.
 * The project is expected to cost over $2 billion, making it the largest transportation P3 in the U.S. according to Gov. Larry Hogan (Donovan, 2019).
 * It is a public-private partnership (P3), between the state of Maryland and concessionaire Purple Line Transit Partner, which is responsible for design, build, finance, operate, and maintain the project for 30 years.
 * The Purple Line Transit partners locked in $85 million through the Transportation Infrastructure finance innovation act loan and got 50% of the $162 million from the FTAs Capital Investment Grant contribution. The other half of this project costs are being funded by various sources such as approved transit income tax, City of Indianapolis, Department of public works, and some other Federal Highway Administrations and FTA sources.
 * On June 23 2020, PLTP formally notified the Maryland Transit Authority and Maryland Department of Transportation of its intent to terminate the partnership due to over $800 million in disputed cost overruns. (Zachary, 2020)
 * In November 2020, The Maryland Transit Administration (MTA) procured a second P3 to finish the work on its troubled Purple Line project. A second P3 contract would help the state with the remaining $1 billion in work that needs to be completed before the line reaches commercial operation. A second P3 would also see the company operate and maintain the 16-mile railway. (Zachary, 2020)

Discussion/ Questions

 * The project encountered termination and delays. What contract type or funding mechanisms can be modified to make the project move forward?
 * There were many controversies with this project. Did you feel one sector was more “at fault” than the other?
 * Do you think that the complications from this project will impact the development of other P3s in the future? Particularly public transit P3s.


text: Tongan/Printable version

title: Tongan/Printable version


text: Applicable Mathematics/Printable version


text:
Talk:Public International Law/Approaches/Feminism & Queer Theory

Review: May 29, 2023
Dear Verena & Tamsin,

I agree with the others that this is a great chapter and what I particularly like are the numerous example from international legal practice that you mention. However, I have the suspicion that the chapter is getting far too long. Furthermore, I felt that the structure is not yet ideal and that there are multiple repetitions that could be avoided, for example by introducing them at the very beginning and then only referring back without spelling out again (perceived neutrality, hierarchies, but also intersectionality etc.)

Best, Raffaela --Raffaela Kunz (discuss • contribs) 15:36, 29 May 2023 (UTC)

Review: May 21, 2023
Dear Verena, Dear Tamsin,

Congratulations on doing a stellar job with this chapter! I agree with Max's impression that the chapter veers a bit too much into a general introduction and could use some more direct connections to international law, some examples of doctrines etc that are being questioned by feminist and queer theory. Maybe the parts that are more of a general introduction to feminist and queer theory could be moved into advanced knowledge boxes so that they aren't lost entirely and will at least stay on Wikibooks. I have added some comments with suggestions for Global South / TWAIL / non-white feminists you could cite more and I also did some language editing. Regarding the required knowledge: maybe you could link to the general introduction to the 'Approaches' chapter, which has yet to be written. Let me know if I can assist you in any way in finishing this chapter. I'd be happy to discuss the things I wrote in the comments in case they are unclear.

Warmly, Sué Sué González Hauck (discuss • contribs) 08:18, 21 May 2023 (UTC)

Review: May 19, 2023
One of the strengths of your chapter lies in its ability to introduce feminist and queer approaches to international law in a manner that is accessible to students. You effectively present the fundamental concepts associated with these approaches, allowing students to grasp the concepts with clarity and ease. This aspect is particularly valuable, as it enables students to develop a foundational understanding of the approaches.

However, at certain points, the chapter veers into a more general introduction to feminist and queer studies, which exceeds the scope of this textbook. While this broader context may be informative, it is essential to maintain a focus on the application of these approaches to international law within the given space constraints. I would recommend that the chapter strikes a balance by presenting the basic principles of the approaches and then honing in on their specific relevance to international law.

Related to this, it is worth noting that your chapter is quite lengthy. This creates an imbalance between your chapter and the other chapters on approaches to international law. While all the information included is crucial, we will need to shorten it – in my opinion – by 1,500 to 2,000 words for publication in the book.

You will also find some comments in your chapter in which I elaborate on something more specifically. To view these comments, just open your chapter page and click on "Edit" in the top-right menu bar.

Some minor things:
 * Some parts of the chapter are still missing. It would be great if you could finish the chapter by mid-June at the latest. The sooner you finish, the better we can review your chapter and the more time you have to use our comments to improve the chapter. Be prepared to edit your chapter at very short notice if you hand it in late.
 * There are some issues with the formatting of the footnotes, which are not always consistent with the OSCOLA citation style. To ensure the chapter is fully compliant with OSCOLA, you should review the formatting of the footnotes and make necessary corrections.
 * Note also that the following parts are still missing: required knowledge, learning objectives, further readings, conclusion
 * You could add some links to other chapters of the textbook.
 * Note that I have made some linguistic improvements to the text

--Max Milas (discuss • contribs) 11:05, 19 May 2023 (UTC)

Review 2 November 2021
Dear Tamsin and Verena, the outline and first paragraphs already look fantastic and I am really looking forward to seeing how the chapter will develop. One thing that came to my mind is that I am not quite sure what the function of the specific section highlighting individual works of feminist and queer theory will be. Wouldn't it be better to discuss the works you want to showcase in the context of the specific issues they are concerned with and also highlight essential works in the 'further readings' section? I also think that the chapter could benefit from clearer explanations of basic concepts right at the beginning of the chapter, e.g. intersectionality, bias, structural discrimination, maybe heteronormativity and maybe also explain a bit more how feminism and queer theory relate to each other. In any case, this is going to be such an important contribution to the book. Thank you for agreeing to write this important chapter! Sué Sué González Hauck (discuss • contribs) 07:50, 2 November 2021 (UTC)

Life Orie
Law that protect south african citizens against gender based violence

Life Orientation
Law that protect south african citizens against gender based violence


text:
Wikibooks:Requests for import/Archives/2021/September

Templates in Carnatic Music Templates
Can you import these from Wikimedia Commons becuase I need them for a Wikibook I'm making. Faster than Thunder (discuss • contribs) 23:09, 14 September 2021 (UTC)
 * ✅ importing Template:Jantai and Template:Jantai descent. Please check.--Jusjih (discuss • contribs) 02:22, 27 September 2021 (UTC)


text:
Talk:Public International Law/Sources of International Law/Customary Law

Review: May 21, 2023
Dear Victor,

Thank you also from my side. I agree with everything Max and Raffaela said, and I have also added some comments in the text. I also think that the role of custom with respect to the states that became 'newly independent' in the 1950s and 1960s is a lacuna in the text, as well as the role of UNGA resolutions and 'instant custom' etc. Both of these topics overlap, and including them is a great opportunity to cite more women and voices from the Global South, which is another thing that could be improved in the chapter overall. Besides Chimni's article and other texts I have suggested in the comments, here are some more suggestions for contributions you could work into your chapter:
 * Arajärvi, Noora, The Changing Nature of Customary International Law (she has also published several articles on customary international law)
 * Deplano, Rossana, The Riddle of Custom
 * Daugirdas, Kristina, International Organizations and the Creation of Customary International Law
 * Meguro, Maiko, Customary International Law and Non-State Actors
 * Okubuiro, Joycelin Chinwe, Application of Hegemony to Customary International Law: An African Perspective
 * Sreenivasa Rao, Pemmaraju, The Identification of Customary International Law

Warmly,  Sué

Sué González Hauck (discuss • contribs) 16:26, 21 May 2023 (UTC)

Review: May 18, 2023
Dear Victor, Thanks for the great chapter! I agree with Max' comments below and added some in-text comments. Just a few suggestions here:

-In the introduction, it would be nice to mention that custom might be of renewed relevance in times of crisis of classic treaty making (if you think that this is the case). - Also in the introduction: roadmap (we will circulate an authors checklist next week). - I think the "who creates custom" might in parts be a bit repetitive or at least too long. Under B. I.1. you say in short what you will explore in depth under C. Possible to shorten? - On the other hand, what I am missing is a small section on "who is bound" by custom. I think the persistent objection doctrine definitely belongs to the main text (and not advanced knowledge); also the "clean slate" debate for newly emerging states should be mentioned, I suppose. - Also very interesting is the fact that when it comes to custom, law-making might happen through law-breaking, with grey zones often emerging (example immunities). Maybe this could be mentioned somewhere. - I also wonder whether the discussion about "specially affected states" needs some more explanation. Maybe you could give an example? E.g. law of the sea where states with sea access have more relevance than states such as Switzerland. - In the section on opinio juris, I think it would be nice to mention that non-binding law such as GA resolutions through CIL can "harden" into binding law.

Best, Raffaela --129.132.99.69 (discuss) 10:26, 18 May 2023 (UTC)

Review: May 12, 2023
Overall, this chapter on customary international law provides an excellent resource for students looking to deepen their knowledge of this important area of law. With clear and accessible language, detailed analysis of relevant ICJ decisions, and text boxes providing additional context and insight, this is a valuable tool for anyone seeking to better understand the complexities of customary international law.

The language used in the chapter is simple and easy to understand, making it accessible to students who are new to the subject. You have done an excellent job of explaining this complex legal concept in an approachable manner, which is a real strength of the chapter. In particular, I was impressed by the detailed analysis of relevant ICJ decisions, which provides a valuable resource for students looking to deepen their understanding of the topic.

You have made excellent use of text boxes throughout the chapter, which provide additional context and insight into details of customary law. This is an excellent way of engaging with students and making the material more accessible.

There are some issues with the formatting of the footnotes, which are not always consistent with the OSCOLA citation style. To ensure the chapter is fully compliant with OSCOLA, you should review the formatting of the footnotes and make necessary corrections.

Note also that the following parts are still missing: further readings, conclusion

You could add some links to other chapters of the textbook.

Note that I have made some linguistic improvements to the text. Max Milas (discuss • contribs) 19:35, 12 May 2023 (UTC)

Review 2 November 2021
Dear Victor, Thank you for accepting to write this important chapter. I am really looking forward to seeing how it develops. As I mentioned in more detail in the comments, I think the introductory section needs to be carefully rearranged in order to be more easily accessible for students. For your further work on the chapter, I have some suggestions for topics on which you could focus: 1) the idea of instant custom and the role of UNGA resolutions in the development of customary law, especially in the debates between the Global South and Global North in the 1960s and 1970s 2) non-State actors in the formation of customary law 3) critiques that the ICJ mainly refers to its own previous judgments as evidence for CIL 4) relationship between treaty rules and customary law

Some important works written by women and/or scholars located in the Global South, which I would strongly encourage you to incoporate into your chapter, include: B.S. Chimni, Customary International Law: A Third World Perspective; Joycelyn Chinwe Okibuiro, Application of Hegemony to Customary International Law: An African Perspective; Noora Arajärvi, The Changing Nature of Customary Law; Rossana Deplano, The Riddle of Custom; Malgosia Fitzmaurice, Customary Law, General Principles, Unilateral Acts; Pemmaraju Sreenivasa Rao, The Identification of International law: A Process that Defies Prescription; Galindo, G.R.B., and C. Yip, “Customary International Law and the Third World: Do Not Step on the Grass”, Chinese Journal of International Law, 16 (2017), No. 2, pp. 251-270; Anthea Roberts, Traditional and Modern Approaches to Customary International Law Sué González Hauck (discuss • contribs) 08:31, 2 November 2021 (UTC)


text:
Managing enterprises with advanced ICT

Introduction
The purpose of this wikibook is to explain basic terms from the fields: informatics, information systems, system analysis, information technologies. Its primary learning objective is to prepare a student (a future manager) to assess, analyze, select, acquire, manage and maintain an information system for his/her company.

The target group of these selected chapters are students of management study programmes of business schools or applied science faculties.

Basic terms

 * A manager who want to manage their company with the support of information technologies should be familiar with basic terms such as:
 * Information system
 * Information technology
 * Information and communications technology
 * Enterprise software
 * Application software
 * Web application
 * Mobile application

Software and business models

 * A manager is often confronted which type of software to use. Which is better, proprietary or open-source?
 * See more:
 * Proprietary software
 * Open-source software
 * Outsourcing IT-related services is often a good choice for a manager, especially if there is no IT department within the company.
 * See more:
 * Managed services
 * Managed services

Types of information systems:

 * Each part of a company requires different type of an information system. The most common types of information systems are:
 * Management information system
 * Enterprise resource planning
 * Document management system
 * Customer relationship management
 * Human resource management system
 * Business intelligence
 * Business process management

Data & computing

 * When it comes to acquiring a software and hardware, a manager should decide whether to build their own IT / data center or lease already established one:
 * Cloud computing
 * Data center

IT strategy & processes

 * A manager's primary responsibility is to establish a technology strategy for their organization:
 * Technology strategy
 * A modern company includes IT related activities and services such as Service desk, Incident management and similar. A set of good practices was developed and it can be reused also for your organization:
 * ITIL
 * ITIL

Business & requirements analysis

 * Requirements gathering and analysis is one of the first steps of the company's digital transformation:
 * Requirements analysis
 * Software requirements specification

Business continuity and IT Security

 * A manager's primary responsibility is to ensure the company's continuous delivery of products or services at pre-defined acceptable levels following a disruptive incident:
 * Business continuity
 * Protecting computer systems from information disclosure, theft or damage:
 * Computer security
 * Computer security

title: Managing enterprises with advanced ICT


text: Expert Systems/Printable version

title: Expert Systems/Printable version


text:
User talk:Belomaad

Hello, pages here are supposed to be parts of a book. What you are editing looks like a strangely named single page - please explain what it is for. Additionally, it seems very unlikely you created this material from scratch, particularly the diagrams, and I suspect you copied it from somewhere else. If so, please provide the source so it can be checked for copyright compliance. Thanks. QuiteUnusual (discuss • contribs) 16:08, 3 November 2021 (UTC)

 * This chapter is part of a book about History according to the Hungarian curriculum in English. I am not sure how to add this chapter into a book. I created other chapters but also couldn't add them for the same reason. The text was created from scratch with the help of sources in Hungarian. The 2 diagrams(timeline and pyramid) are own work. Belomaad (discuss • contribs) 20:30, 3 November 2021 (UTC)
 * There are no other chapters, and you've made no other edits here. QuiteUnusual (discuss • contribs) 09:00, 4 November 2021 (UTC)
 * As I explained before, I couldn't add the other chapters since I don't know how to do so. Belomaad (discuss • contribs) 22:05, 5 November 2021 (UTC)
 * Hello Belomaad. It's been about a week since the query tag has been added. I'm reluctant to delete the page as I've done my own investigation and haven't found any other sources that come near to your work. Shall I move this page under your userspace to prevent any deletions? —Atcovi (Talk - Contribs) 04:20, 16 November 2021 (UTC)
 * Yes, according to our policy, this work must be moved as a book page or a user draft. JackPotte (discuss • contribs) 17:15, 21 November 2021 (UTC)
 * How can I create a book? Belomaad (discuss • contribs) 17:17, 21 November 2021 (UTC)
 * Hello, actually there is a book for that: Using Wikibooks. JackPotte (discuss • contribs) 20:23, 3 December 2021 (UTC)

title: User talk:Belomaad


text:
Talk:PostgreSQL

Hint
As of November/December 2021, I plan to work on extensions to the book. --Kelti (discuss • contribs) 20:59, 3 November 2021 (UTC)

title: Talk:PostgreSQL


text:
Signetics 2650 & 2636 programming

A guide to programming the family of video game consoles based on the Signetics 2650 microprocessor and 2636 Programmable Video Interface

 * Introduction

Reference

 * Console Hardware
 * System architecture ― Clock generation ― Processor ― Memory map ― PVI ― Sound circuits ― Hand-controller circuits

 * 2650 processor
 * Registers ― Program Status Word ― Reset ― Interrupts ― Instruction set ― Addressing modes

 * 2636 programmable video interface
 * PVI registers ― Objects ― Score ― Background grid ― Sound ― Analogue to digital conversion

Tutorials - system elements

 * Getting started  WinArcadia ― Assembler ― Debugger
 * Objects  Programming objects
 * Score  Score programming ― WinArcadia PVI monitor & memory editor
 * Programming colours  Colour registers ― Colour codes
 * Background grid  Grid programming ― Bar extensions
 * Sync to VRST  Testing VRST ― Moving an object
 * Sync to Object completion  Detect object completion ―  Reprogram objects ― Creating shapes, WithCarry, and Rotate
 * Object collision
 * Sound  Sound
 * Keypad and console buttons
 * Joysticks
 * Interrupts

Tutorials - game elements

 * Speed and animation
 * Sound effects
 * Music

Tutorials - programming techniques

 * BCD arithmetic  BCD  ―  Decimal adjust  ―  Incrementing the score
 * Indexed branching  BXA and BSXA  ―  Creating a state machine

How did they do that?

 * Leapfrog screen programming
 * Super Space Interton game, specifically the terrain
 * Games that use interrupts

Tutorial code

 * Tutorial code - Contains the hardware definitions
 * Getting started - An introduction to using WinArcadia
 * Objects
 * Score
 * Programming colours
 * Background grid
 * Sync to VRST
 * Sync to object completion
 * State machine
 * Interrupts

Appendices

 * Glossary
 * Bibliography
 * Analogue TV
 * 2650 cheat sheet
 * 2636 cheat sheet
 * Background worksheet
 * Development systems
 * WinArcadia
 * Pi2650
 * PVI audio frequency chart
 * Contributions
 * Welcome — Local manual of style — Wiki snippets — Contributors

title: Signetics 2650 & 2636 programming


text:
Signetics 2650 & 2636 programming/Programming colours

Tutorial — Programming colours
This family of consoles have a very limited palette of colors to work with. The PVI has three digital (i.e. either on or off) colour signals that are connected to the red, green and blue inputs of the PAL encoder. This limits the system to a palette of eight colours: black, red, green, blue, cyan, magenta, yellow and white.

This seems simple at first sight, but is complicated by two other signals that can affect the colour on the display:
 * the $\overline{OBJ/SCR}$ output of the PVI which goes low whenever an object or a score digit is being displayed. Remember: SCR is score, not screen!
 * bit 5 of the 74LS138 'effects' register.

''A further complication is that some consoles such as the Interton VC4000 use these signals to alter the brightness of the colour, while others use it to invert the colour. The rest of this page is applicable to the colour inversion method, specifically as implemented on the Voltmace Database.''

Hardware description

The three active-high colour inputs to the PAL encoder are connected directly to the active-low colour outputs of the PVI: $\overline{R}$, $\overline{G}$, $\overline{B}$.

The active-high INV input to the PAL encoder is derived from a wire-AND circuit comprising an open-collector transistor, the open-drain $\overline{OBJ/SCR}$ and a pull-up resistor. Either one of those devices can pull the invert input to a low logic level.

The $\overline{INVERT}$ signal is set by writing to bit 5 of the hex D-type flip-flop, 74LS378, at memory address $1E80. Writing a 1 to that bit causes the transistor to turn on, and pull the INV input to the PAL encoder to a logic 0 irrespective of the state of $\overline{OBJ/SCR}$.

Registers
All the colour information is controlled by four registers, three in the PVI and one logic chip. Note that these registers are all write-only. It is up to the programmer to keep track of what is in them.

$1E80 'Effects' register
The other bits in this register are used by the audio circuitry.

$1FC6 Background and screen — enable and colours
If Background Enable is set to zero, both the screen and background grid are output from the PVI as '111'.

If the background grid is not used for graphics, the registers that define it, $1F80 - $1FAC, may be used for variable storage. They are hidden on the display by setting background and screen to the same colour.

Colours
If you find the hardware description hard to follow with the multiple inversions, you aren't alone. All you really need to do is use the table below when programming colours.

The score colour cannot be programmed independently; it is always the inverse of the colour programmed for the background.

Neither the object colours or the score colour are affected by the state of bit 5 of the 74LS138 'effects' register since the $\overline{INVERT}$ will be low while they are being displayed.

The $\overline{R}$ bit is used in some games such as Interton's Super Space as a screen-saver. While it is tempting to normally set the $\overline{G}$ bit to 0, it might be better to have it normally set to 1. In this way the colour codes are the same for objects, score, background and screen, and will be in negative logic, i.e. a 0 turns the colour on.

Code snippets
All the colours are set by these four registers: effects    equ $1E80 colours12  equ $1FC1 colours34  equ $1FC2 backgnd    equ $1FC6

It is a good idea to clear the effects register early on in your program. This will not only turn off the colour inversion, but will also turn off the audio. eorz   r0        stra,r0 effects Alternatively, as discussed above, the audio can be turned off and the colour inversion turned on so that all colours can be programmed with the same codes. lodi,r0 $20 stra,r0 effects Remember that the objects colours are always active low, so the RGB sequence 101 would appear as green, etc: lodi,r0 %00010101      ; XX  /  011     /   110 stra,r0 colours12      ;     / obj1 red / obj2 blue The background and screen colours depend on the state of the invert bit. When the invert bit is 0, their colours are always active high, so the RGB sequence 010 would appear as green, etc: eorz   r0        stra,r0 effects         ; invert bit = 0 lodi,r0 %00001110      ;  X / 100            /   1     / 001 stra,r0 backgnd        ;    / background red / enabled / screen blue Conversely, when the invert bit is 1, their colours are active low, so the RGB sequence 101 would appear as green, etc: lodi,r0 $20 stra,r0 effects        ; invert bit = 1 lodi,r0 %00001110      ;  X / 011            /   1     / 110 stra,r0 backgnd        ;    / background red / enabled / screen blue

Tutorial program
The code for this tutorial can be found at Signetics 2650 & 2636 programming/Tutorial code - programming colours. When this program is run, you should see a static screen that looks like this:

The fours objects are programmed in different colours. When the first row of objects have been displayed, the $\overline{B}$ bit in the effects register is set to one. This inverts the colour of the screen (yellow 110 becomes blue 001) and the background switches from black to white.

Notice that the objects and the score digits are the same above and below this transition. Also note that the score is the inverse of the colour programmed for the background.

Exercises

 * 1) Change the colours of the four objects to red, cyan, yellow and blue.
 * 2) Change the initial colour of the background grid to cyan.
 * 3) Change the colour of the score to magenta.


text:
Signetics 2650 & 2636 programming/Tutorial code

Tutorial code - Introduction
This section of the book contains all the code used in the tutorials.

The code below must be appended to every program before it can be assembled. It contains the equate direcitives that assign labels to all the hardware addresses and related constants. This is done both to avoid repetition and also to ensure consistent labelling of registers throughout this book.

Hardware definitions
This is a standard block of assembler directives that give names to constants and memory addresses of all the registers in the system. Notice that some addresses such as $1F00 have several labels. This allows the programmer to use the one most appropriate to the task being performed as an aid to making readable code. For example, if all the PVI registers are being initialised to 0, use pvi; if setting up object 1 shape and position use 'object1' etc.
 * HARDWARE DEFINITIONS
 * updated 11 Jan 2021

carrybit       equ $01 compare        equ $02 withcarry      equ $08 registerselect equ $10 intinhibit     equ $20 stackpointer   equ $07 sense          equ $80 flag           equ $40
 * PROCESSOR CONSTANTS

effects        equ $1e80
 * EFFECTS REGISTER

player1keys147c equ $1E88 ;player1 keypad, bits: 1,4,7,clear,x,x,x,x player1keys2580 equ $1E89 ;player1 keypad, bits: 2,5,8,0,x,x,x,x player1keys369e equ $1E8A ;player1 keypad, bits: 3,6,9,enter,x,x,x,x player2keys147c equ $1E8C ;player2 keypad, bits: 1,4,7,clear,x,x,x,x player2keys2580 equ $1E8D ;player2 keypad, bits: 2,5,8,0,x,x,x,x player2keys369e equ $1E8E ;player2 keypad, bits: 3,6,9,enter,x,x,x,x keymask123     equ $80     ;top row of keys keymask456     equ $40 keymask789     equ $20 keymaskc0e     equ $10     ;bottom row of keys console        equ $1E8B ;start and select buttons on console consolestart   equ $40 consoleselect  equ $80
 * BUTTONS

pvi         equ $1F00
 * PVI ADDRESSES AND CONSTANTS

object1     equ $1F00 shape1      equ $1F00 hc1         equ $1F0A ; hc = Horizontal Coordinate hcd1        equ $1F0B ; hcd = Horizontal Coordinate Duplicate hcb1        equ $1F0B ; hcb =  ditto  (Signetics datasheet name) vc1         equ $1F0C ; vc = Vertical Coordinate voff1       equ $1F0D ; voff = Vertical Offset vcb1        equ $1F0D ; vcb =  ditto  (Signetics datasheet name)

object2     equ $1F10 shape2      equ $1F10 hc2         equ $1F1A hcd2        equ $1F1B hcb2        equ $1FCB vc2         equ $1F1C voff2       equ $1F1D vcb2        equ $1F1D

object3     equ $1F20 shape3      equ $1F20 hc3         equ $1F2A hcd3        equ $1F2B hcb3        equ $1F2B vc3         equ $1F2C voff3       equ $1F2D vcb3        equ $1F2D

object4     equ $1F40 shape4      equ $1F40 hc4         equ $1F4A hcd4        equ $1F4B hcb4        equ $1F4B vc4         equ $1F4C voff4       equ $1F4D vcb4        equ $1F4D

grid        equ $1F80     ; background grid vbars       equ $1F80     ; vertical bar definitions hbars       equ $1FA8     ; horizontal bar extensions

objectsize  equ $1FC0

colours12   equ $1FC1     ; colour objects 1,2 colours34   equ $1FC2     ; colour objects 3,4 coloursback equ $1FC6     ; background grid colour / background grid enable / screen colour backgnd     equ $1FC6     ;     deprecated

pitch       equ $1FC7

scoreformat equ $1FC3 score12     equ $1FC8 score34     equ $1FC9

objectstatus equ $1FCA    ; object-background collision / object complete obj1complete equ $08 obj2complete equ $04 obj3complete equ $02 obj4complete equ $01 collisions  equ $1FCB     ; VRLE / inter-object collision vrle        equ $40 adpot1      equ $1FCC adpot2      equ $1FCD


text:
Signetics 2650 & 2636 programming/Tutorial code - programming colours

Tutorial code - Programming colours
This is the code for the tutorial Programming colours

org    0 reset_vector:                  ; the microprocessor starts here when the reset button is pressed bcta,un reset org    3 interrupt_vector:              ; interrupts shouldn't happen, but we set this just in case retc,un reset: ;initialise program status word, just to be sure! ppsu   intinhibit      ;inhibit interrupts cpsu   stackpointer    ;stack pointer=%000 cpsl   registerselect  ;register bank 0 cpsl   withcarry       ;without carry cpsl   compare         ;arithmetic compare
 * Tutorial Colours

eorz   r0        stra,r0 effects         ;initialise the 74LS378 stra,r0 objectsize     ;all objects size 0 bsta,un DefineObjects  ;define all objects bsta,un DefineGrid     ;define the grid lodi,r0 $67 stra,r0 score12 lodi,r0 $89 stra,r0 score34 lodi,r0 %00001110      ;  X / 000              /   1     / 110 stra,r0 backgnd        ;    / black background / enabled / yellow screen bsta,un Vsync0         ; make sure VRST hasn't started endless: bsta,un Vsync1         ; wait for VRST to start eorz   r0        stra,r0 effects         ; !invert = 0 stra,r0 scoreformat    ; 2 + 2 score digits at top  (see Tutorial......) lodi,r0 %00010101      ; XX  /  010        /   101 stra,r0 colours12      ;     / obj1 magenta / obj2 green lodi,r0 %00111000      ; XX  /  111        /   000 stra,r0 colours34              ;     / obj 3 black / 4 white bsta,un Vsync0         ; wait for VRST to end lodi,r1 1 bsta,un WaitObj        ; wait for object 4 to complete  (see Tutorial......) lodi,r0 $20 stra,r0 effects        ; !invert = 1 lodi,r0 3 stra,r0 scoreformat    ; 4 score digits at bottom bctr,un endless

; (see Tutorial......) DefineObjects: lodi,r3 $0A lodi,r0 $FF loopDS: stra,r0 shape1,r3-     ; create rectangular shapes stra,r0 shape2,r3 stra,r0 shape3,r3 stra,r0 shape4,r3 brnr,r3 loopDS lodi,r0 40             ; set their positions stra,r0 hc1 stra,r0 hcd1 lodi,r0 60 stra,r0 hc2 stra,r0 hcd2 lodi,r0 80 stra,r0 hc3 stra,r0 hcd3 lodi,r0 100 stra,r0 hc4 stra,r0 hcd4 lodi,r0 88 stra,r0 vc1 stra,r0 voff1 stra,r0 vc2 stra,r0 voff2 stra,r0 vc3 stra,r0 voff3 stra,r0 vc4 stra,r0 voff4 retc,un ; (see Tutorial......) DefineGrid: lodi,r0 $FF stra,r0 $1f80 stra,r0 $1fa4 lodi,r0 $FE stra,r0 $1f81 stra,r0 $1fa5
 * subroutine -  define shapes and position of all objects
 * subroutine -  define shapes and position of all objects
 * subroutine -  define background grid
 * subroutine -  define background grid

lodi,r3 $81 loopDG: lodi,r0    $80 stra,r0 $1f00,r3+ lodi,r0 $01 stra,r0 $1f00,r3+ comi,r3 $a3 bcfr,eq loopDG lodi,r0 $01 stra,r0 $1fa8 lodi,r0 $08 stra,r0 $1fac lodi,r0 $00 stra,r0 $1fa9 stra,r0 $1faa stra,r0 $1fab stra,r0 $1fa6 stra,r0 $1fa7 retc,un ; (see Tutorial......) Vsync0: tpsu   sense bctr,eq Vsync0         ; wait for Sense bit to clear retc,un Vsync1: tpsu   sense           ; wait for Sense bit to be set bctr,lt Vsync1 retc,un ; (see Tutorial......) WaitObj: loda,r0 objectstatus andz   r1        bctr,eq waitobj retc,un
 * subroutine - wait for vertical reset to clear
 * subroutine - wait for vertical reset to clear
 * subroutine - wait for vertical reset to set
 * subroutine - wait for vertical reset to set
 * subroutine - wait for object to finish
 * subroutine - wait for object to finish
 * enter with r1=mask for bit to be tested:
 * obj1=$08, obj2=$04, obj3=$02, obj4=$01


text: Category:Book:Signetics 2650 & 2636 programming


text:
Signetics 2650 & 2636 programming/Introduction

This book is a guide to programming a family of video game consoles based on the Signetics 2650 microprocessor and 2636 Programmable Video Interface. These consoles were manufactured and marketed in the late 1970s and early 1980s by numerous companies in Europe, Australia and New Zealand. They are largely software-compatible, though there are physical differences in the games cartridges. Some of the joysticks are self-centering while others are not. The audio effects and colour circuitry also vary slightly between clones.

This book will initially concentrate on the Videomaster / Voltmace Database, as that is the console I have to work with. When differences are documented from reliable sources, they will be discussed here where appropriate. I stress reliable as there seems to be a lot of badly sourced misinformation about these consoles on the web.

Readers should have some basic knowledge of assembler level programming, perhaps with processors of a similar vintage such as the 6502 or Z80. A little background in digital and analogue electronics would be helpful too. The glossary and bibliography will include basic information and links to further reading to fill in gaps in knowledge concerning these fundamentals.

This book starts with a description of the hardware of the console, and information about the microprocessor and programmable video interface. The intent is to keep these sections concise yet detailed so that they serve as a handy reference for programmers. This is followed by a series of tutorials showing how to program the various elements of the console so that eventually the reader will have enough knowledge to build their own games. Code for these tutorials will be found in the appendices. It is intended that this code will not only make it easy for the reader to gain hands-on experience, but will also provide useful chunks of code that can be built upon to create more useful programs. A second set of tutorials will delve further into code that combines these basic elements into something more interactive.

My objective in starting this book is to encourage the creation of new games for these consoles.


text:
Talk:Signetics 2650 & 2636 programming

Welcome to the Contributors lounge — where we discuss how to create an even better Wikibook.

To discuss the content of a specific page, please use the Discussion tab on that page.

Getting Started
This book is just starting as of November 2021. Fell free to jump in, contribute to Book pages and make comments about book pages on their Discussion page. Newcomers are encouraged to be bold. If you create a user account, you have your own sandbox where you can experiment with wiki markup.

Please try to follow the same general style already in use. In time a local style manual may develop for this book, but in the meantime there is the generic Manual of Style and more general Editing guideline.

If you are a novice programmer and have questions about programming that aren't already covered in the text, mention them on the most relevant Discussion page and it can be used as a seed for adding more content. Do remember though that Discussion pages are there for developing this book, not answering individual programming problems.

Don't forget to sign your comments on Discussion pages by typing four tildes at the end. Derek Andrews (discuss • contribs) 10:42, 4 November 2021 (UTC)

Book Title pitch
Not sure if this is needed, but I made a small cover image with accessible text by stringing together some templates for the TOC page. --Mbrickn (discuss • contribs) 16:47, 5 November 2021 (UTC)

 * Thank you, that's terrific and I have added it to the main page. Thanks also for your help with the other edits in the book. Derek Andrews (discuss • contribs) 00:01, 6 November 2021 (UTC)

Minor changes
Went through and changed shelving on most pages to use bookcat instead, since only one declaration is needed to shelve (Thus making only one place where shelving is needed to be updated should that change). If this was incorrect, let me know and I'll change it back!

Also updated the status of subpages to match the main TOC, and some other small formatting tweaks. --Mbrickn (discuss • contribs) 17:04, 5 November 2021 (UTC)

title: Talk:Signetics 2650 & 2636 programming


text:
User:Verena Kahl

Verena Kahl is a PhD candidate at the University of Hamburg writing her thesis on "A Human Right to Climate Protection". Her research particularly focuses on human and fundamental rights, international environmental law, climate change law, PIL schools of thought and feminist approaches to law. From 2015 to 2018 she served as junior lawyer at the Inter-American Court of Human Rights. She holds a scholarshrip from the Albrecht Mendelssohn Bartholdy Graduate School of Law and was a Fulbright Visiting Scholar at the Center for Human Rights and Global Justice (NYU) in fall 2022.

title: User:Verena Kahl


text:
Mechanics of Materials/Force-based Static Equilibrium/Free Body Diagrams

=3.1 Free Body Diagrams = In physics, we often employ free body diagrams (FBDs) to describe forces between objects and body forces. When thinking about the equilibrium of forces acting on an object/body, FBDs are a tremendous aid when used correctly. As shown in Figure 3.1, we can use a FBD on an object/body (the blue block on the inclined plane) to describe vectorial forces acting on the body (gravity, friction, and a normal force from the inclined plane). We can also describe action-reaction pairs of forces between objects using FBDs and remembering Newton's third law of motion. In the case of the block and inclined plane, we can envision one action-reaction pair as $$\vec{\mathsf{N}}$$ acting from the inclined plane against the blue block and the vectorial component from gravity with magnitude $$mg \cos\theta$$ acting from the block against the inclined plane. Another action-reaction pair would include the friction $$\vec{\mathsf{f}}$$ from the inclined plane acting on the block, along with the equal and opposite frictional force from the block acting on the inclined plane.

Identifying action-reaction pairs is key to understanding how the surrounding environment interacts with a structural object. When thinking of a free body as a particle or only having axial forces (i.e., forces going acting along an axis going through the centroid of a body), one might follow these steps:
 * 1) Define appropriate coordinate systems (e.g., XYZ, xyz).
 * 2) Draw vectors that describe the motion of the body -- usually none for stationary objects in statics/mechanics.
 * 3) Draw vectors for body forces acting on the body.
 * 4) Draw vectors for contact forces and  surface forces acting on the body (i.e., select the force acting on the body from action-reaction pairs)

For this course, we envision most of our structures as fixed, unmoving sets of beams, trusses, or pressure vessels. Yes, these structures might be portions of moving vehicles, but the loading due to the acceleration will usually be minimal, unless there is rotation with high angular velocity (e.g. centripetal acceleration $$r\omega ^2$$ where $$r$$ is a radial distance and $$\omega$$ is an angular velocity).

Body Forces or Contact Forces?
These questions explore the characteristics of body forces and contact forces. Go back to 3. Force-based Static Equilibrium.


text:
User talk:Irina Matweewa

Kausale Beziehungen I. Formulieren Sie Begründungen (Wenden Sie Konjunktionen, Subjunktionen, Textadverbien, Präpositionen an)

1. Was meinen Sie: Warum macht man Salz ins Kochwasser?

2. Was meinen Sie: Warum freut man sich wie ein Schneekönig?

3. Was meinen Sie: Warum gibt es in südlichen Regionen mehr Gifttiere als in Deutschland?

 II. Welche Redewendungen kennen Sie im Deutschen und wo haben sie ihren Ursprung? ''Recherchieren Sie in einem Lexikon der sprichwörtlichen Redensarten. Benutzen Sie bei Ihrer Erläuterung kausale Konnektoren.'' z.B. Man sagt im Deutschen "wie das Schwein ins Uhrwerk gucken", weil...

title: User talk:Irina Matweewa