FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W1572124819> ?p ?o ?g. }

• W1572124819 startingPage "253" @default.
• W1572124819 abstract "Some reinsurers believe that the fortuity or known loss doctrine will protect them from Y2K bug problems, but that may not be so BY NOW, almost everyone is aware of the Year 2000 or Y2K problem-the inability of some computer operating systems and computer chips to recognize dates beyond December 31, 1999. The response of the worldwide insurance industry to claims arising from this crisis will be the product of many factors,l but the positions of reinsurers will be crucial. Several reinsurers have signaled that they will question whether such losses are fortuitous. The fortuity issue, however, may not be so easy to apply. There is no universal definition of fortuity. Some states interpret the concept broadly and some narrowly. Even under broad definitions, most courts require that an insured have actual knowledge that it has caused a loss or that its actions will lead to a certain loss. In the context of Year 2000 claims, this test applies only to the most egregious of circumstances. An insured will not lose coverage merely because it knows that the Year 2000 problem exists generally. must know that the problem exists in its own computers, databases or other equipment, and that its computer operations are sure to fail on January 1, 2000. In some states, even that knowledge is not enough. The insured must be aware of an actual claim or loss. FORTUITY AND Y2K All insurance rests on the idea that a loss must be fortuitous-that it cannot be certain or known.2 Yet, few things are more certain than that when the new century comes, computers with older programs may have problems. For at least 10 years, the news media have reported on the millennium bug. In 1988, for example, the New York Times quoted one federal government official: Those who don't take the problem seriously are going to be faced with a real problem in the 1990s. The same story continued: It could be an absolute horror show for anyone with mainframe computers.3 The Internet is filled with web sites devoted to the Year 2000 bug, such as www.Year2000.com. Even Business Insurance has a site on its web page for Year 2000 articles-www.businessinsurance. com. How can a problem so certain to occur still cause fortuitous losses? Some reinsurers question whether fortuity is possible. Swiss Re America has told clients that the majority of [Year 2000] claims should fail based on the doctrine of fortuity; moreover, courts should be expected to uphold such denials of goes on to comment: While the picture of potential Millennium Bug liability is a threatening one, there is, in fact, sound reason to believe that many claims will not trigger coverage. With the exception of certain directors & officers, professional liability and surety claims, most standard coverages do not apply because Millennium Bug claims are not fortuitous. This is especially so with claims made against general liability policies. The lack of fortuity of computer failure caused by the Millennium Bug is the first line of defense against general liability claims, even before policy language is cited, and should prove a successful defense.... The plain and simple fact is that the use of a two-digit code to represent a year was an intended economical act that has become obsolete. So, the existence of the Millennium Bug is well known. No one can credibly argue that he or she was unaware of the potential complications.4 Another reinsurer, General Reinsurance, says the key issue is: Whether the loss was expected or intended and whether the insurer or policyholder has the burden of proof. The companion principles of known loss or loss in progress are also applicable fortuity arguments. This reinsurer cautioned: Software and hardware manufacturers and users will be hard pressed to deny that they were not made ware of the potential Year 2000 issue before any injury has occurred. They will also find it difficult to deny that they have not known of potential Year 2000 system failures in time to cure the problems. …" @default.
• W1572124819 created "2016-06-24" @default.
• W1572124819 creator A5079941983 @default.
• W1572124819 date "1999-04-01" @default.
• W1572124819 modified "2023-09-28" @default.
• W1572124819 title "Fortuity, Reinsurers and Year 2000 Problems: Will These Theories Carry the Day?" @default.
• W1572124819 hasPublicationYear "1999" @default.
• W1572124819 type Work @default.
• W1572124819 sameAs 1572124819 @default.
• W1572124819 citedByCount "0" @default.
• W1572124819 crossrefType "journal-article" @default.
• W1572124819 hasAuthorship W1572124819A5079941983 @default.
• W1572124819 hasConcept C144133560 @default.
• W1572124819 hasConcept C151730666 @default.
• W1572124819 hasConcept C162118730 @default.
• W1572124819 hasConcept C162324750 @default.
• W1572124819 hasConcept C166957645 @default.
• W1572124819 hasConcept C17744445 @default.
• W1572124819 hasConcept C190253527 @default.
• W1572124819 hasConcept C199539241 @default.
• W1572124819 hasConcept C2524010 @default.
• W1572124819 hasConcept C2776211767 @default.
• W1572124819 hasConcept C2777267654 @default.
• W1572124819 hasConcept C2779343474 @default.
• W1572124819 hasConcept C33923547 @default.
• W1572124819 hasConcept C41008148 @default.
• W1572124819 hasConcept C86803240 @default.
• W1572124819 hasConcept C90673727 @default.
• W1572124819 hasConcept C95457728 @default.
• W1572124819 hasConceptScore W1572124819C144133560 @default.
• W1572124819 hasConceptScore W1572124819C151730666 @default.
• W1572124819 hasConceptScore W1572124819C162118730 @default.
• W1572124819 hasConceptScore W1572124819C162324750 @default.
• W1572124819 hasConceptScore W1572124819C166957645 @default.
• W1572124819 hasConceptScore W1572124819C17744445 @default.
• W1572124819 hasConceptScore W1572124819C190253527 @default.
• W1572124819 hasConceptScore W1572124819C199539241 @default.
• W1572124819 hasConceptScore W1572124819C2524010 @default.
• W1572124819 hasConceptScore W1572124819C2776211767 @default.
• W1572124819 hasConceptScore W1572124819C2777267654 @default.
• W1572124819 hasConceptScore W1572124819C2779343474 @default.
• W1572124819 hasConceptScore W1572124819C33923547 @default.
• W1572124819 hasConceptScore W1572124819C41008148 @default.
• W1572124819 hasConceptScore W1572124819C86803240 @default.
• W1572124819 hasConceptScore W1572124819C90673727 @default.
• W1572124819 hasConceptScore W1572124819C95457728 @default.
• W1572124819 hasIssue "2" @default.
• W1572124819 hasLocation W15721248191 @default.
• W1572124819 hasOpenAccess W1572124819 @default.
• W1572124819 hasPrimaryLocation W15721248191 @default.
• W1572124819 hasRelatedWork W114322259 @default.
• W1572124819 hasRelatedWork W1511479948 @default.
• W1572124819 hasRelatedWork W1572054648 @default.
• W1572124819 hasRelatedWork W2050924980 @default.
• W1572124819 hasRelatedWork W2253539093 @default.
• W1572124819 hasRelatedWork W2282824751 @default.
• W1572124819 hasRelatedWork W2328457217 @default.
• W1572124819 hasRelatedWork W2330556957 @default.
• W1572124819 hasRelatedWork W2485466357 @default.
• W1572124819 hasRelatedWork W274361867 @default.
• W1572124819 hasRelatedWork W2993502487 @default.
• W1572124819 hasRelatedWork W301147982 @default.
• W1572124819 hasRelatedWork W31315555 @default.
• W1572124819 hasRelatedWork W3134546459 @default.
• W1572124819 hasRelatedWork W3204633613 @default.
• W1572124819 hasRelatedWork W72272958 @default.
• W1572124819 hasRelatedWork W214949588 @default.
• W1572124819 hasRelatedWork W2597992125 @default.
• W1572124819 hasRelatedWork W2612527127 @default.
• W1572124819 hasRelatedWork W2613280735 @default.
• W1572124819 hasVolume "66" @default.
• W1572124819 isParatext "false" @default.
• W1572124819 isRetracted "false" @default.
• W1572124819 magId "1572124819" @default.
• W1572124819 workType "article" @default.