text:
XML - Managing Data Exchange/A single entity

Introduction
In this chapter, we start to practice working with XML using XML documents, schemas, and stylesheets. An XML document organizes data and information in a structured, hierarchical format. An XML schema provides standards and rules for the structure of a given XML document. An XML schema also enables data transfer. An XSL (XML stylesheet) allows unique presentations of the material found within an XML document.

In the first chapter, Introduction to XML, you learned what XML is, why it is useful, and how it is used. So, now you want to create your very own XML documents. In this chapter, we will show you the basic components used to create an XML document. This chapter is the foundation for all subsequent chapters--it is a little lengthy, but don't be intimidated. We will take you through the fundamentals of XML documents.

This chapter is divided into three parts:
 * XML Document
 * XML Schema
 * XML Stylesheets (XSL)

As you learned in the previous chapter, the XML Schema and Stylesheet are essentially specialized XML Documents. Within each of these three parts we will examine the layout and components required to create the document. There are links at the end of the XML document, schema, and stylesheet sections that show you how to create the documents using an XML editor. At the bottom of the page there is a link to Exercises for this chapter and a link to the Answers.

The first thing you will need before starting to create XML documents is a problem--something you want to solve by using XML to store and share data or information. You need some entity you can collect information about and then access in a variety of formats. So, we created one for you.

To develop an XML document and schema, start with a data model depicting the reality of the actual data that is exchanged. Once a high fidelity model has been created, the data model can be readily converted to an XML document and schema. In this chapter, we start with a very simple situation and in successive chapters extend the complexity to teach you more features of XML.

Our starting point is a single entity, CITY, which is shown in the following figure. While our focus is on this single entity, to map CITY to an XML schema, we need to have an entity that contains CITY. In this case, we have created TOURGUIDE. Think of a TOURGUIDE as containing many cities, and in this case TOURGUIDE has no attributes nor an identifier. It is just a container for data about cities.

Exhibit 1: Data model - Tourguide

XML document
An XML document is a file containing XML code and syntax. XML documents have an .xml file extension.

We will examine the features & components of the XML document.

 * Prologue (XML Declaration)
 * Elements
 * Attributes
 * Rules to follow
 * Well-formed & Valid XML documents

Below is a sample XML document using our TourGuide model. We will refer to it as we describe the parts of an XML document.

Exhibit 2: XML document for city entity

Prologue (XML declaration)
The XML document starts off with the prologue. The prologue informs both a reader and the computer of certain specifications that make the document XML compliant. The first line is the XML declaration (and the only line in this basic XML document).

Exhibit 3: XML document - prologue

xml  =   this is an XML document

version="1.0"  =   the XML version (XML 1.0 is the W3C-recommended version)

encoding="UTF-8"  =   the character encoding used in the document - UTF 8 corresponds to 8-bit encoded Unicode characters (i.e. the standard way to encode international documents) - Unicode provides a unique number for every character.

Another potential attribute of the XML declaration:

standalone="yes"  =   the dependency of the document ('yes' indicates that the document does not require another document to complete content)

Elements
The majority of what you see in the XML document consists of XML elements. Elements are identified by their tags that open with < or  or />. The start tag looks like this:, with a left angle bracket (<) followed by the element type name, optional attributes, and finally a right angle bracket (>). The end tag looks like this:, similar to the start tag, but with a slash (/) between the left angle bracket and the element type name, and no attributes.

When there's nothing between a start tag and an end tag, XML allows you to combine them into an empty element tag, which can include everything a start tag can: . This one tag must be closed with a slash and right angle bracket (/>), so that it can be distinguished from a start tag.

The XML document is designed around a major theme, an umbrella concept covering all other items and subjects; this theme is analyzed to determine its component parts, creating categories and subcategories. The major theme and its component parts are described by elements. In our sample XML document, 'tourGuide' is the major theme; 'city' is a category; 'population' is a subcategory of 'city'; and the hierarchy may be carried even further: 'males' and 'females' could be subcategories of 'population'. Elements follow several rules of syntax that will be described in the Rules to Follow section.

We left out the attributes within the  start tag — that part will be explained in the XML Schema section.

Exhibit 4: Elements of the city entity XML document

Element hierarchy

 * root element -   This is the XML document's major theme element. Every document must have exactly one and only one root element. All other elements are contained within this one root element. The root element follows the XML declaration. In our example,  is the root element.

 * parent element -   This is any element that contains other elements, the child elements. In our example, is a parent element.

 * child element -   This is any element that is contained within another element, the parent element. In our example, is a child element of.

 * sibling element -   These are elements that share the same parent element. In our example, , ,, , , , , , , and are all sibling elements.

Attributes
Attributes aid in modifying the content of a given element by providing additional or required information. They are contained within the element's opening tag. In our sample XML document code we could have taken advantage of attributes to specify the unit of measure used to determine the area and the elevation (it could be feet, yards, meters, kilometers, etc.); in this case, we could have called the attribute 'measureUnit' and defined it within the opening tag of 'area' and 'elevation'.

Cayo

Selangor

The above attribute example can also be written as:

1. using child elements

2. using an empty element

Attributes can be used to:

 * provide more information that is not defined in the data
 * define a characteristic of the element (size, color, style)
 * ensure the inclusion of information about an element in all instances

Attributes can, however, be a bit more difficult to manipulate and they have some constraints. Consider using a child element if you need more freedom.

Rules to follow
These rules are designed to aid the computer reading your XML document.

 * The first line of an XML document must be the XML declaration (the prologue).

 * The main theme of the XML document is established in the root element and all other elements must be contained within the opening and closing tags of this root element.

(e.g. data stuff ).
 * Every element must have an opening tag and a closing tag - no exceptions

=> the parent element's opening and closing tags must contain all of its child elements' tags; in this way, you close first the tag that was opened last:  data  <subChildElementA>data</subChildElementA> <subChildElementB>data</subChildElementB> </childElement2> <childElement3>data</childElement3> </parentElement>
 * Tags must be nested in a particular order

 * Attribute values should have quotation marks around them and no spaces.

 * Empty tags or empty elements must have a space and a slash (/) at the end of the tag.

 * Comments in the XML language begin with "".

XML Element Naming Convention
Any name can be used but the idea is to make names meaningful to those who might read the document.

 * XML elements may only start with either a letter or an underscore character.

 * The name must not start with the string "xml" which is reserved for the XML specification.

 * The name may not contain spaces.

 * The ":" should not be used in element names because it is reserved to be used for namespaces (This will be covered in more detail in a later chapter).

 * The name may contain a mixture of letters, numbers, or other characters.

XML documents often have a corresponding database. The database will contain fields which correspond to elements in the XML document. A good practice is to use the naming rules of your database for the elements in the XML documents.

Simple Internal DTD
Every element that will be used MUST be included in the DTD. Don’t forget to include the root element, even though you have already specified it at the beginning of the DTD. You must specify it again, in an <!ELEMENT> tag. <!ELEMENT cdCollection (cd)> The root element, <cdCollection>, contains all the other elements of the document, but only one direct child element: <cd>. Therefore, you need to specify the child element (only direct child elements need to be specified) in the parentheses. <!ELEMENT cd (title, artist, year)> With this line, we define the <cd> element. Note that this element contains the child elements, , and. These are spelled out in a particular order. This order must be followed when creating the XML document. If you change the order of the elements (with this particular DTD), the document won’t validate. <!ELEMENT title (#PCDATA)> The remaining three tags,, , and don’t actually contain other tags. They do however contain some text that needs to be parsed. You may remember from an earlier lecture that this data is called Parsed Character Data, or #PCDATA. Therefore, #PCDATA is specified in the parentheses. So this simple DTD outlines exactly what you see here in the XML file. Nothing can be added or taken away, as long as we stick to this DTD. The only thing you can change is the #PCDATA text part between the tags.

Adding complexity
There may be times when you will want to put more than just character data, or more than just child elements into a particular element. This is referred to as mixed content. For example, let’s say you want to be able to put character data OR a child element, such as the <b> tag into a element:

<!ELEMENT description (#PCDATA | b | i )*>

This particular arrangement allows us to use PCDATA, the <b> tag, or the <i> tag all at once. One particular caveat though, is that if you are going to mix PCDATA and other elements, the grouping must be followed by the asterisk (*) suffix. This declaration allows us to now add the following to the XML document (after defining the individual elements of course)

With attributes this is done a little differently than with elements. Please see following example:

In order for this to validate, it must be specified in the DTD. Attribute content models are specified with:

<!ATTLIST element_name attribute_name attribute_type default_value>

Let’s use this to validate our CD example:

<!ATTLIST cd remaster_date CDATA #IMPLIED>

Choices
<ATTLIST person gender (male|female) “male”>

Grouping Attributes for an Element
If a particular element is to have many different attributes, group them together like so:

<!ATTLIST car horn CDATA #REQUIRED seats CDATA #REQUIRED steeringwheel CDATA #REQUIRED price CDATA #IMPLIED>

Adding STATIC validation, for items that must have a certain value
<!ATTLIST classList  classNumber CDATA #IMPLIED building (UWINNIPEG_DCE|UWINNIPEG_MAIN) "UWINNIPEG_MAIN" originalDeveloper CDATA #FIXED "Khal Shariff">

Suffixes
So what happens with our last example with the CD collection, when we want to add more CDs? With the current DTD, we cannot add any more CDs without getting an error. Try it and see. When you specify a child element (or elements) the way we did, only one of each child element can be used. Not very suitable for a CD collection is it? We can use something called suffixes to add functionality to the <!ELEMENT> tag. Suffixes are added to the end of the specified child element(s). There are 3 main suffixes that can be used:

 * ( No suffix ): Only 1 child can be used.
 * ( + ): One or more elements can be used.
 * ( * ): Zero or more elements can be used.
 * ( ? ): Zero or one element may be used.

Validating for multiple children with a DTD
So in the case of our CD collection XML file, we can add more CDs to the list by adding a + suffix: <!ELEMENT cd_collection(cd+)>

Using more internal formatting tags
Bold tags, B's for example are also defined in the DTD as elements, that are optional like thus:

<ELEMENT notes (#PCDATA | b | i)*> <!ELEMENT b (#PCDATA)*> <!ELEMENT i (#PCDATA)*> ]> _______________ <classList classNumber="303" building="UWINNIPEG_DCE" originalDeveloper="Khal Shariff"> <firstName>Kenneth </firstName> <lastName>Branaugh </lastName> <studentNumber> </studentNumber> Excellent , Kenneth is doing well. etc

{| width="100%" border="1"
 * - style="horizontal-align:wraptext;"
 * style="background-color:lightyellow" |

Case Study on BMEcat
One of the first major national projects for the use of XML as a B2B exchange format was initiated by the federal association for material management, purchasing and logistics (BME) in cooperation with leading German companies, e.g. Bayer, BMW, SAP and Siemens. They all created a standard for the exchange of product catalogues. This project was named [http://www.bmecat.org/English/index.asp? BMEcat]. The result of this initiative is a DTD collection for the description of product catalogues and related transactions (new catalogue, updating of product data and updating of prices).

Companies operating in the electronic commerce (suppliers, purchasing companies and market places) exchange increasingly large amounts of data. They quickly reach their limits here by the variety of data exchange formats. The BMEcat solution creates a basis for a straightforward transfer of catalogue data from various data formats. This lays the foundation to bringing forward the goods traffic through the Internet in Germany. The use of the BMEcat reduces the costs for all parties as standard interfaces can be used.

The XML-based standard BMEcat was successfully implemented in many projects. Nowadays a variety of companies applies BMEcat and use it for the exchange of their product catalogs in this established standard.

A BMEcat catalogue (Version 1.2) consists of the following main elements:

CATALOG This element contains the essential information of a shopping catalog, e.g. language version and validity. BMEcat expects exactly one language per catalog.

SUPPLIER This element includes identification and address of the catalog suppliers. BMEcat expects exactly one supplier per catalog.

BUYER This element contains the name and address of the catalogue recipient. BMEcat expects no more than one recipient per catalog.

AGREEMENT This element contains one or more framework agreement IDs associated with the appropriate validity period. BMEcat expects all prices of a catalogue belonging to the contract mentioned above.

CLASSIFICATION SYSTEM This element allows the full transfer of one or more classification systems, including feature definitions and key words.

CATALOG GROUP SYSTEM This element originates from version 1.0. It is mainly used for the transfer of tree-structures which facilitate the navigation of a user in the target system (Browser).

ARTICLE (since 2005 PRODUCT) This element represents a product. It contains a set of standard attributes.

ARTICLE PRICE (since 2005 PRODUCT PRICE) This element represents a price. The support of different pricing models is very powerful in comparison with other exchange formats. Season prices, country prices, different currencies and different validity periods, etc. will be supported.

ARTICLE FEATURE (since 2005 PRODUCT FEATURE) This element allows the transfer of characteristic values. You can either record predefined group characteristics or individual product characteristics.

VARIANT This element allows listing of product variants, without having to duplicate them. However, the variations of BMEcat only apply to individual changes in value, leading to a change of Article ID. Otherwise there can’t exist any dependences on other attributes (especially at prices).

MIME This element includes any number of additional documents such as product images, data sheets, or websites.

ARTICLE REFERENCE (since 2005 REFERENCE PRODUCT) This element allows cross-referencing between articles within a catalogue as well as between catalogues. These references may used restrictedly for mapping product bundles.

USER DEFINED EXTENSION This element enables transportation of data at the outside the BMEcat standards. The transmitter and receiver have to be coordinated.

You can find a typical BMEcat file here.
 * }

ONLINE Validator
GIYBF

Well-formed and valid XML
Well-formed XML -  An XML document that correctly abides by the rules of XML syntax.

Valid XML -  An XML document that adheres to the rules of an XML schema (which we will discuss shortly). To be valid an XML document must first be well-formed.

A Valid XML Document must be Well-formed. But, a Well-formed XML Document might not be valid - in other words, a well-formed XML document, that meets the criteria for XML syntax, might not meet the criteria for the XML schema, and will therefore be invalid.

For example, think of the situation where your XML document contains the following (for this schema):

<cityName>Boston</cityName> United States <adminUnit>Massachusetts</adminUnit> :  :   :

Notice that the elements do not appear in the correct sequence according to the schema (cityName, adminUnit, country). The XML document can be validated (using validation software) against its declared schema – the validation software would then catch the out of sequence error.

Using an XML Editor
Check chapter ../XML Editor/ for instructions on how to start an XML editor. Once you have followed the steps to get started you can copy the code in the sample XML document and paste it into the XML editor. Then check your results. Is the XML document well-formed? Is the XML document valid? (you will need to have copied and pasted the schema in order to validate - we will look at schemas next)

XML schema
An XML schema is an XML document. XML schemas have an .xsd file extension.

An XML schema is used to govern the structure and content of an XML document by providing a template for XML documents to follow in order to be valid. It is a guide for how to structure your XML document as well as indicating your XML document's components (elements and attributes - and their relationships). An XML editor will examine an XML document to ensure that it conforms to the specifications of the XML schema it is written against - to ensure it is valid.

XML schemas engender confidence in data transfer. With schemas, the receiver of data can feel confident that the data conforms to expectations. The sender and the receiver have a mutual understanding of what the data represent.

Because an XML schema is an XML document, you use the same language - standard XML markup syntax - with elements and attributes specific to schemas.

A schema defines:

 * the structure of the document
 * the elements
 * the attributes
 * the child elements
 * the number of child elements
 * the order of elements
 * the names and contents of all elements
 * the data type for each element

For more detailed information on XML schemas and reference lists of: Common XML Schema Primitive Data Types, Summary of XML Schema Elements, Schema Restrictions and Facets for data types, and Instance Document Attributes, click on this wikibook link => http://en.wikibooks.org/wiki/XML_Schema

Schema reference
This is the part of the XML Document that references an XML Schema:

Exhibit 5: XML document's schema reference

This is the part we left out when we described the root element in the basic XML document from the previous section. The additional attributes of the root element <tourGuide> reference the XML schema (it is the schemaLocation attribute).

xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'  -  references the W3C Schema-instance namespace

xsi:noNamespaceSchemaLocation='city.xsd'  -  references the XML schema document (city.xsd)

Schema document
Below is a sample XML schema using our TourGuide model. We will refer to it as we describe the parts of an XML schema.

Exhibit 6: XML schema document for city entity

Prolog
Remember that the XML schema is essentially an XML document and therefore must begin with the prolog, which in the case of a schema includes:

The XML declaration:
 * the XML declaration
 * the schema element declaration

The schema element declaration:

The schema element is similar to a root element - it contains all other elements in the schema.

Attributes of the schema element include:

xmlns -  XML NameSpace - the URL for the site that describes the XML elements and data types used in the schema.

You can find more about namespaces here => ../Namespace/.

xmlns:xsd -  All the elements and attributes with the 'xsd' prefix adhere to the vocabulary designated in the given namespace.

elementFormDefault -  elements from the target namespace are either required or not required to be qualified with the namespace prefix. This is mostly useful when more than one namespace is referenced. In this case, 'elementFormDefault' must be qualified, because you must indicate which namespace you are using for each element. If you are referencing only one namespace, then 'elementFormDefault' can be unqualified. Perhaps, using qualified as the default is most prudent, this way you do not accidentally forget to indicate which namespace you are referencing.

Element declarations
Define the elements in the schema.

Include:

 * the element name
 * the element data type (optional)

Basic element declaration format:

Simple type
declares elements that:

 * do NOT have Child Elements
 * do NOT have Attributes

example:

Default Value

If an element is not assigned a value then the default value is assigned.

example:

Fixed Value

An attribute that is defined as fixed must be empty or contained the specified fixed value. No other values are allowed.

example:

Complex type
declares elements that:

 * can have Child Elements
 * can have Attributes

examples:

1. The root element 'tourGuide' contains a child element 'city'. This is shown here:

Nameless complex type

Occurrence Indicators:

 * minOccurs = the minimum number of times an element can occur (here it is 1 time)
 * maxOccurs = the maximum number of times an element can occur (here it is an unlimited number of times, 'unbounded')

2. The parent element 'city' contains many child elements: 'cityName', 'adminUnit', 'country', 'population', etc. Why does this complex element set not start with the line: ? The element 'city' was already defined above within the complex element 'tourGuide' and it was given the type, 'cityDetails'. This data type, 'cityDetails', is utilized here in identifying the sequence of child elements for the parent element 'city'.

Named Complex Type - and therefore can be reused in other parts of the schema

The <xsd:sequence> tag indicates that the child elements must appear in the order, the sequence, specified here.

Compare the sample XML Schema and the sample XML Document - try to observe patterns in the code and how the XML Schema sets up the XML Document.

3. Elements that have attributes are also designated as complex type.

a. this XML Document line: would be defined in the XML Schema as: b. this XML Document line: would be defined in the XML Schema as:

Attribute declarations
Attribute declarations are used in complex type definitions. We saw some attribute declarations in the third example of the Complex Type Element.

Data type declarations
These are contained within element and attribute declarations as:  type=" " .

Common XML Schema Data Types

XML schema has a lot of built-in data types. The most common types are:

For an entire list of built-in simple data types see http://www.w3.org/TR/xmlschema-2/#built-in-datatypes

Using an XML Editor => ../XML Editor/

This link will take you to instructions on how to start an XML editor. Once you have followed the steps to get started you can copy the code in the sample XML schema document and paste it into the XML editor. Then check your results. Is the XML schema well-formed? Is the XML schema valid?

XML stylesheet (XSL)
An XML Stylesheet is an XML Document. XML Stylesheets have an .xsl file extension.

The eXtensible Stylesheet Language (XSL) provides a means to transform and format the contents of an XML document for display. Since an XML document does not contain tags a browser understands, such as HTML tags, browsers cannot present the data without a stylesheet that contains the presentation information. By separating the data and the presentation logic, XSL allows people to view the data according to their different needs and preferences.

The XSL Transformation Language (XSLT) is used to transform an XML document from one form to another, such as creating an HTML document to be viewed in a browser. An XSLT stylesheet consists of a set of formatting instructions that dictate how the contents of an XML document will be displayed in a browser, with much the same effect as Cascading Stylesheets (CSS) do for HTML. Multiple views of the same data can be created using different stylesheets. The output of a stylesheet is not restricted to a browser.

During the transformation process, XSLT analyzes the XML document and converts it into a node tree – a hierarchical representation of the entire XML document. Each node represents a piece of the XML document, such as an element, attribute or some text content. The XSL stylesheet contains predefined “templates” that contain instructions on what to do with the nodes. XSLT will use the match attribute to relate XML element nodes to the templates, and transform them into the resulting document.

Exhibit 7: XML stylesheet document for city entity

The output of the city.xsl stylesheet in Table 2-3 will look like the following:

You will notice that the stylesheet consists of HTML to inform the media tool (a web browser) of the presentation design. If you do not already know HTML this may seem a little confusing. Online resources such as the W3Schools tutorials can help with the basic understanding you will need =>(http://www.w3schools.com/html/default.asp).

Incorporated within the HTML is the XML that supplies the data, the information, contained within our XML document. The XML of the stylesheet indicates what information will be displayed and how. So, the HTML constructs a display and the XML plugs in values within that display. XSL is the tool that transforms the information into presentational form, but at the same time keeps the meaning of the data.

Prolog

 * the XML declaration;
 * the stylesheet declaration;
 * the namespace declaration;
 * the output document format.

The XML declaration

The stylesheet & namespace declarations
 * identifies the document as an XSL style sheet;
 * identifies the version number;
 * refers to the W3C XSL namespace - the URL for the site that describes the XML elements and data types used in the schema. You can find more about namespaces here => ../Namespace/.  Every time the xsl: prefix is used it references the given namespace.

The output document format This element designates the format of the output document and must be a child element of

Templates
The <xsl:template> element is used to create templates that describe how to display elements and their content. Above, in the XSL introduction, we mentioned that XSL breaks up the XML document into nodes and works on individual nodes. This is done with templates. Each template within an XSL describes a single node. To identify which node a given template is describing, use the 'match' attribute. The value given to the 'match' attribute is called a pattern. Remember:  (node tree – a hierarchical representation of the entire XML document.  Each node represents a piece of the XML document, such as an element, attribute or some text content). Wherever there is branching in the node tree, there is a node. <xsl:template> defines the start of a template and contains rules to apply when a specified node is matched.

the match attribute

<xsl:template match="/">

This template match attribute associates the XML document root (/), the whole branch of the XML source document, with the HTML document root. Contained within this template element is the typical HTML markup found at the beginning of any HTML document. This HTML is written to the output. The XSL looks for the root match and then outputs the HTML, which the browser understands.

<xsl:template match="tourGuide"> This template match attribute associates the element 'tourGuide' with the display rules described within this element.

Elements
Elements specific to XSL:

For more XSL elements => http://www.w3schools.com/xsl/xsl_w3celementref.asp.

PHP Methods of XML Dom Validation
Using the DOM DocumentObjectModel to validate XML and with a DTD DocumentTypeDeclaration and the PHP language on a server and more http://wiki.cc/php/Dom_validation

Browser Methods
Place this line of code in your .xml document after the XML declaration (prologue).

PHP Methods of XSLT Transformation
This one is good for PHP5 and wampserver (latest). Please ensure that *xsl* is NOT commented out in the php.ini file.

Example 1, Using within PHP itself (use phpInfo function to check XSLT extension; enable if needed) This example might produce XHTML. Please note it could produce anything defined by the XSL. Example 2:

XML Colors
For use in your stylesheet: these colors can be used for both background and font

http://www.w3schools.com/html/html_colors.asp

http://www.w3schools.com/html/html_colorsfull.asp

http://www.w3schools.com/html/html_colornames.asp

--- Using an XML Editor => ../XML Editor/

This link will take you to instructions on how to start an XML editor. Once you have followed the steps to get started you can copy the code in the sample XML stylesheet document and paste it into the XML editor. Then check your results. Is the XML stylesheet well-formed? ---

/Definitions/
XML SGML Dan Connelly RSS XML Declaration parent child sibling element attribute

*Well-formed XML

PCDATA

/Exercises/
Exercise 1.

a)Using "tourguide" above as a good example, create an XML document whose root is "classlist" . This CLASSLIST is created from a starting point of single entity, STUDENT. Any number of students contain elements: firstname, lastname, emailaddress.


text:
Glyaden-4

Glyaden-4 (Глядень-4) is a rural locality (a selo) in Blagoveshchensky District, Altai Krai, Russia. The population was 149 as of 2013. There is 1 street.

Geography
Glyaden-4 is located 43 km southeast of Blagoveshchenka (the district's administrative centre) by road. Glyaden is the nearest rural locality.

source: wikimedia

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

title: Glyaden-4


text:
Wikipedia:Articles for deletion/R-Mean (2nd nomination)

The result was soft delete. WP:REFUND applies.  So Why  08:52, 12 October 2017 (UTC)

R-Mean
AfDs for this article:
 * – ( View AfD View log  Stats )

Does not meet WP:MUSIC, no reliable secondary coverage or releases on notable labels. Tone is somewhat promotional. -  C HAMPION  (talk) (contributions) (logs) 02:23, 19 September 2017 (UTC)
 * Note: This debate has been included in the list of Bands and musicians-related deletion discussions. -  C HAMPION  (talk) (contributions) (logs) 02:23, 19 September 2017 (UTC)

 Relisted to generate a more thorough discussion and clearer consensus.
 * Delete 31 references and none meets WP:RS, which is weirdly impressive. Sources are either promotional, e.g., music downloads, PR Web, forum posts, record labels, etc. or not significant, e.g., album announcements, track listings, etc. Eggishorn (talk) (contrib) 21:47, 26 September 2017 (UTC)

Please add new comments below this notice. Thanks,  MBisanz  talk 02:24, 27 September 2017 (UTC)  Relisted to generate a more thorough discussion and clearer consensus.

Please add new comments below this notice. Thanks, Optakeover (U)(T)(C) 04:51, 4 October 2017 (UTC)


text:
Stan Leonard

Stan Leonard (February 2, 1915 – December 15, 2005) was a Canadian professional golfer who played on the PGA Tour in the 1950s and 1960s. Leonard won three PGA Tour events, eight Canadian PGA Championships, and 16 other events on the Canadian Tour. He is a member of the Canadian Golf Hall of Fame.

Early years
Leonard was born in Vancouver, British Columbia. He worked as a caddie, and had success in top British Columbia events. He became a professional golfer in 1938, and played almost exclusively, and very successfully, on the Canadian Professional Golf Tour until 1954, while concurrently maintaining a club job at the Marine Drive Golf Club in Vancouver. He competed mainly in western Canada; money was tight, prize money was low, and travel costs to eastern Canada were high. In one of his early events on the PGA Tour, Leonard challenged to win the 1946 Crosby Pro-Am in California, before losing to Lloyd Mangrum.

Canadian success
Leonard won the Canadian PGA Championship eight times from 1940–1961, and this is a record. He was the low Canadian in the Canadian Open nine times from 1945–1961. He won the British Columbia Open five times, the Alberta Open nine times, and the Saskatchewan Open twice. He won a total of six significant amateur and 40 professional tournaments in Canada over the course of his career – second only to Moe Norman in Canadian golf history.

International success
Leonard won the individual title at the Canada Cup in both 1954 and 1959. Leonard joined the PGA Tour full-time in 1954, at age 39. He won three PGA Tour events between 1957 and 1960. He enjoyed a great deal of success in one major tournament – The Masters. His best finishes at the Augusta National Golf Club were T-4 in 1958 and 1959, T-8 in 1955 and T-9 in 1960. Leonard's game was respected by his PGA Tour rivals; legend Sam Snead said that he was glad Leonard had not come out onto the PGA Tour full-time until he was 40 years old!

Later years
Leonard retired from the PGA Tour in the 1960s, and took a club pro job at the Desert Island Golf Club in Palm Springs, California; however, he eventually made his way back home to Vancouver. He competed successfully at the Senior level in Canada, winning three Canadian Senior PGA Championships between 1967 and 1975.

He assisted in designing the Redwood Meadows Golf Course, in Bragg Creek, Alberta, near Calgary.

Leonard was one of the best ball strikers and longest hitters of his era, despite being a diminutive 5' 6" in height. Part of his powerful swing could be attributed to his massive forearms. The other players noticed this physical feature and gave him the nickname Popeye.

Leonard was inducted into Canada's Sports Hall of Fame in 1964, the BC Sports Hall of Fame in 1966, and the Canadian Golf Hall of Fame in 1972. He died of heart failure in Vancouver at the age of 90.

Amateur wins

 * 1932 British Columbia Amateur
 * 1934 Vancouver & Dist. Championship
 * 1935 British Columbia Amateur
 * 1936 Vancouver & Dist. Championship

PGA Tour wins (3)
PGA Tour playoff record (1–1)

Other wins (38)

 * This list may be incomplete

 * 1937 (2) Northwest Open (as an amateur), Alberta Open
 * 1938 (1) Tacoma Jubilee
 * 1939 (1) Alberta Open
 * 1940 (1) Canadian PGA Championship
 * 1941 (2) Alberta Open, Canadian PGA Championship
 * 1942 (1) Alberta Open
 * 1943 (1) Alberta Open
 * 1947 (2) Alberta Open, British Columbia Open
 * 1948 (1) Vancouver City Match Play Championship
 * 1949 (3) Alberta Open, British Columbia Open, Vancouver City Match Play Championship
 * 1950 (6) Alberta Open, Canadian PGA Championship, British Columbia Open, Vancouver City Match Play Championship, Saskatchewan Open, Western Canada Open
 * 1951 (1) Canadian PGA Championship
 * 1953 (1) Vancouver City Match Play Championship
 * 1954 (3) Canadian PGA Championship, British Columbia Open, Vancouver City Match Play Championship
 * 1955 (2) Alberta Open, Saskatchewan Open
 * 1956 (1) Canadian Match Play
 * 1957 (1) Canadian PGA Championship
 * 1959 (2) Canadian PGA Championship, Canada Cup (individual event)
 * 1960 (2) Northwest Open, Canadian Match Play Open
 * 1961 (1) Canadian PGA Championship
 * 1962 (1) British Columbia Open

Senior wins (3)

 * 1967 Canadian PGA Seniors' Championship
 * 1972 Canadian PGA Seniors' Championship
 * 1975 Canadian PGA Seniors' Championship

Results in major championships
Note: Leonard never played in the PGA Championship. {{legend|yellow|Top 10}} {{legend|#eeeeee|Did not play}} CUT = missed the half-way cut "T" indicates a tie for a place

Summary

 * Most consecutive cuts made – 6 (1957 Masters – 1961 Masters)
 * Longest streak of top-10s – 3 (1958 Masters – 1960 Masters)

Team appearances

 * Canada Cup (representing Canada): 1953, 1954, 1955, 1956, 1957, 1959 (individual winner), 1960, 1963
 * Hopkins Trophy (representing Canada): 1952, 1953, 1954, 1955, 1956

title: Stan Leonard


text:
Protictis

Protictis ("first weasel") is an extinct paraphyletic genus of placental mammals from extinct subfamily Didymictinae within extinct family Viverravidae, that lived in North America from early Paleocene to middle Eocene.

Etymology
The name of genus Protictis comes and Latin ictis.

Description
Protictis was a mongoose-like animal that was lightly built. The species had variable sizes. Parts of the skeleton of P. haydenianus are known and this species was about 75 cm long, comparable to the related Didymictis and the modern day Asian civets. The skull of P. simpsoni shows that this species was larger than P. haydenianus. P. minor on the other hand was smaller than P. haydenianus. The morphology of the limb bones of P haydenianus points at a scansorial lifestyle. Protictis had two times as many teeth as modern carnivores. The characteristic carnassials of carnivores were already clearly developed in Protictis, but the long and pointy teeth show that insects were still a major component of this diet. Endocasts of the skull shows that both vision and hearing were important senses, but the position of the eye sockets shows that threedimensional vision was not as well developed as in modern carnivores.

History of classification
Fossils of Protictis are found in the United States and Canada and date mainly from the early to late Paleocene. The holotype of first discovered species (a part of the upper and lowe jaw) were described in 1882 by Edward Drinker Cope based on finds in the San Juan Basin in New Mexico and classified as Didymictis haydenianus. William Diller Matthew described Protictis as a subgenus of Didymictis in 1937 and in 1966 MacIntyre classified it as a separate genus.

title: Protictis


text:
John Nissen

John Nissen is a British inventor, technologist and musician. He was a music scholar at Bryanston and a student at Clare College, Cambridge, where he obtained a degree in natural sciences.

Early career
Nissen worked for many years at GEC in telecommunications as a software engineer, designing the instruction set and real-time operating system for the Mark 2BL processor, possibly the world's first commercial fault-tolerant load-balancing multiprocessing computer, which was selected for use in the control of System X. He had also worked on specification and programming languages, contributing to the development of SDL and Ada, later joining GEC Software as research director.

SMART Award
In 1996, Nissen won a SMART award and set up Cloudworld Ltd. to develop assistive technology, with the mission to use computer-based systems to help disabled and disadvantaged people improve their quality of life. This led to the development of the WordAloud product and the invention of the Tactaphone.

His company, Cloudworld Ltd., produces assistive readers (notably the WordAloud product) and conducts research into literacy and technology, including in developing countries such as Sri Lanka.

Musical career
Nissen is an accomplished 'cellist and double bass player. He had played in the National Youth Orchestra, the Cambridge University Musical Society orchestra under Sir David Willcocks, and the Salomon Orchestra, one of London's finest amateur orchestras. He had played professionally in the band for Royal Shakespeare Company plays. And he had performed concertos, including Dvořák's 'cello concerto, and solos, including Bach's unaccompanied 'cello sonatas.

Investigating geo-engineering
Since early 2008, Nissen has been investigating geo-engineering, which he believes is urgently needed to save the Arctic sea ice. He has developed the theory that the Gulf Stream and Arctic ice caps serve as thermostatic control systems for preventing the planet from heating above a certain temperature, approximately the current global temperature. The Arctic sea ice is an essential part of that control system, and it threatens to disappear (at end summer) possibly as soon as 2012 but likely by 2030 or 2040, thus disabling the thermostatic control of the planet and allowing massive methane discharge from permafrost and disintegration of the Greenland ice sheet.

title: John Nissen


text:
Orestes draegeri

Orestes draegeri is a species of stick insects in the subfamily Dataminae and tribe Datamini.

Characteristics
Orestes draegeri is a very slender and elongated species with relatively short legs. It is very similar to Orestes mouhotii, from which it differs in its relatively shorter legs.

Males are approximately 40.0 to 41.2 mm long. In front of and behind the eyes there are mostly pairs of more or less distinct structures that are species-specific (see also acanthotaxy of Heteropterygidae). The three pairs of occipital spines are designed as follows: The anterior supra-antennals are recognizable spinose and slightly pointed outwards. The pairs of anterior and posterior supra-occipitals behind it are smaller. The vertex is significantly enlarged, blunt and laterally compressed with the anterior coronals, which creates conspicuous, ear-like horns (auricles). The paired supra-orbitals behind the eyes are recognizable bluntly spinous. Posterior and lateral coronals are recognizable as small pointed tubercles that form a crown with the tip of the postocular carina located behind the eye, a distinct edge. The eyes are relatively small, circular and protruding strongly hemispherical. The antennae are shorter than the legs and consist of 23 segments. While the structures on the head resemble those of Orestes mouhotii, these are missing in the males of Orestes draegeri distinct conical hump at posterior margin of the mesonotum which is slightly sulcate medially.

The females are approximately 45.7 to 47.1 mm long. Their head is flat and shows only indistinct structures in the form of tubercles. The tibae of middle legs are compressed laterally at the top and have an indistinct tooth at the end and a clear tooth in the middle. The fourth tergite of the abdomen is indistinctly widened and almost parallel to the rear. On the back of the ninth tergite there is a clearly elongated, strongly roof-like ridge in the center. In the females of Orestes mouhotii this crest is not roof-like and elongated and not notched at the back.

Distribution area
The species was found by Joachim Bresseel and Jérôme Constant in 2012 in the seasonal tropical forests in the Vietnamese provinces Lâm Đồng and Đồng Nai and here in the Dong Nai Biosphere Reserve, which includes Cát Tiên National Park (type locality). Following the investigations by Sarah Bank et al., in which Bresseel and Constant were also involved, it can also be found in the provinces Thừa Thiên Huế, Nghệ An and the northern provinces Vĩnh Phúc and Bắc Kạn. This means that their known distribution area extends almost over the whole of Vietnam.

Taxonomy
From June 25 to July 6, 2012, Bresseel and Constant found representatives of the species in the biosphere reserve of Đồng Nai and on July 16, 2012 another male and four females in the Cát Tiên National Park. In their work on the genus Orestes published in 2018, they described this species as well as five others. The species name is dedicated to Holger Dräger, a German phasmid breeder who, along with other representatives of the Heteropterygidae, in particular keeps and breeds species or stocks which Bresseel and Constant brought with them from Southeast Asia. The male from Cát Tiên was deposited as holotype, two other males and twelve females, some of them were bred from the ones from Đồng Nai, were deposited as paratypes. The holotype and nine paratypes are deposited in the Museum of Natural Sciences in Brussels. The remaining five paratypes are in the Vietnam National Museum of Nature in Hanoi.

How genetic analysis by Sarah Bank et al show, forms Orestes draegeri within the genus Orestes together with Orestes mouhotii and another species from the Andamans, which is called Orestes sp. 'Andaman' and is an undescribed species, a clade of very similar species. In all of them, the males have two almost semicircular horns (auricles) on their heads, while the females have a flat head without any major elevations. Bresseel and Constant, who took over the taxonomic assignment of the species as co-authors, only referred to animals originating from the Kirirom National Park in Cambodia as Orestes mouhotii, while all the other investigated populationss identified as Orestes draegeri. Should the species from Kiriom not be identical to the holotype of Orestes mouhotii and the holotypes of their two synonyms Dares fulmeki and Orestes verruculatus, the ones from Kiriom would be another species and Orestes draegeri would be a synonym of one of the mentioned three names.

Rearing
The species has been sexually bred since 2012. The breeding stock goes back to the animals collected by Bresseel and Constant in Đồng Nai, which were successfully reproduced by Rob Krijns. Up to its description it was called as Pylaemenes sp. 'Dong Nai'. It is listed by the Phasmid Study Group under PSG number 397. According to more recent studies, at least one of the stocks originally kept as Orestes mouhotii with PSG number 192 from Thailand and West Malaysia can be assigned to this species. In addition, further parthenogenetic stocks of Orestes draegeri were introduced from Vietnam by Bresseel and Constant, for example in 2015 from the Ba Bể National Park and the Melinh biodiversity station and in 2017 from the Bạch Mã National Park and from the Pu Mat National Park.

title: Orestes draegeri


text:
tswa

Verb

 * 1) to emerge

Verb

 * 1) to emerge, go out

Verb

 * 1) to steal

Noun

 * 1) breast

title: tswa


text:
Kybartai

Kybartai (Kibarten, קיבאַרט, Кибартай) is a town in Marijampolė County, Vilkaviškis District Municipality in south-western Lithuania. It is located 20 km west of Vilkaviškis and is on the border of Kaliningrad Oblast, Russia.

History
Kybartai was founded under the reign of Sigismund I the Old by the colonization efforts of his wife, Queen Bona Sforza. In 1561, it was listed in the land-register of Jurbarkas and Virbalis.

When in 1861 a branch of the Saint Petersburg–Warsaw Railway was built from Vilnius to the Prussian border, where it was linked to the Prussian Eastern Railway, the Russian border station near the village of Kybartai was named after the neighbouring town of Verzhbolovo (Вержболово), Lithuanian Virbalis, German Wirballen. Meanwhile, Kybartai has become a town bigger than Virbalis and the now Lithuanian border station is called Kybartai, too. The German station of the Prussian Eastern Railway on the western side of the frontier was Eydtkuhnen, today it is the Russian border station and called Chernyshevskoye (Чернышевское).

In 1914, Kybartai had 10 000 inhabitants. The town was destroyed in World War I, but soon recovered and grew again. In 1919 and 1924, Kybartai was granted town rights and privileges. Small businesses began to set up. In 1919, the Žiburys Society founded a secondary school (later to become a gymnasium). Lithuanian, German and Jewish schools and folk universities were established.

In 1919, the first football club in Lithuania, FK Sveikata, was founded. In 1923, the town recorded a population of 6000. In 1927-1928, the Eucharistic Saviour Church was built according to the design of architect Vytautas Landsbergis-Žemkalnis.

Kybartai was the last place where President Antanas Smetona was staying in Lithuania. Late in the evening of 15 June 1940, when the Soviet Army invaded Lithuania, President Smetona fled from Kybartai to Germany after crossing the Liepona stream. On 23 June 1940, the Kybartai Acts were signed actually in Bern, but dated retrospectively by 15 June supposedly in Kybartai, marking the formal transfer of power to the so-called Provisional Government of Lithuania when Lithuania was occupied by the Soviet Army.

During World War II, Kybartai was again severely devastated (only 100 inhabitants remained). On June 30, 1941, an Einsatzgruppe of Germans and a few Lithuanian policemen perpetrated a mass execution of the local Jewish population. 106–116 men were murdered in a sand quarry. From July to Autumn 1941, other Jews from the town were executed with hundreds of victims from the nearby town of Virbalis on another execution site.

In 1945, the Kybartai Secondary School was founded and in 1964 was named after Kristijonas Donelaitis.

People born in Kybartai

 * the Russian landscape painter Isaac Ilyich Levitan (Russian language: Исаак Ильич Левитан, 1860–1900)
 * the Polish composer Emil Młynarski (1870–1935)
 * the Lithuanian painter Jacob Mesenblum (1895–1933)
 * the Polish ethnographer Maria Znamierowska-Prüfferowa (1898-1990)
 * the Austrian singer Harald Serafin (born 1931)
 * the Lithuanian singer and politician Inga Valinskienė (born 1966)

title: Kybartai


text:
Talk:David Garrison

External links modified
Hello fellow Wikipedians,

I have just modified 2 external links on David Garrison. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20120103232153/http://www.2st.com/index.php?option=com_plays&task=viewPlay&Itemid=0&id=140&saction=cal to http://www.2st.com/index.php?option=com_plays&task=viewPlay&Itemid=0&id=140&saction=cal
 * Added archive https://web.archive.org/web/20160116030247/http://www.silencethemusicalnyc.com/ to http://www.silencethemusicalnyc.com/

Cheers.— InternetArchiveBot  (Report bug) 06:57, 5 September 2017 (UTC)

title: Talk:David Garrison


text:
Wikiversity and Wikipedia services

Wikipedia is a Wikimedia Project that is like a wiki. Wikipedia allows different people all around the world to edit Wikipedia, changing and correcting. Wikipedia is like an encyclopedia, it holds information about different things, like people, events, places, etc.

Wikiversity strives to provide useful services to WikiMedia sister projects. A continual problem facing Wikipedia is finding good sources to cite. Many Wikipedia editors have a specific agenda and are perfectly willing to cite poor and unverifiable sources to support claims that are made in Wikipedia articles. Wikiversity is a center for scholarship in finding and critically evaluating sources. Wikiversity participants are encouraged to create Wikiversity pages corresponding to any Wikipedia article. Three types of Wikiversity Learning Project can be take a Wikipedia article as a starting point:
 * 1) Projects designed to find high quality, verifiable sources. These projects seek to evaluate the quality of sources used in existing Wikipedia articles and support study groups that seek to find better sources. See: Citing Sources. Example: the Free education Wikipedia page needs help.
 * 2) Wikipedia articles are written with the assumption that the reader has a certain basic level of knowledge. Wikipedia readers who do not have the assumed level of knowledge can benefit from a guide that might be called "what you should know in order to understand this Wikipedia article". Wikiversity Learning Projects that develop such introductory guides to Wikiversity pages are welcome.
 * 3) Some Wikipedia users may want more detailed information than is provided by a Wikipedia article. Wikiversity Learning Projects can be developed that take Wikipedia articles as a starting place for more detailed investigations of a topic. Example: Cell biology improvement drive.

Template for linking Wikipedia articles to Wikiversity projects
See: w:Template:Wikiversity.

title: Wikiversity and Wikipedia services


text:
Thanks for the Dance

Thanks for the Dance is the fifteenth and final studio album by Canadian singer-songwriter Leonard Cohen, released posthumously through Columbia Records and Legacy Recordings on November 22, 2019. It is the first release following Cohen's death in November 2016, and includes contributions from various musicians, such as Daniel Lanois, Beck, Jennifer Warnes, Damien Rice and Leslie Feist. The song "The Goal" was released with the announcement of the album, on September 20, 2019.

Described as a "continuation" of Cohen's previous studio album, You Want It Darker (2016), the album's vocal tracks were recorded during the same sessions, with Cohen's son and album producer Adam Cohen noting that the album should not be considered an album of "discarded songs or B sides".

Background
The songs on the album comprise "sketches" left over from the sessions for Cohen's final studio album You Want It Darker that were finished by Cohen's son Adam Cohen in a "garage near his father's old house". Regarding the tracks, Adam Cohen noted: "Had we had more time and had [Leonard] been more robust, we would have gotten to them. [We had] conversations about what instrumentation and what feelings he wanted the completed work to evoke – sadly, the fact that I would be completing them without him was given."

The title song, "Thanks for the Dance", was originally recorded by Anjani for her 2007 album Blue Alert, produced and written by Cohen, and composed by Anjani, while Cohen's own version of the song was recorded later.

Some songs were years in the making in Cohen's notebooks and home studio. "The Night of Santiago" is an adaptation of Federico Garcia Lorca's poem "The Unfaithful Housewife". Probably started at the same time as Cohen's 1986 single "Take This Waltz" and never finished, the lyrics were much later published in Book of Longing as "The Faithless Wife". Adam Cohen finally set it to music: "I'd heard it under construction for years, on the front lawn or while we were having coffee or dinner, and I'd always begged him to attempt to write music to it. In a weakened state, he said, 'Look, I'll just recite the poem to a certain tempo and you go ahead and you write the music and try to tell the story."

The only Cohen's original composition on the album, "The Hills" was previously broadcast as a demo track, titled "The Book of Longing" (based on the opening poem of Book of Longing), during Cohen's interview at the KCRW radio station in 2006, along with his own musical version of "Puppets", also originally published as the poem in the same book (here released to Adam Cohen's music).

Some tracks were composed around Leonard Cohen's recitations. "Listen to the Hummingbird" used Cohen's impromptu recitation of the partial poem at his last public appearance to promote You Want It Darker album on October 13, 2016. The full text of the poem was later published in the posthumous book The Flame, as well the poems "Moving On" and "Happens to the Heart".

"The Goal" is a 1998 poem published in Book of Longing, already set to music by Anjani and released on her 2014 album I Came to Love. Here Cohen's own recitation is set to Adam Cohen's music.

"It's Torn", originally another Cohen's collaboration with Sharon Robinson, here in the version produced and additionally composed by Adam Cohen, included guitar effects by Daniel Lanois, who in 2021 released his own version of the track, titled "Torn Again", using Leonard Cohen's original voice track.

Critical reception
Thanks for the Dance received critical acclaim. At Metacritic, which assigns a normalized rating out of 100 to reviews from mainstream critics, the album received an average score of 84, which indicates "universal acclaim", based on 25 reviews.

Rolling Stone gave the album 4 stars, praising the album and saying it is "a magnificent parting shot that's also that exceptionally rare thing — a posthumous work as alive, challenging, and essential as anything issued in the artist's lifetime".

The album was a Juno Award nominee for Adult Alternative Album of the Year at the Juno Awards of 2020.

Personnel

 * Leonard Cohen – vocals (1–9)
 * Pietro Amato – horns (8)
 * Erika Angell – vocals (8)
 * Kobi Arditi – trombone (1)
 * Avi Avital – mandolin (2)
 * Beck – Jew's harp (3), acoustic guitar (3)
 * Romain Bly – trumpet (1)
 * Howard Bilerman – recording engineer (8)
 * Charlie Bisharat – violin (1)
 * Jacob Braun – cello (1)
 * David Campbell – conductor (1)
 * – choir (7)
 * Matt Chamberlain – drums (8), percussion (8)
 * Michael Chaves – bass (1,2,3,4,5,7,9), acoustic guitar (1,5,8), claps (3), drums (4), percussion (5), electric guitar (7,8), synthesizer (8)
 * Adam Cohen – acoustic guitar (3), claps (3), synthesizer (7), vocals (9)
 * Stewart Cole – trumpet (4), flugelhorn (4), clarinet (4), modular synthesizer (4)
 * Carlos de Jacoba – acoustic guitar (3)
 * André Deritter – conductor (1)
 * George Doering – baritone ukulele (4)
 * Andrew Duckles – viola (1)
 * Leslie Feist – vocals (4)
 * Caimin Gilmore – double bass (1)
 * Larry Goldings – flute (1), piano (9)
 * Steve Hassett – vocals (9)
 * Rob Humphreys – percussion (1)
 * Daniel Lanois – piano (1,3), vocals (3), guitar effects (5)
 * Lilah Larson – vocals (8)
 * Patrick Leonard – piano (6)
 * Javier Mas – Spanish laud (1,4), acoustic guitar (2,3,4,6,9), claps (3)
 * Dustin O'Halloran – piano (5)
 * Georg Paltz – clarinet (1)
 * Silvia Perez Cruz – vocals (2,3)
 * Zac Rae – felt piano (1,3), ride cymbal (2), Wurlitzer (2,3), vibraphone (2,4), toy piano (2), synthesizer (3,5), kick drum (3), organ (4), zither (5), strings (6,7), piano (7), bells (7), keyboard (9)
 * Zoe Randell – vocals (9)
 * Mariza Rizou – vocals (2)
 * Richard Reed Parry – bass (3)
 * Damien Rice – vocals (9)
 * Sharon Robinson – percussion (5), vocals (5)
 * Shaar Hashomayim Men's Choir – choir (7)
 * Jason Sharp – saxophone (8)
 * Jessica Staveley-Taylor – vocals (9)
 * Mishka Stein – bass (8)
 * Aaron Sterling – cymbals (4)
 * Dave Stone – string bass (1)
 * Alistair Sung – cello (1)
 * Molly Sweeney – vocals (8)
 * Jamie Thompson – drums (8)
 * Maaike van der Linde – flute (1)
 * Marlies van Gangelen – oboe (1)
 * Josefina Vergara – violin (1)
 * Mariam Wallentin – vocals (9)
 * Jennifer Warnes – vocals (4)
 * Patrick Watson – organ (8), synthesizer (8 and 9), horn arrangement (8)

title: Thanks for the Dance


text:
User:Mrsamimohamedali

Pyramids of Giza, Arabic Ahrāmāt Al-Jīzah, Giza also spelled Gizeh, three 4th-dynasty (c. 2575–c. 2465 bce) pyramids erected on a rocky plateau on the west bank of the Nile River near Al-Jīzah (Giza) in northern Egypt. In ancient times they were included among the Seven Wonders of the World. The ancient ruins of the Memphis area, including the Pyramids of Giza, Ṣaqqārah, Dahshūr, Abū Ruwaysh, and Abū Ṣīr, were collectively designated a UNESCO World Heritage site in 1979.

The designations of the pyramids—Khufu, Khafre, and Menkaure—correspond to the kings for whom they were built. The northernmost and oldest pyramid of the group was built for Khufu (Greek: Cheops), the second king of the 4th dynasty. Called the Great Pyramid, it is the largest of the three, the length of each side at the base averaging 755.75 feet (230 metres) and its original height being 481.4 feet (147 metres). The middle pyramid was built for Khafre (Greek: Chephren), the fourth of the eight kings of the 4th dynasty; the structure measures 707.75 feet (216 metres) on each side and was originally 471 feet (143 metres) high. The southernmost and last pyramid to be built was that of Menkaure (Greek: Mykerinus), the fifth king of the 4th dynasty; each side measures 356.5 feet (109 metres), and the structure’s completed height was 218 feet (66 metres). All three pyramids were plundered both internally and externally in ancient and medieval times. Thus, the grave goods originally deposited in the burial chambers are missing, and the pyramids no longer reach their original heights because they have been almost entirely stripped of their outer casings of smooth white limestone; the Great Pyramid, for example, is now only 451.4 feet (138 metres) high. That of Khafre retains the outer limestone casing only at its topmost portion. Constructed near each pyramid was a mortuary temple, which was linked via a sloping causeway to a valley temple on the edge of the Nile floodplain. Also nearby were subsidiary pyramids used for the burials of other members of the royal family.

Khufu’s pyramid is perhaps the most colossal single building ever erected on the planet. Its sides rise at an angle of 51°52′ and are accurately oriented to the four cardinal points of the compass. The Great Pyramid’s core is made of yellowish limestone blocks, the outer casing (now almost completely gone) and the inner passages are of finer light-coloured limestone, and the interior burial chamber is built of huge blocks of granite. Approximately 2.3 million blocks of stone were cut, transported, and assembled to create the 5.75-million-ton structure, which is a masterpiece of technical skill and engineering ability. The internal walls as well as those few outer-casing stones that still remain in place show finer joints than any other masonry constructed in ancient Egypt.

The entrance to the Great Pyramid is on the north side, about 59 feet (18 metres) above ground level. A sloping corridor descends from it through the pyramid’s interior masonry, penetrates the rocky soil on which the structure rests, and ends in an unfinished underground chamber. From the descending corridor branches an ascending passageway that leads to a room known as the Queen’s Chamber and to a great slanting gallery that is 151 feet (46 metres) long. At the upper end of this gallery, a long and narrow passage gives access to the burial room proper, usually termed the King’s Chamber. This room is entirely lined and roofed with granite. From the chamber two narrow shafts run obliquely through the masonry to the exterior of the pyramid; it is not known whether they were designed for a religious purpose or were meant for ventilation. Above the King’s Chamber are five compartments separated by massive horizontal granite slabs; the likely purpose of these slabs was to shield the ceiling of the burial chamber by diverting the immense thrust exerted by the overlying masses of masonry.

The question of how the pyramids were built has not received a wholly satisfactory answer. The most plausible one is that the Egyptians employed a sloping and encircling embankment of brick, earth, and sand, which was increased in height and in length as the pyramid rose; stone blocks were hauled up the ramp by means of sledges, rollers, and levers. According to the ancient Greek historian Herodotus, the Great Pyramid took 20 years to construct and demanded the labour of 100,000 men. This figure is believable given the assumption that these men, who were agricultural labourers, worked on the pyramids only (or primarily) while there was little work to be done in the fields—i.e., when the Nile River was in flood. By the late 20th century, however, archaeologists found evidence that a more limited workforce may have occupied the site on a permanent rather than a seasonal basis. It was suggested that as few as 20,000 workers, with accompanying support personnel (bakers, physicians, priests, etc.), would have been adequate for the task.

To the south of the Great Pyramid near Khafre’s valley temple lies the Great Sphinx. Carved out of limestone, the Sphinx has the facial features of a man but the body of a recumbent lion; it is approximately 240 feet (73 metres) long and 66 feet (20 metres) high. (See sphinx.)

In 1925 a pit tomb containing the transferred burial equipment of Khufu’s mother, Queen Hetepheres, was discovered near the upper end of the causeway of Khufu. At the bottom of a deep stone-filled shaft was found the queen’s empty sarcophagus, surrounded by furniture and articles of jewelry attesting to the high artistic ability and technical perfection of the 4th-dynasty craftsmen.

Surrounding the three pyramids are extensive fields of flat-topped funerary structures called mastabas; arranged in a grid pattern, the mastabas were used for the burials of relatives or officials of the kings. Besides the core mastabas of the 4th dynasty, numerous mastabas from the 5th and 6th dynasties (c. 2465–c. 2150 bce) have been found around and among the earlier structures.

In the late 1980s and ’90s, excavations in the environs of the pyramids revealed labourers’ districts that included bakeries, storage areas, workshops, and the small tombs of workers and artisans. Mud sealings seem to date the workshop areas to the late 4th dynasty. The tombs range from simple mud-brick domes to more-elaborate stone monuments. Statuettes were found within some of the structures; hieroglyphic inscriptions on tomb walls occasionally identify the deceased.

Bibliography Table Of ContentsHelp us expand the resources for this topic. Click below to submit new publication for review and accepted updates will be published to the site. Submit a publication Submit a publicationSearch for an ISBN number: ISBN:Or enter the publication information: Author Name: Publication Title: Date: Editor: I agree to the Terms and Conditions* *This field is required Websites Table Of ContentsExternal Websites •How Stuff Works - Adventure - The Pyramids Of Giza And The Great Sphinx•Cleveleys - The Great Pyramid of Giza•Discoveringegypt.com - The Pyramids of Giza in Egypt•PBS Online - Pyramids•KingTutOne.com•Virtual-EgyptIntroduction to ancient Egypt, its history and culture, and gods and pharaohs. Includes a timeline, pictorial tour of a number of pyramids along with brief description, and articles dealing with various aspects of society. Also contains texts on Egyptian myths, love poems, and proverbs and poetry, details of hieroglyphics, video clips, and photo galleries. Encyclopædia Britannica Online, s. v. "Pyramids of Giza", accessed July 10, 2012, http://www.britannica.com/EBchecked/topic/234470/Pyramids-of-Giza. While every effort has been made to follow citation style rules, there may be some discrepancies. Please refer to the appropriate style manual or other sources if you have any questions. “I Didn't Know That...”What made you want to look up "Pyramids of Giza"? Please share what surprised you most...

Citations

title: User:Mrsamimohamedali


text:
User:CryptidZilla912/sandbox

Aside from the expected ways revitalization of the Ainu language, Urespa is a university program to educate high-level persons on the language of the Ainu. The effort is a collaborative and cooperative program for individuals wishing to learn about Ainu languages. This includes performances which focus on the Ainu and their language, instead of using the dominant Japanese language.

As another result of Ainu language revitalization,there is also a national annual competition which is Ainu language-themed. People of many differing demographics are often encouraged to take part in the contest. Since 2017 ,the popularity of the contest,, has increased.

title: User:CryptidZilla912/sandbox


text:
Dušan Slobodník

Dušan Slobodník (11 April 1927, Pezinok - 13 December 2001, Bratislava) was a Slovak literary theoretician, translator and politician.

Early life
He attended the elementary school and high school in Zvolen. In February and March 1945 (at the time of the First Slovak Republic), as a member of the semi-obligatory organisation Hlinka Youth, he is said to have participated in a training course led by the German secret service in Sekule.

At the end of World War II, before he could pass the matura, he was abducted by the Soviet SMERSH into a Russian gulag, where he spent the years 1945 - 1954 (he was supposed to spend 15 years there, but was released after Joseph Stalin's death on an amnesty).

Back in Slovakia, he passed his matura and started to study Slovak language and literature in Bratislava. He was excluded by the Communists from the school for being "politically unreliable". He was rehabilitated in 1960 and finished his studies in Prague.

He was an employee of the Slovak Academy of Sciences from 1962 and after the Velvet Revolution (in 1990) became the director of its Institute of World Literature.

Political career
As a member of the HZDS party, which won the elections in 1992, he was Slovakia's Minister of Culture from 1992 to 1994. Afterwards (1994 - 2001), he was deputy to the parliament (National Council of the Slovak Republic) for his party and from 1994 - 1998 the chairman of the Foreign Affairs Committee of the parliament.

In 1992, he was involved in the legal case Feldek vs. Slobodník (see Ľubomír Feldek for details).

Work
He translated modern Russian, English and French literature (e.g. Isaac Asimov's Foundation) into Slovak. He described his experience in the Russian gulag in the book Paragraf:Polárny kruh (Section:Polar Circle; 1991). He specialised in modern world literature. Theoretical problems are dealt with e.g. in the book Vedecké a literárne poznanie (Scientific and Literary Knowledge; 1988), and in the monographs Genéza a poetika science fiction (Genesis and Poetics of Science Fiction; 1981) and Teória a prax básnického prekladu (Theory and Practice of Poetical Translation; 1990).

title: Dušan Slobodník