Non DubitoA Mind in Many Languages
Search搜索搜尋
EN

The Rhine · 1986–2000莱茵河 · 1986—2000萊茵河 · 1986—2000 · After the Shared Decision共同决定之后共同決定之後

When the River Crosses the Border

河水流过国界以后

河水流過國界以後

The fire was put out; contaminated firefighting water continued downstream. The Rhine already had a cooperation system. The question was what that system could learn to do differently.

火被扑灭了,用来灭火的水却带着有毒物质流向下游。莱茵河并非没有合作机制;真正的问题,是已有的合作还能怎样改变。

火被撲滅了,用來滅火的水卻帶著有毒物質流向下游。萊茵河並非沒有合作機制;真正的問題,是已有的合作還能怎樣改變。

Han Qin · · Historical essay · English independently written历史散文 · 英文独立重写歷史散文 · 英文獨立重寫

Water used to put out a fire became water that people downstream had to avoid.

On 1 November 1986, a warehouse belonging to Sandoz caught fire at Schweizerhalle, near Basel in Switzerland. Firefighting water carried pesticides and other chemicals into the Rhine. Fish and other aquatic organisms died along hundreds of kilometres. The consequences did not remain at the site where the emergency had begun.[1]

This was not an accident caused by an international organization. A company owned the warehouse; emergency response and regulation had their respective responsibilities. The question here concerns the shared arrangements that had to respond when the damage crossed borders. Their later achievements cannot stand in for an account of the original accident.

A waterworks downstream needs more than the news that the fire is out. It needs to know what entered the river, where it is moving, when it may arrive, and what to do about its intake. An emergency over in one place can still be approaching another.

The questions sound technical until we remember where they end: in a water supply used by people who did not make the upstream decisions. When an intake closes, the upstream emergency enters daily life downstream.

Cooperation was there before the fire

A familiar way to tell this story would begin with catastrophe and end with countries finally learning to sit together. That would leave out an important fact. In 1963, five governments signed the Berne agreement giving an existing Rhine commission a basis in international law. Investigating the river, proposing remedial measures, and preparing further agreements were already part of its work.[2]

The fire did not break out in an institutional void. There were meetings, investigations, and a place for negotiations. Serious contamination happened nonetheless. Having an institution and having an arrangement that helps at the necessary moment are not the same achievement.

That distinction changes the task afterward. A new organizational name is not necessarily what is missing. We need to identify a broken connection: prevention at a plant, the handling of contaminated water, transmission of information, or the ability of a recipient to act on a warning.

The commission’s accident-prevention account records waterworks suspending abstraction along roughly 900 kilometres, as far as the Netherlands. The subsequent work included an inventory of hazardous storage and production sites and recommendations on industrial safety.[3]

Some of the resulting proposals are strikingly physical: containment and collection facilities, separate storage of substances that can react dangerously, and retention of firefighting agents. Cooperation becomes useful through decisions that change what happens to a substance, not merely through promises to cooperate more closely.[3]

This is not an accusation that firefighters should have solved an entire river basin’s problems before tackling a burning warehouse. If everything depends on people in an emergency improvising the full protection of strangers far away, the arrangements have not prepared enough for them. Much of that work belongs before the fire.

Another response was to reduce uncertainty downstream. Following the disaster, Rhine ministers commissioned the development of a pollution alarm model through cooperation between the Rhine protection and hydrology commissions. Predicting the movement of a pollutant wave helps the authorities and waterworks time their response.[4]

A model does not close an intake. It gives the people responsible for that decision something better to work with. The common task is not necessarily to move all judgment into a single office. It can be to connect information that separate offices cannot adequately obtain on their own.

That is one way cooperation gains substance. Different people remain responsible for different actions, but they are no longer trying to identify the same moving danger from isolated pieces of evidence. Information is useful when it reaches someone able to do something with it.

After agreement, somebody still has to act

The Rhine Action Programme began in 1987. In its later balance, the commission reported reductions of 70–100 percent in point-source inputs of most priority pollutants between 1985 and 2000, alongside increased connections to wastewater treatment.[5]

The qualification matters as much as the impressive range. These are inputs of particular substances from point sources, not a single percentage measuring every kind of pollution throughout the river. The comparison also begins in 1985, before the fire. It cannot by itself isolate what one post-accident programme caused.

Real improvements require many different parts to be carried out. A shared target does not issue a national permit. International monitoring does not install equipment at a factory. A warning does not act for the waterworks receiving it. Calling the result purely national misses coordination; attributing it entirely to the international organization erases the people doing the implementing.

The Convention on the Protection of the Rhine, signed in 1999, describes a more developed connection. Article 11 communicates the relevant measures as recommendations for implementation through national law, with reporting and consultation requirements. This is a later treaty design, not a description to project backward onto every part of the 1986 response.[6]

A recommendation in this setting is not simply a courtesy that disappears into correspondence. Implementation is to be accounted for; difficulties must be explained. Yet this does not establish a common authority able to bypass national institutions and take over the basin’s factories.[6]

Whether the arrangement looks enough like a state is not the most useful question. What shared capacities does the problem require? Which decisions remain with the parties? If something has not been done, can anyone see the gap and ask for an explanation? Those questions reach further than assigning the organization a permanent grade for strength.

An arrangement can become more detailed through measurement, warnings, controls, and visible implementation. Not every such improvement requires a new superior authority. But dependence on cooperation is not automatically a virtue, either. Where the connection fails, the missing protection still has somewhere to land—often downstream.

The history does not establish that cooperation without a common enforcer must work better. It shows a more limited possibility: some cross-border problems can be improved by sustained coordination and information carried into national action. Establishing that possibility does not settle every other kind of problem.

A recovering river is not every person’s answer

A basin-wide pollution trend is one scale on which to read an improvement. Someone affected by the accident may ask a different question. Why was it not prevented? What happened to a particular loss? Was the information available to the affected person adequate?

Those questions belong beside environmental recovery, not beneath it. Lower emissions and a usable route to an explanation, correction, or compensation are different achievements. A water-quality curve cannot do all their work.

The 1999 convention provides for participation by nongovernmental organizations and for disputes between the contracting parties. It does not establish the commission as a court where a resident can sue the company and obtain a damages judgment. Participation and an individual claim reaching adjudication are distinct kinds of access.[6]

The governance records cited here therefore cannot establish that every affected person obtained a remedy. Nor do they establish that nobody had one. Specific regulatory, compensation, and judicial routes would have to be examined in the relevant national systems and cases. A recovering river cannot write the outcome of every individual claim.

There is a comforting temptation to say that the disaster taught everyone a lesson and made the system better. But learning afterward does not make the earlier loss necessary or worthwhile. The organisms already killed do not return to life because a prevention measure is later adopted. Days of interrupted abstraction do not become days for which everyone was prepared.

The opposite temptation is to say that an organization which failed to prevent the accident was always useless. That removes the subsequent work from view. A loss that cannot be undone does not make the next avoided spill, or the next warning arriving in time, unimportant.

The useful reading keeps both. It asks what became possible afterward without turning improvement into an acquittal of the past. It asks where protection still depends on national choices without treating the common work as decorative.

Cooperation then has less abstract forms: safer relations between dangerous substances and water, information crossing borders before danger arrives, comparable records, and reasons owed when implementation falls short. None is the whole answer. Each may make another stretch of life depend a little less on luck.

The companion essay concerns cholera in Haiti, where an international operation itself was implicated in the harm and people sought an answer from it. Two stories involving water do not have the same source of responsibility. Reading them together is not a competition between success and failure. It is a way to keep asking what was repaired and whose question remained outside.

A fire can be extinguished in one place. Whether a shared arrangement has done something more has to be examined where the water goes next.

灭火的水,后来成了下游要躲开的水。

1986年11月1日,瑞士巴塞尔附近施韦策哈勒的一座山多士公司仓库失火。消防用水混入农药等化学物质,进入莱茵河。火灾发生在一个地点,后果却沿水流继续:数百公里河段的鱼类和其他水生生物死亡,沿河取水受到影响。[1]

这不是一个国际组织制造的事故。仓库属于企业,事故应对和监管有各自的责任。我们要看的,是另一件事:当后果流出了一个国家,已有的共同安排能不能跟上?不能把后来合作的成绩,拿来代替对最初事故的解释。

河边的水厂不能只问火灭了没有。它还得知道,什么东西进了水,往哪里走,什么时候到,自己的取水口该怎么办。上游处理完的一个紧急事件,在下游可能才刚刚开始。

谁先收到消息,谁手里有检测结果,谁能决定暂停取水,这些听起来很技术的问题,会决定一个人照常打开水龙头之前,别人有没有替他把那一段路看住。取水口一旦关闭,上游的事故就进入了下游的日常。

不是先没有合作,后来才有

如果把故事写成灾难唤醒各国、各国终于坐到一起,会漏掉重要的一半。1963年,法国、德国、卢森堡、荷兰和瑞士已经在伯尔尼签署协议,给更早成立的国际莱茵河保护委员会确立了国际法地位。调查河流状况、提出治理措施、准备进一步的国际约定,都已进入它的工作。[2]

所以,那场火不是烧在一片制度空地上。有人负责开会,有调查和协商的地方,仍然发生了严重污染。机构已经存在,与它能不能在关键时刻帮上忙,是两个问题。

这也让事故之后的选择变得不同。要补的未必是再造一个委员会,更不是只给已有机关换一个更响亮的名字。要查的是哪一段没有接上:工厂的防范,事故中的水,消息的传递,还是下游拿到消息以后能不能及时行动。

委员会的事故预防资料把一项后果记得很清楚:沿河直至荷兰,约九百公里范围内有水厂停止取水。此后推进的工作,包括清查流域内危险物质的仓储与生产场所,以及拟定工业设施安全建议。[3]

这些改进并不总有宏大的样子。防止泄漏的收集设施,不能混放的物质,灭火用水怎样截留,都可能比一句保证以后加强合作更接近问题。它们让下次的应急不必再次把危险往更远的地方送。[3]

这不是在说,当时的消防员应该先想完一条河再灭火。恰恰相反,若一套安排总要靠紧急时刻的人临场顾全所有后果,它还没有替他们准备好。许多需要共同想清楚的事,应当在没有火的时候就想过。

事故后的另一条路,是让下游少一些猜测。莱茵河部长会议要求委员会与莱茵河流域水文委员会合作发展污染预警模型,用来推算突然排放形成的污染团怎样移动,帮助有关机构和水厂把应对放在恰当的时间。[4]

模型不会替水厂关掉取水口,却能让作决定的人有根据。它不是把一国的判断全部搬到另一个地方,而是把各国单独拿不到、拿不全的信息连起来。协作有用,有时正是因为它让原来各做各事的人,终于能对同一件正在发生的事作出相互衔接的判断。

约定以后,谁把事情做出来

1987年,莱茵河行动计划开始推进。后来委员会总结,1985至2000年,多数列为优先控制的污染物,其点源排放量下降了百分之七十至百分之百,城镇和工业接入污水处理设施的比例也有所提高。[5]

这个数字值得写,也值得写准。它说的是多数特定污染物的点源排放,不是整条河的所有污染都减少了同一个比例;比较的起点还是1985年,在事故以前。不能把一项长时段变化,压缩成事故之后一个机构单独创造的成绩。

真正发生的改善,需要许多人把不同部分做出来。共同目标不能替代国内许可,国际检测不能替代工厂的设施,通报也不能替代下游的行动。说这一切只是各国自己做的,会看不见协调的作用;说这一切都是国际组织做的,又会把执行的人和他们的责任抹掉。

1999年签署的《保护莱茵河公约》,把这种承接写得更清楚。对有关措施的决定,第十一条规定以建议形式传给缔约方,依各方国内法实施,并设有报告与磋商要求。这是后来公约的安排,不能拿来假装1986年已经全部如此运作。[6]

建议这个名字,不等于只剩礼貌。条文要求交代做到了哪里,实施不了的要说明理由。问题可以从共同决定,继续问到各方的实际行动。反过来,这套承接也不是一个能够越过各国机关、直接接管流域工厂的共同政府。[6]

这里最值得注意的,不是合作够不够像一个国家。它要做成的具体事情,需要哪些共同能力?哪些决定仍由各方作出?出了缺口,别人看不看得见,能不能再要求解释?这些问法比给组织盖上一枚强或弱的章更有用。

监测、预警、排放控制与实施记录,可以让安排变得更细密。这种细密未必都要表现为一个新的上级。可也不能因为没有上级,就称赞所有依赖配合的部分都是优点;配合不到位时,缺下来的那一段,仍会落在下游。

这段历史没有替我们证明一条普遍规律:没有共同强制者,合作就一定更好。它只给出一件值得细看的事实——一些跨国的问题,确实能通过持续协调、共同信息与各国落实得到改善。能做成这件事,不等于所有事情都能用同样的办法做成。

河水改善了,人的问题呢

后来汇总的排放数据,是从一条河的尺度看事情。受事故影响的人却不一定只问河现在怎么样。他还可能要问,那一次为什么没有防住,自己的损失怎样处理,收到的信息是否足够。

这些问与共同治理有关,却不能全部交给一条水质曲线回答。把污染物降下来,和让一个具体的人得到解释、纠错或赔偿,都是需要做的事,不能互相顶替。

在1999年公约里,可以找到非政府组织参与和观察员安排,也有缔约方之间的争端处理。但它没有把委员会设成一个让受影响居民直接起诉企业、获得赔偿判决的法院。参与讨论,与能让自己的请求进入审理,是不同的入口。[6]

所以,仅凭所引的治理材料,我们不能宣布每一个人的救济问题都解决了,也不能反过来宣布所有人都无路可走。具体监管、赔偿与司法救济,还要去相应的国内制度和个案里查。一条河的改善,不能替每一份个人请求写出结局。

有一个看法很容易令人舒服:经历灾难以后,机制变好了,于是灾难便成了通往改善的一课。可是,后来学到了东西,不会使此前死去的生物重新活过来,也不会把当时停止取水的日子改写成早有准备。我们可以肯定修复,不必替过去找一个值得发生的理由。

另一个同样容易的看法是,既然没有挡住事故,这个组织从来就没有用。它把事后的学习也删掉了。已经发生的损失不能撤回,不意味着以后少一次泄漏、早收到一次警报,对别人便不重要。

莱茵河这件事,让合作有了几种不那么抽象的样子:危险物质不再随意接近水,消息不再停在一个国家,排放数字能放在一起比较,某一方做不到时需要说清楚。每一项都不等于解决全部,却可以使下一段生活少靠一点侥幸。

本专题的另一篇写海地霍乱。那里涉及的,是国际行动自身被指带来的损害,以及受害者怎样要求它回答。两件事不能因为都有河水,就被说成同一种责任。并列阅读,不是要把一个评为成功、一个评为失败,而是继续问:我们修好了什么,又把谁的问题留在了门外?

火可以在一个地方被扑灭。一份共同安排有没有真正多做一点,要到水流过去的地方再看。

滅火的水,後來成了下游要躲開的水。

1986年11月1日,瑞士巴塞爾附近施韋策哈勒的一座山多士公司倉庫失火。消防用水混入農藥等化學物質,進入萊茵河。火災發生在一個地點,後果卻沿水流繼續:數百公里河段的魚類和其他水生生物死亡,沿河取水受到影響。[1]

這不是一個國際組織製造的事故。倉庫屬於企業,事故應對和監管有各自的責任。我們要看的,是另一件事:當後果流出了一個國家,已有的共同安排能不能跟上?不能把後來合作的成績,拿來代替對最初事故的解釋。

河邊的水廠不能只問火滅了沒有。它還得知道,什麼東西進了水,往哪裡走,什麼時候到,自己的取水口該怎麼辦。上游處理完的一個緊急事件,在下游可能才剛剛開始。

誰先收到消息,誰手裡有檢測結果,誰能決定暫停取水,這些聽起來很技術的問題,會決定一個人照常打開水龍頭之前,別人有沒有替他把那一段路看住。取水口一旦關閉,上游的事故就進入了下游的日常。

不是先沒有合作,後來才有

如果把故事寫成災難喚醒各國、各國終於坐到一起,會漏掉重要的一半。1963年,法國、德國、盧森堡、荷蘭和瑞士已經在伯爾尼簽署協議,給更早成立的國際萊茵河保護委員會確立了國際法地位。調查河流狀況、提出治理措施、準備進一步的國際約定,都已進入它的工作。[2]

所以,那場火不是燒在一片制度空地上。有人負責開會,有調查和協商的地方,仍然發生了嚴重污染。機構已經存在,與它能不能在關鍵時刻幫上忙,是兩個問題。

這也讓事故之後的選擇變得不同。要補的未必是再造一個委員會,更不是只給已有機關換一個更響亮的名字。要查的是哪一段沒有接上:工廠的防範,事故中的水,消息的傳遞,還是下游拿到消息以後能不能及時行動。

委員會的事故預防資料把一項後果記得很清楚:沿河直至荷蘭,約九百公里範圍內有水廠停止取水。此後推進的工作,包括清查流域內危險物質的倉儲與生產場所,以及擬定工業設施安全建議。[3]

這些改進並不總有宏大的樣子。防止洩漏的收集設施,不能混放的物質,滅火用水怎樣截留,都可能比一句保證以後加強合作更接近問題。它們讓下次的應急不必再次把危險往更遠的地方送。[3]

這不是在說,當時的消防員應該先想完一條河再滅火。恰恰相反,若一套安排總要靠緊急時刻的人臨場顧全所有後果,它還沒有替他們準備好。許多需要共同想清楚的事,應當在沒有火的時候就想過。

事故後的另一條路,是讓下游少一些猜測。萊茵河部長會議要求委員會與萊茵河流域水文委員會合作發展污染預警模型,用來推算突然排放形成的污染團怎樣移動,幫助有關機構和水廠把應對放在恰當的時間。[4]

模型不會替水廠關掉取水口,卻能讓作決定的人有根據。它不是把一國的判斷全部搬到另一個地方,而是把各國單獨拿不到、拿不全的資訊連起來。協作有用,有時正是因為它讓原來各做各事的人,終於能對同一件正在發生的事作出相互銜接的判斷。

約定以後,誰把事情做出來

1987年,萊茵河行動計劃開始推進。後來委員會總結,1985至2000年,多數列為優先控制的污染物,其點源排放量下降了百分之七十至百分之百,城鎮和工業接入污水處理設施的比例也有所提高。[5]

這個數字值得寫,也值得寫準。它說的是多數特定污染物的點源排放,不是整條河的所有污染都減少了同一個比例;比較的起點還是1985年,在事故以前。不能把一項長時段變化,壓縮成事故之後一個機構單獨創造的成績。

真正發生的改善,需要許多人把不同部分做出來。共同目標不能替代國內許可,國際檢測不能替代工廠的設施,通報也不能替代下游的行動。說這一切只是各國自己做的,會看不見協調的作用;說這一切都是國際組織做的,又會把執行的人和他們的責任抹掉。

1999年簽署的《保護萊茵河公約》,把這種承接寫得更清楚。對有關措施的決定,第十一條規定以建議形式傳給締約方,依各方國內法實施,並設有報告與磋商要求。這是後來公約的安排,不能拿來假裝1986年已經全部如此運作。[6]

建議這個名字,不等於只剩禮貌。條文要求交代做到了哪裡,實施不了的要說明理由。問題可以從共同決定,繼續問到各方的實際行動。反過來,這套承接也不是一個能夠越過各國機關、直接接管流域工廠的共同政府。[6]

這裡最值得注意的,不是合作夠不夠像一個國家。它要做成的具體事情,需要哪些共同能力?哪些決定仍由各方作出?出了缺口,別人看不看得見,能不能再要求解釋?這些問法比給組織蓋上一枚強或弱的章更有用。

監測、預警、排放控制與實施記錄,可以讓安排變得更細密。這種細密未必都要表現為一個新的上級。可也不能因為沒有上級,就稱讚所有依賴配合的部分都是優點;配合不到位時,缺下來的那一段,仍會落在下游。

這段歷史沒有替我們證明一條普遍規律:沒有共同強制者,合作就一定更好。它只給出一件值得細看的事實——一些跨國的問題,確實能通過持續協調、共同資訊與各國落實得到改善。能做成這件事,不等於所有事情都能用同樣的辦法做成。

河水改善了,人的問題呢

後來匯總的排放資料,是從一條河的尺度看事情。受事故影響的人卻不一定只問河現在怎麼樣。他還可能要問,那一次為什麼沒有防住,自己的損失怎樣處理,收到的資訊是否足夠。

這些問與共同治理有關,卻不能全部交給一條水質曲線回答。把污染物降下來,和讓一個具體的人得到解釋、糾錯或賠償,都是需要做的事,不能互相頂替。

在1999年公約裡,可以找到非政府組織參與和觀察員安排,也有締約方之間的爭端處理。但它沒有把委員會設成一個讓受影響居民直接起訴企業、獲得賠償判決的法院。參與討論,與能讓自己的請求進入審理,是不同的入口。[6]

所以,僅憑所引的治理材料,我們不能宣佈每一個人的救濟問題都解決了,也不能反過來宣佈所有人都無路可走。具體監管、賠償與司法救濟,還要去相應的國內制度和個案裡查。一條河的改善,不能替每一份個人請求寫出結局。

有一個看法很容易令人舒服:經歷災難以後,機制變好了,於是災難便成了通往改善的一課。可是,後來學到了東西,不會使此前死去的生物重新活過來,也不會把當時停止取水的日子改寫成早有準備。我們可以肯定修復,不必替過去找一個值得發生的理由。

另一個同樣容易的看法是,既然沒有擋住事故,這個組織從來就沒有用。它把事後的學習也刪掉了。已經發生的損失不能撤回,不意味著以後少一次洩漏、早收到一次警報,對別人便不重要。

萊茵河這件事,讓合作有了幾種不那麼抽象的樣子:危險物質不再隨意接近水,消息不再停在一個國家,排放數字能放在一起比較,某一方做不到時需要說清楚。每一項都不等於解決全部,卻可以使下一段生活少靠一點僥倖。

本專題的另一篇寫海地霍亂。那裡涉及的,是國際行動自身被指帶來的損害,以及受害者怎樣要求它回答。兩件事不能因為都有河水,就被說成同一種責任。並列閱讀,不是要把一個評為成功、一個評為失敗,而是繼續問:我們修好了什麼,又把誰的問題留在了門外?

火可以在一個地方被撲滅。一份共同安排有沒有真正多做一點,要到水流過去的地方再看。

Records & reading note史料与阅读说明史料與閱讀說明

Historical readings, not invented scenes or a current-law guide. Documented facts, contemporaneous legal decisions, institutional self-assessments, and the author’s interpretation are kept distinct. No private thoughts, dialogue, or composite victims are invented. English is independently written; both Chinese scripts are complete. The source research report helped select cases but does not replace the linked records. Different organizations do not automatically fit the theory’s non-coercive model.

本专题写真实历史,不虚构场景,也不作现行法律指南。史料事实、当时法律判断、机构自我总结与作者的解读分开,不虚构内心、对话或拼合受害者。英文独立重写,简繁中文均为完整正文。初步研究报告帮助选题,不代替下列可回查的原始材料;不同组织不自动属于理论定义的无共同强制性上级的协作。

本專題寫真實歷史,不虛構場景,也不作現行法律指南。史料事實、當時法律判斷、機構自我總結與作者的解讀分開,不虛構內心、對話或拼合受害者。英文獨立重寫,簡繁中文均為完整正文。初步研究報告幫助選題,不代替下列可回查的原始材料;不同組織不自動屬於理論定義的無共同強制性上級的協作。

  1. ICPR · The turning point: the Sandoz accident莱茵河保护委员会:山多士事故这一转折萊茵河保護委員會:山多士事故這一轉折

    Institutional retrospective: 1 November 1986, contaminated firefighting water, aquatic deaths and public pressure. An institutional account, not an independent allocation of legal liability.

    机构回顾,记1986年11月1日事故、受污染消防水、水生生物死亡与公众压力;不据此单独分配法律责任。

    機構回顧,記1986年11月1日事故、受污染消防水、水生生物死亡與公眾壓力;不據此單獨分配法律責任。

  2. ICPR · The Berne Convention (1963)莱茵河保护委员会:1963年伯尔尼协议萊茵河保護委員會:1963年伯爾尼協議

    The 29 April 1963 signature gave an existing commission international legal status; investigation, proposals and preparation of further agreements. It did not create cooperation from nothing in 1986.

    1963年4月29日签署及既有委员会的国际法地位、调查与建议职责;不把1986年写成合作的起点。

    1963年4月29日簽署及既有委員會的國際法地位、調查與建議職責;不把1986年寫成合作的起點。

  3. ICPR · Prevention of accidents and security of industrial plants莱茵河保护委员会:事故预防与工业设施安全萊茵河保護委員會:事故預防與工業設施安全

    Records interruption of water abstraction along about 900 km and later recommendations. The current recommendations are later lessons, not rules assumed already in force at the time of the fire.

    记约九百公里范围的取水中断及后来的安全建议;后来的经验不倒写成事故时已全部适用的规则。

    記約九百公里範圍的取水中斷及後來的安全建議;後來的經驗不倒寫成事故時已全部適用的規則。

  4. ICPR · Rhine Alarm Model莱茵河保护委员会:莱茵河污染预警模型萊茵河保護委員會:萊茵河污染預警模型

    Opening account of the post-accident commission to develop a transport model and its warning function. No current accuracy estimate or future update is projected into the historical narrative.

    开头所述事故后受托发展模型及预警功能;不将当前准确率或未来更新计划写入历史情境。

    開頭所述事故後受託發展模型及預警功能;不將當前準確率或未來更新計劃寫入歷史情境。

  5. ICPR · Rhine Action Programme (1987) and balance to 2000莱茵河保护委员会:1987年行动计划与2000年总结萊茵河保護委員會:1987年行動計劃與2000年總結

    The 70–100% range concerns point-source inputs of most priority pollutants, with a 1985 baseline. Institutional evaluation, not proof of an isolated programme effect or a measure of all pollution.

    百分之七十至百分之百指多数优先污染物的点源排放,以1985年为基线;机构总结不构成单一项目的因果识别,也不是所有污染的总指标。

    百分之七十至百分之百指多數優先污染物的點源排放,以1985年為基線;機構總結不構成單一項目的因果識別,也不是所有污染的總指標。

  6. Convention on the Protection of the Rhine · signed 12 April 1999《保护莱茵河公约》· 1999年4月12日签署文本《保護萊茵河公約》· 1999年4月12日簽署文本

    Articles 5 and 8 (duties/functions), 11 (implementation; PDF p. 8), 14 (NGO/observer participation), 16 and the Annex (inter-party disputes). Article 9 concerns plenary sessions, not implementation. English translation; authentic texts are Dutch, French and German under Article 20.

    第五、八条为职责与功能,第十一条为实施(PDF第8页),第十四条为非政府组织及观察员参与,第十六条与附件为缔约方间争端。第九条讲全体会议,不是实施。此为英文译本,第二十条所列作准文本为荷、法、德文。

    第五、八條為職責與功能,第十一條為實施(PDF第8頁),第十四條為非政府組織及觀察員參與,第十六條與附件為締約方間爭端。第九條講全體會議,不是實施。此為英文譯本,第二十條所列作准文本為荷、法、德文。

Optional philosophical background ↗可选阅读:哲学背景论文 ↗可選閱讀:哲學背景論文 ↗ · Questions to test against history, not conclusions history must prove.把问题交给历史检验,不要求历史证明理论。把問題交給歷史檢驗,不要求歷史證明理論。