From 6b4093bd76524b33ef5ba40649d6605f7c38d9c7 Mon Sep 17 00:00:00 2001
From: Christopher Ronnewinkel <christopher.ronnewinkel@sap.com>
Date: Fri, 6 Dec 2013 10:39:50 +0000
Subject: [PATCH] Updated dataconsistency (markdown)

---
 .../planning/businesscases/dataconsistency.md | 68 +------------------
 1 file changed, 2 insertions(+), 66 deletions(-)

diff --git a/wiki/planning/businesscases/dataconsistency.md b/wiki/planning/businesscases/dataconsistency.md
index 8f3b94ad44d..f87a46dc52e 100644
--- a/wiki/planning/businesscases/dataconsistency.md
+++ b/wiki/planning/businesscases/dataconsistency.md
@@ -97,70 +97,6 @@ Since this project targets at increasing the robustness of SAP sailing solutions
 
 n/a
 
+### Further Information
 
-## Minutes from Initial Brainstorming Meeting (December 2, 2013)
-
-### Live-Delay Analysis
-* GPS per competitor
-* wind for advantage line
-
-### Outlier detection
-* GPS tracks
-* Wind
-
-### Dropout interpolation
-* GPS tracks
-* Wind
-
-### Connection loss
-* GPS Track:
-  * introduce states "no data" / "no connection"
-    * has to be based on transmission rates
-    * no ping available
-* Wind
-
-### Data consistency measures
-* Start Phase
-  * correctness of start time on start boat
-  * stabilize start detection algorithms / heuristic
-* Completeness of Leg
-  * mark tracks & passings
-  * gps fixes
-  * wind measurements
-  * leg type detection
-* Completeness of Race
-  * competitor tracks: gps, mark passings
-  * mark tracks: validation (compare marks & competitor tracks); recalculation of mark passings
-  * all competitor or topN competitors
-  * all marks or future (remaining) marks
-  * take into account #{common legs} of competitors in aggregate calculation
-* Completeness of Regatta
-  * (all races complete) only in rare cases achievable
-  * cleansing of races, if possible
-  * include race states, e.g. DNF, into aggregate calculations, e.g. average speed
-  * take into account #{common races} of competitors in aggregate calculation
-* Robustness of Aggregate Calculations
-  * on all levels: leg, race, regatta, regatta series
-  * aggregate calculation can be corrupted by filtered outliers, lost connection
-* Quality based on Outliers and/or Dropouts
-  * GPS
-  * Wind
-* Network Connectivity
-  * all required channels
-
-### Master Data
-* Competitors: names
-* Sail numbers
-* Boat classes: names
-* Scoring schemes: score corrections
-
-### Data properties to be visualized or accessible
-* Sampling frequency for GPS
-* Number of active GPS satellites
-* Reflect accuracies of measurements somehow on the UI, e.g. tails along GPS tracks
-
-### Extra-/Interpolation of GPS tracks
-* bridge phase without connection to network or connection to GPS satellites
-
-### Extra-/Interpolation for wind
-* bridge phases without estimation or measurement
+* [[Meeting Minutes, December 2, 2013|wiki/planning/businesscases/DataConsistency20131202]]
\ No newline at end of file