-is not achieved. The application is a intuitive system that allows users to
-manage RSS crawlers. With the application it is easy to generate, change, test
-and remove crawlers. However while trying real world data we stumbled upon a
-problem. Lack of RSS feeds and misuse of RSS feeds.
+is not achieved completely. The application is a intuitive system that allows
+users to manage RSS crawlers and for the specific domain, RSS feeds, any by
+doing that it does shorten the feedback loop but only within the specific
+domain. In the testing phase on real world data we stumbled on a small problem.
+Lack of RSS feeds and misuse of RSS feeds leads to a domain that is
+significantly smaller then first theorized.
+
+Lack of RSS feeds is a problem because a lot of entertaintment venues have no
+RSS feeds available for the public. They are either using different techniques
+or they just do not use it at all. This shrinks the domain quite a lot. Taking
+pop music venues as an example. In a certain province of the Netherlands we can
+find about $25$ venues that have a website and only $3$ have a RSS feed.
+Extrapolating this information combined with information from other regions we
+can speculate that less then $10\%$ of the venues use RSS feeds.
+
+The second problem is misuse of RSS feeds. RSS feeds are due to their
+limitations possible fields very structured. We found that a lot of venues
+using a RSS feed are not content with the limitations and try to bypass such
+limitation by misusing the protocol. A common misuse is to use publication date
+as the date of the actual event. When loadig such a RSS feed into a general RSS
+feed reader the outcome is very strange because a lot of events will have a
+publishing date in the future and therefore messing up the order of
+publication. The misplacement of key information leads to lack of key
+information in the expected fields and by that lower overall extraction
+performance.