Johann Nepomuk Karl, Prince of Liechtenstein

Johann Nepomuk Karl, Prince of Liechtenstein (Johann Nepomuk Karl Borromäus Josef Franz de Paula; 6 July 1724 – 22 December 1748) was the Prince of Liechtenstein between 1732 and 1748. He was the son of Johann Josef Adam.

Johann Nepomuk Karl
Prince of Liechtenstein
Reign17 December 1732 – 22 December 1748
PredecessorJoseph Wenzel I
SuccessorJoseph Wenzel I
Born(1724-07-06)6 July 1724
Died22 December 1748(1748-12-22) (aged 24)
Wischau
Burial
Church of the Nativity of the Virgin Mary, Brno
SpouseCountess Maria Josepha of Harrach-Rohrau
Full name
Johann Nepomuk Karl Borromäus Josef Franz de Paula
HouseLiechtenstein
FatherJoseph Johann Adam
MotherCountess Marie Anna of Oettingen-Spielberg

Life

When his father died, Johann Nepomuk Karl was only eight and his uncle Josef Wenzel ruled as regent and took care of his nephew's education, preparing him for his future role. When Johann Nepomuk Karl took over the rule of his domains alone in 1745, it seemed that his uncle had taught him nothing, because the prince soon neglected the government and otherwise had seen little economic success.

Because of the evident inability of the prince, a royal Hungarian and Bohemian royal chamberlain was appointed to rule. The prince died shortly afterwards in 1748 at Wischau aged 24 years, being the youngest Prince of Liechtenstein to die.

Marriage and issue

In Vienna on 19 March 1744 he had married his cousin Maria Josepha, Countess of Harrach-Rohrau (20 November 1727 – 15 February 1788), daughter of Count Friedrich August von Harrach-Rohrau. They had three children:

  • Maria Anna (October 1745 – 27 April 1752).
  • Prince Joseph Johannes Nepomuk Xaver Gotthard Adam Franz de Paula Frederick (5 May 1747 – 20 May 1747).
  • Maria Antonia Josepha Theresia Walburga (posthumously 13 June 1749 – 28 May 1813), married on 17 January 1768 to Prince Wenzel Paar.

Ancestry

gollark: > > App behavior changes slightly if they know you're trying to figure out what they're doing> this sentence makes no sense to me, "if they know"? he's dissecting the code as per his own statement, thus looking at rows of text in various format. the app isn't running - so how can it change? does the app have self-awareness? this sounds like something out of a bad sci-fi movie from the 90's.It's totally possible for applications to detect and resist being debugged a bit.
gollark: > this is standard programming dogma, detailed logging takes a lot of space and typically you enable logging on the fly on clients to catch errors. this is literally cookie cutter "how to build apps 101", and not scary. or, phrased differently, is it scary if all of that logging was always on? obviously not as it's agreed upon and detailed in TikTok's privacy policy (really), so why is it scary that there's an on and off switch?This is them saying that remotely configurable logging is fine and normal; I don't think them being able to arbitrarily gather more data is good.
gollark: > on the topic of setting up a proxy server - it's a very standard practice to transcode and buffer media via a server, they have simply reversed the roles here by having server and client on the client, which makes sense as transcoding is very intensive CPU-wise, which means they have distributed that power requirement to the end user's devices instead of having to have servers capable of transcoding millions of videos.Transcoding media locally is not the same as having some sort of locally running *server* to do it.
gollark: That doesn't mean it's actually always what happens.
gollark: Legally, yes.

References

  • Evelin Oberhammer (Hrsg.): Der ganzen Welt ein Lob und Spiegel, Das Fürstenhaus Liechtenstein in der frühen Neuzeit. Publisher of history and politics/R. Oldenbourg ed., Vienna/München 1990,
Johann Nepomuk Karl, Prince of Liechtenstein
House of Liechtenstein
Born: 1724 Died: 1748
Regnal titles
Preceded by
Joseph Wenzel I
Prince of Liechtenstein
1732–1748
Succeeded by
Joseph Wenzel I

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.