In heraldry, a bar is an ordinary consisting of a horizontal band across the shield. If only one bar appears across the middle of the shield, it is termed a fess; if two or more appear, they can only be called bars. Calling the bar a diminutive of the fess is inaccurate, however, because two bars may each be no smaller than a fess. Like the fess, bars too may bear complex lines (such as embattled, indented, nebuly, etc.). The diminutive form of the bar (narrower than a bar yet wider than a cottise) is the barrulet, though these frequently appear in pairs, the pair termed a "bar gemel" rather than "two barrulets".

Common ordinaries
A single bar placed across the top of the field is called a chief. A single bar placed over the center of the field is called a fess. Two to four of these appearing on a shield are called bars, and more than four are called barrulets.

Diminutives
Thin bars are termed barrulets. A still thinner bar or riband is known as a cottise. Cottises never appear alone and have no direction of their own, but are borne on each side of an ordinary (such as a fess, pale, bend or chevron). The ordinary thus accompanied by a cottise on each side is then described as "cottised", or these may even be "doubly cottised" (i.e. surrounded by four cottises, two along each side).

The "closet" is described as a band of the thickness between a bar and a barrulet, but is rarely found.

A bar that has been "couped" (cut) at the ends so as not to reach the edges of the field is called a hamade, hamaide or hummet, after the town of La Hamaide in Hainaut, Belgium. As a charge, it is almost always depicted in threes. The adjective is hummety.

Barry and barruly
A field divided by many bars — often six, eight or ten parts with two alternating tinctures — is described as barry (of x, y and z, where x is the number of bars, y is the first (uppermost) tincture, and z is the second tincture). A field divided into five, seven or nine parts with two alternating tinctures is not called barry, however, but two, three or four bars. A barry design consisting of ten or more parts is comparatively rare and is called barruly rather than barry.

Examples

References

Heraldic ordinaries


The 2009 Australian motorcycle Grand Prix was the fifteenth round of the 2009 Grand Prix motorcycle racing season. It took place on the weekend of 16–18 October 2009 at the Phillip Island Grand Prix Circuit. Ducati rider Casey Stoner won the grand prix, in his home race. Championship leader Valentino Rossi finished second, further increasing his championship lead over rival Jorge Lorenzo, who crashed out and failed to score any points. This also marked the final Grand Prix win in the career of Marco Simoncelli before his death 2 years later on 23 October 2011 at the 2011 Malaysian motorcycle Grand Prix after suffering a fatal crash in Race.

MotoGP classification

250 cc classification
The race, scheduled to be run for 25 laps, was stopped after 18 full laps due to Roberto Locatelli having an accident and did not restart as two-thirds of the race distance had been completed.

125 cc classification

Notes

Championship standings after the race (MotoGP)

Below are the standings for the top five riders and constructors after round fifteen has concluded.

Riders' Championship standings

Constructors' Championship standings

 Note: Only the top five positions are included for both sets of standings.

References

Australian motorcycle Grand Prix
Australian
Motorcycle
Motorsport at Phillip Island
October 2009 sports events in Australia


Hendrik van den Bergh (), 1573 to 22 May 1638, was a Flemish noble and professional soldier. Hereditary lord of Stevensweert, from 1618 to 1637 he was also stadtholder of Upper Guelders, the only part of Guelders to remain loyal to Habsburg Spain during the Eighty Years War. Known as a brave and resourceful cavalry commander, he spent most of his career with the Spanish Army of Flanders and became its Maestre de campo in 1628. Accused of treachery after the loss of Den Bosch in 1629, he defected to the Dutch Republic following the 1632 Conspiracy of Nobles.

Personal details
Hendrik was born in 1573, sixth surviving son of Willem IV van den Bergh (15371586) and Maria of Nassau (15391599), eldest sister of William the Silent. One of nine sons and eight daughters, his siblings included Herman (15581611), Frederik (15591618), Oswald (15611586), Adam (15631590), Adolf (15711609), Lodewijk (15721592) and Catharina (15781640).

Before his marriage in 1612 to Margaretha van Wittem (15801627), Hendrik had two children, Anna Maria Elisabeth (16001653) and Herman Frederik (16001669); although he acknowledged both, they do not appear in the family genealogy, so may have been illegitimate.
He and Margaretha had
a daughter, Maria Elisabeth (16131671), later married Eitel Frederick II, Prince of Hohenzollern-Hechingen,
and a son, Herman Oswald (16141622).
Two years after her death in 1627, he married again, this time to Hiëronyma Catharina, Countess of Spaur-Flavon (16001683), and they had five daughters; Elisabeth Catharina (16321681), Amalia Lucia (16331711), Mary Agnes, Anna Carolina, and Wilhelmina Juliana (16381714).

Career
At the beginning of the Dutch Revolt against Spain in 1566, his father Willem IV was among those who supported Protestant demands for greater religious freedom. Charged by the Spanish government with treason and heresy, his estates were seized and Willem fled to Bremen, where Hendrik was born in 1573. Willem returned home in 1576 after an amnesty and in 1581 was appointed stadtholder of Guelders by the States General of the Netherlands. Arrested by the Dutch for suspected treason in 1583, he joined the Spanish in 1584 and died in 1586.

Hendrik followed his father into the Spanish Army of Flanders, as did his brothers, four of whom died on active service; Oswald at Boksum in 1586, Adam at Groningen in 1590, Lodewijk at Steenwijk in 1592, and Adolf in 1609. In 1595, he was seized by Dutch troops outside Weert, and released only after paying a large ransom; he later took part in the 1606 capture of Groenlo, but was taken prisoner again in 1607 near Roermond. In 1618, he succeeded his elder brother Fredrik as Stadtholder of Upper Guelders, which along with its capital Geldern  was the only part of Guelders that remained loyal to Spain, rather than joining the Dutch province of Gelderland.

When the Dutch War resumed in 1621 following the end of the Twelve Years' Truce, Hendrik served as deputy to the Spanish commander Ambrogio Spinola and took part in the sieges of Jülich, Breda and Groenlo. Frustrated by what he perceived as Madrid's failure to provide enough money and men, Spinola resigned in January 1628 and Hendrik was appointed Maestre de campo of the Army of Flanders. The promotion of a Flemish "native" was intended to placate critics of the Spanish administration in Brussels, but Hendrik also acquired numerous enemies, many of them disappointed competitors.

His financial problems worsened when a Dutch squadron captured the Spanish treasure fleet at Matanzas in September 1628; this meant Spanish troops went unpaid, while the Dutch used the windfall to fund an attack on Den Bosch in 1629. Deciding their siege lines were too strong to assault directly, Hendrik tried to force Frederick Henry, Prince of Orange, to lift the siege through a series of diversionary attacks, including an invasion of the Veluwe which he led in person. These achieved little and Den Bosch surrendered in August 1629, a significant setback for the Spanish cause.

Dutch military success, plus growing discontent with Spanish management of the war and its cost, meant elements within the Southern Netherlands now began seeking to end it. Hendrik had several incentives for joining them, one being that his domestic opponents blamed him for the loss of Den Bosch, while estates owned by his wife outside the city had been confiscated by the Dutch. The plotters originally planned to re-unite the largely Catholic and loyalist south with the Protestant dominated rebels in the north, but support for this option crumbled due to the mistreatment of Catholics in Den Bosch by their Calvinist conquerors.

In April 1632, Hendrik and René de Renesse, 1st Count of Warfusée, organised an alternative plot known as the Conspiracy of Nobles. This would have divided the Spanish Netherlands between the Dutch Republic and France, simultaneously ousting the Spanish and ending the war, while protecting Catholic rights in the south. The plotters published a manifesto explaining their ideas but could not rally sufficient support to threaten the Brussels government. They also held secret talks with Frederick Henry, who was persuaded to abandon plans to attack Antwerp, and move instead against Maastricht. The town surrendered on 26 August 1632, an outcome made considerably easier when Hendrik made no attempt to defend Roermond or Venlo.

By engineering the loss of Maastricht, Hendrik and Warfusée had hoped to increase discontent with the Spanish and thus support for a negotiated solution, but while a serious blow, it failed to achieve this. Hendrik fled to neutral Liège, where he unsuccessfully continued his attempts to incite a revolt and joined the Dutch States Army in 1633. However, his past record and that of his father meant the Dutch did not fully trust him, while he was replaced as Stadtholder of Upper Guelders by Guillaume de Bette, a Spanish loyalist. He retired to Elburg in 1634, where he died on 22 May 1638.

Notes

References

Sources

1573 births
1638 deaths
Military personnel from Bremen (city)
Dutch people of the Eighty Years' War (Spanish Empire)
Dutch people of the Eighty Years' War (United Provinces)


The 2009 Malaysian motorcycle Grand Prix was the sixteenth round of the 2009 Grand Prix motorcycle racing season. It took place on the weekend of 23–25 October 2009 at the Sepang International Circuit. In wet conditions the race was dominated by Casey Stoner in a return to form following a mystery illness which ended his hopes of regaining the world championship title. Valentino Rossi finished third, which clinched the 2009 MotoGP championship for him.

MotoGP classification

250 cc classification

125 cc classification

Notes

Championship standings after the race (MotoGP)

Below are the standings for the top five riders and constructors after round sixteen has concluded.

Riders' Championship standings

Constructors' Championship standings

 Note: Only the top five positions are included for both sets of standings.

References

Malaysian motorcycle Grand Prix
Malaysia
Motorcycle Grand Prix


Torsburgen, Tors borg or þors borg ("Thor's fort/castle") are the remains of an ancient hillfort in Kräklingbo on the Swedish island of Gotland in the Baltic Sea. The fort is approximately , was constructed in the 1st-4th century and in use until the 12th century. Situated on a plateau hill it is protected by high cliffs and wall sections, almost  long in total. The fort is featured in the Gutasaga. The plateau is also a nature reserve.

Geography
Torsburgen is situated on, and encompasses the whole of, an eponymous plateau hill in the central east part of Gotland. With  steep cliffs in the west, north and east, it rises above the surrounding flat landscape. About 10,300–10,800 years ago it was a low island in the Baltic Ice Lake. The motions of that lake deposited gravel embankments in the southwest part of the plateau. Inside the embankments, now walls, has formed a small mire called Torsburgsmyr.

There are several caves in the cliffs along the northwest side, the deepest is the Burglädu (Gutnish for "Castle barn") at . Another is Linnaeus' Cave, named after Carl Linnaeus who visited the hillfort in 1741. There is also the Rindarhulet. Rindi is Gutnish for ivy, a common plant on Gotland, and hulet means "the hole".

The hill and the surrounding area used to be covered with dense coniferous forest. Most of the forest was destroyed during the large Kräklingbo fire in the dry summer of 1992. Nevertheless, the area has given life to a wide variety of fire-dependent fungus, plants and insects, some of which are endangered species. Torsburgen has been ravaged by fires before. On his visit to the hill, Linnaeus noted that the plateau was almost void of trees. He was probably referring to the great fire of 1655, which ravaged the Alskog, Ala, Ardre and Kräklingbo sockens.

History

The hillfort was originally constructed at the beginning of the 1st century AD. Reinforced during the 4th century, it was in use until c. 1100 AD. Another source, based on an archaeological survey done in the 1970s, dates the two stages of constructing the fort to 300 AD and 900 AD. A timber-laced stone rampart encircled an area of . Scholars estimate that nearly 1000 soldiers would have been needed to defend it  and it could have been providing refuge to the entire population of Gotland that is calculated to be between 6,000 and 10,000 in the early medieval period.

The fortification is approximately  (E–W). The enclosed area on Torsburgen is about twice the size of the land enclose by the Visby city wall. The fort follows the natural edge of the plateau. The steep cliffs provide a natural protection for the hillfort in the west, north and east part of the plateau, with reinforcements and constructed walls in some places. In the northeast is a  long wall made of large limestone blocks. The area is known as "The Castle" (). In the southwest and south, the fort is protected by a  long wall. The most western part of the wall is built of limestone slabs, while the southwest and south parts are made of limestone rubble and dirt. The wall is  high and up to  wide. On top of the wall was a palisade of logs. The limestone used for building the wall was quarried on site at a small quarry in the north part of the plateau. It has been estimated that the wall would take 3,000 men a year to build. Very little archaeological work has been done on Torsburgen, most of it is unexamined. Only four small metal objects have been retrieved during a minor excavation in connection to a restoration of the stone work at Ardre luke in 1983.

There are several openings in the walls, in Gutnish called luke (), each with its own name:
 Tjängvide like
 Hajdeby luke
 Glose luke
 Ardre luke
 Halsgårde luke
 Ala luke

It has been suggested that Torsburgen was part of a defense system for lighting fire beacons on the many hill forts and plateau hills on the island, to warn the population about approaching enemy ships.

Torsburgen is the third largest fortified hill-fort in Scandinavia, with an area of . It was most likely created during the Late Roman Iron Age (200 - 400 AD), the walls surrounding the area of the hillfort were made of dry stone, rubble from boulders, limestone, and a raised beach. While other hillforts in Sweden are described as vitrified, meaning the remains were turned to a glasslike substance by exposure to heat, Torburgen is a calcined hillfort, the remains of this site were reduced by roasting, leaving a different sort of rubble behind– it is sandy, almost black and strongly magnetic. In the latter case, the residue was a clayey to silty, yellowish brownish material. It is suggested that the walls of this fort were destroyed by fire from enemies.

The largest hillfort is Halleberg in Västergötland, Sweden at about , and the second largest is Lollands Österborg on east Lolland, Denmark at about . The fourth largest in Scandinavia and second largest on Gotland is the hillfort on Grogarnsberget.

Guta Saga
In the exodus story of the Guta Saga, the mythological history of Gotland, a third of Gotland's residents once temporarily settled themselves in Torsburgen after they were ordered by the local government to move due to overpopulation concerns. These residents were eventually forced to leave Gotland altogether; they subsequently settled in Fårö and Hiiumaa before finally moving through Russia to Greece, where they became the descendants of the Goths.

Nature reserve
In 1994, Torsburgen was designated as a nature reserve. The reserve comprises the whole plateau and the area immediately surrounding its base, which translates to . The flora includes a number of plants that are rare in Sweden, such as hard shield-ferns, scorpion senna, Orobanche alba and the Pulsatilla vulgaris gotlandica; all of which survived the fire in 1992. On 30August 2005, the nature reserve became a Natura 2000 protected area. A number of endangered species of plants and insects on the IUCN Red List have been found within the area.

Gallery

References

Buildings and structures in Gotland County
Nature reserves in Gotland County
Hill forts in Sweden
Natura 2000 in Sweden


Sir William Glenholme Falconbridge,  (May 12, 1846 – February 8, 1920) was a Canadian lawyer and judge in Ontario, Canada.

Born in Drummondville (now Niagara Falls, Ontario), Upper Canada, he was the son of John Kennedy Falconbridge, an Irish immigrant, and Sarah Fralick. Falconbridge studied at the Richmond Hill grammar school, Barrie grammar school, and at the Model Grammar School in Toronto. He received a BA degree in 1866 from University College, University of Toronto. He served as the chair of modern languages at Yarmouth Seminary in Nova Scotia for his health and then returned to Toronto where he was a lecturer in Spanish and Italian at University College. At the same time, he studied law with the law firm Morphy, Sullivan, and Fenton. He also studied with the firm of Patton, Osler, and Moss before being called to the Ontario Bar in 1871. He practiced law in the firm of Harrison, Osler, and Moss. In 1879, he was made a partner of the firm.

In 1870, he received an MA degree from the University of Toronto and was registrar of the University from 1872 to 1881.  In 1873, he married Mary Phoebe, the daughter of Robert Baldwin Sullivan.  He was made a bencher of the Law Society of Upper Canada and created a Queen's Counsel in 1885.

In 1887, he was appointed a judge in the Queen's Bench division of Ontario's High Court of Justice. In 1900, he was appointed Chief Justice of the King's Bench, High Court of Justice of the Province of Ontario.

From 1905 to 1908 he served as Chair of the Toronto Public Library Board.

In 1908, he was made a Knight Bachelor.

Falconbridge died of pneumonia in Toronto at the age of 73.  The geographic township of Falconbridge was named in his honour.

References

Bibliography

External links
William Glenholme Falconbridge archival papers held at the University of Toronto Archives and Records Management Services

1846 births
1920 deaths
Canadian Knights Bachelor
Judges in Ontario
Lawyers in Ontario
University of Toronto alumni
Canadian King's Counsel
Deaths from pneumonia in Ontario
Burials at St. James Cemetery, Toronto


The 2009 Valencian Community motorcycle Grand Prix was the last round of the 2009 Grand Prix motorcycle racing season. It took place on the weekend of 6–8 November 2009 at the Circuit Ricardo Tormo. It was the final race of the 250cc two-stroke class, as Moto2 (600cc four-stroke) replaced it from 2010 onwards. The MotoGP race was won by Dani Pedrosa.

MotoGP classification

  – Casey Stoner did not start the race. His place on the grid was left vacant.

250 cc classification
Alex Debón was due to start on pole position, but due to injuries sustained in qualifying practice he did not take part in the race. Therefore, everyone else was moved up one place on the final starting grid.

125 cc classification

Championship standings after the race (MotoGP)

Below are the standings for the top five riders and constructors after round seventeen has concluded.

Riders' Championship standings

Constructors' Championship standings

 Note: Only the top five positions are included for both sets of standings.

References

Valencian Community motorcycle Grand Prix
Valencian
Valencian motorcycle
21st century in Valencia


Hendrik van den Bergh may refer to:
Hendrik van den Bergh (count) (1573-1638), Dutch count, who served in the Spanish military
Hendrik van den Bergh (police official) (1914-1997), South African police official


Sơn Thủy is a commune (xã) in the Lệ Thủy District, Quảng Bình Province, North Central Coast region of Vietnam. This commune is located near Ho Chi Minh Highway. Hanoi–Saigon Railway crosses this commune.

Communes of Quảng Bình province


The 2010 South Asian Games, officially the XI South Asian Games, was a major multi-sport event that took place from 29 January to 8 February 2010 in Dhaka, Bangladesh. This was the third time that the Bangladeshi capital hosted the South Asian Games, thus becoming the first city to hold the games three times.

Roughly 2000 athletes from eight countries competed at the games in 23 different sports. The sporting giant of the region, India continued its dominance in the game's medal tally with a staggering 175 medals including 90 gold medals. Pakistan narrowly beat the host country in gold medals count with 19, while the host Bangladesh captured 18 golds including the region's most popular and prestigious football and cricket titles. Bangladesh, however, earned second spot in total medal count beating out Pakistan. Sri Lanka's Shehan Abeypitiya becomes the fastest man while Pakistan's Naseem Hamid was crowned the fastest woman of the region winning 100 meter sprint.

Organization

The 11th South Asian Games were originally scheduled to take place in November 2009. However, the host country (Bangladesh) faced difficulties due to general elections. As a result, the South Asian Association Council (SAOC) held the 39th Executive Meeting and decided against hosting the Games in 2009, postponing the games to early 2010.

The estimated budget of the 2010 Games was about BDT 160 million (US$2.3 million).

The South Asian Games Organizing Committee (SAGOC) approved the formation of 20 sub-committees to focus on specific aspects of the games. The sub=committees included the ceremonious committee, the coordination committee, and the security committee.

Logo and mascot

The logo of the 11th SAF Games was Kutumb: a doel, known in English as the Oriental magpie robin. It is the national bird of Bangladesh. The logo was designed by Bangladeshi artist Moniruzzaman. The mascot of the games also featured a magpie robin, which was holding the torch to begin the games.

Participating nations

A total of eight countries participated in the 2010 South Asian Games.

Sports

A total of 23 sports competitions were held at the 11th SAF Games.

  Archery ()
  Athletics ()
  Badminton ()
  Basketball ()
  Boxing ()
  Cricket ()
  Cycling ()
  Football ()

  Golf ()
  Hockey ()
  Handball ()
  Judo ()

  Karate ()
  Shooting ()
  Squash ()

  Swimming ()
  Table tennis ()
  Taekwondo ()
  Volleyball ()
  Weightlifting
  Wrestling ()
  Wushu ()

For the first time, Twenty20 cricket was included in the Games. Except India all participating nations sent under-21 teams for the cricket tournament.

Despite early rumours that hockey, volleyball, rowing, and wrestling were to be excluded from the Games, of the four only rowing did not make the final list of sports.

Highlights
Following are the highlights of each of the sports:

Archery – Men & Women

India won all 4 gold medals in the men's and women's events. Host Bangladesh was a distant second with two silvers.

Athletics (Track & Field) – Men & Women

India and Sri Lanka dominated the event with India taking 10 gold and 11 silver while Sri Lanka followed with 7 gold and 8 silver. Pakistan won 4 gold while Nepal won a solitary gold.

Badminton – Men & Women

India won all 7 gold medals, dominating in both men's and women's events.

Basketball – Men

Afghanistan won the gold medal by beating India in the final while Bangladesh claimed the Bronze in the Men Basketball event.

Boxing – Men

India won 3 gold medal followed by host Bangladesh with 2 gold and a silver. Pakistan won 1 gold and 1 silver.

Cricket – Men

Under-21 Cricket T20 was introduced for the first time in the SA Games, with Bangladesh emerged victorious beating Sri Lanka in the closely contested final. Pakistan won the bronze by beating Maldives. India, the other test playing nation of the region, did not participate in the event.

Cycling – Men & Women

India dominated with 3 gold and a silver while Sri Lanka won 1 gold and 1 silver.

Football – Men & Women

Host Bangladesh reclaimed the regional supremacy by winning gold medal in the most one-sided final in the history of the game. They beat the surprise package Afghanistan in the final by 4–0. Bangladesh won each of their matches without conceding a single goal in their 5 matches including the final. Afghanistan, who rushed into the final for the first time in this regional showpiece, was unbeaten until the final registering wins against the likes of India, Maldives and the defending champion Pakistan. Maldives won the bronze by beating India.

In the women football, India won the gold medal beating Nepal in the final while Bangladesh claimed the bronze.

Golf – Men

Host Bangladesh made a clean sweep in both team and individual event. Team Bangladesh won the gold beating India and Sri Lanka who won silver and bronze respectively. In the Individual event, Bangladesh bagged all the three medals.

Handball – Men

Pakistan won the Handball gold beating India in the final. Bangladesh won the bronze.

Hockey – Men

Pakistan beat their arch-rival India in the final through tie-breaker to win the gold medal in hockey. After the teams ended the regular and extra time with 1–1 draw, Pakistan comes superior through penalty strokes by 4–3. Bangladesh edged past Sri Lanka to win the bronze.

Judo – Men & Women

India won 5 gold and 1 silver while Pakistan won 3 gold and 3 silver in Judo. India won both the gold medals in women's category while the men's glory were shared equally between India and Pakistan each winning 3 gold each.

Kabadi – Men & Women

India maintained their supremacy in this regional sports by winning gold in both men and women event. Pakistan won the silver in men's category while Bangladesh bagged the silver in the women's Kabadi.

Karate – Men & Women

Bangladesh won 4 gold and 1 silver followed by Nepal with 3 gold and 2 silver. Afghanistan won two gold while Pakistan and Sri Lanka won 1 each. In men's event Nepal and Afghanistan won two gold each while Bangladesh and Sri Lanka have 1-a piece. In the women's event, host Bangladesh dominated with 3 gold while Pakistan and Nepal shared the remaining two.

Shooting – Men & Women

India dominated in both men's and women's event bagging 19 out of 22 gold medals along with 8 silver medals. Host Bangladesh won the remaining 3 gold medals with 6 silvers.

Swimming – Men & Women

India and Sri Lanka dominated the pool with India winning 11 out of 12 gold in men's event, while 5 out of 7 in women's event. They also won 5 silvers in the men's and 2 in the women's category. Sri Lanka won 3 gold and 6 silver.

Squash – Men

Pakistan maintained their supremacy in Squash winning both gold and silver in individual event and gold in the team event. India and Bangladesh won silver and bronze respectively in team event.

Table Tennis – Men & Women

India made a clean sweep by winning all the 7 gold medals in this sports. They also won 5 silver medals. Sri Lanka claimed silver in both men and women team event.

Taekwondo – Men & Women

Afghanistan won 3 gold in men's event and 1 silver in women's while Nepal won 1 gold and 1 silver each in men's and women's event. India won two gold in men's event, while Bangladesh won equal number of gold in women's event. Sri Lanka won 1 gold in women's event.

Volleyball – Men

India, Pakistan and Sri Lanka won the gold, silver and bronze respectively in Volleyball.

Weightlifting – Men

India won 3 gold and 1 silver followed by Pakistan, who won 2 gold and 3 silver. Sri Lanka won 2 gold and 2 silver while Bangladesh won 1 gold and 2 silver.

Wrestling – Men

India won 3 gold and a silver in Wrestling while Pakistan won 2 gold and a silver. Afghanistan won 1 gold and 2 silver.

Wushu – Men & Women

India won 4 gold and 3 silvers, followed by Nepal with 2 gold and 2 silver. Bangladesh and Pakistan won 2 gold each.

Medal tally

Incidents

Reduced marathon
Due to preparations for the closing ceremony at the National Stadium (which was the actual finishing point for marathon ) in a last moment decision, the finishing line was relocated to outside of the National Stadium. However, the distance was not properly re-calculated and, after a Nepali athlete completed the race with 12 minutes less than the world record, it was noticed that the course only measured 35 km; over 7 km less than the required distance. The results of competition were allowed to stand but the times were deemed ineligible for record purposes.

Lift accident
Six Nepali athletes were slightly injured when a hotel lift crashed just hours before the launching of the games.

Cycling incident
One of the host nation's cyclists, Fatema Chingby Marma, was disqualified as she was being pushed by an enthusiastic local motor cycle rider from behind during the cycling event at Khulna - Gopalganj.

Sponsors
 Grameenphone
 Agrani Bank
 Pepsi
 Bangladesh Olympic Association

References

2010
2010 in multi-sport events
2010 in Asian sport
2010 in Bangladeshi sport
International sports competitions hosted by Bangladesh
Multi-sport events in Bangladesh
Sport in Dhaka
January 2010 sports events in Bangladesh
February 2010 sports events in Bangladesh


Xuân Thủy is a commune (xã) in Lệ Thủy District, Quảng Bình Province, North Central Coast region of Vietnam. This commune is located on the left bank of the Kiến Giang River. The commune contains villages: Xuân Bồ, Tiền Thiệp, Hoàng Giang, Phan Xá, Xuân Lai, Mai Hạ. This commune borders the district capital, Kiến Giang township.

References

Communes of Quảng Bình province


Bass Hit! is a 1956 album by Ray Brown, his first album as a leader.

Track listing
 "Bass Introduction" / "Blues for Sylvia" (Ray Brown / Brown, Marty Paich) – 5:04
 "All of You" (Cole Porter) – 4:00
 "Everything I Have Is Yours" (Harold Adamson, Burton Lane) – 4:28
 "Will You Still Be Mine?" (Tom Adair, Matt Dennis) – 3:42
 "Little Toe" (Brown) – 4:52
 "Alone Together" (Howard Dietz, Arthur Schwartz) – 4:46
 "Solo for Unaccompanied Bass" (Brown) – 2:30
 "My Foolish Heart" (Ned Washington, Victor Young) – 4:09
 "Blues for Lorraine" / "Bass Conclusion" (Brown, Paich / Brown) – 5:36

Bonus tracks on CD reissue in 1999:
"After You've Gone Medley" (False Start/Breakdown/False Start/Complete Take) (Henry Creamer, Turner Layton) – 2:50
 "After You've Gone" (Complete Take) – 4:49
 "After You've Gone Medley" (False Start/Breakdown/Breakdown/Complete Take) – 3:01
 "After You've Gone" (Complete Take) – 2:44

Personnel

Performance
 Ray Brown – double bass
 Pete Candoli – trumpet
 Herbie Harper – trombone
 Jack DuLong – alto saxophone
 Jimmy Giuffre – clarinet, tenor saxophone
 Bill Holman – tenor saxophone
 Jimmy Rowles – piano
 Herb Ellis – guitar
 Mel Lewis – drums
 Marty Paich – arranger, conductor

References

1957 debut albums
Ray Brown (musician) albums
Albums arranged by Marty Paich
Albums produced by Norman Granz
Verve Records albums
Albums conducted by Marty Paich


Dương Thủy is a rural commune (xã) in the Lệ Thủy District, Quảng Bình Province, North Central Coast region of Vietnam. This commune borders communes of Mỹ Thủy and Tân Thủy.

This is an agricultural commune.

Communes of Quảng Bình province


Maria Von Nassau-Dillenburg (18 March 1539, in Dillenburg – 28 May 1599, in Kasteel Ulft), Countess of Nassau, Katzenelnbogen, Vianden and Dietz, was a Dutch noblewoman.

Life
She was the second daughter of William I, Count of Nassau-Siegen and Juliana of Stolberg, making Maria a sister of William the Silent. On 11 November 1556 she married count Willem IV van den Bergh (1537–1586) in Meurs. Count Willem committed treason against his brother-in-law William by defecting to the Spanish. He and Maria were caught, but were quickly freed on William's intervention.

Maria is buried in the crypt of the church at 's-Heerenberg.

Issue
Maria and Willem IV van den Bergh had 16 children:
 Magdalena van den Bergh-'s Heerenberg (1 Aug. 1557 - 25 May 1579)
 Herman van den Bergh Count van den Bergh-'s Heerenberg ( 2 Aug. 1558 -  12 Aug. 1611)
 Frederik van den Bergh Count den Bergh-'s Heerenberg (18 Aug. 1559 - 3 Sep. 1618)
 Oswald van den Bergh (16 Jun. 1561 - 17 Jan. 1586)
 Wilhelmina van den Bergh-'s Heerenberg (7 Jul. 1562 - drowned in the IJssel near Ulft, 15 Nov. 1591)
 Elisabeth van den Bergh-'s Heerenberg (31 Dec. 1563 - 1572)
 Joost van den Bergh Count van den Bergh-'s Heerenberg (25 jan. 1565 -  8 Aug. 1600)
 Adam van den Bergh Count van den Bergh-'s Heerenberg (1568 - 7 Nov. 1590)
 Juliana van den Bergh-'s Heerenberg (1571 - drowned in the IJssel near Ulft, 15 Nov. 1591)
 Adolf van den Bergh Count van den Bergh-'s Heerenberg (1572 - 25 May 1609)
 Lodewijk van den Bergh Count van den Bergh-'s Heerenberg (1 Nov. 1572 - 10 .Jun 1592)
 Hendrik van den Bergh Count van den Bergh-'s Heerenberg, Lord of Stevensweerd en Stadhouder of Gelre (1573 - 12 May 1638)
 Catharina van den Bergh-'s Heerenberg (1578 - 19 Oct. 1640). She married Floris II of Pallandt 2nd Count of Culemborg (1601)
 Anna van den Bergh-'s Heerenberg (1579 - 17 Aug 1630)
 Elisabeth van den Bergh-'s Heerenberg princess-abdes of Essen (1581 - 12 Jan 1614)
 Charlotte van den Bergh-'s Heerenberg (1582 - 2 Nov 1631)

1539 births
1599 deaths
Dutch nobility


The Handle System is the Corporation for National Research Initiatives's proprietary registry assigning persistent identifiers, or handles, to information resources, and for resolving "those handles into the information necessary to locate, access, and otherwise make use of the resources".

As with handles used elsewhere in computing, Handle System handles are opaque, and encode no information about the underlying resource, being bound only to metadata regarding the resource. Consequently, the handles are not rendered invalid by changes to the metadata.

The system was developed by Bob Kahn at the Corporation for National Research Initiatives (CNRI). The original work was funded by the Defense Advanced Research Projects Agency (DARPA) between 1992 and 1996, as part of a wider framework for distributed digital object services, and was thus contemporaneous with the early deployment of the World Wide Web, with similar goals.

The Handle System was first implemented in autumn 1994, and was administered and operated by CNRI until December 2015, when a new "multi-primary administrator" (MPA) mode of operation was introduced. The DONA Foundation now administers the system's Global Handle Registry and accredits MPAs, including CNRI and the International DOI Foundation.
The system currently provides the underlying infrastructure for such handle-based systems as Digital Object Identifiers and DSpace, which are mainly used to provide access to scholarly, professional and government documents and other information resources.

CNRI provides specifications and the source code for reference implementations for the servers and protocols used in the system under a royalty-free "Public License", similar to an open source license.

Thousands of handle services are currently running. Over 1000 of these are at universities and libraries, but they are also in operation at national laboratories, research groups, government agencies, and commercial enterprises, receiving over 200 million resolution requests per month.

Specifications
The Handle System is defined in informational RFCs 3650, 3651 and 3652 of the Internet Engineering Task Force (IETF); it includes an open set of protocols, a namespace, and a reference implementation of the protocols. Documentation, software, and related information is provided by CNRI on a dedicated website

Handles consist of a prefix which identifies a "naming authority" and a suffix which gives the "local name" of a resource. Similar to domain names, prefixes are issued to naming authorities by one of the "multi-primary administrators" of the system upon payment of a fee, which must be renewed annually. A naming authority may create any number of handles, with unique "local names", within their assigned prefixes. An example of a handle is:

 20.1000/100
 2381/12345

In the first example, which is the handle for the HANDLE.NET software license, 20.1000 is the prefix assigned to the naming authority (in this case, Handle.net itself) and 100 is the local name within that namespace. The local name may consist of any characters from the Unicode UCS-2 character set. The prefix also consists of any UCS-2 characters, other than "/". The prefixes consist of one or more naming authority segments, separated by periods, representing a hierarchy of naming authorities. Thus, in the example 20 is the naming authority prefix for CNRI, while 1000 designates a subordinate naming authority within the 20 prefix. Other examples of top-level prefixes for the federated naming authorities of the DONA Foundation are 10 for DOI handles; 11 for handles assigned by the ITU; 21 for handles issued by the German Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen (GWDG), the scientific computing center of the University of Göttingen; and 86 for the Coalition of Handle Services – China. Older "legacy" prefixes issued by CNRI before the "multi-primary administrator" (MPA) structure was instituted are typically four of five digits, as in the second example above, a handle administered by the University of Leicester. All prefixes must be registered in the Global Handle Registry through an DONA Foundation approved registrar, normally for a fee.

As with other uses of handles in computing, the handle is opaque; that is, it encodes no information about the underlying resource and provides only the means to retrieve metadata about the resource.

This may be contrasted with a Uniform Resource Locator (URL), which may encode within the identifier such attributes of the resource as the protocol to be used to access the server holding the resource, the server host name and port number, and perhaps even location specifics such as the name of a file in the server file system containing the resource. In the Handle System, these specifics are not encoded in the handle, but are found in the metadata to which the handle is bound.

The metadata may include many attributes of the information resource, such as its locations, the forms in which it is available, the types of access (e.g. "free" versus "paid") offered, and to whom. The processing of the metadata to determine how and where the resource should be accessed, and the provision of the resource to the user, are performed in a separate step, called "resolution", using a Resolver, a server which may be different from the ones involved in exchanging the handle for the metadata. Unlike URLs, which may become invalid if the metadata embedded within them becomes invalid, handles do not become invalid and do not need to change when locations or other metadata attributes change. This helps to prevent link rot, as changes in the information resource (such as location) need only be reflected in changes to the metadata, rather than in changes in every reference to the resource.

Each handle may have its own administrator and administration of the handles can be done in a distributed environment, similar to DNS domain names. The name-to-value bindings may also be secured, both via signatures to verify the data and via challenge response to verify the transmission of the data, allowing handles to be used in trust management applications.

It is possible for the same underlying information resource to be associated with multiple handles, as when two university libraries generate handles (and therefore possibly different sets of metadata) for the same book.

The Handle System is compatible with the Domain Name System (DNS), but does not require it, unlike persistent identifiers such as PURLs or ARKs, which are similar to handles, but which utilise domain names. However, unlike these domain-name based approaches, handles do require a separate prefix registration process and handle servers separate from the domain name servers.

Handles can be used natively, or expressed as Uniform Resource Identifiers (URIs) through a namespace within the info URI scheme; for example, 20.1000/100 may be written as the URI, info:hdl/20.1000/100. Some Handle System namespaces, such as Digital Object Identifiers, are "info:" URI namespaces in their own right; for example, info:doi/10.1000/182 is another way of writing the handle for the current revision of the DOI Handbook as a URI.

Some Handle System namespaces define special presentation rules. For example, Digital Object Identifiers, which represent a high percentage of the extant handles, are usually presented with a "doi:" prefix: doi:10.1000/182.

Any Handle may be expressed as a Uniform Resource Locator (URL) through the use of the generic HTTP proxy server,:
 https://hdl.handle.net/20.1000/100
Some Handle-based systems offer an HTTP proxy server that is intended for use with their own system such as:
 https://doi.org/10.1000/182.

Implementation
Implementation of the Handle System consists of Local Handle Services, each of which is made up of one or more sites that provide the servers that store specific handles. The Global Handle Registry is a unique Local Handle Service which stores information on the prefixes (also known as naming authorities) within the Handle System and can be queried to find out where specific handles are stored on other Local Handle Services within this distributed system.

The Handle System website provides a series of implementation tools, notably the HANDLE.NET Software and HANDLE.NET Client Libraries. Handle clients can be embedded in end user software (e.g., a web browser) or in server software (e.g., a web server) and extensions are already available for Adobe Acrobat and Firefox.

Handle client software libraries are available in both C and Java. Some applications have developed specific add-on tools, e.g., for the DOI System.

The interoperable network of distributed handle resolver servers (also known as the Proxy Server System) are linked through a Global Resolver (which is one logical entity though physically decentralised and mirrored). Users of Handle System technology obtain a handle prefix created in the Global Handle Registry. The Global Handle Registry maintains and resolves the prefixes of locally maintained handle services. Any local handle service can, therefore, resolve any handle through the Global Resolver.

Handles (identifiers) are passed by a client, as a query of the naming authority/prefix, to the Handle System's Global Handle Registry (GHR). The GHR responds by sending the client the location information for the relevant Local Handle Service (which may consist of multiple servers in multiple sites); a query is then sent to the relevant server within the Local Handle Service. The Local Handle Service returns the information needed to acquire the resource, e.g., a URL which can then be turned into an HTTP re-direct. (Note: if the client already has information on the appropriate LHS to query, the initial query to GHR is omitted)

Though the original model from which the Handle System derives dealt with management of digital objects, the Handle System does not mandate any particular model of relationships between the identified entities, nor is it limited to identifying only digital objects: non-digital entities may be represented as a corresponding digital object for the purposes of digital object management. Some care is needed in the definition of such objects and how they relate to non-digital entities; there are established models that can aid in such definitions e.g., Functional Requirements for Bibliographic Records (FRBR), CIDOC CRM, and indecs content model. Some applications have found it helpful to marry such a framework to the handle application: for example, the Advanced Distributed Learning (ADL) Initiative brings together Handle System application with existing standards for distributed learning content, using a Shareable Content Object Reference Model (SCORM), and the Digital Object Identifier (DOI) system implementation of the Handle System has adopted it together with the indecs framework to deal with semantic interoperability.

The Handle System also makes explicit the importance of organizational commitment to a persistent identifier scheme, but does not mandate one model for ensuring such commitment. Individual applications may choose to establish their own sets of rules and social infrastructure to ensure persistence (e.g., when used in the DSpace application, and the DOI application).

Design principles
The Handle system is designed to meet the following requirements to contribute to persistence

The identifier string:
 is not based on any changeable attributes of the entity (location, ownership, or any other attribute that may change without changing the referent's identity);
 is opaque (preferably a 'dumb number': a well known pattern invites assumptions that may be misleading, and meaningful semantics may not translate across languages and may cause trademark conflicts);
 is unique within the system (to avoid collisions and referential uncertainty);
 has optional, but nice to have, features that should be supported (human-readable, cut-and-paste-able, embeddable; fits common systems, e.g., URI specification).

The identifier resolution mechanism:
 is reliable (using redundancy, no single points of failure, and fast enough to not appear broken);
 is scalable (higher loads simply managed with more computers);
 is flexible (can adapt to changing computing environments; useful to new applications):
 is trusted (both resolution and administration have technical trust methods; an operating organization is committed to the long term);
 builds on open architecture (encouraging the leverage efforts of a community in building applications on the infrastructure);
 is transparent (users need not know the infrastructure details).

Applications
Among the objects that are currently identified by handles are journal articles, technical reports, books, theses and dissertations, government documents, metadata, distributed learning content, and data sets. Handles are being used in digital watermarking applications, GRID applications, repositories, and more. Although individual users may download and use the HANDLE.NET software independently, many users have found it beneficial to collaborate in developing applications in a federation, using common policy or additional technology to provide shared services. As one of the first persistent identifier schemes, the Handle System has been widely adopted by public and private institutions and proven over several years. (See Paradigm, Persistent identifiers.)

Handle System applications may use handles as simple persistent identifiers (as most commonly used, to resolve to the current URL of an object), or may choose to take advantage of other features. Its support for the simultaneous return as output of multiple pieces of current information related to the object, in defined data structures, enables priorities to be established for the order in which the multiple resolutions will be used. Handles can, therefore, resolve to different digital versions of the same content, to mirror sites, or to different business models (pay vs. free, secure vs. open, public vs. private). They can also resolve to different digital versions of differing content, such as a mix of objects required for a distance-learning course.

There are thousands of handle services running today, located in 71 countries, on 6 continents; over 1000 of them run at universities and libraries. Handle services are being run by user federations, national laboratories, universities, computing centers, libraries (national and local), government agencies, contractors, corporations, and research groups. Major publishers use the Handle System for persistent identification of commercially traded and Open Access content through its implementation with the Digital Object Identifier (DOI) system.

The number of prefixes, which allow users to assign handles, is growing and stands at over 12,000 as of early 2014. There are six top-level Global Handle Registry servers that receive (on average) 68 million resolution requests per month. Proxy servers known to CNRI, passing requests to the system on the Web, receive (on average) 200 million resolution requests per month. (Statistics from Handle Quick Facts.)

In 2010, CNRI and ITU (International Telecommunication Union) entered into an agreement to collaborate on use of the Handle System (and the Digital Object Architecture more generally) and are working on the specific details of that collaboration; in April 2009 ITU listed the Handle System as an "emerging trend".

Licences and use policy
Handle System, HANDLE.NET and Global Handle Registry are trademarks of the Corporation for National Research Initiatives (CNRI), a non-profit research and development corporation in the USA. The Handle System is the subject of patents by CNRI, which licenses its Handle System technology through a public license, similar to an open source license, in order to enable broader use of the technology. Handle System infrastructure is supported by prefix registration and service fees, with the majority coming from single prefix holders. The largest current single contributor is the International DOI Foundation. The Public License allows commercial and non-commercial use at low cost of both its patented technology and the reference implementation of the software, and allows the software to be freely embedded in other systems and products. A Service Agreement is also available for users who intend to provide identifier and/or resolution services using the Handle System technology under the Handle System public license.

Related technologies

The Handle System represents several components of a long-term digital object architecture. In January 2010 CNRI released its general-purpose Digital Object Repository software, another major component of this architecture. More information about the release, including protocol specification, source code and ready-to-use system, clients and utilities, is available.

See also

Archival Resource Key (ARK)
Digital Library
Electronic Publishing
Hypertext
Institutional Repository
Linked Data
OpenURL
Permalink
Persistent URL
Resource Description Framework
Semantic Web
Uniform Resource Name

References

External links

Internet protocols
Identifiers
Computer-related introductions in 1994


LabelTag can create a circular label on the data side of any DVD+R, DVD-R, or CD-R disc containing basic information visible to the eye. When burning the data, the label is printed directly behind that data in the same recording session, and on normal recording speed on the same recording layer side. LabelTag works on any disc and does not require a special disc like LightScribe. Currently, LabelTag is an exclusive technology of Lite-On for its DVD writer drives.

An older alternative disc labeling technique was DiscT@2. To record the label on the opposite or back side of the disc by the drive itself LightScribe and LabelFlash are current standards. Besides that, printing using an inkjet printer is currently widely used.

System description
The PC host application controls the data location of the regular user data, including the structure of the file system. In the host application the user label input is transformed into a bit-map representation. The host sends print commands with the pixel information of the image to the drive. The drive interface, records the regular data, including lead in, session intros and closures, and finally lead out. The drive Interface (IF) part takes care of the interpretation of the pixel information and location of the image on the disc. The drive Servo part finally records the pixel information on the correct location including the encoded line numbering. The drive Servo part controls the record power, motor frequency, pixel frequency and channel bit frequency.

Location and time of image recording
The label can be added or appended to the disc at any time if disc space is available. The disc status has to be “appendable” prior to the image recording. The label is recorded adjacent to the last recorded user data. It is up to the user to finalize the disc after the label is added. In case the disc remains "appendable" more user data or more labels can be added. The first section of the disc (26 mm) is used for all drives to do the start-up calibrations. Therefore, no label can be recorded at the inner diameter of the disc. If there is a label in this area, the risk of poor performance is big.

Space usage
If you add a label on the data side of the disc, then this space is no longer available for data. The amount of space it takes depends on the size (width) of the label and the location of the label on the disc. The wider the label and the more it is located on the outside of the disc, the more space it takes. In other words: the bigger the label, the more disc surface is occupied and thus the more data-space you sacrifice. For example: a 5 mm label at the inside requires 10% capacity, and at the outside of the disc about 20% of the disc capacity.

Image visibility and recording process
For LabelTag the Eight-to-Fourteen Modulation (EFM+) channel code properties are modulated to create the visual label. In the EFM+ code table, the user data bytes are transformed into specific sequences of pits and lands, ranging from 3T up to 14T channel bits. To create a pit, a high power pulse from the laser is focused into a small spot on the dye layer. This heats the dye material such that an irreversible transformation of the dye material creates the pit. To create a land, the laser is turned to a low power, such that no transformation in the dye material occurs. In general for DVD+/-R media, the recorded marks have a different visual reflection. Therefore, by recording long sequences of reflective marks or reflective spaces one can create the visible label. To maintain maximum backwards compatibility, LabelTag uses a majority of long marks in the recording layer for a dark pixel, while the bright image pixels are created by a majority of long spaces in the recording layer. Only in that case a sufficient large Differential Phase Detection (DPD) tracking signal is generated. This DPD signal is required for DVD players to jump over the Label area to reach beyond the label appended user data.

During the recording the normal servo processes are used. The beam follows the tracks (grooves). The spot is in focus on the recording layer. Each image line is recorded by repeating the same recording pattern several tracks. In case of DVD with a track pitch of 740 nm, a 100μm image line width is obtained by repeating the pattern 132 consecutive tracks. Because every label pixel is constructed by 132 consecutive tracks, higher image sharpness and contrast is obtained compared to DiscT@2.
Each visible pixel is about 40μm × 100μm (w × l) at the inner radius up to 100μm × 100μm (w × l) at the outer radius. This leads to a picture quality above 250DPI.

As the label and the user data are recorded in the same dye layer of the DVD+/-R media, and label pattern uses run-lengths within the EFM+ range, the same (castle) write pulse form is used as for the regular user data recordings. To enhance the contrast a higher recording power is optional.

Backwards compatibility and logical format
After the visual tag is written to the disc, this disc remains accessible, readable and appendable for any legacy drives. For that, the label is recorded within the user data zone of the disc in its own Image Session. Then any regular DVD drive capable to read multi session DVDs is able to access the user data zone beyond the label. Very old DVD drives, supporting only single session DVD, might only retrieve data stored in the first session.

Access of the LabelTag area itself is prevented by two protection mechanisms:
At File system level, ISO 9660 or Universal Disk Format (UDF), no file pointers to the label area are present.
At Physical Format Level, both the Inner Drive Area and & Lead-in area Session pointers (TOC or RMD) and the Session Control Data Information in the Intro or Border-in skip the Visual Image Window by pointing to the actual end of the Image Session Data Zone or RZone.

Besides, directly around the label a buffer zone is present that enhances the seek performance for the adjacent user data zones. Finally, a sufficient DPD tracking signal is required at the image location. For that reason, the bright and dark pixels are created by recording marks and spaces within the EFM+-runlength range.

Multiple labels and data sessions
The LabelTag format is flexible. It allows as many labels on a disc as space is available. A multisession discs allows burning more data and labels at a later stage. Once the disc is finalized, no more data or labels can be added. But, the more labels you add, the less space you have left for data.

LabelTag application
To record a label on the disc, the application sends pixel information to the drive with a SCSI command.

The application
 Generates pixels based on User Input.
 Defines the LabelTag properties, like size and location.
 Sends the LabelTag pixel information to the drive, using an SCSI-command sequence.
 Sends the FS-Zone1 and FS-Zone2 data containing imported pointers to the location of the root directory as recorded in the last active Primary Volume Descriptor
 Closes the Label by creating the Image Session Structures in the Lead-in TOC/RMD and recording the Closure/Border out.

WRITE12 SCSI commands

For LabelTag no new commands are introduced; the changes are made to the already existing commands. Pixel data describing the pixels for one or more image lines is sent to the drive via the WRITE12 SCSI Write Commands. The line width and number of pixels in each line are set in the LabelTag SCSI mode pages. The WRITE12 command is called TAGWRITE command to emphasize the dedicated LabelTag SCSI mode pages settings. After this command the image data is located in the drive buffer. The drive starts writing after the buffer is full or a SYNCHRONIZE CACHE command is sent.

Image data format
The image data is formatted by the application as bitmap into bright pixels and dark pixels. The bright pixel corresponds to bitmap 0 and the dark pixel to bitmap 1. Therefore, LabelTag allows both text and logos to be printed.

In the LabelTag mode page the following properties are exchanged:
The number of lines n.
The number of dots per line M.
The line width in units of tracks.

Process-flow
The application confirms if the drive is capable of making visual images using the LabelTag technology by sending the GETCONFIGURATION command. In case the LabelTag feature is current, a supported disc with an appendable session is inserted into the drive. The printing of the Label can begin.

First the FS-Zone1 data is recorded on the next writable address. To write the image following the FS-Zone1, the mode bit is set in the LabelTag mode page. The drive is now in LabelTag mode. The data in TAGWRITE commands contains the Label pixel data. The label starts on the Next Writable Address of the inserted disc. The application sends a SYNCHRONIZE CACHE to the drive to let the drive start the image burning. The application unsets the mode bit in the LabelTag mode page to let the drive go back in data write mode. Before the drive can add the FS-Zone2, the application has to inquire the Next Writable Address from the drive to know where the end address is of the Image Window. The application finishes the LabelTag writing by closing the Image Session.

See also
DVD+R
DVD-R
DVD
CD/DVD file system description ISO 9660
DVD file system description UDF Universal Disk Format
LightScribe, a labeling technology for the label side of the disc
Labelflash, a labeling technology for the label side of the disc
DiscT@2, a similar to LabelTag but incompatible technology

References

Ecma DVD-R standard
Ecma DVD+R standard
Ecma CD File system
HP LightScribe Information Site (closed)
Official Yamaha DiscT@2 Page (closed)
Official LabelFlash Page
LiteOn homepage
Nero homepage

Computer storage media
Consumer electronics
Computer printers