Pragmatic Segmenter
Pragmatic Segmenter is a rule-based sentence boundary detection gem that works out-of-the-box across many languages.
Install
Ruby
Supports Ruby 2.1.5 and above
gem install pragmatic_segmenter
Ruby on Rails
Add this line to your application’s Gemfile:
gem 'pragmatic_segmenter'
Usage
- If no language is specified, the library will default to English.
- To specify a language use its two character ISO 639-1 code.
text = "Hello world. My name is Mr. Smith. I work for the U.S. Government and I live in the U.S. I live in New York."
ps = PragmaticSegmenter::Segmenter.new(text: text)
ps.segment
# => ["Hello world.", "My name is Mr. Smith.", "I work for the U.S. Government and I live in the U.S.", "I live in New York."]
# Specify a language
text = "Այսօր երկուշաբթի է: Ես գնում եմ աշխատանքի:"
ps = PragmaticSegmenter::Segmenter.new(text: text, language: 'hy')
ps.segment
# => ["Այսօր երկուշաբթի է:", "Ես գնում եմ աշխատանքի:"]
# Specify a PDF document type
text = "This is a sentence\ncut off in the middle because pdf."
ps = PragmaticSegmenter::Segmenter.new(text: text, language: 'en', doc_type: 'pdf')
ps.segment
# => ["This is a sentence cut off in the middle because pdf."]
# Turn off text cleaning and preprocessing
text = "This is a sentence\ncut off in the middle because pdf."
ps = PragmaticSegmenter::Segmenter.new(text: text, language: 'en', doc_type: 'pdf', clean: false)
ps.segment
# => ["This is a sentence cut", "off in the middle because pdf."]
# Text cleaning and preprocessing only
text = "This is a sentence\ncut off in the middle because pdf."
ps = PragmaticSegmenter::Cleaner.new(text: text, doc_type: 'pdf')
ps.clean
# => "This is a sentence cut off in the middle because pdf."
Live Demo
Try out a live demo of Pragmatic Segmenter in the browser.
Background
According to Wikipedia, sentence boundary disambiguation (aka sentence boundary detection, sentence segmentation) is defined as:
Sentence boundary disambiguation (SBD), also known as sentence breaking, is the problem in natural language processing of deciding where sentences begin and end. Often natural language processing tools require their input to be divided into sentences for a number of reasons. However sentence boundary identification is challenging because punctuation marks are often ambiguous. For example, a period may denote an abbreviation, decimal point, an ellipsis, or an email address – not the end of a sentence. About 47% of the periods in the Wall Street Journal corpus denote abbreviations. As well, question marks and exclamation marks may appear in embedded quotations, emoticons, computer code, and slang. Languages like Japanese and Chinese have unambiguous sentence-ending markers.
The goal of Pragmatic Segmenter is to provide a "real-world" segmenter that works out of the box across many languages and does a reasonable job when the format and domain of the input text are unknown. Pragmatic Segmenter does not use any machine-learning techniques and thus does not require training data.
Pragmatic Segmenter aims to improve on other segmentation engines in 2 main areas:
1) Language support (most segmentation tools only focus on English)
2) Text cleaning and preprocessing
Pragmatic Segmenter is opinionated and made for the explicit purpose of segmenting texts to create translation memories. Therefore, things such as parenthesis within a sentence are kept as one segment, even if technically there are two or more sentences within the segment in order to maintain coherence. The algorithm is also conservative in that if it comes across an ambiguous sentence boundary it will ignore it rather than splitting.
What do you mean by opinionated?
Pragmatic Segmenter is specifically used for the purpose of segmenting texts for use in translation (and translation memory) related applications. Therefore Pragmatic Segmenter takes a stance on some formatting and segmentation gray areas with the goal of improving the segmentation for the above stated purpose. Some examples:
- Removes 'table of contents' style long string of periods ('............')
- Keeps parenthetical sentences within a sentence as one segment for clarity even though technically there are multiple grammatical sentences within the segment
- Strips out any xhtml code
- Conservative in cases where the sentence boundary is ambigious and Pragmatic Segmenter does not have a built in rule
There is an option to turn off text cleaning and preprocessing if you so choose.
The Golden Rules
The Golden Rules are a set of tests I developed that can be run through a segmenter to check its accuracy in regards to edge case scenarios. Most of the papers cited below in Segmentation Papers and Books either use the WSJ corpus or Brown corpus from the Penn Treebank to test their segmentation algorithm. In my opinion there are 2 limits to using these corpora:
1) The corpora may be too expensive for some people ($1,700).
2) The majority of the sentences in the corpora are sentences that end with a regular word followed by a period, thus testing the same thing over and over again.
In the Brown Corpus 92% of potential sentence boundaries come after a regular word. The WSJ Corpus is richer with abbreviations and only 83% [53% according to Gale and Church, 1991] of sentences end with a regular word followed by a period.
Andrei Mikheev - Periods, Capitalized Words, etc.
Therefore, I created a set of distinct edge cases to compare segmentation tools on. As most segmentation tools have very high accuracy, in my opinion what is really important to test is how a segmenter handles the edge cases - not whether it can segment 20,000 sentences that end with a regular word followed by a period. These example tests I have named the “Golden Rules". This list is by no means complete and will evolve and expand over time. If you would like to contribute to (or complain about) the test set, please open an issue.
The Holy Grail of sentence segmentation appears to be Golden Rule #18 as no segmenter I tested was able to correctly segment that text. The difficulty being that an abbreviation (in this case a.m./A.M./p.m./P.M.) followed by a capitalized abbreviation (such as Mr., Mrs., etc.) or followed by a proper noun such as a name can be both a sentence boundary and a non sentence boundary.
Download the Golden Rules: [txt | Ruby RSpec]
Golden Rules (English)
1.) Simple period to end sentence
Hello World. My name is Jonas.
=> ["Hello World.", "My name is Jonas."]
2.) Question mark to end sentence
What is your name? My name is Jonas.
=> ["What is your name?", "My name is Jonas."]
3.) Exclamation point to end sentence
There it is! I found it.
=> ["There it is!", "I found it."]
4.) One letter upper case abbreviations
My name is Jonas E. Smith.
=> ["My name is Jonas E. Smith."]
5.) One letter lower case abbreviations
Please turn to p. 55.
=> ["Please turn to p. 55."]
6.) Two letter lower case abbreviations in the middle of a sentence
Were Jane and co. at the party?
=> ["Were Jane and co. at the party?"]
7.) Two letter upper case abbreviations in the middle of a sentence
They closed the deal with Pitt, Briggs & Co. at noon.
=> ["They closed the deal with Pitt, Briggs & Co. at noon."]
8.) Two letter lower case abbreviations at the end of a sentence
Let's ask Jane and co. They should know.
=> ["Let's ask Jane and co.", "They should know."]
9.) Two letter upper case abbreviations at the end of a sentence
They closed the deal with Pitt, Briggs & Co. It closed yesterday.
=> ["They closed the deal with Pitt, Briggs & Co.", "It closed yesterday."]
10.) Two letter (prepositive) abbreviations
I can see Mt. Fuji from here.
=> ["I can see Mt. Fuji from here."]
11.) Two letter (prepositive & postpositive) abbreviations
St. Michael's Church is on 5th st. near the light.
=> ["St. Michael's Church is on 5th st. near the light."]
12.) Possesive two letter abbreviations
That is JFK Jr.'s book.
=> ["That is JFK Jr.'s book."]
13.) Multi-period abbreviations in the middle of a sentence
I visited the U.S.A. last year.
=> ["I visited the U.S.A. last year."]
14.) Multi-period abbreviations at the end of a sentence
I live in the E.U. How about you?
=> ["I live in the E.U.", "How about you?"]
15.) U.S. as sentence boundary
I live in the U.S. How about you?
=> ["I live in the U.S.", "How about you?"]
16.) U.S. as non sentence boundary with next word capitalized
I work for the U.S. Government in Virginia.
=> ["I work for the U.S. Government in Virginia."]
17.) U.S. as non sentence boundary
I have lived in the U.S. for 20 years.
=> ["I have lived in the U.S. for 20 years."]
18.) A.M. / P.M. as non sentence boundary and sentence boundary
At 5 a.m. Mr. Smith went to the bank. He left the bank at 6 P.M. Mr. Smith then went to the store.
=> ["At 5 a.m. Mr. Smith went to the bank.", "He left the bank at 6 P.M.", "Mr. Smith then went to the store."]
19.) Number as non sentence boundary
She has $100.00 in her bag.
=> ["She has $100.00 in her bag."]
20.) Number as sentence boundary
She has $100.00. It is in her bag.
=> ["She has $100.00.", "It is in her bag."]
21.) Parenthetical inside sentence
He teaches science (He previously worked for 5 years as an engineer.) at the local University.
=> ["He teaches science (He previously worked for 5 years as an engineer.) at the local University."]
22.) Email addresses
Her email is Jane.Doe@example.com. I sent her an email.
=> ["Her email is [email protected].", "I sent her an email."]
23.) Web addresses
The site is: https://www.example.50.com/new-site/awesome_content.html. Please check it out.
=> ["The site is: https://www.example.50.com/new-site/awesome_content.html.", "Please check it out."]
24.) Single quotations inside sentence
She turned to him, 'This is great.' she said.
=> ["She turned to him, 'This is great.' she said."]
25.) Double quotations inside sentence
She turned to him, "This is great." she said.
=> ["She turned to him, \"This is great.\" she said."]
26.) Double quotations at the end of a sentence
She turned to him, \"This is great.\" She held the book out to show him.
=> ["She turned to him, \"This is great.\"", "She held the book out to show him."]
27.) Double punctuation (exclamation point)
Hello!! Long time no see.
=> ["Hello!!", "Long time no see."]
28.) Double punctuation (question mark)
Hello?? Who is there?
=> ["Hello??", "Who is there?"]
29.) Double punctuation (exclamation point / question mark)
Hello!? Is that you?
=> ["Hello!?", "Is that you?"]
30.) Double punctuation (question mark / exclamation point)
Hello?! Is that you?
=> ["Hello?!", "Is that you?"]
31.) List (period followed by parens and no period to end item)
1.) The first item 2.) The second item
=> ["1.) The first item", "2.) The second item"]
32.) List (period followed by parens and period to end item)
1.) The first item. 2.) The second item.
=> ["1.) The first item.", "2.) The second item."]
33.) List (parens and no period to end item)
1) The first item 2) The second item
=> ["1) The first item", "2) The second item"]
34.) List (parens and period to end item)
1) The first item. 2) The second item.
=> ["1) The first item.", "2) The second item."]
35.) List (period to mark list and no period to end item)
1. The first item 2. The second item
=> ["1. The first item", "2. The second item"]
36.) List (period to mark list and period to end item)
1. The first item. 2. The second item.
=> ["1. The first item.", "2. The second item."]
37.) List with bullet
38.) List with hypthen
39.) Alphabetical list
a. The first item b. The second item c. The third list item
=> ["a. The first item", "b. The second item", "c. The third list item"]
40.) Errant newline in the middle of a sentence (PDF)
This is a sentence\ncut off in the middle because pdf.
=> ["This is a sentence\ncut off in the middle because pdf."]
41.) Errant newline in the middle of a sentence
It was a cold \nnight in the city.
=> ["It was a cold night in the city."]
42.) Lower case list separated by newline
features\ncontact manager\nevents, activities\n
=> ["features", "contact manager", "events, activities"]
43.) Geo Coordinates
You can find it at N
44.) Named entities with an exclamation point
She works at Yahoo! in the accounting department.
=> ["She works at Yahoo! in the accounting department."]
45.) I as a sentence boundary and I as an abbreviation
We make a good team, you and I. Did you see Albert I. Jones yesterday?
=> ["We make a good team, you and I.", "Did you see Albert I. Jones yesterday?"]
46.) Ellipsis at end of quotation
Thoreau argues that by one
47.) Ellipsis with square brackets
"Bohr [...] used the analogy of parallel stairways [...]" (Smith 55).
=> ["\"Bohr [...] used the analogy of parallel stairways [...]\" (Smith 55)."]
48.) Ellipsis as sentence boundary (standard ellipsis rules)
If words are left off at the end of a sentence, and that is all that is omitted, indicate the omission with ellipsis marks (preceded and followed by a space) and then indicate the end of the sentence with a period . . . . Next sentence.
=> ["If words are left off at the end of a sentence, and that is all that is omitted, indicate the omission with ellipsis marks (preceded and followed by a space) and then indicate the end of the sentence with a period . . . .", "Next sentence."]
49.) Ellipsis as sentence boundary (non-standard ellipsis rules)
I never meant that.... She left the store.
=> ["I never meant that....", "She left the store."]
50.) Ellipsis as non sentence boundary
I wasn
51.) 4-dot ellipsis
One further habit which was somewhat weakened . . . was that of combining words into self-interpreting compounds. . . . The practice was not abandoned. . . .
=> ["One further habit which was somewhat weakened . . . was that of combining words into self-interpreting compounds.", ". . . The practice was not abandoned. . . ."]
52.) No whitespace in between sentences Credit: Don_Patrick
Hello world.Today is Tuesday.Mr. Smith went to the store and bought 1,000.That is a lot.
=> ["Hello world.", "Today is Tuesday.", "Mr. Smith went to the store and bought 1,000.", "That is a lot."]
Golden Rules (German)
1.) Quotation at end of sentence
2.) Abbreviations
Es gibt jedoch einige Vorsichtsma
3.) Numbers
Was sind die Konsequenzen der Abstimmung vom 12. Juni?
=> ["Was sind die Konsequenzen der Abstimmung vom 12. Juni?"]
Golden Rules (Japanese)
1.) Simple period to end sentence
2.) Question mark to end sentence
3.) Exclamation point to end sentence
4.) Quotation
5.) Errant newline in the middle of a sentence
Golden Rules (Arabic)
1.) Regular punctuation
2.) Abbreviations
3.) Numbers and Dates
4.) Time
5.) Comma
Golden Rules (Italian)
1.) Abbreviations
Salve Sig.ra Mengoni! Come sta oggi?
=> ["Salve Sig.ra Mengoni!", "Come sta oggi?"]
2.) Quotations
Una lettera si pu
3.) Numbers
La casa costa 170.500.000,00
Golden Rules (Russian)
1.) Abbreviations
2.) Quotations
3.) Numbers
Golden Rules (Spanish)
1.) Question mark to end sentence
2.) Exclamation point to end sentence
3.) Abbreviations
Hola Srta. Ledesma. Buenos d
4.) Numbers
5.) Quotations
Golden Rules (Greek)
1.) Question mark to end sentence
Golden Rules (Hindi)
1.) Full stop
Golden Rules (Armenian)
1.) Sentence ending punctuation
2.) Ellipsis
3.) Period is not a sentence boundary
Golden Rules (Burmese)
1.) Sentence ending punctuation
Golden Rules (Amharic)
1.) Sentence ending punctuation
Golden Rules (Persian)
1.) Sentence ending punctuation
Golden Rules (Urdu)
1.) Sentence ending punctuation
Golden Rules (Dutch)
1.) Sentence starting with a number
Hij schoot op de JP8-brandstof toen de Surface-to-Air (sam)-missiles op hem af kwamen. 81 procent van de schoten was raak.
=> ["Hij schoot op de JP8-brandstof toen de Surface-to-Air (sam)-missiles op hem af kwamen.", "81 procent van de schoten was raak."]
2.) Sentence starting with an ellipsis
81 procent van de schoten was raak. ...en toen de hel los.
=> ["81 procent van de schoten was raak.", "...en toen barste de hel los."]
Comparison of Segmentation Tools, Libraries and Algorithms
| Name | Programming Language | License | GRS (English) | GRS (Other Languages)† | Speed‡ |
|---|---|---|---|---|---|
| Pragmatic Segmenter | Ruby | MIT | 98.08% | 100.00% | 3.84 s |
| TactfulTokenizer | Ruby | GNU GPLv3 | 65.38% | 48.57% | 46.32 s |
| OpenNLP | Java | APLv2 | 59.62% | 45.71% | 1.27 s |
| Standford CoreNLP | Java | GNU GPLv3 | 59.62% | 31.43% | 0.92 s |
| Splitta | Python | APLv2 | 55.77% | 37.14% | N/A |
| Punkt | Python | APLv2 | 46.15% | 48.57% | 1.79 s |
| SRX English | Ruby | GNU GPLv3 | 30.77% | 28.57% | 6.19 s |
| Scapel | Ruby | GNU GPLv3 | 28.85% | 20.00% | 0.13 s |
†GRS (Other Languages) is the total of the Golden Rules listed above for all languages other than English. This metric by no means includes all languages, only the ones that have Golden Rules listed above.
‡ Speed is based on the performance benchmark results detailed in the section "Speed Performance Benchmarks" below. The number is an average of 10 runs.
Other tools not yet tested:
- FreeLing
- Alpino
- trtok
- segtok
- LingPipe
- Elephant
- Ucto: Unicode Tokenizer
- tokenizer
- spaCy
- GATE
- University of Illinois Sentence Segmentation tool
- DetectorMorse
Speed Performance Benchmarks
To test the relative performance of different segmentation tools and libraries I created a simple benchmark test. The test takes the 50 English Golden Rules combined into one string and runs it 100 times through the segmenter. This speed benchmark is by no means the most scientific benchmark, but it should help to give some relative performance data. The tests were done on a Mac Pro 3.7 GHz Quad-Core Intel Xeon E5 running 10.9.5. For Punkt the tests were run using this Ruby port, for Standford CoreNLP the tests were run using this Ruby port, and for OpenNLP the tests were run using this Ruby port.
Languages with sentence boundary punctuation that is different than English
If you know of any languages that are missing from the list below, please open an issue. Thank you.
Pragmatic Segmenter supports the following languages with regards to sentence boundary punctuation that is different than English:
- Amharic
- Arabic
- Armenian
- Burmese
- Chinese
- Greek
- Hindi
- Japanese
- Persian
- Urdu
Segmentation Papers and Books
- Elephant: Sequence Labeling for Word and Sentence Segmentation - Kilian Evang, Valerio Basile, Grzegorz Chrupała and Johan Bos (2013) [pdf | mirror]
- Sentence Boundary Detection: A Long Solved Problem? (Second Edition) - Jonathon Read, Rebecca Dridan, Stephan Oepen, Lars Jørgen Solberg (2012) [pdf | mirror]
- Handbook of Natural Language Processing (Second Edition) - Nitin Indurkhya and Fred J. Damerau (2010) [amazon]
- Sentence Boundary Detection and the Problem with the U.S. - Dan Gillick (2009) [pdf | mirror]
- Thoughts on Word and Sentence Segmentation in Thai - Wirote Aroonmanakun (2007) [pdf | mirror]
- Unsupervised Multilingual Sentence Boundary Detection - Tibor Kiss and Jan Strunk (2005) [pdf | mirror]
- An Analysis of Sentence Boundary Detection Systems for English and Portuguese Documents - Carlos N. Silla Jr. and Celso A. A. Kaestner (2004) [pdf | mirror]
- Periods, Capitalized Words, etc. - Andrei Mikheev (2002) [pdf]
- Scaled log likelihood ratios for the detection of abbreviations in text corpora - Tibor Kiss and Jan Strunk (2002) [pdf | mirror]
- Viewing sentence boundary detection as collocation identification - Tibor Kiss and Jan Strunk (2002) [pdf | mirror]
- Automatic Sentence Break Disambiguation for Thai - Paisarn Charoenpornsawat and Virach Sornlertlamvanich (2001) [pdf | mirror]
- Sentence Boundary Detection: A Comparison of Paradigms for Improving MT Quality - Daniel J. Walker, David E. Clements, Maki Darwin and Jan W. Amtrup (2001) [pdf | mirror]
- A Sentence Boundary Detection System - Wendy Chen (2000) [ppt | mirror]
- Tagging Sentence Boundaries - Andrei Mikheev (2000) [pdf | mirror]
- Automatic Extraction of Rules For Sentence Boundary Disambiguation - E. Stamatatos, N. Fakotakis, AND G. Kokkinakis (1999) [pdf]
- A Maximum Entropy Approach to Identifying Sentence Boundaries - Jeffrey C. Reynar and Adwait Ratnaparkhi (1997) [pdf | mirror]
- Adaptive Multilingual Sentence Boundary Disambiguation - David D. Palmer and Marti A. Hearst (1997) [pdf | mirror]
- What is a word, What is a sentence? Problems of Tokenization - Gregory Grefenstette and Pasi Tapanainen (1994) [pdf | mirror]
- Chapter 2: Tokenisation and Sentence Segmentation - David D. Palmer [pdf | mirror]
- Using SRX standard for sentence segmentation in LanguageTool - Marcin Miłkowski and Jarosław Lipski [pdf | mirror]
TODO
- Add additional language support
- Add abbreviation lists for any languages that do not currently have one (only relevant for languages that have the concept of abbreviations with periods)
- Get Golden Rule #18 passing - Handling of a.m. or p.m. followed by a capitalized non sentence starter (ex. "At 5 p.m. Mr. Smith went to the bank. He left the bank at 6 p.m. Next he went to the store." --> ["At 5 p.m. Mr. Smith went to the bank.", "He left the bank at 6 p.m.", "Next he went to the store."])
- Support for Thai. This is a very challenging problem due to the absence of explicit sentence markers (i.e. like a period in English) and the ambiguity in Thai regarding what constitutes a sentence even among native speakers. For more information see the following research papers (#1 | #2).
Change Log
Version 0.0.1
- Initial Release
Version 0.0.2
- Major design refactor
Version 0.0.3
- Add travis.yml
- Add Code Climate
- Update README
Version 0.0.4
- Add
ConsecutiveForwardSlashRuleto cleaner - Refactor
segmenter.rbandprocess.rb
Version 0.0.5
- Make symbol substitution safer
- Refactor
process.rb - Update cleaner with escaped newline rules
Version 0.0.6
- Add rule for escaped newlines that include a space between the slash and character
- Add Golden Rule #52 and code to make it pass
Version 0.0.7
- Add change log to README
- Add passing spec for new end of sentence abbreviation (EN)
- Add roman numeral list support
Version 0.0.8
- Fix error in
list.rb
Version 0.0.9
- Improve handling of alphabetical and roman numeral lists
Version 0.1.0
- Add Kommanditgesellschaft Rule
Version 0.1.1
- Fix handling of German dates
Version 0.1.2
- Fix missing abbreviations
- Add footnote rule to
cleaner.rb
Version 0.1.3
- Improve punctuation in bracket replacement
Version 0.1.4
- Fix missing abbreviations
Version 0.1.5
- Fix comma at end of quotation bug
Version 0.1.6
- Fix bug in numbered list finder (ignore longer digits)
Version 0.1.7
- Add Alice in Wonderland specs
- Fix parenthesis between double quotations bug
- Fix split after quotation ending in dash bug
Version 0.1.8
- Fix bug in splitting new sentence after single quotes
Version 0.2.0
- Add Dutch Golden Rules and abbreviations
- Update README with additional tools
- Update segmentation test scores in README with results of new Golden Rule tests
- Add Polish abbreviations
Version 0.3.0
- Add support for square brackets
- Add support for continuous exclamation points or questions marks or combinations of both
- Fix Roman numeral support
- Add English abbreviations
Version 0.3.1
- Fix undefined method 'gsub!' for nil:NilClass issue
Version 0.3.2
- Add English abbreviations
Version 0.3.3
- Fix cleaner bug
Version 0.3.4
- Large refactor
Version 0.3.5
- Reduce GC by replacing
#gsubwith#gsub!where possible
Version 0.3.6
- Refactor SENTENCE_STARTERS to each individual language and add SENTENCE_STARTERS for German
Version 0.3.7
- Add
unicodegem and use it for downcasing to better handle cyrillic languages
Version 0.3.8
- Fix bug that cleaned away single letter segments
Version 0.3.9
- Remove
guard-rspecdevelopment dependency
Version 0.3.10
- Change load order of dependencies to fix bug
Version 0.3.11
- Update German abbreviation list
- Refactor 'remove_newline_in_middle_of_sentence' method
Version 0.3.12
- Fix issue involving words with leading apostrophes
Contributing
If you find a text that is incorrectly segmented using this gem, please submit an issue.
- Fork it ( https://github.com/diasks2/pragmatic_segmenter/fork )
- Create your feature branch (
git checkout -b my-new-feature) - Commit your changes (
git commit -am 'Add some feature') - Push to the branch (
git push origin my-new-feature) - Create a new Pull Request
License
The MIT License (MIT)
Copyright (c) 2015 Kevin S. Dias
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
