Municipal law

Municipal law is the national, domestic, or internal law of a sovereign state defined in opposition to international law. Municipal law includes many levels of law: not only national law but also state, provincial, territorial, regional, or local law. While the state may regard them as distinct categories of law, international law is largely uninterested in the distinction and treats them all as one. Similarly, international law makes no distinction between the ordinary law of the state and its constitutional law.

Article 27 of the Vienna Convention on the Law of Treaties from 1969 provides that if a treaty conflicts with a state's municipal law (including the state's constitution), the state is still obliged to meet its obligations under the treaty. The only exception is provided by Article 46 of the Vienna Convention if a state's expression of consent to be bound by a treaty was a manifest violation of a "rule of its internal law of fundamental importance".[1]

Sources

  • Reydams, Luc Universal Jurisdiction: International and Municipal Legal Perspectives, (Oxford Monographs in International Law), (Oxford University Press, 2004) ISBN 978-0-19-927426-0.
  • Paolo Davide Farah e Piercarlo Rossi, "National Energy Policies and Energy Security in the Context of Climate Change and Global Environmental Risks: A Theoretical Framework for Reconciling Domestic and International Law Through a Multiscalar and Multilevel Approach", European Energy and Environmental Law Review (EEELR), Kluwer Law International, Vol. 20, No. 6, pp. 232–244, 2011.
gollark: Replying to https://discord.com/channels/346530916832903169/348702212110680064/750047961043697774Well, the zim people had to invest effort into writing it, I would not be surprised if it had some security issues, and it likely has worse bindings/higher-level tooling than SQLite3.
gollark: ... an x86 assembly typing test link?
gollark: > sqlite is not less complex than this formatYes. *But*, you don't actually have to interact with the SQLite disk format directly because libsqlite3 exists.
gollark: I suspect SQLite would lose out somewhat in storage efficiency, but it could plausibly be faster for many things at runtime.
gollark: It's less complex for everyone interacting with it, since they can just... use SQLite, which has bindings for everything, instead of "zimlib". And by "efficiency" do you mean "space efficiency" or "lookup efficiency"? Because, as I said, SQLite would probably only add a few bytes per directory entry row, which is not a significant increase.

References


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